alex

Bryan, while you're focusing on the upcoming FS2crew version for the Airbus Pro, will you include a choice of beverages interaction with the flight crew? I hate coffee - have the flight attendant convince me it's coca cola, or hot chocolate with lactose-free milk, please ; ). (I'm just kidding). Cheers, looking forward to the FS2Crew version.

After reading about this issue and having already updated the P3D client, I decided to go for all or nothing and load a saved scenario with the 747 (parked at Hilo). I have my P3D starting up with a default scenario using the extra but I didn't load it before loading the 747. And I did experience the black screen. No sound, no response. But after a few seconds I noticed the p3d menu was still active. And then everything returned and the 747 virtual cockpit was back. And smoother than ever. I'm in the middle of a flight now and no more issues so far. On the contrary, I'd been using oculus rift with the 747 for taxi, takeoff and approach and landing and it wasn't a fluid experience (to put it mildly), specially given I am using a bellow specs video card. But I endured due to the spectacularity of the experience. But if this first flight is any indication, P3D and the 747 in virtual reality is now smoother than ever! Edit: I did notice this small issue: using single pass stereo view, the logo light was visible only through the left eye. The right eye displayed the logo light only from certain positions. This issue wasn't limited to PMDG 747, I also saw this happen to an AI taxi light.

I can confirm that copying the t2g2.dds and t2g2lm.dds files from FSX/texture folder to P3dv4/texture folder solves the black autogen buildings issue in MMMX. Thanks for those that helped me out with this.

I'd like to restate effeme's request. IT appears that without the original scenery's afcad it won't display properly in v4. If anyone could post it I'd be grateful as well. Edit: I found an updated AFCAD file here: https://flightx.net/index.php?thread/84019-skyhighsim-lybe-afcad/#post986603 Now all the addon buildings and jetways show. But I still have default buildings and ramp showing up and don't know what file could be the culprit, I've searched for and disabled all *lybe*.bgl I could find.

Does anyone know if there any chance of CLS 747-200 having a second life in P3d v4? How come I can't find even questions about this anywhere? I like to fly my study level Pmdg cargo 744 but once in a while I'd love to hop onto the flite 742, cargo version, for a change.

Keven, The axis are working now! :) But the X axis is reversed for me. In order to move left and right I had to reverse the axis in the chaseplane assignment window because the left selection makes the POV move right and viceversa. Not sure if it's an issue on my side or yours, though. Edit: Found out that in outside mode I am now unable to pan left or right or up or down but instead I move in those directions around the aircraft. In the cockpit assignments work as expected. DISREGARD - I had the "track the aircraft" option on! :)

For some reason it didn't work for me. I had to go around the issue by assigning buttons to replace those axis. But thanks for your suggestion.

Same problem! Chaseplane was updated today and my playstation controller has lost X/Y axis (which I used to move forward/backward and sideways). Something happened here. EDIT In Chaseplane, I tried to reassign the axis to their previous functions. Chaseplane recognizes the axis when I move them in the assign window, even though they don't function afterwards.

Thank you, Vic. This solved my two shader file problems. Uninstalled client. Rebooted. Reinstalled client. Rebooted. Ran P3D. Exited. Ran PTA. No red error messages this time.

Hi! Not sure if I should post this issue here - I installed the 2.6 version and I keep having these reports: ERROR: shader file G:\P3Dv4\ShadersHLSL\Cloud.fx is not original Prepar3D shader and can't be used ERROR: shader file G:\P3Dv4\ShadersHLSL\General.fx is not original Prepar3D shader and can't be used I've unninstalled P3D's v4.1 content and reinstalled it twice with no results. Also tried reinstalling the client module. Should I be installing the scenery module? Thank you : ) Rui

With Bryan's fantastic support it was possible to work around this issue and I now have FS2Crew working in my QOTSII. If I ever discover what is keeping my manager from starting I'll post it here.

