June 2, 20179 yr Hi, For reasons i dont know i am unable to use P3Dv3 (at least with the FSLA320-X) . I have tried a couple of drivers and also looked in the forums at P3D, but still stuck, Was there a work around ? Thanks , apreciated Michael Moe Michael Moe
June 2, 20179 yr Just now, Michael Moe said: Hi, For reasons i dont know i am unable to use P3Dv3 (at least with the FSLA320-X) . I have tried a couple of drivers and also looked in the forums at P3D, but still stuck, Was there a work around ? Thanks , apreciated Michael Moe Im assuming so, not had it with the newest driver 32GB ddr4, [email protected], Zotac 1080ti Extreme
June 2, 20179 yr Author 13 minutes ago, glider_uk said: Im assuming so, not had it with the newest driver well i still get this with SLI and none SLI, moderate settings and no overclock. I thought it was related to shadows but it cant be. PS! I am also having it with the PMDG´s now Strange Michael Moe Michael Moe
June 2, 20179 yr 1 minute ago, Michael Moe said: well i still get this with SLI and none SLI, moderate settings and no overclock. I thought it was related to shadows but it cant be. Strange Michael Moe Im no longer SLI so I cant comment on that im afraid 32GB ddr4, [email protected], Zotac 1080ti Extreme
June 2, 20179 yr is it just fslabs? A stream I watched had that error on the pmdg 777 in p3dv3 Try running the display driver uninstaller program, then reboot and install the latest nvidia driver using the "clean install" option.
June 3, 20179 yr Author 9 hours ago, 777200lrf said: is it just fslabs? A stream I watched had that error on the pmdg 777 in p3dv3 Try running the display driver uninstaller program, then reboot and install the latest nvidia driver using the "clean install" option. Thanks, Tried that including driver that worked before (373.06) but the problem is now 100% even with default aircraft Also tried a brand new P3D.cfg Michael Moe Michael Moe
June 3, 20179 yr As I have the same issue with the Milviz F4E Advanced (only plane sofar) I inquired with Milviz. They told me that this is due to an error in P3Dv3, which is corrected in ver4. Aparantly related to a time out interaction with the graphics card!
June 3, 20179 yr I found that deleting my shaders and allowing it to recompile stopped me getting this error on load but I have an older GTX680 currently. Rgds - Sam Harridann
June 3, 20179 yr Author Nope 10 hours spent on 3.4 so i desided to go back to 3.4.9.18400 and the problem whent away but CTD. so a little search disabling/enabling all .dll entrys and it was down to FSL Spotlights. Now everything is back in order except spotlights but i guess i can try a reinstall of that. Update:reinstall FSLSpotlights and CTD again. Just going to leave it out Thanks Michael Moe Michael Moe
Archived
This topic is now archived and is closed to further replies.