StefanA

Second solved! Lights problems I'm discussing with PMDG since at least last year here and by e-mail. Can't imagine that it didn't get added. Please advice how to put it into the queue. It's really annoying and it's really easy to solve. Just look at the lines above, which were definitely in the old version one of the B747. It's missing in B737 and new B747, probably it's missing in the B747-8 too.

Hello together, unfortunately there's still no information in the change logs, that this really small issue has been solved now. You did so much fixes now, so why is it such difficult to add some small lines to two panel switches? The workaround is awful and it would be such easy to fix this. Regards, Stefan Additional information OFF-Topic: The update with operation center only worked for the B737, it didn't work for the B747.

Thank's for the hint. I was at this site, but I didn't see the register button at once. So I followed from the support to the forum instead. Now I found it. You are right, I'll open a ticket there and I agree that the description should help others to understand why they get the penalties.

First, thank you for support. It was my intention to "overload" the built-in command with the additional key stroke. Unfortunately this doesn't work. Perhaps you can add this as option (Built-In, Both, Substitute original by VOXKEY command). Best would be to attach the keystroke it to the switch (FSUIPC?). In every case the switch is moved, it will work as wanted, by command to the FO as well as by doing it self. I'll check out how to deal with it. Yes, PF3 runs on same machine. It's a really high end machine with second screen for external addons (ASE, PFPX/FSC9, PF3, MCE) and I don't want to run two machines for the simulation. Very good that you are reading the PF3 settings, that makes sense and is the best solution in that case. Yes I'm aware about changing the checklists and the "flows". I already started to change the Level-D checklist. I only wanted to inform about that for discussion to include it into initial settings for sharing it with all other users too. But it's a good idea with the documents folder, because I experienced that the original was overwritten by installing your last patch. Doesn't matter, because it was only a small change and when I completed all settings, there will be a big backup of all and an additional backup of all required cfg, ini, xml and other settings files. I'll check the MCE/PF3 combination again soon. Hopefully it works, because that would be a big improvement for realistic procedures and ATC. Regards, Stefan

Hello together, it was discussed several times, but I couldn't find an appropriate solution and a deep analysis I didn't find as well. Disabling the penalty isn't really what I want. That's because I'm using FSPassengers, it's to be forced to proceed with the realistic procedures. For investigation I logged all events with FSUIPC and found following: B737: Beacon -> TOGGLE_BEACON_LIGHTS event appears, which is absolutely right. Basically it works with PMDG addon aircraft. NAV (Steady) - Off - NAV + Strobe (Strobe & Steady) -> in every case there's a TOGGLE_NAV_LIGHTS. What is missing is STROBES_TOGGLE. Best solution to have correct state in every case would be sending following events: Steady: TOGGLE_NAV_LIGHTS + STROBES_OFF OFF: TOGGLE_NAV_LIGHTS + STROBES_OFF Strobe & Steady: TOGGLE_NAV_LIGHTS + STROBES_ON B747 V2: Beacon every change (OFF, Lower, Both) -> TOGGLE_BEACON_LIGHTS -> correct NAV -> TOGGLE_NAV_LIGHTS -> correct Strobes -> STROBE_TOGGLE not appearing -> reason for problems with 3rd party like FSPassengers detecting this state. B747 V1: Beacon every change (OFF, Both) -> TOGGLE_BEACON_LIGHTS -> correct NAV -> TOGGLE_NAV_LIGHTS -> correct Strobes -> STROBES_SET -> that's correct too because it's similar to STROBES_TOGGLE It's really only a couple of additional code lines to be added. Would appreciate if there will be a PATCH for the B747-V2 and the B737NGX to correct this small issue causing problems with 3rd party addons detecting these variables. Regards, Stefan

