John Dowson

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?

All standard (user object/aircraft) data is requested via simconnect using the SIMCONNECT_DATA_REQUEST_FLAG_CHANGED and SIMCONNECT_DATA_REQUEST_FLAG_TAGGED flags, so we only receive the data value from simconnect when they have changed. This is the case for all the data we request/receive.

The latest version of MakeRunways (5.11) is compatible with MSFS. Its up to you if you want to use it or not, depending upon if you have any utilities that need the output it produces.

You should not delete it, you should uninstall rather than deleting. An unistaller is created in your installation folder - please use that to uninstall FSUIPC7, or the windows App management panel. Its EXE.xml. Does the installer just stop there or does it continue? What happens if you click 'Next'? Do you have an MS Store install or a Steam install? Could you try uninstalling FSUIPC7, if installed. Run the uninstaller located in your installation folder. If it is not installed at the moment, you can skip that. Then check your EXE.xml file, and if there is still an FSUIPC7 entry, remove it. For MS Store installs, the file is located under LOCALAPPDATA\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\EXE.xml and for Steam installs, under: APPDATA\Microsoft Flight Simulator\EXE.xml Then run the installer again. For your installation folder, make sure that you select a location outside of your Documents folder (where it defaults to!) and outside of your MSFS installation (e.g. somewhere like C:\FSUIPC7 or C:\MSFS-Add-ons\FSUIPC7). Make sure the installer finishes, and if you have any issues, please attach your InstallFSUIPC7.log file. P.S. Please give your support requests an appropriate title, not your user name. I have updated it for you this time.

FSUIPC7 only supports a max of one 'accelerator' key. Did you try with just one - this was working in previous MSFS versions, but I haven't tested it in the latest version. Also, FSUIPC7 handles these accelerator keys (shift, ctrl, alt) in a different manner than other keys. It doesn't receive these keys via simconnect, but detects if they are pressed/held down when the main key is received via simconnect. Thats why the logging is different. So, please try with a single accelerator key. If thats not working, I'll take a look.

@DakotaPilot Its probably not going to happen as I just don't have the resources. There is so much development needed for FSUIPC7/MSFS, and with also keeping FSUIPC6 up-to-date with P3D, and support for all products (including FSUIPC4 and WideFS6/7), I just don't have the time and can't see this getting any better at least for the next couple of years...

But you can just leave MSFS running, you don't have to re-start it everytime. You can reload your button/axis assignments when needed (if editing the ini), or stop and re-start FSUIPC7. If assigning a device in FSUIPC, we recommend to initially start with an empty profile for that device. Just create a new profile for each device (apart from keyboard and mouse) in MSFS and assign then to your devices - new profiles are created empty. Your ini file shows that you are using v7.0.3. The latest version is v7.0.4 - please update. Your ini file is also a bit of a mess....! Have you manually edited this and not ran FSUIPC7 after editing? Some assignments are made to joyletters, others to joy numbers. This is very strange...did you add these manually? Do you have a 'Saitek Aviator Stick'? Its listed in your JoyNames section (assigned to letter Q) but has no GUID. You have assignments to it in your 'Bell Helo' profile. And you 'Robinson Helo' profile has assignments to device '0', which is your rudder pedels. Is this correct? The Cessnam Skyhawk 172SP is also assigned to two profiles 'FSX C172 Lessons' and 'single_engine_piston'. An aircraft should only be in one profile! You also have quite a few assignments to PAN_VIEW and other PAN controls - these are not currently working in MSFS. To control the views, you have to assign keypresses to the view controls in MSFS, and then assign your POV to those key presses. Anyway, please clarify what devices you have and also show me your FSUIPC7.log file, and I'll update your ini for you to try. You should also download and install v7.0.4, although don't run it yet until I've provided you with an updated ini. As for your flaps issue, I'm not sure what that is or for which aircraft, but we can look at that after we've cleaned-up your FSUIPC7.ini.

Thanks for the clarification. Please update if/when you get a response. John

Yes, this is a known problem and seems to effect the activity scenarios more than others. Not sure why, but again seems to be related to SimConnect usage by external clients. I can only re-iterate that if you get a CTD with MSFS (even if its only when using FSUIPC), then this is an issue with MSFS and should be reported to Asobo, Of course, if its FSUIPC that is crashing, then I'd like to know....I've had many reports of this but each one I've investigated is an MSFS crash and FSUIPC auto-closing as a result.... John