Pete Dowson

What happened to the new lines? I'll have to extract the data from the mess. Maybe a bit like this (with loads missing by the look of it!): Launch dll.xml False False Addon Manager False False bglmanx.dll Object Placement Tool True False ..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll Traffic Toolbox True False ..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll Visual Effects Tool True False ..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll Kokpit False False SimObjects\Airplanes\HUGHES_H1B\panel\Cockpit_Sound.dll module_init module_deinit A2A Service False A2A\Shared\A2A_Service.dll module_init module_deinit FSDX False False FSDX.dll module_init module_deinit FDav False False Gauges\FDav.dll module_init module_deinit Captain Sim 767 Menu False Captain_Sim\Captain_Sim.b767.menu.dll FSUIPC 4 False Modules\FSUIPC4.dll Of that mess, these modules are part of FSX's SDK (which you must have installed) and they aren't running in any case: Object Placement Tool True False ..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll Traffic Toolbox True False ..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll Visual Effects Tool True False ..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll Then you have five (5! Phew!) other add-ons being loaded as SimConnect modules before FSUIPC4: Kokpit False False SimObjects\Airplanes\HUGHES_H1B\panel\Cockpit_Sound.dll module_init module_deinit A2A Service False A2A\Shared\A2A_Service.dll module_init module_deinit FSDX False False FSDX.dll module_init module_deinit FDav False False Gauges\FDav.dll module_init module_deinit Captain Sim 767 Menu False Captain_Sim\Captain_Sim.b767.menu.dll I don't know any of those, but as a process of elimination you could try renaming each it turn. You'll find them all in the paths shown -- the second emboldening on each line above. All of those are in folders in the FSX folder. It looks like FSDX.dll is in the main FSX folder. BTW, you didn't say, but what version of FSX are you runing? If it isn't fully updated, that should be your first job. Regards Pete

The wind smoothing won't be activated since your FSUIPC isn't registered. The Weather modes entries merely records settings made by ASA -- though I find it odd that it is setting Global first THEN "real world". I suspect that second setting is actually being made by a Flight being loaded. Since you've edited the log we can't see it here -- but maybe you have a flight saved with FSX real weather mode set, and that is loading AFTER ASA has initialised and so destroying its "Global" mode setting? That may well explain the conflicts -- though not why having FSUIPC present or not changes it, unless it is merely a matter of timing. I'm surprised you are using ASA's Global weather mode -- that makes all the world's weather the same, everywhere, and ASA then tries to change it as you fly. I use it's normal options which would be logged as "Custom Weather" The 0924s and 088Cs are throttle settings being written. 0BB6 is the Aileron input to FSX. All that is merely FSUIPC regularly reading the weather so it can populate weather data for applications which might want to read it. To me, it looks like ASA's Global Weather mode is being lost, resetting FSX to downloading weather. Thereafter you'll get conflicts as ASA tries to update weather. Try first NOT running ASA, and then try starting it later, after everything has loaded and ready to fly. Regards Pete

Ah, sorry, the "." before the a2a looked like a comma. My eyes are getting worse and there were no spaces. In that case the correct file is probably the one which to you looks like "dll" -- it seems you have widows Explorer set to hide filenames from you. I'd strongly advise you to go into the Explorer options and change that setting! And don't try to attach or upload the file. It won't be accepted. I said "pate" the file -- i.e. open it in an editor, like Notepad, then cut and paste it into a message, as text. Pete

What are you using to find this out? If you are reading FSUIPC offsets, which have you tried. There are a lot realting to flaps. And what version of FS? Pete

Yes. Pete

1. SimConnect is part of FSX. It is essential for most add-ons. 2. DLL.XML is part of the list you just made, so why do you think it isn't there? Why not show it to me -- you can paste it here. Pete

That is rather annoying. I'll have to write and ask them what they think they are doing. Pete

I can't help with VB, but I can advise you NOT to try using MessageBox displays with FS, unless you are sure you are running FS in Windowed mode. Otherwise you won't see them. You might want to browse some of the many threads discussing VB programming in this Forum, and at least re-posting with a good Subject title. Few folks, even if they know the answer, will bother looking at a thread entitled "Question". Be specific. Regards Pete

Does the signature actually check, though? That's the question. Select it and ask for details. It then says whether it is okay or not. There's a bug in SimConnect which was especially annoying in the original version of FSX which crashed FSX when loading multiple SimConnect clients. This was mostly fixed by the SP1 and SP2/Acceleration updates (along with a lot more bugs), so I'm surprised if you get the problem with a fully updated copy of FSX. Sometimes it can be fixed by changing the order of things for SimConnect. If you show me your EXE.XML and DLL.XML files (in the same folder as your FSX.CFG file), I could check for you. You could also try downloading the very latest incremental update for FSUIPC4, from the Updates & Goodies Announcement above. Just unzip it and put it int the FSX Modules folder. Pete

