IanAbel

Chad, not sure if you're involved in the tracking tool you use/in question, but you may want to pass this on to whomever is; I'm the author of the BAVirtual ACARS program, in the past with several platforms/developer aircraft parking brake and other items have become "questionably reported". To that end I have for a while now adopted the following for start/end of flight recognition; Start - Either, parking brake state, OR ground speed non-zero, OR an engine start End - zero ground speed and engines off. BAVirtual ACARS works fine with the MSFS/FBW as a result of this, in spite of such issues. Hope this helps.

Paul, Question regarding the helper classes, is there any indication available that the data is unavailable if the appropriate "EnableDataBroadcast" is not set in the _options.ini file for the aircraft? Just wondering what is returned if that's not set.

Sorry Pete, my mistake. I don't own the NGXu so asked one of the BAVirtual members to send the header file. He supposedly sent the one in the SDK folder from PMDG.

Paul, Thanks so much for adding the Helper classes, just what I'm looking for in fact, and I'd not noticed them or the update you pushed, have it now, thanks. One question/comment/what-have-you, one of the things I've been struggling with is that the offsets are different between the earlier 737NGX and the 737NGXu. Would it be possible to create/add the NGXu helper class also? I've attached the NGXu header file in case you don't have it available... Ian. PMDG_NG3_SDK.h

Sorry. I didn't think to check the FSUIPC7 doc, haven't looked at it since it went from beta to final, my apologies 😞

John, Just added the various wx components to my ACARS tool, and it appears the Dew Point 0E8E is being returned as ZERO from MSFS. Returned OK in FSX and P3D. Any idea if this is something not being provided or is it missed along the way between MSFS/FSUIPC?

Paul/John, just want to offer my remarks on the pricing... I've ALWAYS thought the pricing is actually insane! Pay once, get improvements/updates for ever - MADNESS I SAY?!?!?! You have always provided such excellent and highly responsive support for the product(s) over the years and it is an absolute necessity for most serious simmers. Having to simply pay once for each platform version - and with discounts for newer platforms into the bargain - I think you are one of the best and truly most important, add-ons we have. I'm off to purchase the MSFS version, having been beta testing as soon as it was available, even though I personally won't use it much myself for a long while. I maintain/buy/support all the versions of FSUIPC as I am responsible for the BAVirtual ACARS tool, and even though mostly MSFS isn't quite ready for prime-time virtual airline flying, I have to be sure the ACARS tool works for the members that use it. It does and for that I'm grateful. Seems such a small price ANYWAY for something that improves the sim experience so much. Keep up the amazing work and kudos to you both for being so on top of this new product even with its almost non-existant and fluid SDK.

Seems like the pause is working correctly now, I'm not seeing the In Menu flag setting though. Both P the ESC result in 6 returned, then each are cleared down correctly. Example: hit ESC get the "4" value, but then opening any menu such as General/Assistance/Controls etc, doesn't seem to change the x3365 value... remains at zero.

John, funny, that's what I thought!! I was SURE I'd got it all working as "expect" and was just doing a final test yesterday before a release of my ACARS when I discovered the problem. I'm betting on the last update 1.9.3.0 broke it

To add to the discussion/nightmare 😮 I'm also "trying" to determine the PAUSE states offset x264 (given the Active Pause can't be detected) and discovered the following, not sure if it's with FSUIPC or an Asobo problem, I'm guessing the latter; Using the "P" keyboard pause, the value returned is 2 and this clears down to 0 when the Ctrl-"P" is seen. You get a "pause" and "un-pause" as expected. Using the ESC-style pause, heading to the menus, the value returned is 4 and this clears down to 0 when the second ESC is seen. You get a "pause" and "un-pause" as expected. So far, so good... If you - in EITHER ORDER - use the "P" to pause and THEN use ESC to head to the menus, the value returned is 6, all well and good, HOWEVER, reversing either pause state in either order NEVER changes the value to 0 it remains at 6 "forever", until you return to the main menu and restart a flight. You do get a "pause"/"un-pause" in the sim but the value is stuck! Tried in both the C170 and A320... This is also for an ACARS-style program "BAVACARS", attempting to recognize pauses in flight, which we time-limit. For now I'm using a position vs. speed, poor second choice method, to determine it, but at least THAT does handle the "Active Pause" into the bargain. Not sure if this helps, if it's an FSUIPC issue or needs to pass to Asobo...

