John Dowson

First, you are using an old version of FSUIPC7. Please download the latest (and only supported) version, v6.2.9. Also, looks like your device GUIDs have changed at some point, and you have assignments to the letter assigned to the old GUID as well as the new ones. I have tried to correct this in the attached FSUIPC7.ini, so please try this once you have updated and let me know how it goes. John FSUIPC7.ini

Yes, this offset area is free for general use and many users use this area for lvars. Yes - if you let me know what your software does, I'll let you know an area you can use. I am also planning to update the offset status document with info on that the reserved areas are reserved for, and if they can also be used as 'free user offsets' if the user isn't using the 3rd party app that the area was reserved for. John

Did you click the Register button after entering your details? If not re-install and do that, If you did that, what did the pop-up say? John

What was the issue?

See the User guide, P36: Alternatively, you could try manually editing the ini, removing the raw specifier and changing the delta back to 256 (from1) - see the Advanced User guide for the format of the axis assignment lines in your .ini, P41: John

You need to check the available lvars and hvars. You can list available lvars from the Add-ons->WASM->List lvars menu option. For hvars, you need to make them known to FSUIPC7 by adding a hvar file (for the A320 or FBW A320) to the WASM. Instructions are provided in the Advanced User manual, and a hvar file for the FBW A320 is provided in the FSUIPC7 HvarFiles folder (although it will be out of date, it should be ok to get you going). Alternatively, if using the FBW A320, you could install the MobiFlight WASM module and use the MobiFlight events - check the EventFiles folder for various event files (although they will also be out-of-date). The following link is a good (MF) resource for the MF presets. Even if you don't install the MF WASM, you can still use this to see what lvars/hvars and calculator code their presets use: https://hubhop.mobiflight.com/#/list Also quite a bit of information in this forum on using lvars/hvars/MF for the A320.

Could you please activate: - logging for Buttons & Keys and Lua Plugins in FSUIPC7 (from FSUIPC7 Log menu) - WAPI debug logging (from FSUIPC7.ini file) - WASM debug logging (from FSUIPC_WASM.ini) Then generate an FSUIPC7.log and FSUIPC_WASM.log showing your issue. Also send the calc code from the WASM menu so that is also logged. Please remember to close/exit FSUIPC7 before attaching your log - the one you attached is useless as you don't even have an a/c loaded or get to the ready-to-fly state. If you can then attach the 2 log files I will take a look - but tomorrow, finishing for the day now. John

Please see Appendix 3 in the Advanced User guide: Handling VRInsight serial devices in FSUIPC. Also take a look at the document Lua Plugins for VRInsight Devices.pdf. John

Please try the following version: FSUIPC7.exe John

I do not need to see any images, the issue is clear. There is no FSUIPC server (well, there is at www.fsuipc.com) - these are SimFlight servers. I have replied. Why another PM? I do not provide support via PMs. For any issues with posting on the forum/SimFlight, please contact SimFlight support directly as they are in charge of the support forums. John

Ok, I can also see a dmp file created when FSUIPC exits, although the FSIOPC7.log shows FSUIPC exiting normally. I don't think this is anything to worry about, but I will look into it. It is probably related to the exception generated when MSFS quits due to a stale SimConnect handle - you will also see a faulting application event in the Windows Event viewer. I'll see if I can handle MSFS shut-down more gracefully so that this does not occur.

Strange. Does this occur every time you close down MSFS? Can you show me your FSUIPC7/log file please, from a session when it created a dump file on exit.

似乎 SimMarket 注意到了这一点，并为您生成了一个新的。 无国界医生是我支持的主要战车（之一） - 你做得很好！ Sìhū SimMarket zhùyì dàole zhè yīdiǎn, bìng wèi nín shēngchéngle yīgè xīn de. Wú guójiè yīshēng shì wǒ zhīchí de zhǔyào zhàn chē (zhī yī) - nǐ zuò dé hěn hǎo! Thank you! John

Also, please note, that FSUIPC does nothing with flight plans except instruct/ask MSFS to load them, via the simconnect API call that (I already mentioned) is documented as not (or only partially) working. This means that there is nothing I can possibly do in FSUIPC to improve this at the moment, except maybe to update the documentation on what is and what is not working. However, when this depends on other mods installed, it becomes even more difficult for me to do this, but I can mention mods that are known to cause issues, if this is actually the problem/difference between your two set-ups. John

我有你的电子邮件 - 让我知道使用什么名字，我会PM你一把钥匙。 Wǒ yǒu nǐ de diànzǐ yóujiàn - ràng wǒ zhīdào shǐyòng shénme míngzì, wǒ huì PM nǐ yī bǎ yàoshi. That is, I have your email - let me know what name to use and I will PM you a key.

