Possible Workaround for CTD with Graphics Card Error

[flyingpauls 66]

I posted about this problem before. You get a dialog at each start of the flight saying that an error on your graphics card occurred and you should switch off overclocking and get recent drivers. My workaround now is to disable the scenery cache completely. No CTD after that change.

[Axis3600 50]

How to delete the cache ?

[danhenri 24]

Thank you for the tip.

[flyingpauls 66]

1 hour ago, Axis3600 said:

How to delete the cache ?

Go to the general options and data.

[bobcat999 8,444]

4 hours ago, flyingpauls said:

I posted about this problem before. You get a dialog at each start of the flight saying that an error on your graphics card occurred and you should switch off overclocking and get recent drivers. My workaround now is to disable the scenery cache completely. No CTD after that change.

There could be something in this.  I deleted my scenery cache and stopped it from running again - no CTD of this type since.

[flyingpauls 66]

Still checking if it was a Placebo. 🙂

 

[Alvega 2,119]

7 hours ago, flyingpauls said:

I posted about this problem before. You get a dialog at each start of the flight saying that an error on your graphics card occurred and you should switch off overclocking and get recent drivers. My workaround now is to disable the scenery cache completely. No CTD after that change.

Maybe that's why I never had that error. I always had the scenery cache disabled.

[Bernard Ducret 790]

3 hours ago, flyingpauls said:

Still checking if it was a Placebo.

I hate to spoil your party, but I had that error too - before updating to the new Nvidia driver released yesterday -, however I never used scenery cache.

Edited September 28, 2022 by Bernard Ducret

[flyingpauls 66]

1 hour ago, Bernard Ducret said:

I hate to spoil your party, but I had that error too - before updating to the new Nvidia driver released yesterday -, but I never used scenery cache.

word not allowed ...

[ErichB 3,638]

 I have had this error about 5 times in 4 days.  Anyone else still got the problem?

 

erich

[Mike62 29]

I had this problem during flight a couple times yesterday.  Just recently upgraded to Windows 11, went back to windows 10 and took another flight without issues.  Maybe a coincidence.

 

Mike

 

[_Airbus_Fan_ 26]

Hi

After half an hour I remembered this error. Tried it with and without a full community folder.
Up until SU9 this bug didn't exist, this bug came with the SU10 update.

https://drive.google.com/file/d/1tQY_UpWjCpeXohLEzwEDqUl5b0FbuT90/view?usp=sharing

Unfortunately, I can no longer fly the simulation.
Asobo needs to fix this bug. In the meantime, until the bug is fixed, I'm flying P3D You have alternatives.

 

 

Edited September 29, 2022 by _Airbus_Fan_

[Ianrivaldosmith 5,317]

I get this error every time I pop out a window. And it’s not Vram related as I have a 3090

[ErichB 3,638]

12 hours ago, _Airbus_Fan_ said:

Hi

After half an hour I remembered this error. Tried it with and without a full community folder.
Up until SU9 this bug didn't exist, this bug came with the SU10 update.

https://drive.google.com/file/d/1tQY_UpWjCpeXohLEzwEDqUl5b0FbuT90/view?usp=sharing

Unfortunately, I can no longer fly the simulation.
Asobo needs to fix this bug. In the meantime, until the bug is fixed, I'm flying P3D You have alternatives.

 

 

P3D is not an alternative.

[_Airbus_Fan_ 26]

9 hours ago, ErichB said:

P3D ist keine Alternative.

@ErichB
It's still better than not flying at all.
Before the MSFS came, the P3D was a sim that was flown a lot.
In any case, with this bug, the sim is no fun.