Stephane Leduc

Ok thats a good idea ! thanks for your help, anyways i dont get why they did this. On any other Aircraft you can just take out panels and still have a fully functional VC... weird stuff :(

Hi icemarkom ! Oh ok, so its not possible to fly with a VC and have lets say the PFD on both displays ? i find this to be very special since it doesent make any sense to me. If i would take all Instruments to my second Monitor, the VC would basically look as if it was Cold and Dark. Never saw this on any add on...

Hi, Im usingf the PMDG 777 with P3Dv4 on a Dual Monitor Setup (Second is for gauges) and i have a Problem with undocking the Panels. Whenever i undock a Panel to take it to my second Monitor, the Panel goes black in the VC. Ist like im litterally taking it out to bring it to the other Screen. I have never had this with any other aircraft. Is it Normal ? sorry for my bad english Greetings from switzerland Stephane

yes that could be. Im planning on uninstalling everything sim related and doing it all one by one and with great care, so that i dont get things like this. Is there anything i should know about, or i could do to make sure that im really starting with a clean slate ? add ons i own and will reinstall with P3d: PTA Orbx FTX Global Flytampa Dubai Rex Texture direct + Soft Clouds

Hi everyone i just installed Orbx FTX Global base pack in P3d v4 and it worked without any problems. i dif however see that somehow Orbx is in the main p3d directory but also in an Fsx directory that was created in "programfilesx86" . i was wondering if this is normal, i do not own fsx anymore so the folder has to be created by orbx or another add on ?! thanks Stephane

Hi everybody ! I just started using P3d V4 and i absolutley love it ! however i have some Trouble when it Comes to my Goflight MCP Pro. I searched everywhere but couldnt find an answer. Are the Project Opensky Planes using the Default FSX/P3d Autopilot Module ? Because somehow it didnt work for me with a 737-800 i downloaded. Most of the Default P3d planes work just fine. thanks in advance amd greetngs from LSZH Stephane

I'll go even a step further. Dont trust ANYONE else's opinion for anything in your life :) sure, you listen/read what they have to say but in the end you are "flying the plane" that goes for everything in life....

This finally did it, after some other trouble i went trough with reinstalling windows, i can finally say that everything is up and running. Thank you 1 million times for encouraging me to solve this ! btw: P3Dv4 is indeed the future ! It runs so smooth, its really comforting to know that the journey with "FSX" continues. warm greetings from LSZH (Zürich) Stephane !

ok you convinced me ! I will reinstall Win 10, i wont even have to do a backup because i dont have any files on the computer that i would like to keep. so it wont take that long. ill be in touch as soon as i have installed P3D again, i hope this works... thanks !

actually this is not what they told me.. i think im doing exactly as ive been told. Poppet told me to create a new account on the P3D forums, thats why i did it. A fresh windows install will only be my last option.

Hi Poppet, the things i did without success - Create new User Account with admin rights - Downloaded the latest USB driver and found out that i already have it, so i just clicked on "repair". thanks

frustrating it is... i can assure you :) Ok so i did a clean boot and the error is still the exact same.. :(

if really nothing goes i will do that, but for now i wanna try some more. I am aware of the refund policy.. but i said to myself that i will anyway want to use p3d if not on dis computer then on another so im ok with that.

thanks, i hope that we are getting closer ! I will have to go to work now, so i will try most of the things you mentioned later...one thing i did try, was to unplugg all USB devices when my Computer was turned off. Then i restartet with nothig attached... and somehow P3D took much longer to get to the loading bar on the splash screen. I did get the same error, but maybe this menas something. the whole time until it crashed was like 10 times longer than usually. thanks Stephane

thanks Vic ! i will try the clean boot tommorrow as it is pretty late in switzerland... when i start P3D i get these errors in the event viewer. Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255 Faulting module name: api.dll, version: 4.0.28.21686, time stamp: 0x594a7300 Exception code: 0xc0000005 Fault offset: 0x00000000000155d1 Faulting process id: 0x1814 Faulting application start time: 0x01d2f9ca45b3bd13 Faulting application path: D:\Games\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: D:\Games\Lockheed Martin\Prepar3D v4\api.dll Report Id: 7b60e650-448c-4f7d-afdc-a9a775efdb73 Faulting package full name: Faulting package-relative application ID: i dont know if this one is related, its a second error (not application fault like above) that seems to occur when i start P3D: Unable to start a DCOM Server: {9AA46009-3CE0-458A-A354-715610A075E6} as Nicht verfügbar/Nicht verfügbar. The error: "740" Happened while starting this command: C:\WINDOWS\System32\rundll32.exe C:\WINDOWS\System32\shell32.dll,SHCreateLocalServerRunDll {9aa46009-3ce0-458a-a354-715610a075e6} -Embedding