February 25, 20251 yr 1 hour ago, CO2Neutral said: But as you can see my other complete “clean-install” solution resolved the issue. No, the problem was resolved when he reinstalled P3D ***and didn't enable any of his addons***. The addons, as is so often the case, were the problem. Dave Simulator: P3Dv6.1 System Specs: Intel i7 13700K CPU, MSI Mag Z790 Tomahawk Motherboard, 32GB DDR5 6000MHz RAM, Nvidia GeForce RTX 4070 Video Card, 3x 1TB Samsung 980 Pro M.2 2280 SSDs, Windows 11 Home OS My website for P3D stuff: https://sites.google.com/view/thep3dfiles/home
February 25, 20251 yr Moderator 2 hours ago, CO2Neutral said: Anyway, it was a possibility so I listed it. You’re overlooking the fact he didn’t have a problem with MSFS. So in his case it wasn’t a possibility. Ray (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
February 25, 20251 yr 28 minutes ago, Ray Proudfoot said: You’re overlooking the fact he didn’t have a problem with MSFS. So in his case it wasn’t a possibility. Not overlooking, MSFS doesn’t support IGD and it’s an entirely different code base. Edited February 25, 20251 yr by CO2Neutral
February 25, 20251 yr 47 minutes ago, dave2013 said: No, the problem was resolved when he reinstalled P3D ***and didn't enable any of his addons***. Perhaps the OP can clarify, but a “clean-install” as I outlined will remove all add-ons and anything else than can also be an add-on that doesn’t use the add-on process and uses legacy/compatibility support.
Create an account or sign in to comment