John Dowson

When you turn the encoder, you should see the "button number" (as well as the device number) for the rotary in that direction. You will only see an "offset" if you already have an offset assignment to that button. Sorry, I don't understand what you mean by this. Can you explain? Also, please attach your FSUIPC7.ini file so I can see your assignments.

This error is mention in the included README.txt, and there are many other support requests asking the same question..... You need to (re-)install the VC++ redistributables. Check the README.txt or other support requests for details.

Yes, sorry for not replying sooner. This error is also mentioned in the included README.txt, and there are several support requests already on this error. Please remember to check the documentation and search for similar problems before you post in future. Thanks, John

There was an issue with losing axis prior to 6.0.11 which I corrected, but it seems that there is still something amiss in 6.0.11. I'm looking into it. John

Hi Sergio, I've had a few similar reports recently but haven't been able to reproduce so far, and the other users who reported also couldn't reproduce. Could you tell me exactly what you did to make the new livery profile specific and I'll see if I can reproduce. Thanks, John

In your installation folder, the same location as the log file and the FSUIPC4.dll.

Hi Gary, What exactly isn't working? Your log shows your 4 devices acquired ok, and you have various assignments that should work. The log also shows you loaded the Bonanza G36, for which you have no profile set-up, so it will just use the default (general) profile. Looking at your ini, you have your throttle, PropPitch and Mixture axes set-up in the general Axes section (i.e. your throttle axes) , but no elevator, aileron or rudder. In fact, you do not have these axes (yoke) assigned anywhere (i.e. in any profile) - do you have these set-up in MSFS? Are the assignments you have working ok, i.e. the throttle should work in all aircraft - does it? You have also assigned your axes to 'Direct to FSUIPC Calibration' but have not calibrated your axes. You should really do this - see the User guide for details. Maybe you could calibrate your axes and tell me in more detail what isn't working. Can you see each of your devices axes/buttons in the FSUIPC assignments windows? You could also activate button and event logging (and later axes) and operate some buttons to see what is logged. John

Yes. But of course you can always place it over the sim window... I've attached two lua scripts that display the frame rate, one using the standard lua ipc.display function (that uses SimConnect_Text under the covers) and another that uses the Wnd library. Due to the issues with the SimConnect_Text function, the ipc.display version has various issues (although works fine in P3D). John FPS_Monitor.lua FPS_MonitorW.lua

FSUIPC uses the SimConnect_Text function for displaying text. There are currently many issues with this - from the MSFS SK: There are also problems with updating text in a simconnect text window (multiple windows are created) and the 'time to display'.. For these reasons, I have added the lua Wnd library which can be used instead. This displays the text in a separate (moveable and resizeable) window. To display text without lua, you can use offset 0x32FA, but this uses the SimConnet_Text function and so suffers from the same issues as the lua text display functions. If you are writing your own program, you could also use the SimConnect SDK directly rather than using one of the FSUIPC SDKs. No, this is not possible. John

Hi Gary, Something must have changed! What Logitech/Saitek panels are you using? Are you also using spad or spad.next? Could you show me/attach your FSUIPC7.ini and FSUIPC7.log files please. John

This seems to contradict the title of this post ('crashes when loading flight') - does it crash when you start P3D, or when you load a flight? Do you have a crash log in the windows event viewer? If so, can you please show me that. Also, you should always attach your FSUIPC6.log file when you have such issues. Having said that, P3D crashes on start-up are usually due to a corrupt weather file, usually the wxstationlist.bin file or your start-up scenario *.wx file. If you want to check whether or not it is down to corrupted weather files you can try adding NoWeatherAtAll=Yes to the [General] section of the INI file. If it is a weather file, you should first try deleting the wxstationlist.bin file from your AppData\Roaming\Lockheed Martin\Prepar3D v4 folder (it will be regenerated when you run P3D). If you still have issues, try removing the *.wx files in your Prepar3D documents folder (the folder where your saved flights are). If its not a weather issue, please show me your FSUIPC6.log file and check the event viewer for a crash event and also show me that. John

Strange...you should be able to attach files, not sure whats going on there... Ok, no problem. Hmmm...I don't understand how a restart with no other changes can change things... Ok. If your issue re-appears, try attaching the requested files again and I'll take a look.

Ok, glad its now working, and thanks for reporting back on how you configured this. John

Ok. But I didn't need to see your bat file - I know what is in it! I was just suggesting that you could open it and play around with the command that starts MSFS (including removing the FastLaunch option) to see if you can get it to work. The command is at line 7: cmd.exe /C start shell:AppsFolder\Microsoft.FlightSimulator_8wekyb3d8bbwe!App -FastLaunch Its the same for every MS Store user. This command uses your user AppsFolder settings, which may be the issue. I don't think uninstalling and re-installing FSUIPC7 is going to help. John