The first problem I had too. It seems that it's because of special PMDG handling with the strobes. You have to use the FSX standard key command "o" additional when setting the switch to strobe+steady or wise versa. Unfortunately you don't see if it is on or off after pushing "o". You need to know it from defined state. Level-D works with switches only, I assume they set the right values (FSX variables read by FSP) and PMDG isn't using the FSX variables for that. One possible reason may be, that PMDG has a tri-state button (original B737) and not the on/off used by FSX standard airplanes. But would be interesting if there's a better solution for example with FSUIPC or a fix by PMDG. Second problem. It's similar. The seatbelt switch for the PMDG as well as for the Level-D doesn't control the FSP seatbelt setting. So I use the switch and additionally "SHIFT <" (better to find than original setting). Too it would be nice to have a better solution. Regards, Stefan

Hello together, I've some trouble to get everything to work. I tried to add some VoxKey commands: FSPASSENGERS seatbelt signs ("SHIFT <"): command "seatbelts on" TRIGGER "SHIFT <" FSPASSENGERS seatbelt signs ("SHIFT <"): command "seatbelts off" TRIGGER "SHIFT <" (Would be nice to set seatbelt signs with one command for the aircraft and the FS-Passengers) PF3 FO flying the plane ("SHIFT+CTRL V"): command "your control" TRIGGER "SHIFT+CTRL V" three times! (Especially interesting for long haul flights across North Atlantic) PF3 FO off ("SHIFT+CTRL V"): command "my control" TRIGGER "SHIFT CTRL V" once. PF3 Emergency ("SHIFT+CTRL E"): command "mayday mayday mayday" TRIGGER "SHIFT+CTRL E" Even after restarting MCE it didn't take care about it. And there's only one command file in documents folder assigned to FSX. There are some keyboard conflicts with FSPASSENGERS in combination with PF3. In PF3 I can reassign the key settings. But is that recognized by MCE or where can it be set there. For example the EMERGENCY is "SHIFT+CTRL E". That's the FS-Passenger command for opening the flight report. FO announcements vor V1, rotate, V2: I switched off the FSPassenger callouts and the Level-D FO to have only one FO voice. Only one part is a little disturbing. The "minimum" call is done twice. First from GPWS (airliner) and second from MCE-FO. Is it possible to turn that on/off (small aircraft on, airliner off)? Level-D FO is silent too. Sometimes the ATC calls aren't transferred to PFS, there's no red text line in that case, which I still have activated during setting up all. After repeating several times it works. But that needs too much time to answer ATC instructions. So it happened that I couldn't answer before next handover. Level-D B767: the autobreak isn't set as expected. Autobreak 1, 2, 3, 4 (max) works fine. But "autobreak off" selects RTO or "disarm" depending on current state. From RTO it switches to "disarm" and from "disarm" after landing it is switched to RTO. Small issue which can be corrected very easy by everyone self: The preflight checklist contains "beacon on". In that case your ground team would stop working and leave because of expecting the engines starting soon. That's an item for the "before start" checklist. The NAV lights have to be set in preflight checklist. One (off-)topic which should better be answered by PF3 developer, but I didn't get an answer. So I just put it in that common package for MCE/PF3/FSP. What about transponder penalty in FS-Passengers with PF3 assigned code? Has anybody tried that? Regards.

Repeating only the numbers didn't help. I was successful with this: "Disregard" "Set heading 250" EDIT: your described solution works too (only the corrected value "250"). Second attempt was successful. /EDIT Thanks, seems to work without freeze now. Unfortunately I've a lot of trouble together with keyboard conflicts and PF3 for example. Will start a new topic for that. Regards, Stefan

Hello, I'm sorry but it didn't really help with version 2.7.10. Only one misunderstanding and the FO isn't working any longer. For example "Set heading 250" was recognized as "Set heading 550" with request to confirm. Correcting by repeating "Set heading 250" will be displayed as "Set heading 250" but no additional actions will be taken. The heading selector isn't changed and there's a complete freeze. Only the instructions are still confirmed by text response. Hope this helps. Just try to give a command like "Set heading 550" to check what happens in the code of MCE. EDIT: Additional remark: Can reproduce it by saying "Set heading 550". Regards, Stefan

I recognize exactly the same. After asking to confirm it's required to restart because of MCE freeze. Same version using during a Level-D B767 flight with PF3.