These are the 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, but are now no longer available.
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
Bluebird B757 | Issues reading and setting lvars
Hi,
I am using FSUIPC7 to send and read lvars (MSFS24) in order to use an Overhead Panel with my own software. I was trying to code a profile for the Bluebird B757. Something seems to interfere with FSUIPC7.
Scenario 1: When I start and load the sim with the 757 first, the sim receives my lvar commands. The buttons are moving as programmed. But reading an lvar returns 0. Even reload and list lvars in Add-ons -> WASM mostly shows zeros (only a few aren't 0 - maybe those defaults are not equal to 0?) on variables that are definitely not 0. When I load another aircraft, I am not able to send or read any lvars.
Scenario 2: When I start and load the sim (and FSUIPC) with a different aircraft (other than the 757), reading and sending lvar commands is working as expected. As soon as I am loading the 757 I can't send lvar commands to the 757, reading from the 757 is still not working and when loading another aircraft I did not load before, it's lvars won't work as well. When I restart the sim and FSUIPC the aircraft I was loading after the 757 will work again. Also when listing the lvars, none of the 757 lvars are listed in scenario 2.
Changing the lvars through the in-game tools is working at all times. I also own Spad.Next. I've testet it in scenario 2. Spad was able to successfully send a lvar command to the sim. This is why I am suspecting an interference with FSUIPC. For me it looks like something is crashing when I load the 757, but I could not find any proof except those two scenarios.
I hope my explanations make sense. This is what I was able to find out on my own. Unfortunatley, I am stuck on this. I need some help to be able to use the 757. Any help is greatly appreciated.
(Just in case: I am using FSUIPC7 - Version 7.5.9)
It sounds like the FSUIPC7 WASM module is crashing for some reason. When you get your issue, you can check to see if the WASM has crashed or not by looking at the WASM Debug window (you will ned Devmode enabled) and checking the status in the Module Section page.
I presume you are using MSFS2024, no? Ongoing issues with random WASM CTDs have been reported in MSFS2024, so this may be related, although by the sounds of things this is pretty consistent and not that random...
Could you please activate WAPI Debug logging (Log->WAPI->Debug) as well as logging for Buttons & Keys, and also enable Debug level logging in the WASM (via the FSUIPC_WASM.ini file - see the documentation if you don't know where this is) and show me / attach both your FSUIPC7.log and FSUIPC_WASM.log files and I will take a look. Also check the status of the WASM module in the debug window to confirm if it has crashed or not.
If this is indeed due to a WASM crash, I may also need to see another WASM log file but with Trace logging enabled, as this may provide further information. But first confirm it is a WASM crash and show me the log with Debug logging enabled.
Thank you for your response. The status of the fsuipc-lvar-module (FSUIPC7_WASM.wasm) is "READY". I've screened the wasm debug window for you just to be on the safe side.
Correct, I am using Microsoft Flight Simulator 2024.The issues are consistent and reproducable to 100%. Before I created this topic, I've tried to recognize a pattern which took me like 3h (just to be sure.) I only have these issues when loading a flight with the 757 and I have them everytime when I load this aircraft.
I also attached the logs you wanted. The sim started with the ini A350 selected in the main menu. I changed the aircraft to the 757 and then loaded a flight for the first time. I only replaced my real full name within the paths and email address from the log. In the FSUIPC_WASM log I've already seen a lot of "[ERROR]: Simconnect Exception received: 31 (dwSendID=XX)". After that I got curious and loaded the 757 with the fsuipc wasm log level on trace. I've also attached this log.
Posted by: @lh096After that I got curious and loaded the 757 with the fsuipc wasm log level on trace. I've also attached this log.
This was not needed (and I have removed it to save space!). You also have logging for IPC Reads/Writes set in FSUIPC. This fills the log with useless information - please only set the requested logging.
Posted by: @lh096I've already seen a lot of "[ERROR]: Simconnect Exception received: 31 (dwSendID=XX)"
This is the problem. This error implies that the maximum amount of space for the client data areas (CDAs), which is 1MB, has already been allocated. The FSUIPC WASM has requested around 200k of this space, so something else must be using most of this area/space. What other WASM modules or applications are you using/running at the same time? Or maybe its the aircraft itself that uses CDAs - does it have a WASM component or an external app that it communicates with?
The first thing to do is to try and determine what is using all the allocated area for the client data areas, and see if this can be reduced. If using other add-ons / third party software (any SimConnect clients), then try running without these initially. Does FSUIPC then function as normal without this error? If so, then start each application one by one (or add back to Community folder and restart) and test. This should help to determine if another add-on is using an excessive amount of this space.
You could also maybe ask the aircraft developers/support if the aircraft uses SimConnect CDAs, and if so how much of this data area it uses.
I am not sure what can be done about this. The only thing I can think of (without a complete redesign and rewrite of the FSUIPC WASM) would be to limit the number of CDAs requested/created by the FSUIPC WASM module. As there is no way to determine the amount of space already allocated or remaining, this would have to be a new ini parameter that would have to be manually set. If this was done, this would limit the number of lvars that FSUIPC sees. Looking at your logs, you would have to limit to 23 or possibly 24 CDAs, which would give you visibility of the first 3358 or 3504 lvars found - there are 6528 lvars. This would require a WASM update - I can look into this if this is an acceptable solution.
But first it would be nice to determine what is requesting/using the client data area space. As well as checking other add-ons as already advised, a SimConnect log file would also help with this - maybe you could generate one and show me? See the FAQ section on how to generate a SimConnect log file:
https://fsuipc.com/community/fsuipc-faq-other/logging-simconnect-when-request-by-fsuipc-support/