Pete Dowson

I might have a test version to try before that which will give me more information. Hmm. That should give no problems. Thanks. Hmm. That's very very strange, as the location of the crash is not rleated to ASN at all, at least if you are using FSUIPC 4.927b which is the one with the full ASN fix. I'm using ASN all the time with the hotfix installed. I'll try to post a test version soon. I need more inforation and it should get it for me, I hope. Pete

I'm afraid I cannot support outdated versions of FSUIPC. Pete

There are now three threads on the same subject -- see for example http://forum.simflight.com/topic/75975-ctd-fsuipc4/ not very far below this one! I'm working on it, but I'm reasonably sure there's a work -around -- I just need confirmation. I may be able to supply a test version soon, but no one replies to my requests for information. No one suffering this has supplied any logs and no one has tried the parameter change I suggested. :-( Pete

It sounds like you have a Saitek driver running which is receiving the buttons presses and allowing you to see them as keypresses. FSUIPC only sees standard joystick buttons via DirectInput, as seen in Windows game controllers, and then only a maximum of 16 32 per joystick. Pete

Not helpful without the error code and the module offset. Pete

The only such statements I've seen about this are with folks assigning in FSUIPC, not simply doing joystick calibration and relying on FS assignments. But since I've no idea why Win8 loses these connections, and since FSUIPC uses the same DirectInput methods as FSX, I do not understand why there should be any difference in this matter. Pete

Yes. I've answered the same question elsewhere already. I would like to see logs please -- FSUIPC4 log and Install log. Both with 4.927e. Please paste them into a message. Then try setting "InterceptTextMenu=No" in the [General] section of the INI file and let me know if that helps. I think I also need to know if your FSX installation is the standard International/US version or a specific language version, as I'm a little concerned whether certain modules are different. Perhaps you could right-click on the module API.DLL in the FSX folder and tell me its full version number? Another contributing factor may be specific SimConnect using add-ons, so also please tell me the aircraft, and list other add-ons you are using. I'm trying to determine why this appears to hit some folks so hard and others not at all. I can't make any such failure here. Pete

No, there is no way to set the GS as this is a value computed from the airspeed and wind component. Have you tried setting the IAS or TAS? I don't know if that would work or not, but it is more likely. You might need to keep setting it regularly to stop to Sim engine recomputing it from thrust etc. Pete

CONTROLS.DLL is part of FSX, not FSUIPC. Pete

FSUIPC4's offset 31F4 uses the SimConnect variable PUSHBACK STATE with no problem. If you have a data error using it you are making a mistake somewhere, maybe the data type, which should be "enum"? Pete

Yes. In fact a ready-made one is provided in the ZIP of Lua examples. Pete

FSUIPC implements a work-around for this as well as a couple of other things. Make sure you are using the latest FSUIPC4 version and add P3Dv2fiddles=Yes to the [General] section of the INI file.

I've seen this before. One of the joystick type devices installed on that PC has a bad driver. If you are not using any such devices, check the device manager for drivers installed, nevertheless, and uninstall them or update them. Failing that just stop Wideclient scanning joystick devices by setting ButtonScanInterval=0 in the [Config] section of the INI file. Pete

FSUIPC uses the same Sim Vars so if you have found they don't work directly, they won't work via FSUIPC either, but it is easy enough to try using, say, FSInterrogate or a little Lua plug-in . Is this with default aircraft? All of them? It may depend on specific gauge implementation. [LATER] I just tested offset 0B65, which uses the PARTIAL PANEL AIRSPEED simvar, and certainly in the default FSX 737 is cuases the ASI readout to freeze at its current value, so it does work at least in a fashion, though you were presumably expecting it to simply read zero instead of freezing? It is probably okay in the other default aircraft too -- it was just that I had the 737 loaded at the time. Pete

There is no way FSUIPC "forgets" such things. Are you sure it isn't simply that your devices are going to sleep? Make sure that you disable power management by Windows on all your USB hub devices (in Device manager). There's a known problem with Win8 with controller devices becoming disconnected spontaneously. All entering those options in FSUIPC is doing is causing FSUIPC to rescan the devices and hence wke them up. Pete

"Idle reverse" is the same as "idle thrust" -- FS doesn't really simulated any 'reverse engaged but idle' setting. So setting idle throttle is simply a matter of assigning to the ThrottleN cut controls (N = engine number). Max reverse is a ThrottleN set with a parameter -4096 (assuming max reverse is 25% of full thrust -- you may need to modify that according to the Aircraft CFG setting). Else just assign to "ThrottleN Decr" with repeat enabled and hold the button down. Pete

The RUN options in FSUIPC are just one of the user facilities available to registered users. Without registration you only get the application interface and logging. Pete

Delays will only be due to the lack of processing time being given to Radar Contact. you need to either reduce the loading on your PC (eg by moving either RC or ASN off to a client PC) or make some changes to priorities, perhaps giving RC an "above normal" priority. There's a program called FSXAssist which can do that for you, I think. Pete

Take a look in the User Contributions subforum to see if any one has made one. Else you'd need to do it yourself. Pete

You say "4.927a/e" (?), but it looks like one before 4.927e. Could you supply the FSUIPC4.LOG file, please, and also the Install log -- just paste them here, no pictures or files please. Also try setting "InterceptTextMenu=No" in the [General] section of the INI file and let me know if that helps. Pete

What has reinstalling FSUIPC got to do with it? There is a facility in a registered install of FSUIPC for extending battery life, but you have to enable it. Pete

Sorry, only SimMarket supply FSUIPC4 keys, unless you want the Japanese version from Intercraft. If you've lost your details try creating a new account at SimMarket and raising a problem ticket. You may need to use a different email address, like a free one from gmail. Pete

You are looking in the wrong place, then. WideClient always produces a log. Please read the section in the WideFS user guide about configuring your network. You may need to specify the Server name or IP address and the Protocol. Pete

I cannot support FSUIPC being used in a P3D installation using an incorrectly named EXE file. FSUIPC detects the version of FS from the EXE filename and all sorts of problems will follow if it is renamed to look like an FSX file. You might be able to get around registration by simply renaming the FSX KEY file to match, but beware of other possible consequences if FSUIPC is then confused. Pete

FSUIPC is not measuring it continuously, only every so many seconds. Also it is asking Windows about free memory which will include unused parts of allocated heaps, whereas probably ProcessExplorer lists the actual memory not allocated to the process at all yet. Pete