achilleghilotti Posted January 26 Report Posted January 26 (edited) *** Moved to FSUIPC7 support sub-forum *** Good morning everyone, the following problem occurs with FS2024. When I start the simulator, after a restart of the PC, the LVARs work correctly I can write and read. After a few minutes, in my .NET applications, the LVARs no longer respond. It is not sufficient to restart the simulator but it is necessary to restart the computer to resume operation. I already checked on the forums for fsuipc_wasm.ini, fsuipc7.ini. Fenix A320 aircraft used. With FS2020 everything works correctly. Unfortunately I can't attach the WASM log file because the maximum upload size prevents me from doing so FSUIPC7.log Edited February 1 by John Dowson Moved to FSUIPC7 support forum
achilleghilotti Posted January 26 Author Report Posted January 26 forgive me, I didn't write that .NET applications reside on remote miniPCs and are used to manage touch monitors that emulate overhead, mcdu, efis and more
achilleghilotti Posted January 31 Author Report Posted January 31 sorry for the delay in replying I checked the link and I can say that sometimes closing the simulator in the log that the 'close' and sometimes not I think it's important to remember with fs2020 everything works.
achilleghilotti Posted January 31 Author Report Posted January 31 also try changes to the wasm.ini file but nothing changes as well as positioning it where it is described in the advanced guide FSUIPC7.log FSUIPC_WASM.log FSUIPC_WASM.ini
John Dowson Posted January 31 Report Posted January 31 (edited) 15 hours ago, achilleghilotti said: I checked the link and I can say that sometimes closing the simulator in the log that the 'close' and sometimes not If the WASM crashed, there will be no closing statement, and if the closing statement is there, the WASM didn't crash. Are you saying that you still have your issue when the WASM didn't crash? 15 hours ago, achilleghilotti said: I think it's important to remember with fs2020 everything works. The WASM crash seems to happen more often in MSFS2024, although I still can't trigger this here. I will take another look, next week, time permitting, and investigate this further. On 1/26/2025 at 11:41 AM, achilleghilotti said: forgive me, I didn't write that .NET applications reside on remote miniPCs and are used to manage touch monitors that emulate overhead, mcdu, efis and more Then please show me / attach your FSUIPC7.log file from the remote PC - you seem to have attached the one from the FS PC. Your WASM log does show some issues: Quote ... Fri Jan 31 17:18:02 2025 [ERROR]: Ignoring request to update LVARs as updated internally Fri Jan 31 17:18:02 2025 [ERROR]: Ignoring request to update LVARs as updated internally Fri Jan 31 17:18:03 2025 [ERROR]: Ignoring request to update LVARs as updated internally Fri Jan 31 17:18:03 2025 [ERROR]: Ignoring request to update LVARs as updated internally Fri Jan 31 17:18:03 2025 [ERROR]: Ignoring request to update LVARs as updated internally Fri Jan 31 17:18:03 2025 [ERROR]: Ignoring request to update LVARs as updated internally Fri Jan 31 17:18:03 2025 [ERROR]: Ignoring request to update LVARs as updated internally Fri Jan 31 17:18:04 2025 [ERROR]: Ignoring request to update LVARs as updated internally Fri Jan 31 17:18:04 2025 [ERROR]: Ignoring request to update LVARs as updated internally ... One of your FSUIPC clients is requesting lvar updates (via WAPI ini parameter LvarUpdateFrequency) - you should remove that/set to 0 and let the WASM control all updates. 15 hours ago, achilleghilotti said: also try changes to the wasm.ini file but nothing changes What did you change? 15 hours ago, achilleghilotti said: as well as positioning it where it is described in the advanced guide There are two locations for the FSUIPC_WASM.ini file. if there is on in the permanent storage area, under you user' AppData folder, then this will take presidence. The values used are logged in the log file: Quote Fri Jan 31 16:57:24 2025 [INFO]: Ini file '.\FSUIPC_WASM.ini' loaded from add-on package Fri Jan 31 16:57:25 2025 [INFO]: Ini file '\work\FSUIPC_WASM.ini' loaded from persistant storage Fri Jan 31 16:57:25 2025 [ALWAYS]: lvarUpdateFrequency = 4 Fri Jan 31 16:57:25 2025 [ALWAYS]: lvarScanDelay = 10 Fri Jan 31 16:57:25 2025 [ALWAYS]: lvarScanFrequency = 0 Fri Jan 31 16:57:25 2025 [ALWAYS]: lvarScanPeriod = -2 Fri Jan 31 16:57:25 2025 [ALWAYS]: useAirLocForHvars = 0 Please show me/attach the following files showing your issue: FSUIPC7.ini & FSUIPC7.log: both from the PC that is requesting the lvar changes, and with the following logging activated (only!): Buttons & Switches Events Extras WAPI -> Debug FSUIPC_WASM.log file: with Debug level logging activated P.S. I have moved this post to the FSUIPC7 support sub-forum Edited February 1 by John Dowson PS added
achilleghilotti Posted March 18 Author Report Posted March 18 good morning everyone, I had to suspend the game a bit for work and a bit for other things... In the meantime I looked at the various advancers user guides etc. I also installed the MSFSVariableService example software on the same machine as the simulator but on MSFS2024 it doesn't work either. It connects but doesn't even load the LVAR list.
achilleghilotti Posted March 18 Author Report Posted March 18 I checked the various WASM, FSUIPC etc. ini files. They are also the same as MSFS2020 which instead works perfectly
John Dowson Posted March 18 Report Posted March 18 Sorry but it is difficult to understand what your issue is. Is this with software that you have written using Paul's .Net client dll? If so, when you get the issue, can you still use lvars via FSUIPC or using the WASMClient? Basically you need to determine if the issue is with your software or if the WASM has crashed. So please do that. If the issue is with your software and you are using Paul's .Net client dll, I cannot help you, and you need to post in Pail's .Net dll client forum: https://forum.simflight.com/forum/167-fsuipc-client-dll-for-net/ 15 minutes ago, achilleghilotti said: I also installed the MSFSVariableService example software on the same machine as the simulator but on MSFS2024 it doesn't work either. It connects but doesn't even load the LVAR list. That is also a question for Paul's forum. Many of your posts are very difficult to read and it takes a lot of work just to try and understand them. I understand that this may be a language / translation issue, but please take care to post in a format that is at least readable...e.g. at least no scroll bars please.... And this is VERY important: On 1/31/2025 at 8:21 PM, John Dowson said: Your WASM log does show some issues: Quote ... Fri Jan 31 17:18:02 2025 [ERROR]: Ignoring request to update LVARs as updated internally Fri Jan 31 17:18:02 2025 [ERROR]: Ignoring request to update LVARs as updated internally Fri Jan 31 17:18:03 2025 [ERROR]: Ignoring request to update LVARs as updated internally Fri Jan 31 17:18:03 2025 [ERROR]: Ignoring request to update LVARs as updated internally Fri Jan 31 17:18:03 2025 [ERROR]: Ignoring request to update LVARs as updated internally Fri Jan 31 17:18:03 2025 [ERROR]: Ignoring request to update LVARs as updated internally Fri Jan 31 17:18:03 2025 [ERROR]: Ignoring request to update LVARs as updated internally Fri Jan 31 17:18:04 2025 [ERROR]: Ignoring request to update LVARs as updated internally Fri Jan 31 17:18:04 2025 [ERROR]: Ignoring request to update LVARs as updated internally ... Expand One of your FSUIPC clients is requesting lvar updates (via WAPI ini parameter LvarUpdateFrequency) - you should remove that/set to 0 and let the WASM control all updates. You MUST make sure that any/all clients are NOT requesting lvar updates as this should be controlled by the WASM, not the client(s). John
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now