Oh, not VATSIM or IVAP? sorry, then I've no idea for sure. Of course they don't, unless you keep going into FSX's weather menus and changing things. Then it depends how often ASA sets the weather afresh to undo what you've done. I haven't used FSUIPC much... so would I simply go to the "Logging" tab, check the boxes for "Weather", "IPC Reads", "IPC Writes", and then... what? Where does that info go, and what other options should I choose? Not IPC reads -- why would you be interested in that? Only the two I mentioned. And everything being logged goes into the Log file, which is ALWAYS produced and sits in the Modules folder along with everything else for FSUIPC. There is a chapter about the Logging tab in the User Guide. Regards Pete

Sorry, that whole area is an unknown for me and i am not going to start hacking into FS9 code at this stage.even for FSX I'd be very reluctant as I'm really too old to enjoy the many hours needs to track though convoluted code looking for things, and my eyesight deteriorates week on week anyway. Theoretically that is possible for FSX -- according to SimConnect documentation, the offsets I mapped for those strings deal with "writeable" SimVars. however, I've never tried this. Regards Pete

Not these days, not since i removed checking on what was allowed to connect. You could enable IPC write and maybe Weather Logging in the FSUIPC options and see when commands are being seen and processed. Well ASA doesn't by default (it uses SimConnect unless it is told to interface to FS9 and sees FSUIPC.DLL in the Modules folder), but I think the others may do. However not for weather, no doubt. But what about the on-line interface? Multiplayer supplies the other aircraft you can see , but I didn't think it did everything. I'd check with your on-line flight program support if I were you. Or at least eliminate it as a possibility by flying off-line to check. Anything setting weather in FS will override anyone else setting weather in FS. That's a good way of getting conflicts. Nothing can "own" the weather. If ASA is interfacing via SimConnect, as it does by default, FSUIPC has no control over it, but neither can ASA exert any control over anything else trying to set the weather, whether via FSUIPC or directly via SimConnect. Then your on-line connection is the most likely suspect. Regards Pete

Because, as I said "otherwise it looks like there are two different users (names not being unique on their own)". Both parts are needed to properly identify a unique user. Pete

Sounds like you have a corruption or a conflict. Does the signature on FSUIPC4.DLL check okay (right click-properties)? What version are you trying? If not the latest, update first. Regards Pete

It isn't supported. Use the built in facilities as documented in the FSUIPC User Guide. Pete

No idea, sorry. But something is. Uninstall one add-on at a time till you find the culprit. Didn't you say you were flying on-line? Are you sure you've switched the on-line weather control off? You most certainly don't want both. Pete

Yes. It was a lot of work, and one of the benefits of purchasing FSUIPC. Regards Pete

Sorry, Advdisplay has not been supported now for over four years. Please use the built-in FS Window facilities, as explained in the FSUIPC User Guide. Pete

For starting programs with system start-up you simply drop them into Windows "Startup" folder. Find it in the "all Programs" list from that Start button.# To start it with FS, add it to the [Programs] section of FSUIPC's INI file. There's a chapter in the Advanced User's guide about that. For FSX you can also get it started via the EXE.XML file for simConnect's attention. Regards Pete

As clearly stated in the documentation, you cannot do that. Both the name and email must be the same in both cases, otherwise it looks like there are two different users (names not being unique on their own). Raise a problem ticket with SimMarket and they may re-issue one or other of your registrations. Pete

I've never heard of "Live Dispatch 4". Does it actually use FSUIPC? Is it freeware? Otherwise they should have applied for a license. I've no idea what their error message means, unless they are merely putting out the interface code error number (which is in THEIR code, not FSUIPC's, and therefore under their control and responsibility). If that is the case it means that the SendMessage call to windows, to send a request to FS, failed on all retries. Possibly you are not waiting long enough for FSUIPC to be loaded by FSX, or you are running FSX "as administrator" but not LD4, or vice versa. All programs need to be run with the same privilege levels. Pete

perhaps when it's it wont work ('unknown' isnt in the commands drop-down, is it, so it isnt a command) Correct -- it isn't a known FS command. But it is a way for add-on writers to create new commands -- just use numbers Microsoft have not assigned, as in this case. Unfortunately, FSUIPC's assignment system doesn't allow assignment to unlisted and unknown / unnamed commands. But perhaps there are two possible ways around this: 1. Assign to "Offset dword set", with offset x3110 and with the parameter set to the command number (72123 or x119bb in this case). This should work with any added commands not needing a parameter value. or 2. Write a small Lua plug-in which sends the Command number and Parameters via the "ipc.control" library function. Regards Pete

Please email me at petedowson@btconnect.com Pete

Ah, sorry. In my haste to reply to as many outstanding questions as possibly before departing on holiday that Friday, I never noticed it was for FSX. :oops: :oops: :oops: No, there is no such option in FSX and therefore no way for FSUIPC to change it. FSX operates correctly and has the right frequency interval for the time it was released. The old option was for previous times, dating back as far as FSW95. Regards Pete

FSUIPC does no weather control at all. ASA uses either SimConnect directly, or FSUIPC, depending how you set it up. But there is nothing FSUIPC, by default, does with weather. No: if unregistered it does nothing at all except obey commands from programs which interface to it. If registered there are options to do things like smooth wind changes (which works quite well, despite the bugs in FSX weather). But unless you register it is merely an interface program, a window into FS for other programs, modules, and gauges, nothing more. If you are getting different behaviour with and without an unregistered FSUIPC installed then you have something interfacing to it and using it. Regards Pete