Pete Dowson

This is a good clue. I've seen this before but not for a couple of years. FS is crashing as soon as FSUIPC asks for the weather data. Why it hangs rather than crashes with all those other DLLs loading I don't know, but probably they are stopping the crash itself by getting in some sort of loop waiting for something which won't happen. You have a corrupted file, possibly in a .WX file (though if you've deleted all of those it cannot be), or else maybe the "wxstationlist.BIN" file you'll find in the same folder as the FSX.CFG and EXE.XML and DLL.XML files. That file maintains a list of weather stations, and it is updated occasionally when FSX downloads weather from the Microsoft/Jeppesen website. My bet is that you had some bad data downloading, or it broke half way through updating it. Try copying the default wxstationlist.bin file over the corrupted one. You'll find it in the FSX weather folder. Regards Pete

For a B737NG? No, there's nothing shown there that I cannot select on the upper EICAS. Regards Pete

This is with all of those EXE and DLLs still loading. Look: 0.10545 Exe Launched: Path="C:\Program Files (x86)\EZCA\EZCA.exe" CommandLine="" Version="1.1.7.0" 0.16029 DLL Loaded: Path="D:\FSX\ORBX\FTX_AU\FTXAA_YMML\Scenery\ObjectFlow_YMML.dll" Version="1.0.0.3" 0.16206 DLL Loaded: Path="Captain_Sim\Captain_Sim.b767.menu.dll" Version="1.3.0.0" 0.16342 DLL Loaded: Path="Captain_Sim\Captain_Sim.b757.menu.dll" Version="4.3.0.0" 0.16349 File not found: Path="Captain_Sim\727\Captain_Sim.p727.menu.dll" 0.20014 DLL Loaded: Path="PMDG\DLLs\PMDGOptions.dll" Version="10.0.61355.62" 0.20682 DLL Loaded: Path="PMDG\DLLs\PMDGEvents.dll" Version="10.0.61355.62" 0.21701 DLL Loaded: Path="PMDG\DLLs\PMDGSounds.dll" Version="10.0.61355.62" 0.21843 DLL Loaded: Path="FeelThere\Erj\E145XH.dll" Version="1.3.0.1" 0.22048 DLL Loaded: Path="VistaMare\ViMaCoreX.dll" Version="10.0.0.13" 0.34973 DLL Loaded: Path="Modules\LVLD.dll" Version="1.4.2.1" 0.34980 File not found: Path="D:\FSX\Modules\HyperGauge.dll" 0.34983 File not found: Path="FeelThere\E170\EJetH.dll" 0.36352 DLL Loaded: Path="D:\FSX\Modules\LeonardoSH.dll" Version="<Sconosciuto>" 0.36359 File not found: Path="fsInsider.dll" 0.36361 File not found: Path="E:\FSKEEPER\Module\FSFKCore.dll" 0.36364 File not found: Path="A2A\Shared\A2A_Service.dll" 0.36494 DLL Loaded: Path="D:\FlyingWSimulation\SuperTrafficBoard V2.3\STBServer\STBServer.dll" Version="<Sconosciuto>" 0.48825 DLL Loaded: Path="Modules\FSUIPC4.dll" Version="4.6.6.1" Please, try it with only FSUIPC loading, as I asked! After moving the EXE and DLL.XML files out of the way you should rerun the FSUIPC installer to generate its own DLL.XML. BTW, please note those I've highlighted in RED, which seem to relate to modules you no longer have installed, or you've moved? Incidentally, I'm truly amazed that FSX manages to work at all with all those additional modules installed into its process. I've never seen so many. In fact I never knew there were so many! I'm afraid I'm out this evening, so I won't be able to look at the correct log until tomorrow. But please check it all out without ANY of that other stuff. Regards Pete

So nothing to do with pmSystems interface ot switches etc? Sorry, I'm not going to mess with any of that. My cockpit is beautifully set up as a 737NG and everything is sized and position very carefully on their assorted screens. I can scroll through different EICAS display modes on my one EICAS display by pressing selector buttons on the MIP. This includes the engine values, the control surfaces display, and two difference gauge type displays. I also have the standby instruments, the trim gauge and the flaps gauge on the EICAS screen. None of the PCs in the cockpit have keyboards or mice. I've had problems before with changing things and not being able to get them back as I wanted for ages. you couldn't believe how hard it is with trying to plug keyboards and mice into a Pc behind the firewall and trying to use it through the window whilst observing the MIP displays! Please ask over in the MyCockpit forums. There's a wealth of PM experience over there. my view is quite narrow and specific. All I can testify to is that the pmSystems logics for the 737NG work well, and in conjunction with the other components of PM. It sounds like you have many problems with PM which I couldn't possibly help with, hence my recommendation to head to a better place. Pete

