John Dowson

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,

Without FSUIPC or Linda running? If so, then SetialIFP2 must be getting the input from your rotaries and changing the display. As I have said, there is no point testing this with FSUIPC without MSFS running. Is this with SerialIFP2 running AND configured properly in FSUIPC using the real and virtual com ports? If you have not tried to configure using SerialIFP + FSUIPC as described in the manuals, you should really try this before anything else.. And if using Linda, you should ask on the Linda support forums, if it is Linda that is driving the display. You should also try with other simpler/stock aircraft, and not he FBW A320 - maybe the A320 is not using the Autopilot Heading Lock Dir sim variable. Have you tried with other aircraft? You can also try logging VRI coms by adding the following to the [General] section of your ini (although I doubt this will reveal anything of use): Debug=Please LogExtras=4 Have you used this successfully with any other flight sims - FSX or P3D)? Other than that, I do not know what to advise with this. There have been no changes in this area for many years (apart from the addition of the VRIDisableCMDRST ini parameter 2.5 years ago), so I suspect it is either related to your configuration or maybe MSFS+FBW. Maybe some other VRI users can help...

No, as its not FSUIPC that is crashing but P3D. You could try logging VRI coms, which you can do by adding the following to the [General] section of your ini" Debug=Please LogExtras=4 Sorry, I don't have any VRI devices.. Maybe some othe VRI users can help you. There is also another VRI support request open at the moment with a different issue - see Maybe you can help each other?

It is MSFS that is crashing, not FSUIPC7 - from your log: Check the Asobo forums and/or raise a support ticket with them.

You could maybe convert the them to use the Wnd library. A demo script attached. FPS_MonitorW.lua

unfortunately that is not the case - I'm just another MSFS user to Asobo. I reported this a long time ago - and have heard nothing, as usual. In fact, previously some basic functions of the SimConnect_Text function were working (sort-of) but it is broken completely since the SU5 update. I'll check to see if there is anything about this in the Asobo fotums and maybe raise again, but it IS known by Asobo - from the documentation: Page Contents (click to expand) SimConnect_Text The SimConnect_Text function is not currently available for use. Syntax N/A

I'm sorry but I don't understand what you mean. If you already have profiles defined, you just install the new version of FSUIPC into the same folder and everything should just work - you don't need to change anything. If you install into a new folder, then you need to copy across all your files (.ini, .key, lua, macros, dlls) to the new folder. But why are you doing this? Were your profiles actually working before you did this? But were there any profiles in the ini before you made that change? Maybe show me your original ini, if you still have it, together with your new one and your log.

First, you posted in a sub-forum which states: NOT for support requests. I have moved your post for you. Sorry, bit what do you mean? There is no installer for MakeRwys.

@Eduardo P Please NEVER post details of your keys - you showed these in the image you attached. I have deleted it. If you do this again, your keys will be added to the banned list. Yes, as I said. But you probably sorted this out yourself at toughly the same time. You should of added an additional post though, and not completely changed your initial post, although its not that important - just means my reply to your original post no longer makes sense! John