Pete Dowson

Assuming you made no errors in the SimConnect.INI file (perhaps you should show me it?), it sounds like SimConnect is screwed up. That almost always requires a Windows re-install -- i've certainly never managed to fix a SimConnect problerm without doing so. But perhaps you should first try reinstalling SimConnect -- find the SimConnect msi file in the FSX SDK and run that. Re-boot the PC. Pete

I just told you that it is Shift+9. I don't understand why you then want to refer to the Advanced Users guide? Anyway, you don't have to "look for" it, it is right with all of the FSUIPC documentation, as noted in the Installation document, in FSUIPC Documents. Where else? If your device is spuriously sending Shift + 9 and you don't want it to then you should investigate that. I honestly don't know why you are here in this forum, because nothing so far is really anything to do with FSUIPC or any other program of mine. I am trying to help you but you seem to come back more confused each time! Either you need to stop your device sending keypresses you don't want, or de-assign those keypresses in FS. It is up to you. Regards Pete

First I would try deleting all FLT and WX files from the FSX files folder in your "documents" folder, and maybe the FSX.CFG file also. Then reload FSX and see if it behaves itself. More information might also be obtained from a SimConnect log file -- instructions for this are in the FAQ subforum FSX HELP: Logging SimConnect Regards Pete

Is there a new FSUIPC4.LOG file? The problem here is that the log is stopping at a place I've never seen it stop at before, not in any reports. In fact there's so little happening at that stage that it's difficult to understand. It does look as if something else is going on, outside of FSUIPC which is crashing. Pete

My, that's a lot! Rename the DLL.XML to something else (or just save it somewhere). Then rerun the FSUIPC4 installer and see if FSX runs okay then. If not I have other avenues -- like corrupt WX files. If so, then there's some conflict somewhere, though I also run most if not all of the modules you do without problem. Pete

Sorry, you have me confused. I do not know anything about "K" or "A" variables. FSUIPC only has access to the regular values (via SimConnect in FSX, directly in FS9 -- you don''t even say what FS you are talking about ), and L:Vars, which are local panel variables which are exposed to other parts of the system. Regards Pete

Yes. Is that where it finishes? Can you tell me what version of FSX you are using -- RTM, SP1, SP2 or Acceleration? If hat's the end of the log file, FSUIPC is not even getting as far as connecting with SimConnect. Can you tell me what other DLLs and EXEs are being automatically started when you run FSX? Pete

There's no useful information for me there I'm afraid. Did FSUIPC4 even load? If it did start there will be a log file -- FSUIPC4.LOG in the Modules folder. If it didn't then the problem is either elsewhere, or it is still the SimConnect bug as described and discussed in that FAQ thread I pointed you to. All using the Loader is doing is delaying the crash a little. However, if all you did was "put the FSUIPC Loader into my modules folder" then it isn't being used in any case. You would have to re-run the FSUIPC4 installer after doing so to make any difference. Really you do not want to be using the Loader.if possible in any case. In all previous cases, persistance has paid. Once SimConnect has accepted the DLL it is okay thereafter. I'm afraid I've no cure for this problem, which afflicts only a small number of installations. I've got three separate installations and have tried everything to get it to do the same here, all to no avail. Pete