We need some way of finding out what's happening internally then. Okay, let me think. Just re-checking. As you haven't noticed that FSX was still running in the Task Manager process list, how have you been re-running FSX each time? You need to forcibly terminaste it from that process list if it is hung. Check that FSUIPC still appears to hang with nothing else running. i.e. rename both EXE.XML and DLL.XML files so they aren't used, and run FSX without anything else. If the FSUIPC menu still doesn't appear, or FSX doesn't disappear from the Task manager process list, then: Enable SimConnect logging.as described in the FAQ subforum thread on this. Run FSX till you are sure FSUIPC is hung. Force the close, ZIP the simconnect log (it should be very large) and send it to petedowson@btconnect.com. That's a first step to getting more information. Regards Pete

There's nothing else I can think of. It would help to know which thread is hanging -- you'd need debugging tools for that -- but it seems suspiciously like an FSX corruption to me. Some last things to try, one at a time, as part of the elimination: 1. Remove the FSUIPC4.KEY file from the FSX Modules folder, so FSUIPC loads but does nothing other than interface to SimConnect. 2. Rename the FSX.CFG file (same place as the DLL.XML file), so that FSX loads with default settings 3. ... Oh, I can't think of a 3. I suspect it'd be reinstall FSX I'm afraid. Regards Pete

Hmm. stranger and stranger. Right, so it is hung. I'm wondering if it is a problem with joystick scanning. Can you try setting the PollInterval in the [buttons] section of the FSUIPC.INI file to 0, i.e. PollInterval=0 Though why this should affect EZCA and TrackIR too I don't know -- unless ... yes! They scan joystick buttons too don't they? Whereas probably nothing else you are using does. It could also probably explain why the FSUIPC menu won't open. Regards Pete

So you said -- and would you then assume that they get lots of these and say the same to everyone. As far as I recall, you're the first one to query it here. It just seems so unlikely that if it were a general problem it wouldn't have cropped up here before. And if it cropped up a lot you'd think they'd have worked out some better advice by now. Regards Pete

Ah. I see. But you can with one of them. Done. Regards Pete

Why be unpleasant? You did not mention that. You just said "utility" which I took to mean "FSUIPC". I am not clairvoyant! ;-) Sorry, your original read precisely as if that's what you were asking. You said: "I have downloaded this utility but do not know how to install it. The instructions say to "create a desktop connection using fsuipc"" How was I to guess that by "this utility" you were not referring ot FSUIPC when you mention no other product? REad that line again, please! How is it humiliating you? I know you have revised your message, but the original was not making sense. That's all I pointed out! Evidently, the "simple task" you failed at here was to explain your problem in a way which could be understood the way you intended. If came across loud and clear as from someone who'd hardly heard of FSUIPC before and wondered how to install it. In no way was I either trying to humiliate you or suggesting you had such incapabilities! I answer questions directly as as helpfully as I can. You are obviously a far better person than I, but nevertheless you are evidently reading my responses incorrectly, much as you write your questions so ambiguously and without evidently reading them yourself before posting. In any case there is nothing I know called a "desktop connection using fsuipc". Since your utility is from elsewhere perhaps you ought to go and be nasty to whoever wrote that instead of taking it out on me? Pete