I've a 15,000+ line vb.net project (ACARS) that I'm converting to C# and it's helping immensely.

It may be worth checking out https://converter.telerik.com/ which is a rather useful C# -> VB.Net and the reverse converter. It can quickly show you the structure of something you already have such as the examples you may be looking at.

Pete, No, I wasn't involved at all pre-release, this is a "simple" gamepass new install once released!

I wonder if that relates to/is an issue with the Steam version? I've got the gamepass version, installed in a custom folder and the path; K:\MSFS\Official\OneStore\asobo-aircraft-c172sp-as1000\SimObjects\Airplanes\Asobo_C172sp_AS1000 contains an aircraft.cfg file! Seems there's a lot that's not "standardized" in MSFS <sigh>

Pete, After a little searching it is still there, but now contained in the engines.cfg file For what it's worth, here's the default A320 section; [GENERALENGINEDATA] engine_type = 1 ; 0=Piston, 1=Jet, 2=None, 3=Helo-Turbine, 4=Rocket, 5=Turboprop fuel_flow_scalar = 1 ; Fuel flow scalar min_throttle_limit = -0.2 ; Minimum percent throttle. Generally negative for turbine reverser master_ignition_switch = 0 starter_type = 2 ; 0=Electric, 1=Manual, 2=Bleed Air max_contrail_temperature = -39.724 Engine.0 = -6, -19.2, -4 ThrustAnglesPitchHeading.0 = 0, 0 Engine.1 = -6, 19.2, -4 ThrustAnglesPitchHeading.1 = 0, 0

The A320Neo. Using an add-on livery though I doubt that matters. I can check it again, but I record the weight and fuel along with several other parameters frequently in my BAV Acars program, and another tester also reported the same thing.

Those would all be really helpful - thanks in advance if they're able to be provided 🙂

Just an FYI - looks like this offset isn't updated after its initial value? Asobo issue?

Download the latest version links at top fo the Announcement page, it's included in there...

Read the "README.txt" that comes with FSUIPC7... Under Missing Functionality "2. lVar access: pending facilities to be provided (if lVars still exist!)"

John, thanks for the info/update. Pity about the path, hopefully/possibly they will set a registry entry in future... Not sure if it's because I'm using the FSUIPCClient.dll, but the first call to open the connection shows the following data in 0x3124 = 0 and 0x3308 = 13 I'm assuming the latter is because it's hard coded since FSUIPC7 is explicitly for MSFS. The 0x3124 offset does correctly change from 0 to 110 (currently) after the sim is started.

Slightly off-topic, but do you know of any registry entry that can be used to identify the location (and presence) of MSFS? Was easy with FSX and P3D, but I'm blessed if I can see anything in the way of an entry for MSFS... Also, since FSUIPC7 now runs as an app, is there any offset that can be used to determine that MSFS is actually running? Never a problem before, of course, if I couldn't connect to FSUIPC I knew it wasn't! Befuddled in Minnesota 🙂

Paul, sorry probably my problem, I was running FSUIPC7 as admin. Getting a response now. Thanks.

Paul, Not sure whether to post here or on the FSUIPC forum. Have MSFS installed, FSUIPC7 and the correct simconnect (from the MSFS SDK install) all loaded, FSUIPC log shows a connection to the sim. My application (which works fine with FSX, P3Dv4/5 and XP11 via XPUIPC) has the latest FSUIPCClient.dll installed 3.1.19-beta I get a #12 error from the FSUIPCConnection.Open() call. Says can't connect to FSUIPC...

John/Pete, Hopefully a couple of "simple" question. Will v7 be available/used for P3Dv4/v5 as an update as well as MSFS or will it be specific to the MSFS platform? What will the value(s) of offset 3308 (FS Version) and 3124 (Specific Version) be for the new sim? Just trying to get a bit of a head start for my BA Virtual ACARS tool 🙂 Thanks...