Ray Proudfoot

Thanks John, works a treat as shown with the aircraft parked at Honolulu - 10 hours behind GMT/UT.

Hi John, That's very kind of you thanks.

Hi John / Pete, In the FSUIPC Offsets PDF there is an entry for Zulu Day of Week. Reading this value and together with other offsets and a bit of code I can display Mon, Tue, Wed etc in a LUA display on a wideFS PC. I find this helpful when checking Ai timetables as I can see the local time and date in FS. See attached image. However, the Zulu Day Of Week value has no corresponding Local Day of Week value. So, for example if I'm located in Hawaii or New Zealand at certain UK times the Zulu Day of Week value is for the wrong day. It shows my day of week rather than the local day of week. I appreciate if there's no value in P3D you can't extract it. But is there any way it can be coded in LUA to show the correct day of week?

I would have to learn a whole new system John. It might appear clunky but it works. I tried right-clicking on the separate door lights on the overhead hoping it would make them move. No chance. The CDU system seems the only way in combination with GIT to get the LED on my T8 panel to light up.

John, I have to say FSUIPC is very impressive to run this code so precisely. When you consider it’s navigating its way through the CDU menu it does it extremely quickly. It just needs the user to get things right. 😃

The opening sequence was fine. Just the closing. 😀

Problem identified and solved. I didn't tell you the full picture. I also use GoFlight Interface Tool so I can get the LEDs to illuminate and extinguish depending on the door state. I had already programmed front Left and front Right into GIT and was repeating the action via my code above. So front left and right were being operated twice - hence the problem. I've removed the offending lines and now the code works flawlessly. Thanks all for your suggestions. 👍

I may have a solution. Looking through the events these are listed... // Custom shortcut special events #define EVT_LDG_LIGHTS_TOGGLE (THIRD_PARTY_EVENT_ID_MIN + 14000) #define EVT_TURNOFF_LIGHTS_TOGGLE (THIRD_PARTY_EVENT_ID_MIN + 14001) #define EVT_COCKPIT_LIGHTS_TOGGLE (THIRD_PARTY_EVENT_ID_MIN + 14002) #define EVT_COCKPIT_LIGHTS_ON (THIRD_PARTY_EVENT_ID_MIN + 14003) #define EVT_COCKPIT_LIGHTS_OFF (THIRD_PARTY_EVENT_ID_MIN + 14004) #define EVT_DOOR_FWD_L (THIRD_PARTY_EVENT_ID_MIN + 14005) #define EVT_DOOR_FWD_R (THIRD_PARTY_EVENT_ID_MIN + 14006) #define EVT_DOOR_AFT_L (THIRD_PARTY_EVENT_ID_MIN + 14007) #define EVT_DOOR_AFT_R (THIRD_PARTY_EVENT_ID_MIN + 14008) #define EVT_DOOR_OVERWING_EXIT_L (THIRD_PARTY_EVENT_ID_MIN + 14009) #define EVT_DOOR_OVERWING_EXIT_R (THIRD_PARTY_EVENT_ID_MIN + 14010) #define EVT_DOOR_CARGO_FWD (THIRD_PARTY_EVENT_ID_MIN + 14013) // note number skip to match eDoors enum #define EVT_DOOR_CARGO_AFT So rather than program events to navigate through the CDU these may be the solution. More later...

Yes, it’s LSK5L from memory to move up one level in the CDU menu. The top level is two levels up. I’ll try the logging option and see if it reveals anything.

Luke, I have no experience with LVARS. Given the completeness of the PMDG SDK you would expect all this to work. I’ll check with them if there’s a direct command for the doors operation. The commands beginning with P are the on switch action and U the off switch action. They’re identical for each switch.

Hi John / Pete, P3Dv5.2HF1 with the PMDG737 NGXu and FSUIPC6 v6.1.0.2. There was an excellent tutorial posted here a few years ago that showed how to program actions for the PMDG737 using GoFlight hardware. I used it back then for the 737NGX and have copied / pasted it for the 737NGXu as the SDK is identical for these purposes. One multiple action is to open and close Pax doors (left forward and aft) and the other is for cargo (forward and aft). So 2 doors for each of 2 switches. Whilst the opening sequence always works more often than not the closing one doesn't with one door on each sequence remaining open. I've reexamined the instructions but cannot see a problem. The sequence is shown on the attached jpg. Any help would be appreciated for this frustrating problem. The sequence starts by selecting the MENU option on the CDU and navigating to the Doors menu. After actioning the doors the menu actions take the user back to the top level of the CDU so each sequence starts at the same point.

ShowMultilineWindow=No SuppressSingleline=No SuppressMultilineFS=Yes Has fixed the problem. 👍 No need to delve into very old code. Thanks!

Hi Pete, Happy to do the test you suggest. I’ll report back later today. Thanks for checking this.

Pete, don't spent much time on this. It's soon sorted but it would be nice if it didn't appear at all. Shouldn't SuppressMultilineFS=Yes prevent the RC window from showing? The options in FSUIPC don't make any reference to SimConnect and like most, I'm not an expert on how these things are controlled.

Hi Pete, I use ShowText on a WideFS PC for Radar Contact. Have done for years. No extra space on that monitor for another lua script window I'm afraid. This seems to be a long-standing issue. I had the same in v4 but just lived with it. It's not a major issue but it just seems that if I select the option not to show a multiline SimConnect window for RC it should work.