If that's the complete log, with FS closed, then FSUIPC has hung. It seems not to be getting a response back from something it called. The log is incomplete. BUT, and this is what I don't understand, the very last line says: 96736 Sim stopped: average frame rate for last 71 secs = 20.0 fps which is logged when SimConnect says simulation is stopped, as when going into a Menu. This was after 71 seconds of normal running. If this is due to you ending the session , then I'm rather puzzled as to what there's no final closing lines for the Log. I've not seen that before. If it is "well enough" to log the Stop, why not the line saying it is closed? It still really does look like it isn't the complete log and you still had FS running when you copied it. Can you check that, please? When you close, use the Windows task manager to see the Process list, see if FSX process is still there. Regarding the DLL.XML file, could you try replacing it, just temporarily as part of the process of elimination. There's so many DLL add-ins that I'm sure there is a clash somewhere among them, and we need to find which so I can investigate further. So, rename the existing one, and save this in its place: &lt;?xml version="1.0" encoding="Windows-1252" ?&gt; - &lt;SimBase.Document Type="Launch" version="1,0"&gt; &lt;Descr&gt;Launch&lt;/Descr&gt; &lt;Filename&gt;dll.xml&lt;/Filename&gt; &lt;Disabled&gt;False&lt;/Disabled&gt; &lt;Launch.ManualLoad&gt;False&lt;/Launch.ManualLoad&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;ObjectFlow_YMML.dll&lt;/Name&gt; &lt;Disabled&gt;True&lt;/Disabled&gt; &lt;ManualLoad&gt;False&lt;/ManualLoad&gt; &lt;Path&gt;D:\FSX\ORBX\FTX_AU\FTXAA_YMML\Scenery\ObjectFlow_YMML.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;Addon Manager&lt;/Name&gt; &lt;Disabled&gt;True&lt;/Disabled&gt; &lt;ManualLoad&gt;False&lt;/ManualLoad&gt; &lt;Path&gt;bglmanx.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;Object Placement Tool&lt;/Name&gt; &lt;Disabled&gt;True&lt;/Disabled&gt; &lt;ManualLoad&gt;False&lt;/ManualLoad&gt; &lt;Path&gt;..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;Traffic Toolbox&lt;/Name&gt; &lt;Disabled&gt;True&lt;/Disabled&gt; &lt;ManualLoad&gt;False&lt;/ManualLoad&gt; &lt;Path&gt;..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;Visual Effects Tool&lt;/Name&gt; &lt;Disabled&gt;True&lt;/Disabled&gt; &lt;ManualLoad&gt;False&lt;/ManualLoad&gt; &lt;Path&gt;..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;DBS Airport GPS&lt;/Name&gt; &lt;Disabled&gt;True&lt;/Disabled&gt; &lt;ManualLoad&gt;False&lt;/ManualLoad&gt; &lt;DLLStartName&gt;module_init&lt;/DLLStartName&gt; &lt;DLLStopName&gt;module_deinit&lt;/DLLStopName&gt; &lt;Path&gt;Dbs\dbs.aptGPS.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;Captain Sim 767 Menu&lt;/Name&gt; &lt;Disabled&gt;True&lt;/Disabled&gt; &lt;Path&gt;Captain_Sim\Captain_Sim.b767.menu.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;Captain Sim Menu&lt;/Name&gt; &lt;Disabled&gt;True&lt;/Disabled&gt; &lt;Path&gt;Captain_Sim\Captain_Sim.b757.menu.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;Captain Sim 727 Menu&lt;/Name&gt; &lt;Disabled&gt;True&lt;/Disabled&gt; &lt;Path&gt;Captain_Sim\727\Captain_Sim.p727.menu.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;PMDG Options&lt;/Name&gt; &lt;Disabled&gt;True&lt;/Disabled&gt; &lt;Path&gt;PMDG\DLLs\PMDGOptions.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;PMDG Events&lt;/Name&gt; &lt;Disabled&gt;True&lt;/Disabled&gt; &lt;Path&gt;PMDG\DLLs\PMDGEvents.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;PMDG Sounds&lt;/Name&gt; &lt;Disabled&gt;True&lt;/Disabled&gt; &lt;Path&gt;PMDG\DLLs\PMDGSounds.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;FeelThere ERJX Helper&lt;/Name&gt; &lt;Disabled&gt;True&lt;/Disabled&gt; &lt;Path&gt;FeelThere\Erj\E145XH.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;VistaMare Core&lt;/Name&gt; &lt;Disabled&gt;False&lt;/Disabled&gt; &lt;ManualLoad&gt;False&lt;/ManualLoad&gt; &lt;Path&gt;VistaMare\ViMaCoreX.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;Level-D Simulations&lt;/Name&gt; &lt;Disabled&gt;True&lt;/Disabled&gt; &lt;ManualLoad&gt;False&lt;/ManualLoad&gt; &lt;Path&gt;Modules\LVLD.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;Mindstar Hypergauge&lt;/Name&gt; &lt;Disabled&gt;True&lt;/Disabled&gt; &lt;ManualLoad&gt;False&lt;/ManualLoad&gt; &lt;Path&gt;D:\FSX\Modules\HyperGauge.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;FeelThere EJetX Helper&lt;/Name&gt; &lt;Disabled&gt;True&lt;/Disabled&gt; &lt;Path&gt;FeelThere\E170\EJetH.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;Fly the Maddog&lt;/Name&gt; &lt;Disabled&gt;True&lt;/Disabled&gt; &lt;ManualLoad&gt;False&lt;/ManualLoad&gt; &lt;Path&gt;D:\FSX\Modules\LeonardoSH.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;A2A Service&lt;/Name&gt; &lt;Disabled&gt;True&lt;/Disabled&gt; &lt;Path&gt;A2A\Shared\A2A_Service.dll&lt;/Path&gt; &lt;DllStartName&gt;module_init&lt;/DllStartName&gt; &lt;DllStopName&gt;module_deinit&lt;/DllStopName&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;FSUIPC 4&lt;/Name&gt; &lt;Disabled&gt;False&lt;/Disabled&gt; &lt;Path&gt;Modules\FSUIPC4.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;SuperTrafficBoard Server&lt;/Name&gt; &lt;Disabled&gt;False&lt;/Disabled&gt; &lt;ManualLoad&gt;False&lt;/ManualLoad&gt; &lt;Path&gt;D:\FlyingWSimulation\SuperTrafficBoard V2.3\STBServer\STBServer.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; &lt;/SimBase.Document&gt; Their uninstaller evidently does not update the DLL.XML. You'd need to delete these sections (I've already done so in the version above): - &lt;Launch.Addon&gt; &lt;Name&gt;Multi Crew Experience&lt;/Name&gt; &lt;Disabled&gt;False&lt;/Disabled&gt; &lt;ManualLoad&gt;False&lt;/ManualLoad&gt; &lt;Path&gt;fsInsider.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; - &lt;Launch.Addon&gt; &lt;Name&gt;FS Flight Keeper&lt;/Name&gt; &lt;Disabled&gt;False&lt;/Disabled&gt; &lt;Path&gt;E:\FSKEEPER\Module\FSFKCore.dll&lt;/Path&gt; &lt;/Launch.Addon&gt; Regards Pete

