NaMcO

Thanks a lot John.

Hello, As per the topic, is there a way to disable the auto update feature? A window keeps popping up every now and then because there is a new version out and i don't want to update straight away because i run quite a lot of applications (some developed by myself) and i need to test things out before deciding on the update. This window comes out on top of my sim and i need to close it all the time becoming quite annoying. Thanks.

Indeed. Clearing the browser's application cache entirely reveals the new file. Thanks John!

@John Dowson I have posted in another thread about this... The link still downloads version 7.3.7.

Hello, It looks like the link still points to the previous 7.3.7 version. I mean, the file is the same, apparently it hasn't been replaced on the server.

Sounds great, thank you John!

Hello, First of all, i am not trying to cause any pressure for a release. I am just wondering if the next version will come sometime after SU10 or if something is planned prior to that as i am going to release new software for my Virtual Airline that depends on the new version and wanted to plan accordingly. Thanks! Nuno

Thanks a lot John. I have tested it and 0x0590 is returning the desired values. Awesome! Meanwhile i have tested this simvar some more in longer flights and the altitude is indeed correct. Now if only all other developers start using it for IVAO and so on, everyone will once again be synchronized 😊

Hello again, This is definitely the SIMVAR to read as it holds the calculated altitude based on pressure (or so it seems). I am reading it to 0x2544 and obtained the presumably correct values for a test of FL300 350 and then 380 with PMDG's 737. 0x2544, 4, INDICATED ALTITUDE CALIBRATED,I32, Feet, w (although i don't think it is writable, nor do i need it - just copied for a test) So, thanks a lot for adding it to a fixed offset, it will be very useful indeed! Nuno

I guess this is the solution. I will look into this, and report back for anyone interested. Thanks a lot for your input John.

I read that the Vpilot client developer solved the issue in some way, but i cannot find any information about what he did in order to get the proper altitude from MSFS. I can read the aircraft corrected altitude which usually translates to 35000 38000 or 32000 depending at which altitude you're flying, but this is still not the actual altitude the aircraft is flying at. Is there really no other way except to "do the math" and get the altitude? Does FSUIPC even have all the required offsets for these calculations? I'm sorry, but i'm a complete newbie regarding altitude calculations with pressure and temperature on the mix, so this is why i'm asking. Thanks!

Thanks, just wanted to make sure this was something that had to be addressed (or not) on the Asobo side. Since it is, i'll just wait until they fix it.

@John Dowson I opened a new topic because this one seemed kind of "abandoned" and it was not my own question. But i do agree it is related, so... Question from the other topic: Hello, Is it possible, with the current values provided by MSFS, to calculate the actual altitude the aircraft is flying in? I am currently flying at FL360 and the reported altitude through the regular offsets is way off (37342ft at the moment). Sometimes it's even bigger. I understand that MSFS has a whole different (better) model of the atmosphere, so is there a way to read all the required data to calculate the "correct" altitude we're flying at? I am sorry but this is a very grey area for me, altitude calculations with pressure, temperature and the such make me "dizzy", so any help is appreciated. Thank you!

Hello, Is it possible, with the current values provided by MSFS, to calculate the actual altitude the aircraft is flying in? I am currently flying at FL360 and the reported altitude through the regular offsets is way off (37342ft at the moment). Sometimes it's even bigger. I understand that MSFS has a whole different (better) model of the atmosphere, so is there a way to read all the required data to calculate the "correct" altitude we're flying at? I am sorry but this is a very grey area for me, altitude calculations with pressure, temperature and the such make me "dizzy", so any help is appreciated. Thank you!

Might be a bit late to the party, but currently flying at FL360, STD in the altimeter and reported altitude by my ACARS (through FSUIPC7) is 37440ft. Same altitude on the IVAO map which is reported by the IVAO client, presumably using SimConnect. Latest version of MSFS obviously.

Yeah i only use it to feed my ACARS, i do have a registered copy but i no longer use WideFS and that was the reason why i bought it a long time ago. Anyway thanks a lot for the prompt responses, i'll check what they say in the forums or try to find a solution somewhere, i understand this is a shot in the dark for a (very) unsupported platform, so i don't expect much really 😝

