Continual crashes - any response from FDEV?

Status
Thread Closed: Not open for further replies.
This has always been a thing - the UI can only list 75 missions max at a time, so if you go to ALL there may be many that don't get displayed.
Ah thanks for the extra info! Wonder how hard that would be to fix? (not suggesting they try.. don't want my srv to turn into jam or my avatar to be replaced by a bicycle or something)
 
I'm starting to think this forum needs a dating service for the old and still stupid.
Anyhoo, game problem seems solved for now...

spoken too soon. I -just- had a crash to desktop doing engineering on some beam lasers ... No missions or cg's or turning in stuff. Just rolling upgrades and spending materials at Broo's.

sigh... just ***'ing *sigh.
 
1692477622347.gif
 
Thank you..!!
It is working much better, however when you take on Kill / Assassinate missions, and jump to the target system, the Mission Target signals do not show up anymore, even after scanning the Nav Beacon.
The only way to pull them up on the signals list now is to FSS the system which is crazy time consuming.
Another interesting observation.

My experience with both hit jobs and with salvage ops (of which I perform MANY) is that 90% of the time I find the mission sites far more quickly by using the FSS than if I take the time to fly to, drop at, scan a nav beacon, and re-enter SC. I almost never visit nav beacons to find mission sites.

What secret do I know? 🤷‍♂️
 
Did some missions and just did some engineering

No problems

bugs can be fun like that, where what is actually causing them is not triggered every time the original action is repeated or what's being repeated isn't actually what triggered the bug because users only see the UI and not all the stuff going on behind the scenes that drive the UI.
 
Well I'm not having CTDs anymore. On the other hand yesterday's Ivory Cobras gave way to a wave of Mauve Adders before returning to Ivory Cobras...
As for Northpin's... Aspirations it's probably best if I sit quietly back here and watch the slow motion train wreck...
 
Would love to know what changed that caused this outcome.

I'll give you two tinhatfoilmoments: budgetary cuts affecting the hosted infrastructure (less server nodes in the server farms required for ED to function properly) or some form of anticheat implemented which didnt have the expected effect

Or not as much tinhatfoiling but still tinhatfoiling: some change in the server code didnt had the expected results OR it had the expected results that the management didnt care to listen to (the famous post-factum words: "i told you so")

😇 🙃
 
I'll give you two tinhatfoilmoments: budgetary cuts affecting the hosted infrastructure (less server nodes in the server farms required for ED to function properly) or some form of anticheat implemented which didnt have the expected effect

Or not as much tinhatfoiling but still tinhatfoiling: some change in the server code didnt had the expected results OR it had the expected results that the management didnt care to listen to (the famous post-factum words: "i told you so")

😇 🙃
Yeah, it's weird that a server-side change is causing client crashes. I'd have thought that'd just mean more disconnects. My gut feeling is also an attempt to break the trainers the cheats are using. Hence my curiosity.
 
Yeah, it's weird that a server-side change is causing client crashes.

Not that weird, ED is a truly online game.
With a really bad connection you cannot even do mining in solo - you will get stuck limpets, you will get stuck fragments in refinery and many other things that apparently are validated or depending to a constant flow of packets to/from ED servers
 
Not that weird, ED is a truly online game.
With a really bad connection you cannot even do mining in solo - you will get stuck limpets, you will get stuck fragments in refinery and many other things that apparently are validated or depending to a constant flow of packets to/from ED servers
Yes, I expect those to end with disconnects. Not CTDs. Hence, weird.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom