John Dowson

But you have no axis assigned to Pan View. You only have buttons assigned to Pan Left, Pan Right, Pan Up and Pan Down: You do not need these assignments. Assign to the Pan View control in the Axes assignments dialog, as I have said. John

The installer always goes to the registration page, if it didn't, then it must have crashed. You need to select an installation location that IS NOT a windows protected folder, such as Program Files or Documents. Please select another location. If you continue to get issues, you may need to install/update your VC++ redistributables. Instructions for this are in the provided README.txt. John

That happens when you click the 'New Log' button - that will close the current log file and start a new one. Just don't do that! I see Pete has also just replied.... As well as what Pete has said, your A320 throttle calibration is also very strange: Throttle=-16380,0/16 Try calibrating your throttle or change that to: Throttle=-16380,16380 As Pete said, you should read the User guide before trying to assign and calibrate. John

Just re-run the installer - it will then first uninstall from your current location. When installing, select the installation location outside if your Documents folder, e.g. C:\FSUIPC6. John

Can you not see the AutoSave/GPSOut tab? If not, then you are using an unregistered version. Do you have an FSUIPC6.key file in your FSUIPC6 installation folder? Where have you installed FSUIPC6? Make sure it isn't installed in a windows protected folder, such as Program Files or under your Documents folder. John

I have just tested running and closing/killing various programs, some using symlinks and some directly, without any issues. Could you show me your FSUIPC6.log file - there should be an error logged there if a started process fails to terminate. John

I have no idea.... What did you do? Do you have controllers disabled in FSX? Could your controller ids have changed? I really can't help if you are not showing me any files - please attach your FSUIPC4.log and FSUIPC5.ini files. Load the Baron, activate logging for axes controls in FSUIPC, try moving your rudder through its full range, then shutdown FSX and show me those files. John

How have you assigned this? To assign the hat switch to Pan View, you assign in the Axes Assignment panel, not the button assignments panel. Assign to the FS Pan View control there - there is no option "Control to repeat while held" for axes assignments, so you must be assigning in the wrong place. John

I have now installed Pilot2ATC to check this and cannot reproduce your issue. As I previously said, 3rd part apps cannot connect to FSUIPC if they are not ran at the same privilege level as FSUIPC. Could it be that FSUIPC7 is being ran at a different privilege level (elevated) when auto-started by MSFS? To check this, try running Pilot2ATC with admin rights, to see if it can then connect.

Hi Dave, I cannot advise on the compatibility of hardware. All I can tell you is that FSUIPC will only recognise HID joystick type devices for direct assignments. Other types of HID devices can be used via the lua com library. I can provide you with a trial license if you would like to try it. John

Hmm... So you are using a shortcut/symbolic link to start Navigraph? If so, try changing to run the actual executable rather than starting via a link. I don't have/use Navigraph, so I cannot test with this, but I will check this later. John

The King Air has the following lvars that are settable and look like they should control the landing lights: LIGHTING_LANDING_1 LIGHTING_LANDING_2 First, try setting them to 1/0 using the Add-ons->WASM->Set Lvars... menu option. If that works, then you can use the Adding Lvars to Offsets facility, no need to use lua. An example of how to do this is given in the Advance User guide, P43-44. You can also use a macro to toggle lvars if you prefer - see P35 of Advanced User guide. John

From SimMarket. John

It is the previous log file. When FSUIPC7 runs, it creates a log file called FSUIPC7.log. If that file already exists, it is renamed to FSUIPC7_prev.log. So it will be the log file of your previous session using FSUIPC7.

The auto-save functionality is only available in the licensed versions of FSUIPC (FSUIPC6 for P3Dv5). John

Try just running the FSUIPC7.exe file. If that doesn't work, check the windows Event viewer to see if any event is logged. Also maybe try re-installing your VC++ redistributables - instructions can be found in the included README.txt.

I have not noticed this, but then again I don't use FSX. Sounds strange though, I will take a look. John

