I'd be really interested to find out what is causing it. But I s'pose we'll never know...
Sudden judder or momentary freeze
- Thread starter Tyres O'Flaherty
- Start date
Perhaps true, but I'm sure everyone would settle for a cure rather than the inside story of what's wrong but with no cure
For me, the most obvious piece of evidence for why this simply can't be a server-side-only issue is that the time delays are too short.
Ping times (aka round-trip times for packets) between player computers and the game servers will be well in excess of 10 milliseconds for pretty much everyone, and likely more than 20 ms for >80% of players.
Since intra-frame times are only ~16 ms even at a mere 60 fps, there just isn't enough time between frames to communicate synchronously between the client and server. This means that nobody (not even FD!
) would design a game client which depended on replies from a server to arrive before serving up fresh frames to the GPU. Instead, the netcode in typical games is "asynchronous" and updates things in a separate loop (with data updates often being at less than 10 Hz).I do think (as I said above) that the game client is mistakenly doing something lengthy in a critical thread - i.e. a client-side bug. This may or may not involve comms with the server, but having now seen Mechan's video - where he drops from 400 fps to maybe 260 fps - it's clear that the intra-frame times for him are MUCH too short even at their worst (~ 4 ms) for there to be any "ask a question and get a response" type comms between client and server fitting in between his frames...
So yeah, maybe some server-side issues are compounding a client-side bug, but I believe the absolute minimum is a client-side issue.
This reminds me once again that the minimum system requirements for ED are a big fat lie, and it's disgraceful that FD haven't updated them since the EDO graphics engine became the Live product even for Horizons players. Nonetheless, since people with decent CPUs seem to be having this particular problem, the CPU performance probably isn't so crucial here.
Oh shush, what do you know?Nope, there is not even possible to download an entire game's database.
Pretty easily too.
It is the ED process initiating all the connections through the IP stack so, yes, the client. It does initiate connections and transfer data, but connections are being made up all the time you move between systems, instances, even frameshift/glide/surface.
Stats show it certainly isn't downloading a lot - I've got a 57MB capture (total traffic including ED, but as much else possible shut down) over 30 minutes, during which stutter happens (and GPSS in the log.)
That's about where I have to leave it to a developer to pick apart.
I very much doubt this theory. Not only is there no evidence for it, but an account is owing for why it doesn't affect all players at the same time, since many are clearly not affected.
my cpu or gpu never goes to 100% during the stutters.
also how do you think inara and the others get their data if not via API's ? i dont think we have telepathy technology yet or quantum state database replication
i've only ever seen very few postt on this forum about using the client addon. i think they are using other methods
also how do you think inara and the others get their data if not via API's ? i dont think we have telepathy technology yet or quantum state database replication
i've only ever seen very few postt on this forum about using the client addon. i think they are using other methods
Last edited:
What time resolution are you using?
Odyssey ground conflict zones often drop frames due to CPU usage, but this is not visible at, say, Afterburner's default update frequency - you have to drill down to 1/10th of a second at least to see the issue.
The EDDN gets its data primarily through parsing players' journal files and uploading the refined data, not through a pipe directly inserted into Frontier's servers. If you turn off all the integrations in EDMC, none of the systems you visit are updated using your data. This is well-known; you should learn how the 3rd party apps work.
The stuttering occurs for me regardless of what 3rd party apps I'm using, or even when none of them are running. Moreover:
Artie is the guy who runs Inara. He might know what he's talking about.Nope, there is not even possible to download an entire game's database.
Perhaps it's time to choose not to die on that hill. Just a thought.
Last edited:
this could be any one of the 3rd parties flooding the servers with requests. not just Artie's app, as he would know this.
my pc, my internet, and what i was doing in game all were relatively low use during a stutter.
something is taxing the servers at 10 minute intervals starting at 00:05:50
it's impossible that people's worldwide computers would all slow down on the exact intervals in perfect time sync. 100% impossible for such a coincidence.
it might be possible that the game client has a bug that something is going on at that frequency; however, since so many have reported this i think Frontier would know if their client is doing something on 10 minute intervals. and why would they choose to start it at 350 seconds past the hour?
my pc, my internet, and what i was doing in game all were relatively low use during a stutter.
something is taxing the servers at 10 minute intervals starting at 00:05:50
it's impossible that people's worldwide computers would all slow down on the exact intervals in perfect time sync. 100% impossible for such a coincidence.
it might be possible that the game client has a bug that something is going on at that frequency; however, since so many have reported this i think Frontier would know if their client is doing something on 10 minute intervals. and why would they choose to start it at 350 seconds past the hour?
Last edited:
If I were paid for it or had too much spare time: Wireshark. But even if I did, it wouldn't help since FD still would have to act upon it, and it's way easier for them to do that analysis themselves.
Your cpu has 10 cores. ED only uses 3 or perhaps 4 of them. Any one of those can be running at 100% and still show 15% utilisation.
My performance monitor shows at least one core running at 100% even when ED is just sitting in space doing nothing.
I have seen the stuttering quite noticeablely and regularly over the last few weeks, but played for 2 hours last night (21-23 UTC) and had no sign of stuttering at all.
No, it can not be that. The game, especially so the graphics, runs quite fine without any contact with FDev's servers. For about 30s, then it notices it lost contact and summons a colorful snake. Try unplugging your ethernet while you play.
They most likely know.
That might be part of a clever scheme to make all clients update stuff at the same time, to minimize skew between them. Or some dubious design.
Watch this, it explains quite nicely what is known. In particular that it's most likely a programming bug that causes the main game thread to fail to submit work to the GPU, because it's busy doing something else (that always precedes the GPSS log entries).
Edit: Removed my post since I've noticed most of what I've discovered was already common knowledge in this thread.
Last edited:
Don't worry about it mate, lots of repeated info in every thread. Not to mention lots of circular arguments. It's a forum thing
Don't believe me check out any thread about ship interiors or open vs solo and you will see what I mean
Interesting observation today. Right after the stutters, I opened the galaxy map, selected a system, and the last updated status said "Just now." So I presume the stutters are caused by Powerplay 2 and Trailblazers data being transferred to the client. I also noted a spike in internet data traffic in task manager, but it was well below my internet max speed. Not sure why this would affect the CPU render unless Fdev screwed up core allocation in the client.
This would be consistent with them having put a non-time-critical task (like fetching galaxy info) into a time-critical thread... One would like to think that it'd be an easy job to fix that