Was just looking at this but Pete beat me to it... No, that's the type of the value being written:

Right-click on the MSFSwithFSUIPC7.bat file, located in your FSUIPC7 installation folder (i.e. not the link on your desktop) in windows explorer, an select 'Edit' or 'Edit with Notepad++' (or whatever your preferred editor is). Run the uninstaller that is generated in the installation process. You can also find this in your FSUIPC7 installation folder. You can also uninstall using the windows settings apps uninstall page, which will run the uninstaller for you. John

Could you please activate logging for axes events, produce a short-ish (as short as possible!) log file showing your issue, then show me that together with your FSUIPC4.ini file. I presume you know this is no longer supported. You should really update (if possible!). John

These are FSUIPC7 files not MSFS ones. Your FSUIPC7.ini file will be in the same location as the FSUIPC7.log file. If you cannot see the file extensions, you will need to change your Explorer preferences. John PS. Your log file is cut short after the Carenado loaded. Did you try to operate anything? Wa FSUIPC7 still running or did it crash? Maybe you can activate event logging and produce another log file, load the aircraft, operate a few buttons/switches, then exit and attach that log file, together with your ini.

Ok, thanks for the update. I've identified the problem and the Pan View axis will be back in the drop-down in the next release of FSUIPC6. It was an issue with the update from 6.0.10 to 6.0.11. John

Ok. But this seems to contradict your previous statement: Not to worry, as I don't think this relate to your problem. Well, you shouldn't have done this as an Adminstrator, but it shouldn't matter. But the folder you are starting things from (C \WINDOWS\ system32>) might. Maybe try it again from a non-admin account, and from a non protected folder (if you start a command prompt as a non-admin, it should default to your home folder). Yes, it does seem that something is amiss in your MSFS installation. If its the -FastLaunch option that is confusing things, you could try removing that option from the line in the MSFSwithFSUIPC7.bat file to see if that makes a difference. Really, you need to determine what command to use to start MSFS. The next time you install, I suggest that you opt to create the desktop start icon, which you can then use to determine the command used (from the URL field in the properties). I have no idea why the standard command that works for almost everyone else is not working for you. Have you tried running the desktop link as administrator (right-click and select 'Run as administrator')? Maybe also worth trying, but if the start commands don't work in a command window, I doubt they will work from using the link. John

@asessa I've added the A320Neo autobrake setting to offset 0x0260 in the attached version v7.0.3c which holds the following values: 0 - off, 1 - lo, 2 - med, 3 - hi This comes with the proviso that it will only hold the correct state if the state is changed using FSUIPC7 - if the state is changed from the UI, then the events to maintain this offset are not seen. FSUIPC7.exe John

@jaxx I've removed the correction previously added in the attached version v7.0.3c if you can try it: FSUIPC7.exe

@Paulcoy That does sound strange... Did you try the batch file directly and checking the contents of the command window for the error? Alternatively, open a command prompt and enter the following and let me know what error you get (or if MSFS starts): cmd.exe /C start shell:AppsFolder\Microsoft.FlightSimulator_8wekyb3d8bbwe!App -FastLaunch You can also try start shell:AppsFolder\Microsoft.FlightSimulator_8wekyb3d8bbwe!App -FastLaunch John

Then why not start FSUIPC7 from the MSFSAddon Linker and forget the FSUIPC7 batch script? Well, it won't launch on its own with MSFS unless the provided batch file is used. As I said, can't MSFSAddon linker start FSUIPC7? This is what is confusing me. Are you launching MSFS/FSUIPC7 using the desktop icon manually or using MSFSAddon Linker? If the former, what is starting MSFSAddon linker? If the latter, then that seems to solve any issues, no? Seems like you have a choice of either 1. use MSFSAddon linker to start MSFS and also start FSUIPC7 2. use MSFSAddon linker to start both MSFS and FSUIPC7 by getting it to call the MSFS/FSUIPC7 batch script or desktop link 3. change the FSUIPC7 batch script to start MSFSAddon Linker (which would then start MSFS) instead of MSFS directly The choice is probably restricted by what MSFSAddon linker can do. I'll take a look at the MSFSAddon linker at some point, but I won't have time for this for a while. John

I'm sorry, what do you mean by this? FSUIPC does not use Mobiflight, although Mobiflight may use FSUIPC. I am not familiar with Mobiflight. What does the WASM module do? Is this for a particular aircraft, or generally for the G1000? How does mobiflight handle this? Maybe log the events to see if you need to set something else first, such as one of the _SLOT_INDEX_ events. Does mobiflight communicate directly to MSFS or via FSUIPC (or both)?