smoothchat

Sorry if this has been asked before, but if I purchase now (discounted), will I get the Summer update for free when it's released, or should I wait?

Sure. No Probs. FYI, according to SPAD, they're all the same as NGXu (NG3), but of course, we want the official word from PMDG. Many of us have already set up all our hardware with it. Cheers.

I think they are PMDG 737 NGXu Offsets.

Thanks John. I guess that script won't work until FSUIPC7 can see the new 737 Vars. That video shows that it's no trade secret that SPAD alpha supports the new 737 using the same basic names. I'm happy to test for you. Cheers

I have discovered FreeFD virtual instrument displays. It will work as a solution until the PMDG 737 supports PopOut windows. The software is quite old and expects classic FSX offsets for some display items. Is there some way that FSUIPC7 can grab a PMDGNG3 variable value and push it into an another variable / offset so the client doesn't know the difference? I have had some success with SPAD, but many variables won't pass the value on to the app. It needs to come from FSUIPC7. If it could internaly provide a "conversion", that would solve many problems getting the Home Cockpit working with new planes that use their own vars. Would LVARS to OFFSETS do it for me? It wouldn't be a new offset , but an existing one. I would use the list of FSX offsets to find the ones I need to write to and need some examples of the entries required as this is new to me. My first task is to tackle the Autothrottle speed target as displayed above the left tape in IEDI. It works with the stock 747 in MSFS but not the PMDG737 so I need to grab the PMDG value and push it into the offset that the App will see. Any tools , docs or examples to help me would be greatly appreciated. EDIT: It looks like the PMDG 737 broadcasts the Airspeed hold via PMDGNG3:Glareshield.Mode.control panel.IASMach and I would have to push that into offset 07DC or 07E2. Not sure if FSUIPC can see the PMDGNG3 vars yet. 😁

Ah thank you

30031 *** LUA Error: ...x86)\FSUIPC7\linda/aircrafts/PMDG 737NGX/actions.lua:157: attempt to call global 'GSX_door_automation' (a nil value) Perhaps it is seeing my MSFS PMDG 737. Is this a Linda problem ? Should I just delete that folder? Edit: I just deleted the folders. PMDG 737NGX is P3D plane. I wish I could delete this post.

Thanks John. Lots of very good info. Thanks. FYI: I found this site that has a very good graphical reference for the a32nx .. https://docs.flybywiresim.com/pilots-corner/a32nx-briefing/flight-deck/ Cheers and thanks for a great product. So many of us would have $$$ worth of hardware sitting useless without FSUIPC

Does anyone know of any collection of graphical illustrations to help identify instrument switch and annunciator offsets? Looking through huge lists to find a switch offset for hardware or for an aircraft panel seems like a very long winded way to do it. Like many people, I'll be focusing on getting my aging devices working with MSFS and planes like the a32nx and PMDG737 My first challenge will be the VRInsight 737 Overhead Panel. An upcoming update to SPAD.next will take care of the hardware end, but as for identifying every switch and annunciator of the aircraft overhead, if someone has already created a graphical reference, the job would be much easier. If not, I'll create one and post to help others in the future.

I can consistently cause P3Dv3 to lock up by moving and releasing the main window a few times. It only occurs when something has attached to FSUIPC (like SPAD), hence my reason for raising it here in case someone else has come across this as well. Disabling FSUIPC in the dll.xml solves the issue. Only occurs in P3Dv3. I have not been able to replicate it in P3Dv2.5 similarly configured. I will contact LM, but thought I should give a heads up as it involves FSUIPC connectivity. Nothing special in the logs. Everything just freezes.