darthranger

Just want to say "Thanks" for being here whenever I need 'Help' and to wish everyone a Safe + Happy Holiday !

I think I figured this out.... My P3D v3.3 was installed in my D:\ drive. When the P3D client did the upgrade, it apparently changed + updated the P3D file located in the C:\ drive and changed the path to open that file. Since none of my addon aircraft were in that file, they weren't recognized. Freakin' weird !!! So, I moved my addon aircraft over to C:\Lockheed Martin\ P3D, then changed the sim objects .cfg file path and now it's working. Looks like I'll have to merge the rest of my D:\ P3D files with C:\ P3D (Orbx scenery etc.) and then delete the D:\P3D file. Now I also understand why ORBX Direct was saying that none of my Orbx scenery was loaded. That file was in D:\P3D, not in C:\P3D. I think I'm going to have a look at X-Plane 11. LOL

What should the "Path" be ? (My P3D is located on D:/, not C:/) [Entry.0] Title=Default Airplanes Path=SimObjects\Airplanes Required=True Active=True [Entry.1] Title=Default Avatars Path=SimObjects\Avatars Required=True Active=True [Entry.2] Title=Default Rotorcraft Path=SimObjects\Rotorcraft Required=True Active=True [Entry.3] Title=Default Ground Vehicles Path=SimObjects\GroundVehicles Required=True Active=True [Entry.4] Title=Default Boats Path=SimObjects\Boats Required=True Active=True [Entry.5] Title=Default Animals Path=SimObjects\Animals Required=True Active=True [Entry.6] Title=Default Misc Path=SimObjects\Misc Required=True Active=True [Entry.7] Title=Default Submersible Path=SimObjects\Submersible Required=True Active=True [Entry.8] Title=Default Weapons Path=SimObjects\Weapons Required=True Active=True [Entry.9] Title=Default Countermeasures Path=SimObjects\Countermeasures Required=True Active=True

Hi Elaine No, that didn't work ! FYI, I had already tried deleting the whole: Local Disk (C:) ► Users ► you ► AppData ► Roaming ►Lockheed Martin ► Prepar3D v3 file and let it rebuild, without success.

I finally got around to updating P3D v3 to V 3.49 and now none of my add-on aircraft are displayed with a "Failed to Initialize, visualization only" indication. Can't seem to find a solution anywhere. I tried deleting the C:/program data\ Lockheed Martin\P3Dv3 folder and let it rebuild. Still no addon aircraft. Any thoughts/solutions would be appreciated. Rick

What's your refresh rate running 3 monitors though the GPU ? I've been running 3 monitors through a Matrox TH2Go since long before GPU's supported it... but one of the downsides is the limited Refresh Rate

Going 'Four' it... Thanks !

Interesting video from Frooglesim ! I am a real world pilot and use my 'very' expensive flight sim set-up to practice with... all I can say is that the yoke I got did NOT have the Pitch axis precision that he speaks of, especially on precision approaches and landing. Perhaps I got a defective and/or damaged unit ? I agree with all his comments regarding the switches; but he doesn't mention that it is 'very' front heavy and comes equipped with stick on velcro material to hold down the back end (opposite to the yoke wheel) Unfortunately no one has done a detailed comparison to the PFC or other similar products, including taking the covers off to show the inner workings ? Having had both now, In my humble opinion, the PFC yoke is less expensive (depending on the model chosen) and a much better product. GREAT support + service from GoFlight though !!!!!!! P.S. Totally agree "Blaze" about Hall Sensors !

I have a PFC yoke and pedals, but they're starting to show their age, so, rather than sending my PFC stuff in for a refurb, @ $450 + shipping; I bought one of these as an Xmas present for 'Moi' (on sale @ $599.99 + shipping + US exchange) I already have (6) GF Modules and a TQ6. All are excellent and work great ! Not sure if my yoke was 'defective' or not, but I found that trying to input precise pitch control with one hand was impossible due to the yoke column binding + sticking on the front bushing. Roll input was smooth and precise. In my humble opinion, the yoke control wheel is very front-heavy and I think that is what was causing it to 'bind' in the bushing on pitch input. (if I used both hands, and lifted it slightly it was fine) In comparison, my PFC is as smooth as 'Butter' on all axis. I contacted GoFlight and the guys were great to deal with. They let me return it and provided a full refund (minus shipping of course) Great Service ! But... just wish it would have worked better for me and saved me $200+ in shipping and credit card exchange rates from US to Can. dollars. Live and Learn... Ce La Vie ! Rick / Canada

I'm considering upgrading from a 2gb GPU to a 4gb GPU to take advantage of the potential for P3D to off-load on to the GPU from the CPU. Just wondering if anyone has upgraded and noticed any significant improvement in performance vs the $400 cost ??

No... not overclocking, but thanks for the response !

Thanks for the pointer !

I also posted this in The CTD Forum in hopes of finding an answer... I have been running P3D V2 exclusively for some time now, and all was well until recently... P3D has started to CTD about 10 minutes into a flight. Faulting module: clr.dll, version 4.030319 Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.319\clr.dll Faulting application path: D:\Lockheed Martin\P3Dv2\P3d.exe P3D forum says this is NOT a P3D issue, but rather a Microsoft issue. Microsoft Support says: "Faulting Module name clr.dll when you run .NET Framework based application" "CAUSE: The issue occurs because an object that is being referenced is dereferenced by the collector in common language runtime 4 (CLR4). Therefore, an access violation occurs during garbage collection or when the application tries to access the released object" I'm hoping someone here that has more computer 'Savy' than me can explain what the heck they're talking about... and/or how to fix this. P.S. Microsoft says that there was a Hotfix for this in 2011... but I would think that was dalt with in updates. (I have .NET Framework 4.5.1 installed) Rick / Canada

I have been running P3D V2 exclusively for some time now, and all was well until recently... P3D has started to CTD about 10 minutes into a flight. Faulting module: clr.dll, version 4.030319 Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.319\clr.dll Faulting application path: D:\Lockheed Martin\P3Dv2\P3d.exe P3D forum says this is NOT a P3D issue, but rather a Microsoft issue. Microsoft Support says: "Faulting Module name clr.dll when you run .NET Framework based application" "CAUSE: The issue occurs because an object that is being referenced is dereferenced by the collector in common language runtime 4 (CLR4). Therefore, an access violation occurs during garbage collection or when the application tries to access the released object" I'm hoping someone here that has more computer 'Savy' than me can explain what the heck they're talking about... and/or how to fix this. P.S. Microsoft says that there was a Hotfix for this in 2011... but I would think that was dalt with in updates. (I have .NET Framework 4.5.1 installed) Rick / Canada

EMT made it work !