Yes, it is used by the 767 and apparently it controls some features in the aircraft, if it is not loaded, the aircraft will not initialize properly. There is an option in the 767 menus to "only load the DLL with LevelD 767", so it will only activate if the aircraft is selected (apparently), but changing this does nothing. Yeah i did that. I thought it would be better to let FSUIPC set all the hooks before all other addons, tried it last as well, before and after LVLD.dll to no avail. Only works by disabling either LVLD or FSUIPC. Me neither, maybe some changes that were introduced in the latest versions could cause this? I am clueless really, just trying to figure this out. No, but i will post in their forum. If all else fails, i'll just give up on LevelD 767 (let's face it, it's REALLY old and i'm lucky it even flies today in Windows 11). The logs don't show much. A normal log with no crashes is just a clean startup/exit and the one with the crashes is interrupted. Regular log: ********* FSUIPC4, Version 4.977 (24th November 2021) by Pete Dowson ********* Windows 10 Enterprise 64 Bit reported as Build 22000, Release ID: 2009 (OS 10.0) fsx.exe version = 10.0.62615.0 Reading options from "C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.ini" Running inside FSX Steam Edition on Windows 10 Module base=62520000 User Name="" User Addr="" FSUIPC4 not user registered WIDEFS7 not user registered, or expired 0 System time = 27/01/2022 13:02:43 0 FLT path = "D:\Data\Documents\Flight Simulator X Files\" 0 ------ Module Version Check ------ 0 acontain.dll: 10.0.62615.0 0 api.dll: 10.0.62615.0 0 controls.dll: 10.0.62615.0 0 fs-traffic.dll: 10.0.62615.0 0 G3D.dll: 10.0.62615.0 0 language.dll: 10.0.62615.0 0 sim1.dll: 10.0.62615.0 0 visualfx.dll: 10.0.62615.0 0 weather.dll: 10.0.62615.0 0 window.dll: 10.0.62615.0 0 ---------------------------------- 0 Trying to connect to SimConnect 10.0.62615.0 ... 0 ... Okay! Connected! 0 FS path = "C:\Program Files (x86)\Steam\steamapps\common\FSX\" 63 LogOptions=00000000 00000001 63 ------------------------------------------------------------------- 63 ------ Setting the hooks and direct calls into the simulator ------ 63 --- CONTROLS timer memory location obtained ok 63 --- SIM1 Frictions access gained 63 --- FS Controls Table located ok 63 --- Installed Mouse Macro hooks ok. 63 --- Wind smoothing fix is fully installed 63 --- SimConnect intercept for texts and menus option is off 63 --- All links checked okay 63 ------------------------------------------------------------------- 63 SimConnect_Open succeeded: waiting to check version okay 63 Opened separate AI Traffic client okay 641 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0) 641 Initialising SimConnect data requests now 641 FSUIPC Menu entry added 656 D:\Data\Documents\Flight Simulator X Files\Default LPPT Flight.FLT 656 C:\Program Files (x86)\Steam\steamapps\common\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.air 3844 Weather Mode now = Custom 12766 === Closing session: waiting for DLLStop to be called ... 15219 === DLLStop called ... 15219 === Closing external processes we started ... 16219 === About to kill any Lua plug-ins still running ... 17391 === About to kill my timers ... 17391 === Restoring window procs ... 17391 === Unloading libraries ... 17391 === stopping other threads ... 17391 === ... Button scanning ... 17500 === ... Axis scanning ... 17610 === Releasing joystick devices ... 17610 === Freeing macro memory 17610 === Removing any offset overrides 17610 === Clearing any displays left 17610 === NOTE: not calling SimConnect_Close ... 17610 === AI slots deleted! 17610 === Freeing button memory ... 17610 === Closing my Windows ... 17610 === Freeing FS libraries ... 18625 === Closing devices ... 18625 === Closing the Log ... Bye Bye! ... 18625 System time = 27/01/2022 13:03:01 18625 *** FSUIPC log file being closed Minimum frame rate was 32768.0 fps, Maximum was 0.0 fps Minimum available memory recorded was 32768Mb Maximum AI traffic for session was 0 aircraft Memory managed: 4 Allocs, 4 Freed ********* FSUIPC Log file closed *********** Crash log: ********* FSUIPC4, Version 4.977 (24th November 2021) by Pete Dowson ********* Windows 10 Enterprise 64 Bit reported as Build 22000, Release ID: 2009 (OS 10.0) fsx.exe version = 10.0.62615.0 Reading options from "C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.ini" Running inside FSX Steam Edition on Windows 10 Module base=62520000 User Name="" User Addr="" FSUIPC4 not user registered WIDEFS7 not user registered, or expired 0 System time = 27/01/2022 13:03:46 0 FLT path = "D:\Data\Documents\Flight Simulator X Files\" 0 ------ Module Version Check ------ 0 acontain.dll: 10.0.62615.0 0 api.dll: 10.0.62615.0 0 controls.dll: 10.0.62615.0 0 fs-traffic.dll: 10.0.62615.0 0 G3D.dll: 10.0.62615.0 0 language.dll: 10.0.62615.0 0 sim1.dll: 10.0.62615.0 0 visualfx.dll: 10.0.62615.0 0 weather.dll: 10.0.62615.0 0 window.dll: 10.0.62615.0 0 ---------------------------------- 0 Trying to connect to SimConnect 10.0.62615.0 ... 0 ... Okay! Connected! 16 FS path = "C:\Program Files (x86)\Steam\steamapps\common\FSX\" 63 LogOptions=00000000 00000001 63 ------------------------------------------------------------------- 63 ------ Setting the hooks and direct calls into the simulator ------ 63 --- CONTROLS timer memory location obtained ok 63 --- SIM1 Frictions access gained 63 --- FS Controls Table located ok 63 --- Installed Mouse Macro hooks ok. 63 --- Wind smoothing fix is fully installed 63 --- SimConnect intercept for texts and menus option is off 63 --- All links checked okay 63 ------------------------------------------------------------------- 63 SimConnect_Open succeeded: waiting to check version okay 63 Opened separate AI Traffic client okay 641 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0) 641 Initialising SimConnect data requests now 641 FSUIPC Menu entry added 657 D:\Data\Documents\Flight Simulator X Files\Default LPPT Flight.FLT 657 C:\Program Files (x86)\Steam\steamapps\common\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.air 3672 Weather Mode now = Custom EDIT: Also, the crash is just a simple message which doesn't even make it into the windows event log. It will consistently crash after a few (20-30) seconds, no matter what i'm doing (selecting an airport, an aircraft, loading the simulator scenery, simply idling on the startup screen, etc):

