FIX. YOUR. GAME.

It's just that you are the first time among those who suffer from the bugs. Remember all the times you said "doesn't happen to me, it must be on your end"? This time it's on your end. ;)

PS
Note that it doesn't matter if you ever said that, it's just there for the dramatic effect!

Hehe, I have been on the receiving end of quite a few major bugs, not sure if you use VR, the devs completely broke VR in a major update, couldn't play for a few weeks.
 
It's just that you are the first time among those who suffer from the bugs. Remember all the times you said "doesn't happen to me, it must be on your end"? This time it's on your end. ;)

PS
Note that it doesn't matter if you ever said that, it's just there for the dramatic effect!

Have you used the beta files of reinstalled the game altogether when 3.0 came out?
I am starting to form a theory here. I always make clean install after an update and I experienced minimum bugs (except those deep rooted and widely spread ones). And the only time my game game "crashes" is when something goes wrong with my WMR headset.
 
Do you run any kind of GFX Fx app? reshade / sweet etc - try disabling them if you do. Do you run any kind of performance booster / clock speed boost - if so, try disabling them.
 
Do you run any kind of GFX Fx app? reshade / sweet etc - try disabling them if you do. Do you run any kind of performance booster / clock speed boost - if so, try disabling them.

The CTD's are a genuine bug, reproducible at certain surface ports. I have logged it, nothing to do with GPU or apps, am running a clean ED in VR with a 1080TI and I7700K, game runs fine except certain surface ports will cause a CTD.

something changed in 3.0
 
The CTD's are a genuine bug, reproducible at certain surface ports. I have logged it, nothing to do with GPU or apps, am running a clean ED in VR with a 1080TI and I7700K, game runs fine except certain surface ports will cause a CTD.

something changed in 3.0

Well, reproducible bugs are the good sort. So there's hope.
Have you tried telling someone else to try the same setup and the same port?
 
Have you used the beta files of reinstalled the game altogether when 3.0 came out?
I am starting to form a theory here. I always make clean install after an update and I experienced minimum bugs (except those deep rooted and widely spread ones). And the only time my game game "crashes" is when something goes wrong with my WMR headset.
I didn't reinstall. But I also rarely suffer from bugs (they are all on your ends :D). And this time I can't say anything about bugs at all but I guess this is because I had almost no time to play ED since 3.0.
 
The CTD's are a genuine bug, reproducible at certain surface ports. I have logged it, nothing to do with GPU or apps, am running a clean ED in VR with a 1080TI and I7700K, game runs fine except certain surface ports will cause a CTD.

something changed in 3.0

Oh dear. I have seen a frame rate drop at surface installations since 3, wasn't aware they were causing CTDs for anyone.
 
The only crashes I've had were when I was low on RAM (4Gb machine) loading the map while Firefox was open. Other than that its been solid.
 
I didn't reinstall. But I also rarely suffer from bugs (they are all on your ends :D). And this time I can't say anything about bugs at all but I guess this is because I had almost no time to play ED since 3.0.

Aha, sorry. From your previous post I thought you are the one suffering from all the bugs.
 
Well, reproducible bugs are the good sort. So there's hope.
Have you tried telling someone else to try the same setup and the same port?

Nope, but if anyone wants to test. System - Opala (near Sol) Surface port - Anderson forum.

Been flying out of that port for a over a year, is currently a no go area. No signs that the game is going to crash, FPS and planet textures are fine, a little way into orbital cruise, back to desktop. Tried a few times in a row, other ports work normally, had to cancel my haulage mission to that port, pay the fine and sell the cargo at a black market.
 
Last edited:
Nope, but if anyone want to test. System Opala (near Sol) Surface port - Anderson forum.

Been flying out of that port for a over a year, is currently a no go area. No signs that the game is going to crash, FPS and planet textures are fine, a little way into orbital cruise, back to desktop. Tried a few times in a row, other ports work normally.

I will try, tonight.
Have you tried to drop a way away (100km) and approach the port in already established instance?
 
Since 3.0.3 I'm getting almost continuous crashes in Ross 1057 CNB - solo. I've validated the game files without success and I've sent all the crash reports the game creates but I've not created a bug report. Maybe the OP has some merit?
 
My game is working perfectly.

Well, sort of.

Transitions were taking a while the other day. Then my internet died (which it loves to do while I play ED...).
Only problem I have is this weird "rubber banding" when flying really fast over surfaces. Feels like the game slows down and speeds up randomly, making smooth flying virtually impossible.

Which turns out to be a brilliant excuse to cover why i crash in to stuff. :D
 
Last edited:
Hmmm...they were conspicuously missing from the patch notes, so I wonder what "mysterious things" they put on these planets...that aren't working correctly...
 
Back
Top Bottom