PS5 Error CE-108255-1 (Crashes / Crashing) with Elite Dangerous

Yikes that's Pro numbers as in professional not PS4 Pro. I've really not played Elite in weeks on my PS5 but, it's so disheartening to see this issue utterly ignored.

Stability on console for Horizons was on the list of things that might be in Update 10. What transpired was only a fewfixes for a handful of very specific scenarios. Can't say it's improved much for me.
 
Stability on console for Horizons was on the list of things that might be in Update 10. What transpired was only a fewfixes for a handful of very specific scenarios. Can't say it's improved much for me.
Stability yesterday in populated systems (power play and CG) was the best it has ever been since I started to play on PS5 4 months ago. Not a single CTD in 8-ish hours of game play across two different sessions, so I am hoping that whatever it was causing the CTDs has been fixed...pleeeeease!
 
Stability on console for Horizons was on the list of things that might be in Update 10
Must be something PS related, because on XB the game is rather stable.
An occasional Orange Sidewinder here and there (but i get those on PC too) and some really random and rare sound-loop-crash-to-home-screen issues.

Other then that, for me ED was/is quite stable on XB.
 
It's weird that it's not consistent. The game has been pretty solid for me on PS5 but obviously that's not what everyone is seeing. Seems like it might be related to the number of players in a system (and I wouldn't want to rule out carriers either), but would that be a server issue, at least in part?

That wouldn't be good if they want to keep us interested in CGs anyway.
 
Must be something PS related, because on XB the game is rather stable.
1644840385447.png

Yes, that's right. Horizons on the PS5 is very unstable.
 
Yes we do have those, and Black Adder, Taupe Cobra etc.

i thought for a moment that's the PS "equivalent" for the Orange Sidewinder, because based on my own observations, an Orange SIdewinder does occur during a transition from normal space to supercruise or hyperspace or at the transition from supercruise to normal space in systems that register a lot of carrier traffic (systems with many carriers that are not jumping anywhere seem rather okish)
 
i thought for a moment that's the PS "equivalent" for the Orange Sidewinder, because based on my own observations, an Orange SIdewinder does occur during a transition from normal space to supercruise or hyperspace or at the transition from supercruise to normal space in systems that register a lot of carrier traffic (systems with many carriers that are not jumping anywhere seem rather okish)
These CE errors occur very abruptly and instantaneously drop you to the Playstation’s ‘report error’ screen completely out of the game.

The other ‘ship colour’ errors are still seen, but when those occur, we’re not dumped out of the game, just back to the main menu.
 

stormyuk

Volunteer Moderator
It’s very strange, I cannot correlate what is happening between the crashes, other than they seem to occur as I jump into a system, or upon leaving/entering an instance within a system.
Yeh this is the general gist. I think it's definitely something server side which pushes something the PS5 does not like. In back of beyond places with no player activity it was usually fine. The more populated the worse it became.

Usually as you say at transition times between instances or systems.
 
The last few times I played I did not have any crashes. But I was also exploring around the bubble, so nowhere near any CGs or so.

I think there is a thread Sally started to collect more information on the crashes. But I can't find it right now, wondering if anything came out of that.
 
These CE errors occur very abruptly and instantaneously drop you to the Playstation’s ‘report error’ screen completely out of the game.

The other ‘ship colour’ errors are still seen, but when those occur, we’re not dumped out of the game, just back to the main menu.
Yep that was the problem up until Sunday for me I added loads of examples to Sally's thread on the Dangerous Discussion sub forum of the CTDs I was experiencing usually jumping into, out of or entering super cruise in populated systems.

I was online for a few hours again last night without any CTDs or error messages in populated systems so I am cautiously optimistic that this issue has been addressed...

I'll give Robigo a test tonight when I'm back home but so far Power Play, CG, engineer and squadron systems have all passed the please don't CTD test...
 
Yep that was the problem up until Sunday for me I added loads of examples to Sally's thread on the Dangerous Discussion sub forum of the CTDs I was experiencing usually jumping into, out of or entering super cruise in populated systems.

I was online for a few hours again last night without any CTDs or error messages in populated systems so I am cautiously optimistic that this issue has been addressed...

I'll give Robigo a test tonight when I'm back home but so far Power Play, CG, engineer and squadron systems have all passed the please don't CTD test...
Robigo was mostly a success apart from the last two runs where the game froze in super cruise heading to the Sothis system, had to close the game manually and got a CTD on the first re-log but not the second...both did put 36k LS away from the main star though which was erm interesting :-/

So two game freezes and one CTD in around 16 hours of game play is certainly an improvement but looks as though we're not quite at the point of it being fixed...
 

stormyuk

Volunteer Moderator
Robigo was mostly a success apart from the last two runs where the game froze in super cruise heading to the Sothis system, had to close the game manually and got a CTD on the first re-log but not the second...both did put 36k LS away from the main star though which was erm interesting :-/

So two game freezes and one CTD in around 16 hours of game play is certainly an improvement but looks as though we're not quite at the point of it being fixed...
Do you get this same error code with your crashes?
 
Do you get this same error code with your crashes?
Yep when it crashes back to the report the issue to PlayStation screen it is always the CE error message in the top right...

When the game freezes you don't give any error message at all, you're just stuck with the witch space sounds and a frozen screen...
 
I hoped that my hypothesis is incorrect but, could this issue be ,

Carrier related if so

Servers targeted by ?? Whom ever!!

And this happened 5 times to me on my brand new PS5 media, playing in open play.
Was in wing and lots of Internet activities..

Shift from jumps (loading next system ,check of players)
Docking/landings (loading area, check of players)
Made the crashes.

I think it's network related.. I see frame drops when just moved to new area. New attack on servers ??
 

stormyuk

Volunteer Moderator
I hoped that my hypothesis is incorrect but, could this issue be ,

Carrier related if so

Servers targeted by ?? Whom ever!!
I don't think its any malicious attack on the servers, I just think something in Elite Dangerous networking code upsets the PS5 in backwards compatibility. This thread is full of many hypotheses (busy systems with human players, fleet carrier movements etc) but, Frontier have never acknowledged the problem unfortunately. They must have a massive amount of data from crash reports. I guess with the console version going into maintenance mode its less likely we will ever see a fix especially as a native PS5 app will never see the light of day. :(
 
o7 PS5 Cmdrs!

Finally got a PS5 on Friday and tried Elite. Love the quick loading and the silence 👍🏼
On Saturday I jumped near the CG-system and begun the shipments to the Glorious Prospect and had no issues in open. But yesterday after about 2 shipments I got the first CE-108255-1 (in open). Did 3 further flights then without CTD in Solo.

How is your current experience with CTDs? Especially in the current CG-systems?
 
Back
Top Bottom