Hello, I know we are in an MSFS era or even P3D V5 (i use them both too), but i am a nostalgic person and somehow i missed FSX and all my huge library of addons and decided to reinstall everything and enjoy it for a while. I faced a ton of issues with LVLD.dll and FSUIPC4 (crashes on FSX startup after a few seconds, can reproduce easily), finally managed to solve them by using an older FSUIPC4 DLL (4.9.4.7) up until the third or fourth launch where it decided it couldn't see SimConnect anymore and i had to reinstall FSUIPC again (4.9.7.7), after removing and reinstalling all 4 SimConnects. I don't know if all are required, maybe some older addons connect to a specific version, so... Thing is, the problem once again returned. I can fix it by either disabling LVLD.dll or FSUIPC4.dll in the DLL.XML file, both cannot live together as it is. So, my question is simple: Is there a known compatibility issue between these two DLLs? Should they be loaded in a specific order so that they can work together with no issues? Is there a specific FSUIPC version that will work with LevelD latest version 1.50? This is my DLL.XML file: <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>ObjectFlow.dll</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\Program Files (x86)\Steam\steamapps\common\FSX\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Events</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGEvents.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Options</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGOptions.dll</Path> </Launch.Addon> <Launch.Addon> <Name>PMDG Sounds</Name> <Disabled>False</Disabled> <Path>PMDG\DLLs\PMDGSounds.dll</Path> </Launch.Addon> <Launch.Addon> <Name>SODE Animation Module</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>C:\Program Files (x86)\12bPilot\SODE\SimObjectAnimationModule.dll</Path> </Launch.Addon> <Launch.Addon> <Name>Level-D Simulations</Name> <Disabled>False</Disabled> <Path>Modules\LVLD.dll</Path> </Launch.Addon> <Launch.Addon> <Name>IvAp</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx_bootstrap.dll</Path> <Commandline></Commandline> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> </SimBase.Document> Any help towards solving this (apparent) compatibility issue would be highly appreciated. Reinstalling FSUIPC again will not solve it.

So, after reading Pete's reply, i decided to implement my own method and i got it working. The only way i can think of making this work correctly with FSUIPCClient is if you keep some sort of queue which keeps track of incoming LVARS to read and processing them in different user offsets that can be read and returned. I don't know whether this would work ok over WideFS due to some lag that might exist. So, receive LVAR, process in 0x66c0, read and send response, then next on 0x66c8, read and send response... Once you get out of free space, loop back to 0x66c0, rinse and repeat. The method i'm using is similar to that, creating dynamic offsets and deleting them, i still have to fully test this and see if it's good to go, but it seems ok. Anyway, this has helped me a lot solving my problem, can't thank you enough and @Pete Dowson as well. I guess i'll make a donation for your time, nothing like a fresh pint eh 😛