Thanks for clarifying. Those parameters actually look like control numbers for PMDG NGX, maybe even the ones I mentioned? If you had actually assigned those the displays would show <70090> and <74184> (as I don't build in names for add-on controls). Pete

Thanks. But the details are very hard to read. Nevertheless it looks like you are still assigning to the normal FSX Gear Up and Gear Down controls, nothing specific to PMDG. And though you seem to have set parameters for these, FSX doesn't actually use them so I'm not sure what you are accomplishing. It actually looks like the NGX would work with the normal methods in any case ...? Can you clarifty please? Regards Pete

Please see the thread in the FAQ subforum entitled FSX fails to run after FSUIPC4 first installed . FSUIPC only patches avoidance action for one specific G3D crash. There are many which it cannot help with. Regards Pete

I'm afraid I don't know C# -- it is really nothing like C at all. Perhaps you can explain some things to me: What is "ref token"? Apart from in the calls to FSUIPC_Write I don't see it defined anywhere. The value at that position should surely be a literal number, the length of the write, in bytes (4 in the case of offset 07D4)? I don't understand how this following line can work at all desptite your comment: because the 2nd parameter for the Write is normally a POINTER to the place in memory containing the data. I would have though that number would be an invalid address and cause a crash. As for the rest, I'm sorry, but it makes no sense to me. Perhaps someone else here uses C# and can help? If you are using Paul Henty's .NET interface then he may help you. Regards Pete

Glad it was so quick. Could you describe what worked, so others searching for this will be helped too, please? Regards Pete

I've never heard of it becoming re-enabled by itself. I think it is morte likely that your FSX.CFG file isn't being updated when you close FSX. Perhaps FSX isn't closing correctly, but crashing instead? Take a look in your FSX.CFG file. In the section called [CONTROLS] you should have JOYSTICKS=0 If not just set it that way. Pete

The one invoking the popup window you don't want. Or the one using key codes 16 and 57 (i.e. Shift+9). VK (Virtual Key) codes are listed in many places on the 'net, but probably more conveniently in the FSUIPC Advanced User's guide. Pete

My comment about "expecting help" was only related to the possibility of you using a seven year old version Of course you get help if you want it with any current version. Pete

The onstructions do actually tell you. It's only there just in case it is needed. Do you have a problem after installing FSUIPC? No. certainly not! Why should it? It depends on several things, but, please just do so as instructed. Please PLEASE follow the instructions. Yes, if you've paid for it, else you won't get value for money, will you? You can't register if you've not purchased it in any case becausde you won't have a key. Again, the instructions do tell you. Regards Pete

Sorry, I don't know what you mean. To unassign a keypress in FS just go to the Assignments, find the one which is doing it, and clear it. What's a "simple event like BREAKS"? You've lost me there. Do you mean assigning BRAKES? If you can assign keys surely you can clear key assignments? Pete

There has not been any "ActionKeys" arameter for 7 years! It was abolished in version 6.60 in April 2006! It is not needed. Where on Earth do you get such out of date information from? The only mention in any WideFS documents of that long-obsoleted parameter is in the History document! Really? I've never read that! I'm just amazed that folks are reading or using versions of WideFS over seven years out of date -- and expecting support?! :sad: It is NOT a problem, it is NOT needed. What IS needed is you updating to a current version of WideFS, please! Pete

Most likely it can't find the WAV file. Make sure any "\" characters in the path you provide are doubled, i.e. \\, because a single \ is an escape character which says the next character is a control. eg \n = new line. I thought you were using an example for this? If so you should surely have sen these things already? Pete

The "sound" which you got wrong is a library name, not a file link. Libraries are just lua objects, same as functions and variables. They are really just an array of functions. Pete

Maybe, or just wiring. But first check that you have no other drivers trying to process the device before it gets to FS. The INPUT values for nearly all modern devices range from -16380 or so to +16380 or so. They have digital or optical readers, not so much old fashioned resistance based pots. The latter may have large or small ranges, varying quite a lot according to quality, wiring and things like temperature and actual voltage levels. Pete

Only odd thing there is 17Z is assigned to the generic all-engine throttle, and 17Y to Throttle 2. I would think they'd conflict. There's only one assignment here ot rudder, so either you also have assignments in FSX 9you don't mention whether you've disabled controllers in FSX), or it is a connection problem. Pete

Re-calibrating to the same values does nothing whatsopever. The values are stored both in memory and in the INI file. They are not lost! The symptoms you mention are always either due to conflicting assignments (i.e. another axis assigned to the same function, maybe in FSUIPC or maybe in FS), or to a bad connection either withing the device or in its USB connections. That confirms my assessment above. FSUIPC does have "spike" elimination options (see Miscellaneous options tab), but these only eliminate the very extreme values, due often to sudden temporary loss of power or connection. However, your symptoms do sound much more like conflicting assignments. If you have disabled controllers in FSX completely and still get this, show me your FSUIPC4.INI file. You may have some previous assignments you have not removed. Pete

If this is what you have to do, it would make sense to program the Release part to have one of the spare upper bits set in the Key encoding so you can type successive identical letters, as in EGLL. If yyou don't change 5428 PM will not pick up identical successive letters, so with a normal "press/release" button action you'd need to program each button in the FSUIPC INI file to use a flag to toggle one of the top bits on and off on alternate entries. If SIOC can manage it, wouldn't all this be better with SIOC writing the values directly to 5428 rather than indirectly through virtual buttons and fSUIPC assignment, or are you needing to program it differently for different aircraft via Profiles? Regards Pete