jordanal

Ah ha! Muddy waters to the rescue! Wasn't that a band? Thanks Bryan, and my apologies for distracting you during your final update checks. Now please, get back to work!

Ah, that could explain it - the word "on" was never required in previous versions. Nuance difference like this between versions drive me insane. I will give it go this weekend. Yup, I'm sure as SOP2 is all I have ever used. To clarify however, it's only the fixed landing lights (two right switches) that are always turned on at 18k feet, regardless of the 10k setting in the FS2Crew options.

Hi Bryan, Having just read about the status of the upcoming update to Reboot with Emergencey (cool), I was reminded of a few recent repeatable observations I hope you might be able to check and/or fix before the update is released. The following two phrases used to work flawless for me prior to Reboot. This using the latest available version of reboot and all other Reboot functions and phrases operate normally. Perhaps these are already in the update - not sure... Using SOP2: Landing lights at 10k decent are ignored - still toggled at 18k. Using SOP2 (The phrases are completely inop) Set Course my side xxx Set Course your side xxx Thanks and regards,

PERFECT! Many thanks, Larry! Now I have the PMDG-77x working on P3Dv3.1 with IS KATL 2016 with SODE 1.3.

Good to know, Bryan. Glad I could help!

That's what I mean, he's not doing it before taxi and I'm completing all the checklists on every flight. He doesn't touch the transponder knob until the 'entry procrdure'.

Hi Bryan, I've recently noticed that my transponder is no longer being set to 'TA' during taxi. I've triple-checked this over the past five flights or so, making sure the briefing has ASDEX set to yes. It also doesn't seem to make a difference if the "Use TARA" option is set to yes or no. The transponder is still turned on/TARA when doing the before-entry-procedure. This is using v1.7 with the latest T7 version. All other FS2Crew functions seem to be fully operational. Thanks for your thoughts... Edit: I should probably add, this using Prepar3D v3.1 on Win10x64Pro.

Great job guys and I'm impressed you stopped production to retro a past product. Happy New Year to you and your families, as well!

Thanks Nick, that does sound interesting indeed.

I wouldn't run any FSP failures alongside a PMDG or any other advanced aircraft. I hope FSP allows failures to be completely disabled (haven't read-up on it, yet), which would be a major improvement. In the past, FSP was notorious for causing a 'blown-tire' event on the NGX even with very smooth landings, and there was absolutely no way to disable it; search for the issue on their forums, it went on for many months. It was the number one reason I stopped using the FSP add-on. What's worse, the developer (Dan) absolutely refused to address or even acknowledge any issues. Now he shows backup trying to pump out a version just before Christmas. I almost always give FS developers the benefit of the doubt, but I will be very cautious with this program before it sees one more penny from me.

FWIW, after setting ProATCx to run in Win7 compatibility mode on my FS-client, all my ProATCx crashes seemed to cease; using the latest version 1.7.x. P3Dv3 and the FS-client are running on Win-10 Pro PC's.

Hey Bryan, FYI, MJC8 1.017RC2 with formal P3Dv3 support was posted last night. http://majesticsoftware.com/forums/discussion/2066/mjc8q400-version-1-017rc2#Item_1

If your running the NaviGraph AIRAC Install Manager, compared all the other titles it can install, the PMDG install-path is unusual in that you must chose the root of the flightsim directory (set it to manual or use the 'scan' feature). The Install Manager will automatically find the PMDG and Navdata subfolders when you install and AIRAC. For example, the install-path in the GUI for PMDG should read D:\FSX or D:\P3D. They did this to accommodate all previous possible locations of the PMDG Navdata folder over the years.

Aha, No wonder :excl: LOL... Thanks Bryan - the latest version of the Dash8 installs and starts in P3Dv3 without issue. MJC is waiting on a P3D patch to fix a couple of aircraft bugs. http://majesticsoftware.com/forums/discussion/2028/mjc8q400-pilot-edition-under-prepar3d-v3-0#Item_1 Question - when does the panel.cfg get modified by FS2Crew; during the install or when you enable it? If the later, then it should still be unmodified, correct? Guess I'll go back to installing more scenery for now - let me know if you need a install-beta-tester. :wink:

Hi all, I've been rebuilding my flghtsim rig with P3Dv3. I've successfully installed the latest MJC8 v1.017RC1 and FS2Crew Voice v1.3. As shown in the screen capture, when I attempt to enable FS2crew, I get a FS2Crew error stating the Prepar3D.exe is not correctly registered, then quits. I was sure to chose the 'P3D v2+' option during the install. The latest FS2Crew voice with the PMDG 737 and 777 do not exhibit this behavior (works as expected) in P3Dv3. Thanks for any assistance you can provide.