Bryan, this is the stack list from the configurator failing taken with process explorer. Perhaps this can provide a clue to you: ntoskrnl.exe!memset+0x61a ntoskrnl.exe!KeWaitForMultipleObjects+0xd52 ntoskrnl.exe!KeWaitForMutexObject+0x19f ntoskrnl.exe!PoStartNextPowerIrp+0xba4 ntoskrnl.exe!PoStartNextPowerIrp+0x1821 ntoskrnl.exe!KeWaitForMultipleObjects+0xf5d ntoskrnl.exe!KeWaitForMutexObject+0x19f ntoskrnl.exe!NtWaitForSingleObject+0xde ntoskrnl.exe!KeSynchronizeExecution+0x3a23 ntdll.dll!NtWaitForSingleObject+0xa KERNELBASE.dll!WaitForSingleObjectEx+0x9c mscorwks.dll!ClrCreateManagedInstance+0x5c29 mscorwks.dll!ClrCreateManagedInstance+0x5e1e mscorwks.dll!CopyPDBs+0x1dcf8 mscorwks.dll!PreBindAssembly+0x7eaef mscorwks.dll!CorDllMain+0xa857 mscorwks.dll!CorLaunchApplication+0x1ac7b mscorwks.dll!CorLaunchApplication+0x1cc69 KERNEL32.dll!UnhandledExceptionFilter+0x160 ntdll.dll!EtwEventSetInformation+0x1d74 ntdll.dll!_C_specific_handler+0x9c ntdll.dll!RtlDecodePointer+0xad ntdll.dll!RtlUnwindEx+0xbbf ntdll.dll!RtlRaiseException+0x248 KERNELBASE.dll!RaiseException+0x3d mscorwks.dll!CreateApplicationContext+0x2d813 mscorwks.dll!Ordinal24+0xb927 mscorwks.dll!Ordinal24+0xdaf6 mscorwks.dll!StrongNameSignatureVerificationEx+0x2fb5 mscorwks.dll!StrongNameSignatureVerificationEx+0x2fcb mscorwks.dll!CreateAssemblyNameObject+0x2248a mscorwks.dll!PreBindAssembly+0x25c88 mscorwks.dll!PreBindAssembly+0x53a0d PresentationCore.ni.dll+0x93c1f5 PresentationFramework.ni.dll+0x3f6a58 PresentationFramework.ni.dll+0x3f6815 PresentationFramework.ni.dll+0x3f67a2 PresentationFramework.ni.dll+0x3f04cc PresentationFramework.ni.dll+0x3f043f PresentationFramework.ni.dll+0x3eeaf4 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x36fe82 PresentationFramework.ni.dll+0x374298 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x3126d4 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x3306e9 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x367ea2 PresentationFramework.ni.dll+0x36782e PresentationFramework.ni.dll+0x366a1f PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x367ea2 PresentationFramework.ni.dll+0x36782e PresentationFramework.ni.dll+0x3667f1 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x36fe82 PresentationFramework.ni.dll+0x374298 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.Classic.ni.dll+0x3295a PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x3664e6 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x367ea2 PresentationFramework.ni.dll+0x36782e PresentationFramework.ni.dll+0x366a1f PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x3306e9 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x3664e6 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x36fe82 PresentationFramework.ni.dll+0x374298 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x314a29 PresentationFramework.ni.dll+0x373b3f PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x3126d4 PresentationFramework.ni.dll+0x31a457 PresentationCore.ni.dll+0x78a0ba PresentationFramework.ni.dll+0x36eecf PresentationFramework.ni.dll+0x36ec66 PresentationFramework.ni.dll+0x31a722 PresentationCore.ni.dll+0x78a0ba PresentationCore.ni.dll+0x8452ef PresentationCore.ni.dll+0x847721 PresentationFramework.ni.dll+0x362fa6 PresentationFramework.ni.dll+0x3f2d03 PresentationFramework.ni.dll+0x361d4b PresentationFramework.ni.dll+0x361817 WindowsBase.ni.dll+0x11b0fc WindowsBase.ni.dll+0x11afec WindowsBase.ni.dll+0x11edc0 mscorlib.ni.dll+0x30dd38 mscorwks.dll!IEE+0xdd36

Thanks Bryan. Unfortunately it did not solve it. damn.

Could I try to reinstall .NET? What version does FS2crew require? Should it be of any help, my fs2crew start center where I can configure my FSX MD11 starts up fine.

Bryan I couldn't find any obvious cause. Can you give me any clues at to what kind of software could be preventing your configurator from running? I am not supposed to have any unusual software here unless you count the oculus rift software.