John Dowson

Please download and try the following installer: http://www.fsuipc.com/download/Install_FSUIPC6a.zip It will still display the message, but you can continue to select the P3D version you wish to install into.

Hi Thomas, And you ran P3D at least once after installing (or re-installing) the client? If there are no P3D registry entries, it won't detect your P3D installation and won't install. I'm not sure why you haven't got the registry entries. I will look into this... In the mean-time, I can update the installer to maybe ignore this, and proceed to the selection of the P3D versions to install into (rather than aborting).

And you get no pop-up showing why it can't auto-start FSUIPC7? Your EXE.xml file looks fine. What was the location of this file, and what type of MSFS install to you have - MS Store or Steam? For Steam installs, it should be located under <USER>\AppData\Roaming\Microsoft Flight Simulator and for MS Store installs under <USERL>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\ or <USERL>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\ Can you verify the location is correct, and that the same folder contains your MSFS UserCfg.opt file.

After the path selection page, there should be a Choose Components page. Do you not see that? It is in the Choose Components dialog. This is not only strange but worrying as the installer does not download anything... If you re-installed, did it detect your original installation and uninstall that first? If so, that would have removed the registry entries. Can you re-download the installer and try again, and without selecting the auto-start component this time, to see if that makes a difference.

Ok, so FSUIPC7 starts without a problem, and its only the auto-start that is an issue. Does MSFS show any message giving an error or exception when started? Can you attach or paste the contents of this file please: C:\Users\Maurizio\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.xml

Your install log looks fine. What happens when you try to start FSUIPC7? i.e. by double-clicking the FSUIPC7.exe (no need to have MSFS running) What happens when you start MSFS using the MSFS icon? i.e. how you started MSFS before installing FSUIPC7 What happens if you start MSFS using the FSUIPC7 created desktop icon?

👍

Yes, as Pete says, you shouldn't do this. Re-install in a different location.

No, this sounds very strange! The MSFS.bat file does nothing but display the splash screen and then start MSFS. It does nothing else. What happens if you start MSFS without this (i.e. how you used to)? Installing FSUIPC7 will only affect your steam installation in one way: it will update the EXE.xml (located under $APPDATA\Microsoft Flight Simulator) to have FSUIPC7 auto-started with MSFS, if you selected that option during installation. Try just starting FSUIPC7 (double-click the FSUIPC7.exe) without MSFS - does that work? If so, just exit. Then try starting MSFS from Steam or using your old icon/start method.

Okay. Thanks for the update.

How are you assigning? Have you calibrated properly? Please see the User Guide, sections: THE EASY STEP-by-STEP WAY TO CALIBRATE YOUR CONTROLS - P38 CALIBRATING MULTIPLE THROTTLE, PROP & MIXTURE AXES TO "LINE UP" - P41

FSUIPC7 is np longer started from the MSFS.bat file, it is started from the MSFS EXE.xml, if you select that option when you install. What version of FSUIPC7 are you using? The latest version is v7.0.4. If you are not using this, please update. If you are using this version, and you selected to have FSUIPC7 auto-started with MSFS, you should either see a splash screen when FSUIPC7 is started, or an error message telling you that it cannot be started. If you see neither, then you did not select to have FSUIPC7 auto-started when you installed. So, please check you version and update if necessary. If you still have issues, please provide more details and, as a minimum, show me you InstallFSUIPC7.log file. John

Unfortunately not. This should be in the MSFS SDK documentation, but it doesn't say much on these things at the moment. This is the entry for TOGGLE_MASTER_BATTERY: KEY_TOGGLE_MASTER_BATTERY TOGGLE_MASTER_BATTERY Toggles main battery switch All aircraft Not very informative! Trial and error, as well as searching on the Asobo forums, are your best bet. You can have multiple assignments to a sign button or key press by commenting out the initial assignment (in your FSUIPC7.ini file) and then reload your assignments. You can then make your second assignment and click 'Ok'. Then, edit the ini again an uncomment your first assignment. Then go to the assignments panel again and re-load the ini. When you have multiple assignments to a button or keypress (you can have as many as you want) the assignment fields in the UI will be disabled and just show the first assignment. Alternatively, depending on the button type, if you just want two assignments, you can assign one on the press and the other on the release. Note that using multiple assignments is also typically used with either compound button conditions (where the action of the button is dependent on the state of another button) or offset conditions (where the action is dependent on the value in an offset). See the Advanced Useer Guide for details, starting on P19 Sequences, Combinations and Mixtures. John

No, this is not easy to do. Lvars are accessed directly via a function provided by the Panels.dll. Simulator variables come via a request to simconnect (where you have to set-up a data definition, a request, a group and priority, and finally request the item) and the value is received in a callback message in a different thread. There is also the added complexities of the types - lvars are all double (64bit floating point numbers), whereas each simulator variable has a specific type. This has also been requested before.

That's the location where the add-on.xml must reside if you want it "auto-discovered". As I said, its better to choose a different location for the actual installation folder. I have had one other report of the installer not creating a key file. but I'm not sure how this is possible. Installing in a different folder fixed it for the last user I think.

You are using v6.0.9. That is an old unsupported version. Please update to the latest release, v6.0.12 and try again, and post your .log an .ini if you still have the issue (not the _prev.log).

Do you have any antivirus software running? If so, maybe disable while you install. Can you also try with the latest installer - just download it again from www.fsuipc.com. If you get the same error, try without installing the autostart component.

Yes it does. But there is nothing we can do in FSUIPC to fix this. It needs to be fixed in the RXP GTN750. We are requesting this data in the standard way - they need to correct their software so that SimConnect recognises the value has change and provides the value when updated. John

I see you are also using P3Dv4.5. I hadn't noticed this and checked in P3Dv5.1. I'll check in that version, but should be the same....

The numpad keys won't work, so please don't try/use them while testing. Your log file is also useless to me. You closed and started a new log. Please don't do this - I need to see the entire log. Please follow my instructions again and show me the entire log file. DO NOT activate any other logging other than that requested.

Ok. Thanks for the update. John

Just checked and the ATC menu options are working ok with the number keys (but not the numpad keys!). Could you enable FSUIPC logging for Buttons & Keys, load your aircraft, open the ATC menu and make a selection. Then close P3D and show me your FSUIPC6.log and FSUIPC6.ini files.

If you re-installed, you shouldn't have to re-register. The details should be populated from your existing key file. It looks like a key file wasn't created for some reason. You can create this manually. In your installation folder, create a file called FSUIPC6.key. Then open in an editor (e.g. Notepad++) and enter the following, replacing the parts in bold with the required information: Note you also installed FSUIPC in your P3D Add-ons folder. It is better to choose another location outside of this and outside of the P3D folders (e.g. C:\FSUIPC6 or C"\P3D Add-ons\FSUIPC6) to keep your FSUIPC6 installation outside of the P3D add-ons folder (and outside of a windows protected folder such as Programs Files).

Did you make sure all 3 parts (name, address or email, key) were exactly as specified in your simmarket email? Best to cut and paste to make sure. I don't have access to your order details, but Pete will (maybe) pick this up later and verify them.

No! It has to be there, with your FSUIPC7.log and FSUIPC7.JoyScan.csv files. Do you see them? Are you sure that you are looking in the correct place?