John Dowson

No, there are many buttons on the G1000 that are not working and/or currently unassignable. This has already been reported to Asobo.

But the largest gap in the logged elevator axis values only seems to be around 9 seconds, with most of them being a lot smaller (2-5s):

Hi Keith, those controls have not been exposed via SimConnect. Please see John

Your ID number is pid_b108, and your VID number is vid_044f. Did you find (and remove) anything in the registry under those strings? It is strange that the Windows Game Controllers indicates it is working correctly. Did you try to re-calibrate anyway? If this is a problem with all aircraft in both sims, it does sound like a registry or device driver issue.

Well, the log shows the movements as described - to full forward then straight to (near) full reverse, with no in-between values.... What do you see in the in/out boxes in the axes assignments tab for your throttle axis? I ask as it looks like your throttle is no longer sending the full axis range values. Can you also check that axis in windows game controllers? It may be that your axes has been switched to digital input somehow in the registry - see the following (even though your device isn't a Saitek one):

Check your USB power management settings. Well, first you should not need to reconnect, so best to solve that problem. However, FSUIPC should rescan the axis when you reconnect. The next time this happens, please show me your FSUIPC7.log file, together with your FSUIPC7.ini. Also, make sure you are using the JoyLetters facility if re-connecting USB devices. There was a new ini parameter AxisScanOnSimConnectOpen added in the October 6th build. However, I'm not sure this would help in your case, as it sounds like its not related to when opening SimConnect, but you could try this anyway.

Btw, for the A320, you can assign the throttle (to the THROTTLEn_SET controls) to the full axes range with no reverse zone. You can then assign a button (or key) to the Throttle Reverse Thrust Toggle control. Then, activating this control (when aircraft is on the ground) will allow the full throttle axis range to control reverse thrust. Toggling this control again will switch between reverse and forward thrust.

Those ines I highlighted are incorrect. To comment out lines in the ini file, use a semi-colon ';'. Please correct that, although I don't think this will fix your issue. Can you try with that original ini (with the above corrected), activate Axes Controls logging, load up the Neo and move your throttle through its full range, from idle to full and back again to idle (or into reverse, if you are using reverse zones). Than show me your log and tell me how you saw the throttle move in the UI.

You seem to have an extra folder in your path (FSUIPC4.975) - that bold text should be (at a guess): C:\Documents and Settings\hhm\Mis documentos\MiInet\Steam\steam\steamapps\common\FSX\Modules\FSUIPC4.dll So maybe you have specified the wrong path in the DLL.xml?

Something must have changed. Do you have your original FSUIPC7.ini? If so, please show me that together with your FSUIPC7.log file. But if you let it rebuild a new one you will have lost all your assignments. I really can't help unless you show me your .ini and .log files. For the log, you can also activate logging for Axes Controls, which will show what axes controls are being sent to the sim.

This topic is over 5 years old, and the last update to the web site you pointed to was over 3 years ago. I would just download and try it first, and contact the author (Alvaro Polo @apoloval) via his website if you have issues.

Yes, many aircraft continually send various events, and its aircraft dependent. You can ignore these by using the DontLogThese ini parameter. Chck the Advanced User Guide for details.

The default PollInterval for buttons is 25 milliseconds, i.e. 40 times per second. You could try adjusting this if you want to receive more. You could also try the example lua script Rotaries.lua. When using this, this will trigger 2 virtual buttons in each direction, one of which you should assign to a standard increment (small increase/decrease), and the other to a larger increment/decrement. Note that FSUIPC adds special controls for using with the 'fast' rotary button (from Advanced User manual, p29): However, I'm not sure if these will work with PMDG aircraft.

But "Fthr" is just a parameter value to a function, so I'm not surprised that you didn't find that. You should certainly be able to find the definition of the DspShow function somewhere. But even if you find that, there are other problems, e.g. functions _MCP1() and _MCP2() aren't defined, nor DspMed1 or DspMed2. This script is obviously meant to run in the LINDA environment.

Interesting, and thanks for those links and reporting back. Let me know if you get any further crashes.

Do you mean from offset 0x0130? If so, could you please add offset logging to for that offset (with type AsciiZ) and show me a FSUIPC7.log file when this is 'randomly populated'. I'm not sure what you mean by 'blocked for reading'. How are you reading this data - via the SDK? If so, which one? Later: I have noticed that FSUIPC quite often receives a message from MSFS with an empty plan name, e.g ".PLN". However, this is usually followed by the actual plan file name, e.g. I guess I should ignore these and not update offset 0x0130 for plans with no actual name or path.

No, its only a warning and nothing to worry about. 32 (buttons 0-31) is the standard button limit, but POV buttons (usually) have the 8 button ids from 32-39 which you can assign as either an axis (e.g usually PAN_VIEW, butthis is not working in MSFS) or as buttons. I would certainly try without the saitek software installed first. You can always re-install it later if needed. I would then try without the drivers, and use the default windows drivers (again, you can always re-install later if needed). Finally you could try without that file - i.e. temporarily rename it. You can revert back to the original name if it doesn't help or causes issues.

The keys seen by FSUIPC7 is currently restricted by what is sent via SimConnect. For what is currently available, you should refer to the MSFS SDK documentation, under SimConnect, -> SimConnect_Status_of_Input_Events. It is acknowledged/known. Again, check the documentation. This is a different problem. FSUIPC7 can receive/see the numpad keys, but MSFS only sends them when numlock is off, rather than on. This has been reported to ASOBO. As a workaround, I have added a new ini parameter to get around this (in the build from 26th September): - new ini parameter UseAlternativeNumpadKeyMapping as a workaround for an MSFS bug on numpad key input. Please see this thread for a discussion on how this is used: Cheers, John

Yes, with FSUIPC7 now being a stand-alone exe rather than a dll, you don't need to have MSFS installed to install or run FSUIPC7. But of course, doesn't normally make much sense doing this! Ok, thanks, I'll update the installer to include V0.2.0 and release sometime next week...once I've updated the FSUIPC7 user manual. I'll also update the FSUIPC6 installer to include this, although I'm not sure yet if I'll add the start/stop/etc integration. I may do that at a later stage, via menu items in the P3D Add-on drop down menu entry, but that will depend if needed (i.e. requested). Regards, John

Ok, thanks Paul. I'll update the installer for this version for the next release. I would appreciate some feedback on the current release though first, in case I need to make some other updates. Thanks, John

As Pete says, your lua script is using a LINDA lua library function that isn't present when you run your script outside of the LINDA environment. To use this outside of LINDA, you would need to include that script, and all its dependencies.

Can you also check that you have 'Power Management' disabled' on all your usb devices and hubs.

Maybe you could also try with this added to the [General] section of your FSUIPC7.ini: UseAIClient=No This will instruct FSUIPC to NOT use a separate SimConnect connection for AI, and will use the main connection instead (i.e. no change in functionality). This would help me to determine if the issue is related to multiple SimConnect connections interfering somehow.

@MartyReynolds If you are unplugging and re-connecting USB devices, you should really use the 'JoyLetters' facility (see User guide if you don't know what this is), which will prevent problems if/when Windows assigns a different id to your device(s).

Looks like you have registry issues, but could you please also show me your FSUIPC6.log file. Also, you aren't using the 'JoyLetters' facility. You should really activate this to prevent problems when windows re-assigns your ids. Please see the FSUIPC User guide for details, or simply change AutoAssignLetters=No to AutoAssignLetters=Yes in the [JoyNames] section of your FSUIPC6.ini file and run P3D.