John Dowson

Then you are still using 7.4.4a, the beta. I released 7.4.4 a short time ago, so you should update to this version. Oops, sorry - forgot to update the string version - I will correct. You will need to download and install again in a few minutes....

Then you are still using 7.4.4a, the beta. I released 7.4.4 a short time ago, so you should update to this version.

As this issue seems to be affecting lots of people, I have now released 7.4.4 - please update to this version before posting for any issues. If downloading from the download links section of this forum and you still get the previous version, please clear your browser cache. Alternatively, download from http://fsuipc.com/ John

Then there was no point in your post as the issue was already reported, confirmed and fixed... It will be when released - the version above is 7.4.4a, i.e. the first beta for the 7.4.4 release. Thanks @bob34 for posting the files I asked for, and to @Crosswind59 for testing the update version.

Which "new" version? Did you try the fix for this in the updated version available in my post above?

There is an issue with 7.4.3 that is affecting a lot of people - I have already posted a fix for this in a new version available here:

You should be able to assign to lalt+F1 and/or ralt+F1, i.e. there is a distinction between left and right alt keys. Is this due to the alt (left or right) or the F1 key? i.e. if you just press F1 is that recognised? Are the alt keys recognised with any other key presses?

It wasn't you. This option is set automatically when a new version of FSUIPC7 is available. You need to update to prevent the window opening on start-up.

Please try this version: FSUIPC7.exe If that doesn't fix your issue, please show me/attach your FSUIPC7.log and FSUIPC7.ini files. John

Sorry about this - this version was extensively tested by me and other users, and I am not sure why there is an issue with so many users for this relatively minor change. I have rolled back this now, so can you please all try this version: FSUIPC7.exe You can change this to the value that suits your needs - those are just the defaults. Note however that this will affect all button assignments. John

Can you please refrain from adding screenshots, especially from 3rd party apps. These are useless to me. I am only interested in seeing your FSUIPC7.log file for this issue, nothing else. Also please attach this file, not screenshots, and do this AFTER exiting FSUIPC7. Can someone/anyone add the following to the [General] section of your FSUIPC7.ini file: TestOptions=x800 And then show me/attach an FSYUPC7.ini file showing this issue. Can you also indicate if you are using a registered/licensed copy of FSUIPC7 or not (although if you attached your log file, this would tell me). I must admit that I did not test this version with the unregistered version before release, but I have just tested this here and all seems fine. If you get this issue with an unregistered/unlicensed version, can you please download the trial license (available from a post at the top of this sub-forum) and try with that to see if you get the same issue - and let me know the results please. John P.S. Also please select/load and aircraft and get ready-to-fly and wait a minute or so before exiting FSUIPC7 and attaching your log file. And also attach your FSUIPC7.ini file.

What trouble? The image you attached is nothing to do with FSUIPC7 - that just shows that vaMSYS cannot connect - whatever that is.... Is FSUIPC7 running? How was it started - via auto-start or manually? Did you see the FSUIPC7 splash screen? Try manually starting FSUIPC7 and see if it runs - you will see am FSUIPC7 splash screen and then there will be an icon in your system tray. If not, show me/attach your InstallFSUIPC7.log file. If it is running you can attach your FSUIPC7.log file and I can check for errors there., but the issue will be with your FSUIPC7 client and you need support from them.

The offsets were monitored in the FSUIPC7.log file, but not in the FSUIPC7_prev.log file. And although these offsets were monitored in the 2nd log file, the values never changed from 0. This is because you have not activated the additional FSUIPC offsets for PMDG - can you do this please. Instructions are in the Offset Mapping for PMDG 737-700.pdf document. The only suspicious event I can see in both log files is this: This is a "Spoilers down" control. Do you know where this is coming from? Can you repeat again with the PMDG offsets enabled, and also check the spoilers position as well as the state of the stab controls in the VC.

Ok, but I don't know much about SIOC (never used it), and nothing about .ssi files. They are certainly not anything that FSUIPC would recognise - I suspect they are specific to SIOC. And yes, it is my understanding thar SIOC uses FSUIPC offsets. With such cards, you would usually assign in SIOC to FSUIPC offsets. FSUIPC only recognises HID joystick type cintrollers natively, and you can maybe use lua for other non-joystick type HID conytollers. This is not related to the flight model you are using or how that is configured. There have already been several support requests in using usbkey cards with FSUIPC. Check these posts to see if they help - search this forum for usbkeys. John

Clear your browser cache, or download from http://fsuipc.com/ - both places download the same installer file, and it is 7.4.3.... John

What type of script? What do you expect FSUIPC to do with this? Is it a lua script? The only scripts FSUIPC recognises and can do anything with are lua scripts.

You only need to use a parameter if using the Input Events or *_SET controls. Thanks - you as well! John

Thanks. I tested quite a but here and released this update as 7.4.3 (including a few ither updates) a few hours ago. This should/may also fix the other issue you had (a CTD), but please post again in that topic if it occurs again. Cheers, John

I am not sure what the stabilizer is or what controls this, but I think this is not related to the elevator trim. Can you log the following offsets, both as U8, to see if these change: 6600 - MAIN_annunSTAB_OUT_OF_TRIM 6C3C - TRIM_StabTrimMainElecSw_NORMAL 6C3D - TRIM_StabTrimAutoPilotSw_NORMAL 6C68 - TRIM_StabTrimSw_NORMAL These are the PMDG controls relating to the stabilizer: Maybe also check the state of those stab trim switches in the VC. We can also check for those events that control the stab trim switches in your log, once logging for Events has been activated (they will be logged as ROTOR BRAKE controls with the parameter indicating the event).

These seem to work..or at least the event is sent and received, although I don't know if they activate/deactivate the governor... The mageneto control works switching on, but not off. The plasma control seems to work. All these look to be working, with parameters 1/0 for on/off. I would use these. John

Did you get anywhere with this? Logging shows that the governor is using: ROTOR_GOV_SWITCH_OFF ROTOR_GOV_SWITCH_ON and the two ignition switches (magento and plasma) are using: MAGNETO1_SET PLASMA_SET Did you try those? If not working, there are also these Input Events you can try: ENGINE_Governor_Switch_1 ENGINE_Governor_Switch_2 ENGINE_Magneto_1 ENGINE_Plasma_1

Your logs show the elevator trim decreasing in your prev log file, down to -4208, and when you restart it gradually increase slightly to -2788. I would guess its the AP controlling this, and there is not much difference between the values after the restart so I don't think this can be causing the issue. The spoiler offsets remain at 0, so this looks ok, although maybe PMDG aircraft don't use these offsets - I will check the PMDG SDK/offsets to see if there is anything there to log which could be useful. For now, drop those (0BD4 and 0BD8) and add 0BB4. Looks like you didn't set logging for Events and Axis Controls. Can you set logging for these please Were those logs attached when the problem persists or went away? Seems it was restarted quite soon - after 10 seconds or so....

Yes. Yes - remove all entries for scripts not installed. Yes. Or maybe just: I don't know...try listing the lvars to see what is available.

For which aircraft? Try looking for an appropriate preset - check Select for Preset and use the Find Preset... button. Alternatively, use the HubHop search (https://hubhop.mobiflight.com/presets/) to find the relevant preset and then select that from the preset drop down menu. Also, try searching this forum as this question has been asked several times before...

Yes, it looked like a software driver was missing! Thanks for the update. Cheers, John