John Dowson

Hi Enrico - which offset are you referring to?

Also see

Which aircraft are you using? Have you seen this thread - maybe it helps: For the A320, there are known issues with AP ALT LOCK VAR - see

You can create an empty profile. Click Preset Manager and then + (New). Give the profile a new and then you are done and have an empty profile.

It could be a corrupt weather file. Try adding NoWeatherAtAll=Yes to the [General] section of your FSUIPC6.ini file. If that works, you have a corrupt weather (*.wx) file, or more usually the wxstationlist.bin file - try deleting that from your APP Data\Roaming P3D5 folder if it is there. It will be regenerated the next time you run P3Dv5.

There are no facilities in MSFS to start external programs at the moment, and its still not clear if such facilities will be provided. If/when they are, I will provide an installer to start FSUIPC7 automatically with MSFS. You could start the GFDevESP.exe automatically with FSUIPC7 - check the section Programs: facilities to load and run additional programs in the FSUIPC Advanced User Manual.

You also didn't mention the FSUIPC or sim version. If the question is about FSUIPC7-Beta / MSFS, then you should post in the specific sub-forum for that product: https://forum.simflight.com/forum/183-fsuipc7-beta-for-msfs/

FSUIPC7 cannot cause the sim to crash in normal use - this is one of the benefits of it being in an exe (separate process) rather than a dll. I suspect that its MSFS that is crashing, and when it does it will close FSUIPC7 if you have 'Exit with FS' set, which is set by default. You can test this by de-selecting that option from the Options menu. The FSUIPC7.log file would also indicate a crash if it has not closed properly. You can also check the windows event log which would tell you what crashed.

Yes, bit values are 1,2,4,8,etc, so best to always use =0 and !0 for testing them. No, this is the right way to set up a switch to be properly synchronised.

I was talking about MSFS, not FSUIPC7. I haven't found a way of loading a flight plan in MSFS (without FSUIPC7) once you have started a flight, without restarting. If you go to the 'esc' menu and select 'Load/Save', I can only select .flt files, not plans.

No, as the ini has nothing to do with registration, its the .key file that you need to update. Well, thats because there is no installer for FSUIPC7 at the moment! Instructions on how to register your WideFS key are included in the release note and also the provided README.txt file (included in the downloadable zip file). Please see one of those for details.

Yes, it looks like the route isn't updated in the MFD when you load a new flight plan. Its not an FSUIPC7 issue though, so you should raise this directly with MSFS via their support forums. Btw, I have also noticed that you can't seem to load/change a flight plan directly in MSFS without going back to the main menus and restarting. The Load/Save option seems to be restricted to flights (.FLT) and doesn't allow for changing the flight plan...

By the way, it seems pretty pointless using the offset condition on a toggle control on the same button. If the bit is set, it will send the toggle using one assignment, and if it's not set, it will send the same toggle control using the other assignment. So the same toggle control gets sent either way. Its the same as only having one assignment with no offset condition!

0D0C is 2 bytes, so you need 4 hex digits for the mask. Also, Beacon is the 2nd bit in the first byte, so the offset condition would be ...W0D0C&0002=0 and ...W0D0C&0002!0... (or just ...W0D0C&0002...) You can (probably) use as a byte, by using ....B0D0C&02=0 and ...B0D0C&02 Btw, you should delete lines 449 and 451. Looks like these were assigned to controls that no longer exist.

Ah, the luacom.dll! Sorry, I know nothing about that - its a 3rd party lua library. I thought you were referring to the lua com library, built in to FSUIPC. It seems that the luacom.dll is 32-bit and won't work in a 64-bit process. You could maybe try a workaround for UDP sockets posted here:

@LarryD Just noticed that you posted in the main support forum. There is a separate sub-forum for FSUIPC7-Beta/MSFS. Please use that sub-forum for future posts in FSUIPC7-Beta. I'll move this post to that sub-forum. John

Hi Bernd, First, you posted in the FAQ sub-forum, where it states 'NOT for support requests'. Please post support requests in the correct forum, which is usually the main support forum. How are you assigning the throttles? For PMDG Boeings, you should assign to FS controls and not calibrate in FSUIPC. The PMDG aircraft intercept the FS controls, in the same way as FSUIPC does for calibration, and use them directly. If you use “Direct to ...” (or even FS controls and then calibrate in FSUIPC) then after calibration FSUIPC sends the controls on to the sim at a lower priority level (to avoid the infinite loop). This results in two, probably different, values arriving in the sim and maybe at slightly different times, causing issues. Therefore please check your axes assignments and use 'Send to FS as normal axis' and do not calibrate in FSUIPC. You may also want to check the calibration of the two throttles in the windows game controllers panel to make sure they are calibrated the same. Regards, John Later: also check that you don't have throttle axes assigned in the sim. Best to disable controllers completely in the sim if you are assigning everything in FSUIPC.

Sounds like an MSFS issue, but I'll look into it and get back to you.

What do you mean by this? I thought it was/is working....

@pilotjohn I'll add this to my list and look into it when time permits.

That image shows that you don't have anything assigned to the axis. You need to assign the axis to a throttle control - check the first checkbox and select the Axis Throttle Set or Throttle Set (or the throttle control you want to use). Maybe you previously assigned it in a different aircraft in a profile specific assignment? Anyway, try assigning without a profile and try again. If you still have issues, please attach your .ini and I'll take a look.

Just checked the 747-10 for comparison. The master battery offset and toggle control work for that aircraft, but the fuel valves have the same issue.

I can confirm that, for the 747-8, the Toggle Fuel Valve 1/2/3/4 controls do not work, and the value of the simvar GENERAL ENGINE FUEL VALVE, used in offsets x3590, x3594, x3598 and x359C do not report the correct state of the valves. They are not updated. For the master battery in the 747-8, it looks like the Toggle Master Battery control works, but only for turning off and not on. This seems to be related to the ELECTRICAL MASTER BATTERY simvar (offset x281C) - this always seems to be 1. When you try to toggle this using the control, or update it directly via the offset, it changes to 0 then back to 1 almost straight away, even when the update works (and turns the battery off). Its probably the fact that the simvar is 1/on even when the battery is off which is preventing it from turning on. I will report this to Asobo.

If there is no Assignments menu, then it is running in 'unregistered' mode. This means that it could not find the FSUIPC7.key file in the folder from where it was started. Are you starting FSUIPC7 from the same folder each time? The next time you don't see the Assignments menu, try opening the installation folder (option available from the File menu) and see if the FSUIPC7.key file is there.

I'll take a look, but will have to be tomorrow...