John Dowson

@B77X Your logs just show FSUIPC closing as P3Dv5 exited. If you didn't exit, then it looks like P3D crashed so its surprises me that there is no event shown in the Windows Event Viewer. That was what you did for the log you send me? Very strange. I'll take a look later and get back to you. John

There are many Honeycomb users using FSUIPC, especially for MSFS to get around some of the issues caused by some buttons/switches continually sending events. Yes, it can be used for assignments, but only the registered version. If you have FSUIPC4 installed, then you should also have the documentation - take a look at that (especially the User Guide), which will give you an overview of the facilities provided. Note that for the Honeycomb Bravo (and also Alpha flight controls), some lua scripts were posted for these devices the other day which may also be useful if you want to assign using FSUIPC as they allow you to assign to the button numbers outside of the standard 32 button limit). They were posted in the FSUIPC7/MSFS sub-forum, but are also valid for FSUIPC4/5/6. John

Do you see them in your FSUIPC6.in file under the [MacroFiles] section? Note that there is a maximum limit of 127 files - have you exceeded that?

v6.0.11 is the latest official version. v6.0.12 will be released when ready. John

Please check your assignments in P3D. If assigning in FSUIPC, we recommend to disable controllers as if you don't do this P3D can automatically re-assign if/when it detects a new controller. If you have already disabled controllers, then check to see if you are using the JoyLetters facility (see the FSUIPC User Guide, P22) and that your controller number ids haven't changed.

Yes, that is also a known cause of registration failure, and this also prevents FSUIPC from running. John

Not really. I'll probably release one more version of FSUIPC5 sometime in January. After that, it will be closed for future development - mostly, but I will still update for any important bug-fixes or to keep compatible with any possible future releases of 4.x John

Do you a pop-up box (after clicking the Register button)? If so, what did it say? If you did not see the pop-up, re-install and try again and make sure you click the Register button.

That parameter wouldn't, but the other two would have. I only remembered you had that set when I looked at your .ini, I don't think any will make a difference though as I don't think this issue is related to re-connects. The ProvideAIData=No change was the best option, which would reduce the amount of data going through simconnect, and has helped some.

Please see the provided documentation, especially the README.txt that was in the download. Or check the forums. This has now been reported far too many times. Also, before posting again, please read this post:

Yes and yes (presuming you didn't install FSUIPC7 in a windows protected folder!). John

@pilotjohn Please try the attached version. The initial delay should now be working, and the repeat rate adjusted to give acceptable values for standard and virtual buttons. FSUIPC7.exe Using that version with the following: PollInterval=40 ButtonRepeat=25,12 gives initial and repeat delays near enough identical, and hopefully you should get similar results (but not guaranteed!) for other values. John

FYI, I have no found that its now possible to start FSUIPC7 with MSFS by using the EXE.xml. For the next release, I'll switch to using this method. I will still provide the batch file as an optional install, but this will only be used to display the splash screen and start MSFS, not FSUIPC7. This will be a far better method to start FSUIPC7 with MSFS. John

Yes. This will no prevent the CTD, but as it seems to be an issue with SimConnect, the idea is to put less load on SimConnect so it will last longer... There is no point changing TrafficStallTime if using ProvideAIData=No as there is no traffic data to stall! You have to change them BEFORE starting FSUIPC7. I'm not really interested in seeing any logs for this issue. See my previous post - it is a recognised MSFS bug. I am just suggesting some things to try that MAY prevent or delay this crash. We need an update from Asobo to fix. John

@C6_Pat Ok, thanks for the update. Note that it seems this is a known SimConnect issue since the 22nd December update and is being looked at by Asobo - see https://forums.flightsimulator.com/t/little-nav-map-problem-since-dec-22-update/340065/29?u=volt580 John

Note also that some folks have had success getting around this by removing the population of the AI tables, by adding the following to the [General] section of your FSUIPC7.ini: ProvideAIdata=No See .John

Yes, that does seem to be the issue that @thomas747400 is experiencing. Thanks for the link, John

What version of FSUIPC and which FS are you using? Sorry, what do you mean? If you are using P3D or FSX, then if FSUIPC is installed correctly it will be under the Add-ons menu. If you are using FSUIPC7 with MSFS, then this is a separate executable./ If you want any further help, please take the time to describe what your issue actually is. I cannot help if you do not provide any information. John

I see you are using a Honeycomb Alpha. I have heard reports of this causing MSFS to crash when some switches/buttons are ON, as it repeatedly sends press events. Do you have assignments to the Alpha in MSFS (as you don't have many assignments in FSUIPC7!)? Maybe test with either the Alpha disconnected or create a new empty profile for the Alpha and test with that. Your log shows it was MSFS that crashed, and the FSUIPC7 exited (as you have the option 'Exit with FS' set. You should have a crash event log in your windows event viewer. Can you please check? If so, its worth raising a bug report with Asobo via zendesk, and include the crash event report. John

So you installed MSFS under Program Files. Thats not a good idea as its a Windows protected folder. However, I am still surprised that it doesn't work running as admin... I'm sorry, but as I don't have an MS Store install I don't know what to advise (if running as admin doesn't work). if I were you, I would uninstall MSFS and re-install outside of Program Files (e.g. in C:\MSFS) as this would prevent many possible issues down the road... There are a couple of other things you could possible try: - setting cmd.exe to always run as admin (see google for this) - change the 'cmd.exe /C start...' line by specifying a an admin user with runuser, e.g. runas /user:username cmd.exe /C start shell:.... John

As Microsoft.FlightSimulator_8wekyb3d8bbwe ? Then I'm not sure why it isn't working. Maybe you are using a different shell? Do you have a desktop icon to start MSFS that works? I so, right-click, select Properties, and show me the URL that that uses. John

I think they are called "staycation" these days!

You should never have to manually enable WideFS, it should enable automatically after the following message is logged: 133922 -------------------- Starting everything now ---------------------- 133922 Starting WideServer now ... This only occurs once you have selected a plane (for the first time), set-up your flight and clicked the FLY button. The exception is if you manually disable WideFS - if you do this, WideServer will not automatically start and you have to manually Enable. You can also manually Enable to stat WideServer earlier, but I don't see much point in doing this... As Pete says, this is certainly wrong. Did it 'close' or 'crash'? Could you provide am FSUIPC7.log file when this happens, and also check for any crash events in the Windows event viewer. John

Its pretty simple to add. I'm not familiar with ProSim, so I don't know if it will be populated. I'll make a test version for you in the next few days so that you can test. John

I can do nothing with such a report unless you provide me with further information - I need to see your FSUIPC6.log file (generated when such a crash occurs) as well as any event information from the windows event viewer. Your FSUIPC6.ini would also be useful. John