Well something must have changed for sure. Maybe your hardware is playing up (memory or disk) and something got corrupted? With the symptoms you've described it most certainly sounds as if something is serious corrupted. "Instances" just being DLL, INI, KEY and LOG I assume you mean? Okay. That's different to what I understood from your original report. Er, which "updated" version? Regards Pete

In that case you made a mistake, buying a key for an FS9 product when you are using FSX. How did you not notice what you were buying? Sorry, what does opening doors have to do with things? If you mean FSX daircraft doors, why can't you open them? Try Shift+E. And you most certainly have one good key for fSUIPC4, so why exaggerate? Please do NOT send me any screen picture. What is the point of that? There is no solution with the key you have, it's for the wrong product. No, that is SimMarket's area. As Andy says, raise a Problem Ticket with them and see if they will look on you favourably. You might catch them in a good mood. Please be more careful spending money in future. Always check you are buying what you wanted before pressing that "complete purchase" button. Regards Pete

And after that they no longer worked? Why did you do that in the first place? Since things were running okay before, as you said, why did you reinstall things? Seems that mucked something up? And what do you think "uninstalling" FSUIPC entails? Just deleting the DLL and putting it back again can't change anything. You only way you can reset it, so it starts without all your settings, is to delete the INI file (or rename it). Sorry, say that again. The AddOns menu contains what ... just FSUIPC? And it does nothing? Phew! Simconnect must be really buggered. Sorry, so you were using a very out of date version before? Even the one on that site is nearly a year old. The log you posted appears incomplete. Did you close FS down first. If not, please do so then post it again. The fraction it contains shows nothing out of the ordinary. The only other thing I can think of, apart from a corrupted FSX installation, is that your EXE.XML and/or DLL.XML files are corrupted, or are loading something which is conflicting seriously. Could you therefore also paste those files into your reply. You'll find them in this folder: C:\Users\Vicky\AppData\Roaming\Microsoft\FSX They can be read into Notepad and cut and paste as text into a message here. Best enclose them in "code" parenthese (i.e. select them when pasted and click the <> button above, second from right is the series of icons there. You could also try using the latest version of FSUIPC, 4.661, which is available in the Download Links sub-forum. Regards Pete

Sorry, what instructions say that? Nothing of mine for sure. I've no idea what you are trying to do, but to install FSUIPC you simply run the FSUIPC Installer. That's what the installer is for. The Installation document, included in the ZIP with the Installer, is all you need to read to install. You simply run the Installer! There's nothing else to do unless you want to Register it because you've bought it. Instructions are there for that too. Goodness, the document is only two or three pages long for heaven's sake! What else are you reading? Sorry, you aren't making any sense. I don't know what else to tell you except: run the installer. Full stop. Pete

I've spoken to Simon, the author of SuperTrafficboard, and he says that it is not immune from this problem either, but you might notice notice the problems initially. Basically, what is likely to happen is that as soon as it reaches the limit on the number of requests allowed by SimConnect, the updating of the data will stall. Like myself, he's never seen this happen before and agrees with me that if a user really has that much AI traffic enabled the sim's frame rates would be pretty intolerable in any case. Regards Pete

Something changed then. What did you do to change the FS installation? I use TrackIR and EZCA alongside FSUIPC. They are not related to each other, but they all use SimConnect. So it sounds like you have a SimConnect fault -- the fact that FSUIPC isn't appearing in the Menu confirms this. Without any other information I'm afraid I cannot help. I need at minimum the version number of FSUIPC, the Install log and the FSUIPC4 log. The latter two are in the FS Modules folder. Make sure FS is closed first and paste them into a message here. Pete

Select the text with the mouse, so it is highlit, then click the button above, 3rd from right, which looks like the bubble you get fro comic character speech. The pop-up hints when you hover the mouse over it says "insert quotation". I don't know anything about PM and the B777. I've only ever used the 737NG stuff. By "lower PFD" do you mean "lower EICAS"? Because I haven't got one of those, only the upper EICAS. No. The 737 stuff in the pmSystems ZIP file works fine. I've modified mine in places for extra things in my PFC driver, and to work correctly with the 6-pack system provided by Thomas Richter's B373NG systems program (the one with the braking system in it as well). But apart from that it's all standard issue. Same as the one used on PM's commercial 737 simulator cockpits. Are you sure the problem isn't all to do with your overhead's interface to PM. Who wrote it? I think,now, you would be far better off posting in the appropriate Forum over in MyCockpits. This thread is supposed to be about FSUIPC Client DLL for .NET. Go to http://www.mycockpit.org/forums/forum.php . As well as the PM forum there, which would be a good place, there are probably places dealing with FDS and its interfacing. Regards Pete

Well, that looks rather different now, doesn't it! Two things, both probably related: 1. FSUIPC is never really starting. The log entries "Ready Flags: Ready-To-Fly=N ..." never show "Y" for "Yes, ready to fly". This means it simply is not getting the data it needs from SimConnect, and that is evidently because it is being totally tied up with the failures showing in the log. 2. I've never actually seen the "Exception 12 "TOO_MANY_REQUESTS" error returned to FSUIPC4 before. I know it can happen -- SimConnect only allows 1024 (I think) total requests outstanding before it fails. How on Earth it gets to that many I've no idea, but since all of them are seem to be related to AI, I would say it is down to a huge number of AI aircraft being generated simultaneously at the start of the session. Either that or you have some serious SimConnect bug. However, in your original message you said that SuperTrafficBoard sees the traffic. Does it get that traffic from UT2 direct or from FSX via SimConnect (I know it now has a feeder for UT2 stuff). Additionally you said that AS-FSC9 works with UT2. What does that mean? Does FSC9 not need FSUIPC to read traffic for UT2? I also see you have both UT2 and MyTraffic 2010 installed. Are they both set to give you such huge amounts of AI? This would certainly also explain the dismal frame rates if so. I have MyTrafficX and UT2 running, but MyTraffic is set only to fill in airlines not supported by UT2 -- mostly charter and military. Try with the amount of traffic turned down. In fact turn it down a lot first. If that "fixes" it, turn it up a little at a time till the problem recurs. You might then need it down one notch from there. Also try with the starting flight in a place where there are fewer large airports. Maybe once everything is up and running, so the system is over the initial pile of requests to SimConnect, things smooth enough to tolerate a higher amount of traffic elsewhere. Apart from such suggestions I'm not sure if a problem like this is solvable, or at least not without a hellofa of a re-write to make SimConnect think that FSUIPC is several separate clients with each asking for only bits of the total AI data. That in turn would place more strain on performance. There might be another way too but equally inefficient, but I can't say without revising the SimConnect facilities in some detail. If you do want me to investigate further, to see if a solution is actually possible, I would need a SimConnect log. After you've reached the point where it JUST fails, get me a SimConnect log (see instructions in the FAQ subforum). It'll be absolutely enormous, so keep the session short enough just to be sure the problem is occurring. Then ZIP the file and send as an email attachment to petedowson@btconnect.com. I won't promise anything though, because if it is what I think it is I doubt I'll be wanting to solve it by re-writes which could impact performance for everyone. But I am curious as to why it doesn't affect other AI traffic reading programs like SuperTrafficboard. I'll have to ask Simon about that. Regards Pete

It uses IPX/SPX, TCP or UDP, or all three to different clients. But the protocol is strictly a relationship with WideClient. It isn't generally applicable. No, sorry. Your best bet, and a pretty easy option, is to use a Lua plugin. Examples of using the Lua Sockets facilities are provided with the Lua package installed with FSUIPC. Then you can design your own dedicated protocl to suit your specific needs. Regards Pete

You can still do that in FSUIPC -- assign to FS controls. Maybe you can't calibrate in FSUIPC because that possibly takes a bit of the control away from the aircraft. You can always make that arrangement aircraft-specific to the iFly737, though, which you can't do in FS. And you have to take care if you have some things assigned in both FS and FSUIPC that you don't get duplicate assignments -- FS is fond of re-assigning things for you. What I don't understand is why the problem you are talking about isn't a general one which has been asked and answered many times before. Is the iFly737 such a rarely used aircraft that no one else has seen such a problem before? It doesn't make sense. Regards Pete

No. That's one or the other. Yes, the code for WideServer7 is built into FSUIPC4. As it says. But it won't work unless you buy a key for it. If you bought a WideFS 7 key for FSX you are good to go -- provided you used the same name for yourself when purchasing. Why do you presume this? What are you doing and what result are you getting? Are you Frans van der Meij? If so i can see you purchased FSUIPC4, but not WideFS7 yet. you purchased WideFS6 on the 12th Jan though. Regards Pete

Yes, exactly. Like a postbox. In fact this is how most of PM works -- it uses offsets as postboxes between its components. the published ones are so that others can join in, which of ocurse they do (viz: FSUIPC's own PM controls, which merely manipulate PM's offsets). Ah, possibly. But I'm afraid i don't know enough about intra-PM component operation to be able to advise on any of that. What is it you see on your PM PFD for APU? I see nothing related to APU anywhere outside of pmSystems, excepting of ocuirse that I can stop the battery drain -- but that's just a matter of some software someplace in PM re-writing the battery voltage in the normal FS offset for it. You certainly have something wrong then. I use PMsystems for my 737NG as do many others and it works fine, with virtually all the overhead systems operating well. It sounds like you aren't selecting the correct logics from those currently available. The 737 logics work superbly. I can't comment on the Airbus ones as I've never tried them. Maybe your overhead switches aren't programmed to operate with pmSystems? Don't FDS provide a proper driver? Regards Pete

But if only your code is using offset &Hxxx why tell FS or FSUIPC? What use is this knowledge to them? They can't do anything with it. And how would you propose trying to tell them anyway? If you want to experiment with writing to offsets for your own software, first use the free user area 66C0 - 66FF. if you eventually want to supply your software to others you'd need to apply for an assignment to avoid clashes with other programs. Regards Pete

Strange. Why can't they just tell you what setting is wrong? Making FSUIPC revert to doing nothing is a bit drastic! It they intercept the throttle controls it may simply be a matter or not assigning them in FSUIPC to go "direct to FSUIPC calibration", but via FS instead. The other possibile change is the THROTTLEn_SET option on the 4 throttles calibration page - they might need that switching to the opposite of what you have. At the worst I can only think that their aircraft can't handle throttles calibrated with reverse zones. Regards Pete