Thank you both. I read this and will try to do it the old way, see if i can get around it. Cheers, Nuno

Okay, thank you very much for looking into this. If you need any additional information just drop me a line. Cheers! Nuno

I am operating the lights either in the Virtual Cockpit or in a popup 2D panel to make sure i test all possibilities. I just want to read the status, so i am not writing to the simulator. In the sim, everything stays the same, only what i read is changing which kind of makes sense since i'm not writing data. Nuno

Hello again, Unfortunately the outcome is exactly the same... Here is the simple timer implementation, running every 500ms but even at 2s the outcome is the same. private void FSTimer_Tick(object sender, EventArgs e) { UIPCQuery.UIPCProcess("LightData"); rbLanding.Checked = UIPCQuery.LandingLights(); rbNav.Checked = UIPCQuery.NavLights(); rbBeacon.Checked = UIPCQuery.BeaconLights(); rbStrobe.Checked = UIPCQuery.StrobeLights(); rbTaxi.Checked = UIPCQuery.TaxiLights(); } Each of the called methods is similar to this. This one is testing specific hardcoded FlightSimLabs and TFDI models for landing lights. public static bool LandingLights() { double fsLabsLLLeft = FSUIPCConnection.ReadLVar("L:VC_OVHD_EXTLT_Land_L_Switch"); double fsLabsLLRight = FSUIPCConnection.ReadLVar("L:VC_OVHD_EXTLT_Land_R_Switch"); double tfdiLLLeft = FSUIPCConnection.ReadLVar("L:B717_ovhd_lights_ldgltl"); double tfdiLLRight = FSUIPCConnection.ReadLVar("L:B717_ovhd_lights_ldgltr"); return fsLabsLLLeft > 10 && fsLabsLLRight > 10; } In the simulator PC, everything is working perfectly, each switch operates the respective light and it shows correctly on screen. Using WideFS, a single switch (which seems to be the LAST in the sequence, in this case taxi lights - UNCONFIRMED) operates all others and changes all others state as well: - I switch landing lights to ON, beacon to ON and then operate taxi and change it to OFF and all others turn OFF as well. If i switch it ON, all others switch to ON as well. If you believe a video would help i can make a short video of what's happening. Thank you

Hey jwillyf, remove your key from the forum right now. Never post your keys in forums, many people can see it and use them for their own. Hurry! @jwillyf @Pete Dowson

Thank you Paul, I am also calling your method from within an async task so it doesn't lock the main thread AND inside an open FSUIPC connection. I don't know if that affects anything. Let me try to put the relevant parts of the code here... So, this is the timer: private void FlightTimer_Tick(object sender, EventArgs e) { TimeSpan time = stopwatch.Elapsed; LogClock.Text = string.Format("{0:00}:{1:00}:{2:00}", time.Hours, time.Minutes, time.Seconds); if (!ProcessAcarsData.IsBusy) ProcessAcarsData.RunWorkerAsync(); } This is the task. What it does is simply call the UIPCProcess method below, which is in a helper class for separation: private void ProcessAcarsData_DoWork(object sender, System.ComponentModel.DoWorkEventArgs e) { try { UIPCQuery.UIPCProcess(Resources.UIPCAcarsData); } catch (FSUIPCException) { e.Cancel = true; } } public static void UIPCProcess(string processname) { FSUIPCConnection.Process(processname); } And the work completed method where the checklights function is called, making use of the readLVARS method from your DLL. There is an active FSUIPCConnection at this point. private void ProcessAcarsData_RunWorkerCompleted(object sender, System.ComponentModel.RunWorkerCompletedEventArgs e) { if (e.Error == null && !e.Cancelled) { *** Some other things are done here which were removed for clarity, then i check for the lights here: CheckLights(); } *** Some other checks here, removed for clarity } else { FlightTimer.Enabled = false; OpenFSUIPCTimer.Enabled = true; ProcessFSUIPCError(e.Error == null ? Resources.errorSimCommunication : e.Error.ToString()); } } I don't know if this helps trying to figure out what's going on here, if no ideas come up i guess i'll write a new and clean small piece of code just to test read all the data i need to see if everything is working the way it should.