For those new simvars, the MSFS SDK documentation states: These are the new simvars: I will look into adding these to FSUIPC offsets, using the same offsets if available (an aircraft will use either these or the legacy ones, not both) or I will add new ones where needed. However, all these new simvars are read-only. I can look into making some writeable by using a corresponding control. I will look into this when I can and report back. The following fuel capacity/quantity simvars are also newly available, but I am not planning on adding these unless requested: John

After the FSUIPC splash screen is shown, FSUIPC iconizes itself and sits in your system tray. Are you sure it is not there? Have you tried pressing Alt + F (the default hot key) to open the FSUIPC7 main window? It is not possible for FSUIPC7 to delete itself. If its no longer there (but please check), I can only assume that it is some sort of anti-virus program gas detected it and quarantined it for some reason. Check your anti-virus program.

Those offset use the indexed simvar GENERAL ENG FUEL PUMP SWITCH. This is actually documented as unsettable, so they are not writeable - I will update the offset spreadsheet document to make this clear. Not sure why they are not reflecting the correct value though - maybe those aircraft don't use this simvar... Have you tried using the controls: FUELSYSTEM_PUMP_TOGGLE FUELSYSTEM_PUMP_SET FUELSYSTEM_PUMP_OFF FUELSYSTEM_PUMP_ON ? The offsets may be working (i.e. for reading the current setting) for some aircraft, but not all. For complex aircraft, best to check what to use in the MobiFlight preset app (https://hubhop.mobiflight.com/). However, I can't see much there for the 747 or the 787. Maybe try seeing if there are any lvars available for those aircraft. For the A320 (FBW version), there are toggle presets for the left/right/center pumps - here's the calculator code to toggle the center fuel pump: That looks like its using the control Fuelsystem Pump Toggle to toggle the fuel pump (with the parameter specifying which pump) and also toggling an lvar, presumable to flip the switch in the UI. I can also see there are some new simvars for this, although they are defined as read-only: I can maybe add these to some FSUIPC offsets - possibly the same ones if its an either/or situation. I could possibly also make them writeable by triggering the Fuel System Pump Toggle event when written to. I will put this on my list to investigate, hopefully later this week. John

Sorry but I cannot advise on this. It looks like many of the Virtual Avionics devices are support via FSUIPC (e.g. for default aircraft, PMDG737, ProSim737) but I don't know the AeroSystems 737. Maybe try support from Virtual Avionics and/or Aerosystems. John

As Reinhard says, we need to know what FS, which version of FSUIPC, and which aircraft you are using. For MSFS, most of the G1000 controls are accessed through either hvars or lvars (or MobiFlight events). A G1000.hvar file is included in the FSUIPC7 HvarFiles sub-folder. to use this, you need to copy to the FSUIPC WASM folder (or the WASM permanent storage area) and rename it to a substring match of the aircraft for which you want to use it. Instructions are provided in the Advanced User guide. John

Sorry, but I no nothing about teensy. Not sure I understand... You say 'only the buttons on the encoders are detected', so why don't you assign to those? Rotary encoders come in various types. Some use potentiometers in which case they are assigned to an axis, but many use either one or two buttons in each direction. For these types of rotaries, you assign the buttons to the corresponding inc/dec control. If there are two buttons in each direction, one will be for fast inc/dec, the other for slow inc/dec. If there is only one button in each direction, you can use a lua script to emulate fast/slow turning - such a script is provided in the lua examples: If its a two-phase type rotary, the ones where turning the spindle one way gives pulses on two lines phase shifted one way, and turning the spindle the other way gives the opposite phase relationship, then please see the Advanced User guide (P21). John

There is only one version of FSUIPC that supports MSFS, and that is FSUIPC7. FSUIPC7 does have auto-save, but some issues have been reported when using with some Bush trips. You can download and try it - a trial license is available in a sticky-post at the top of this sub-forum. John P.S. You posted in the FAQ sub-forum where it states NOT for support requests. I have moved your post for you.

Hi Leo, You don't/shouldn't call ipc.exit() in the terminate event function, as the thread is already terminating. Remove that, and also the sleep. Try that first, but if it continues to crash in the same place, try commenting out your event.terminate statement completely (so that the termination event isn't called) and let the thread be forcibly killed, when needed, instead. John