This are the (new) Support Forums for FSUIPC and related products.
These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, and are still available (until the end of the year) for read-only here.
At the moment these new forums are quite empty – I will be updating the FAQ section and copying across the User Contributions from the old forums in the next few months.
Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.
Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE
Posted by: @paul-marchintonIt appears that the problem is after closing a flight down then opening another at the gate (cold and dark) can you please confirm if you would have expected that
No, it should work however you stop / start a flight. As I say, please show me a log. Maybe try with all your buttons assigned to repeats off, and with the requested logging, so that I can actually see what is important rather than having to look at a file containing over 5 million lines…..or, better, sort out that issue!
HI i have been doing some testing to try find a pattern to loosing the connection between the actual switch and the sim I don’t really think I have found one but these were the results
32 x start of a flight
8 x from loading the sim from the desktop, all 8 worked
8 x from using “RESTART” after a previous flight. 7 out of 8 times worked
8 x from using “END FLIGHT” after a previous flight. 7 out of 8 worked
8 x from using “MAIN MENU” after a previous flight 5 out of 8 worked
So the only thing I have learnt from this is to close the sim after every flight to make sure it works on the next flight. I have also removed the repeat.
Can you please advise are you wanting me to send any files
Posted by: @paul-marchintonI will look how i can change the repreat action but have had this configured for well over a year in FS2020 maybe sort a rotary.
I am not saying that this is a cause of your current issue, just that it is not a good way to assign and could cause performance issues – and it also makes it very difficult to look into your issue due to the flooding of the log.
Posted by: @paul-marchintonI definantly did not star FSUIPC manually
Then did you manually edit your EXE.xml at some point? Maybe attach that file so I can take a look. Or wait until I see your next log and we’ll see what that says.
Posted by: @paul-marchintonCan you please advise are you wanting me to send any files
Yes, as I keep saying, I need to see a log file showing your issue, without all the “noise”.
Turn all logging off. Then fly as normal until you get the issue. When you get the issue, make sure any switch / sticky button that is assigned on repeat is off (so the log isn’t flooded), then activate logging for Buttons & Keys and WAPI Debug level logging. Then activate a couple of buttons/switches/assignments that are not working – preferably one assigned to a preset as well as one assigned to a standard control, then exit and attach the following files: FSUIPC7.log, FSUIPC7.ini, FSUIPC_WASM.log. It would also be a good idea to set Debug level logging in the WASM via the FSUIPC_WASM.ini file – see the WASM section of the Advanced User guide for details on the WASM log and ini files.
You could also check if the WASM is still running via the MSFS developer tools menu. There is a known issue where the WASM can crash, which would prevent any assignments to presets/lvars/hvars from working. Nut your FSUIPV_WASM.log file, with Debug logging enabled, in conjunction with your FSUIPC7.ini file should tell me if the WASM had crashed or not.
John
No never edited any file, above my knowledge don’t want to learn the workings of a programme as I see the web full of people trying to sort bugs, fixes etc just want to use the sim as it is designed to be used. I’m happy to just leave it as it is and I know now to close FS2024 before another flight, if you do find there is a problem which needs an update to fix, I would appreciate you letting me know.
Thanks Paul
Posted by: @paul-marchintonI’m happy to just leave it as it is and I know now to close FS2024 before another flight,
You really shouldn’t need to do this, but I would need to see your files to see why this is occasionally not working. I will also test further here in MSFS2024.
Posted by: @paul-marchintonif you do find there is a problem which needs an update to fix, I would appreciate you letting me know.
I will if I remember – but better to check the News section occasionally, and look at the changes.txt file or History document when I release a new version, which will detail any bugs fixed.
John
Posted by: @paul-marchintonI’m happy to just leave it as it is and I know now to close FS2024 before another flight,
One last question on this…Previously you said that you had to ‘reload button assignments’ to get things working – is this not the case then? Does it re-connect and start working as expected if you exit and restart FSUIPC7 (i.e. keep MSFS running)? If the only way to recover is to restart MSFS, then this would indicate a WASM crash. An occasional WASM crash is a known issue (and there is a FAQ entry on this) and seems to be an MSFS issue, and WASM crashes seem to be more common in MSFS2024 than in MSFS2020. I am planning to look into this further in the coming weeks.
Regards,
John
yes, I used to re load buttons that then would make it work but not always the first time but bear in mind i only have been using 2024 for around a week and this was only done on 2024.
The occasional loss of connection in 2020 was restored by disconnect and reconnect to sim within FSUIPC interface but that was rare, but that didn’t seem to work in 2024
Would it pe possible to send the link to the FAQ on this article please.
Paul Marchinton