Constant CTD's on Planetary landing approach

[Anticon]

Anyone else experiencing these?
I can make 1 or maybe 2 landings, then it all goes bad: CTDs when I'm at elevations of 4000-200m on approach. I get brief stutter in sound and graphics sometimes, not all. I've fiddled with Vsync and refresh rates to no avail. Can't figure out if it's a memory problem, graphics problem, or just a hopeless pilot.

 

[colprice2002]

Sorry,
Not had that experience.
Are you using Horizons or Odyssey?
What type of PC - desktop/laptop?
My system doesn't max out for planetary landing (though it does in concourse in Odyssey), does yours hit max CPU/GPU limits? If so, consider the possibility of overheating

 

[varonica]

Nothing. I have had the odd crash just after starting when scanning bodies with the FSS, but once I send off the error log and restart it never happens again no matter how long I play or how many bodies I scan. But I've never had a crash on landing, it may be a graphics issue, try turning them down temporary and see what happens, if it goes away increase the settings one item at a time and see if it recurs with a particular feature turned up.

 

[Anticon]

Sorry - should have said, using a PC for Odyssey. I've fiddled with graphics settings, but maybe I'll go back to Horizons and see if it happens there too. It's ONLY on planetary landings, so graphics seems the likely suspect; maybe unable to render surface textures. Will experiment further. Thanks for comments Cmdrs.

 

[varonica]

Sorry - should have said, using a PC for Odyssey. I've fiddled with graphics settings, but maybe I'll go back to Horizons and see if it happens there too. It's ONLY on planetary landings, so graphics seems the likely suspect; maybe unable to render surface textures. Will experiment further. Thanks for comments Cmdrs.

Don't just fiddle, you can't troubleshoot like that, turn it all down low and run a few tests to see if it stops misbehaving, if it does then start putting setting back up, but fiddling won't do anything if it's a combination of two settings that are causing the issue because you may never two the right two off or down at the same time!

 

[Anticon]

Problem solved.
Apologies - "fiddle" is my shorthand for an approach just as you've described. However, after lengthy testing, the problem persisted to the point where I remembered the First Law : Validate Your Files after each patch/hotfix/update if any problems arise. Lo, the problem went away and now I can land away. I must have had a glitch during Update 4. o7