I'm sorry, but FSUIPC does not support unicode/Chinese characters (kangxi/Hanxi/?), and so the key generation failed. Please supply me with a name and email address in standard ascII, and I will PM you a license key file. That is, please give me a name and email address that I can use to generate a key for you - you can PM me the details if you prefer. John

Did you try the suggested logging? That should show you what is being sent. And ithe port is irrelevant. What is relevant is if you have set-up using the virtual port or not. Have you tried this? If not, why not? And, as I have said, the FSUIPC code for VRI devices hasn't changed much (or at all, apart from the new ini option already mentioned) in 10 or so years, without an issue. You are not responding to my questions or suggestions, so I can't really do anything about this. And I do not know why you keep mentioning specifics about the FBW A320. FSUIPC is aircraft agnostic - it is YOU that nee to know how the aircraft works and configure FSUIPC accordingly. As I previously mentioned, add-on aircraft may not use the FS facilities and implement their own systems, so standard FS controls/offsets may not work. Have you actually tried with any other (preferably stock) aircraft? I'm sorry but I have nothing more to say on this matter until I get some response from what I have already proposed. Mainly, have you actually tried setting things up as described in the documentation? If you are not prepared to try this, this topic is closed. John

Ok, so this sounds like it was a mod interfering with the plan loading, no? Not sure how (or why) mods can do this... Maybe @n0taurius can upload/attach a valid flight plan (i.e. one that works for you) and @Greyheart can upload one that fails, and you can try each others (with and without mods) to confirm it is actually the mod causing this issue? I will also try both, and look into that mod (which I don't have or know much about!). John

Yes, its strange that it is working for some and not others. I think it must be to do with the plan, aircraft or AP system used. But I'm glad its working for you at least. I'll take a look at this in more detail when I get time (hopefully this weekend), to see if and what flight plans I can load via FSUIPC7. Cheers, John

Oh - and save (make a copy) of the FSUIPC WASM installed in the Community folder, if using that, as the latest version will not be compatible with your v7.2.1 (in case you want to roll back).[sorry, for @n0taurius who is using v7.2.1]

Could you please try this - download and install the latest version, v7.2.9 (just released). Save a copy of your current v7.2.1 FSUIPC7.exe (make a copy somewhere) just in case. Nothing has changed in this area since the version you are using, but if its working for you in that version and not in the latest, I will look into it. John

Ok, that's interesting. Maybe it works with flight plans exported from LittleNavMap then, but has issues with plans generated by MSFS? @GreyheartAre you generating your flight plans within MSFS, LittleNavMap or something else? Have you tried loading a flight plan generated from LittleNavMap? FSUIPC7 just uses the SimConnect API function to load the flight plan. If its not working, as the OP's post suggests, then its not really worth me looking into this in FSUIPC7 at the moment as the API function is not documented as Working. Cheers, John

From the MSFS SimConnect SDK documentation: (see https://docs.flightsimulator.com/html/index.htm?#t=Programming_Tools%2FSimConnect%2FSimConnect_API_Reference.htm&rhsearch=file persistent storage) So flight plan load/save functions in the SimConnect SDK (which is what FUIPC uses to communicate to the sim) are not currently working. This needs to be fixed by Asobo. In the mean-time, you should use the MSFS facilities directly for loading/saving flight plans. John

You could try the following hvars: H:Generic_Master_Warning_Push H:Generic_Master_Caution_Push Maybe try them out first using the Add-ons->WASM->Activate Hvar menu option.

Have you been manually changing your ini? This (the part in bold) needs removing: You also have various unrecognised devices: and these are the ons that you are using in your R22 profile, e.g. You need to either: - change those letters to the letter actually assigned to your device (A-F), or - delete those assignments and re-assign. Your log also shows that you were disconnecting and re-connecting your devices while FSUIPC was running. Not a good idea to do this, especially if having issues. You did this manually, or were you using UseProfiles=Files ? If you were, why is this now UseProfiles=Yes ? When you install FSUIPC updates, you just install into the same folder and change nothing, and everything should work. If you don't have your original FSUIPC6.ini, then there is not much I can do. If you were previously using Profiles as separate files, then you could switch to this again, byt as you have lost all your profile sections, you will need to manually create them again in the main FSUIPC6.ini. In summary: - correct your current ini as advised - once that is done, try swithing to profiles-as-separate files - copy your old profile files to your Profile folder (if not already there) - manually create the profile section in your FSUIPC6.ini for the remaining profile files You also need to check what device letters your profile files are using, as they may need updating if they are using those designated as missing. I don't know how you go into this mess. FSUIPC does not touch or alter your ini files in any way during installation, and certainly doesn't remove any profile sections,