John Dowson Posted March 10 Report Share Posted March 10 The next version of FSUIPC7 is now available as a beta release, v7.3.18c. This includes the following changes: - new ini parameter added: ComWriteLoopTime. Default value 10ms - default value of ComReadLoopTime changed from 20ms to 10ms - request for new FuelSystem simulator variables removed to prevent continual MSFS developer console messages: this is still a temporary fix. I will look into a proper fix where these simvars are only requested when used by the loaded aircraft. The simvars removed are: 0x08F8: FUELSYSTEM ENGINE PRESSURE:1 0x0990: FUELSYSTEM ENGINE PRESSURE:2 0x0A28: FUELSYSTEM ENGINE PRESSURE:3 0x0AC0: FUELSYSTEM ENGINE PRESSURE:4 It is still required to set NumberOfPumps=0 in the [General] section of your FSUIPC7.ini file to prevent all MSFS console messages. - WASM updated to 1.0.1: - LvarScanFrequency ini parameter changed to determine max number of scans per second regardless of LvarUpdateFrequency setting - lvar values not updated until at least 200ms after config change (to give time for clients to process changes) - minor memory related bug-fixes and logging updates - WAPI updated to 1.0.2: - lvars-ready callback now called once initial values received - lvar-value reading locked to prevent reading until initial values received - minor updates in logging and to prevent compilation warnings This has been released as a beta in order for anyone using the WAPI / WASM to update before I release - although the current WAPI & WASM versions should be backwards compatible. The FSUIPC7 installer package is available here: Install_FSUIPC7.3.18.zip For developers, the new WASM / WAPI package is available here: FSUIPC-WASMv1.0.2.zip Please comment in this topic for any issues found, and not in the support forums. Regards, John Link to comment Share on other sites More sharing options...
NaMcO Posted March 10 Report Share Posted March 10 It seems that the data being fed to my ACARS application is now read faster from the simulator with 7.3.18b. At least it's what it looks like. I am trying 7.3.18 with PMDG's 739 after upgrading from 7.3.16, when trying to release the parking brakes (sometimes it fails because now you need a different action to release them), i am getting a lot of "Parking brakes RELEASED" then "Parking brakes SET" messages where before i only had them when the brakes were actually released or set. Is this related to those changed timers? Here is the relevant section, everytime i tried and failed, i instantly got a related message. These seem to take longer with 7.3.16 or something as i've never seen them before when trying the same sequence. Link to comment Share on other sites More sharing options...
John Dowson Posted March 11 Author Report Share Posted March 11 11 hours ago, NaMcO said: It seems that the data being fed to my ACARS application is now read faster from the simulator with 7.3.18b. At least it's what it looks like. the latest version is 7.3.18c, not b, 11 hours ago, NaMcO said: Is this related to those changed timers? I don't think so, unless those parking brake messages are based upon lvar changes, but even then I don't think that should be happening as the lvars should be locked for reading until the initial values have been received. This was a change from 7.3.18b to 7.3.18c, so if you are not using the latest version, please update and try again. If you get the same issue, can you show me your FSUIPC7.ini and FSUIPC7.log files, the latter generated with logging for Events activated as well as Debug level logging set in the WAPI. Link to comment Share on other sites More sharing options...
NaMcO Posted March 11 Report Share Posted March 11 Trying 7.3.18c, i guess the "b" was a typo. The parking brakes are not my main concern as the aircraft does MOVE the lever and then returns it to the original position if it fails to release them. I guess the data read from FSUIPC now flows through my cycles faster or something and it gets registered while previously wasn't. No big deal as it IS happening. My main concern is related to other events that seem to occur "randomly", so i am trying to figure out what's happening exactly in order to come to a conclusion whether it is an issue i can fix on my side, or if i'll need some extra feedback to find the cause. These are mostly "out-of-place" situations and until now only detected on the PMDG737 range. Sometimes in mid-air i get the information that the power has been disconnected and reconnected (battery), or when landing while the landing lights switch are "ON", i get a penalty saying i am landing with them "OFF", so it looks like a timer issue. This might be related to my read-and-process loop, so i'm flying quite a lot now and logging my own ACARS data. It's just strange that it worked so nice with 7.3.16 and now with .18c it doesn't 😛 I am reading data from FSUIPC every 1000ms, then check i did obtain data and cycle through a multitude of events to process what's happening. Might have to lower the query time to 500ms or something. Anyway, evaluating... Thanks for the response John. Link to comment Share on other sites More sharing options...
John Dowson Posted March 11 Author Report Share Posted March 11 I can't see how the changes between 7.3.16 and 7.3.18c can have anything to do with this - the changes are mainly related to improving lvar access, plus a change to improve reliability when using VRI com devices. I am not sure what events you are referring to (need to see a log!), but if they are related to simvars and not MSFS events (or k vars), then it could be related to the automatic scanning for new lvars. You can try turning this off by setting the following parameter in your FSUIPC_WASM.ini file to see if iy makes a difference: LvarScanFrequency=0 13 minutes ago, NaMcO said: I am reading data from FSUIPC every 1000ms, then check i did obtain data and cycle through a multitude of events to process what's happening. Might have to lower the query time to 500ms or something. Anyway, evaluating... Ok. If you find anything let me know, and please attach your FSUIPC7.ini and .log files (with appropriate logging activated, as detailed in my previous response). Note I will be off this afternoon and am busy tomorrow, so will look into any issues on Monday now. Cheers, John Link to comment Share on other sites More sharing options...
NaMcO Posted March 14 Report Share Posted March 14 I didn't manage to replicate the issue anymore in 8 flights. I guess that was some sort of desync maybe even caused by MSFS. I have logging on and will keep it for a while, so if i manage to replicate it, i'll have logs this time around. As for the parking brakes "issue", i'll just read the proper var for when the lever is actually in the RELEASED position, that solves the SET/RELEASED ACARS logging with multiple failed attempts. Link to comment Share on other sites More sharing options...
John Dowson Posted March 14 Author Report Share Posted March 14 Ok, thanks for the update. 1 hour ago, NaMcO said: I guess that was some sort of desync maybe even caused by MSFS. I Yes, I seem to get many random issues with MSFS, including quite a few CTDs. And they still occur when I remove everything from my community folder and without FSUIPC7 running. They can last a few days and then seemingly go away with no changes on my side. Can be quite frustrating.... John Link to comment Share on other sites More sharing options...
John Dowson Posted March 15 Author Report Share Posted March 15 FSUIPC7 v7.3.18 has now been released, as well as WASM 1.0.2 and WAPI 1.0.2. There are some minor changes to the WASM in the released version compared to the last beta release: - the LvarScanFrequency ini parameter now accepts negative values which indicate the minimum number of seconds between scans. The default value of this ini parameter has been changed from 2 to -2. - logging updates The default value of the FSUIPC7 NumberOfPumps ini parameter has also been changed from 6 to 0, to prevent the Asobo console log messages in the default configuration. I will now lock this topic. Any issues. please use the FSUIPC7 support forum. John Link to comment Share on other sites More sharing options...
Recommended Posts