That's good - it means the devs have chosen to work on it.
Sudden judder or momentary freeze
- Thread starter Tyres O'Flaherty
- Start date
Opps, I don't know what came over me.
Yes of course they will. And they will get to work on it pronto I am sure.
Dumb question, but where does it show as acknowledged ? Is it just that little tick above the pyramid ?
The only way I've found to show the word "acknowledged" is to hover my cursor over the "vote" button. Maybe the tick means the same thing?
Yeah, that's the point. Instead of useful CPU or GPU activity on the main threads, a specific codepath is sat waiting for things to happen either on the network or in communication with other threads, instead of doing anything useful.
Why is it at the same time on every PC? Because when the servers ask the PCs to collect the data, the requests are not staggered. That is, pretty much, the problem.
They get their data from clients running on the PC which scrape the journal on the PC. This is documented, very well known, and discussed regularly on this forum.
Wow, the issue on the tracker has 30 pages now. Thanks to all who posted!
Yeah, I think it has become considerably worse in the last few weeks.
I can certainly say that I'm no longer in any doubt about whether I'm having the same problem - the timing of my stutters wasn't on the xx:x5 before, but now almost all of the bad episodes are; they are also more frequent for me but they still don't occur 100% of the xx:05:40 times, for example.
I can certainly say that I'm no longer in any doubt about whether I'm having the same problem - the timing of my stutters wasn't on the xx:x5 before, but now almost all of the bad episodes are; they are also more frequent for me but they still don't occur 100% of the xx:05:40 times, for example.
Pointless cynicism?
Opps, I don't know what came over me.
I didn't say they would do it quickly. Your rush to get a cheap dig in does you no favours.
Last edited:
Is there a way of seeing how many upvotes any given issue has?
Incidentally, if, when searching by top-voted, we're... wait for it! Numero uno!
Incidentally, if, when searching by top-voted, we're... wait for it! Numero uno!
Today's stutter sessions shown in the logs - busier periods (i.e. holidays when more people are on) are clearly more prone to the stutterfest - now every 5 minutes. #*^& this
Line 428: {19:10:52GMT 165.636s} GPSS set state foci (49775, 40733, 23892)->(50197, 41169, 24294)
Line 1206: {19:13:04GMT 297.504s} GPSS set state foci (49775, 40733, 23892)->(50197, 41169, 24294)
Line 2129: {19:17:00GMT 533.802s} GPSS set state foci (49775, 40733, 23892)->(50197, 41169, 24294)
Line 3259: {19:22:06GMT 839.736s} GPSS set state foci (49775, 40733, 23892)->(50197, 41169, 24294)
Line 4414: {19:27:09GMT 1142.239s} GPSS set state foci (49775, 40733, 23892)->(50197, 41169, 24294)
PS. Until my separate thread was closed by the mods and linked to here, I was not aware of this OG thread - apologies if my work has stepped on the toes of others who have done the work earlier. On the plus side all the kerfuffle in the various threads here on the forums and reddit has vastly increased the number of reports of the tracked issue and has finally resulted in an "acknowledged" status after 4+ months.
Honestly the lack of pace and feeling of any urgency for work on known issues let alone the really obviously damaging self-sabotaging performance/visual ones which undermine anyone's love of ED and turn off new and old players alike is wearing me down.
Line 428: {19:10:52GMT 165.636s} GPSS set state foci (49775, 40733, 23892)->(50197, 41169, 24294)
Line 1206: {19:13:04GMT 297.504s} GPSS set state foci (49775, 40733, 23892)->(50197, 41169, 24294)
Line 2129: {19:17:00GMT 533.802s} GPSS set state foci (49775, 40733, 23892)->(50197, 41169, 24294)
Line 3259: {19:22:06GMT 839.736s} GPSS set state foci (49775, 40733, 23892)->(50197, 41169, 24294)
Line 4414: {19:27:09GMT 1142.239s} GPSS set state foci (49775, 40733, 23892)->(50197, 41169, 24294)
PS. Until my separate thread was closed by the mods and linked to here, I was not aware of this OG thread - apologies if my work has stepped on the toes of others who have done the work earlier. On the plus side all the kerfuffle in the various threads here on the forums and reddit has vastly increased the number of reports of the tracked issue and has finally resulted in an "acknowledged" status after 4+ months.
Honestly the lack of pace and feeling of any urgency for work on known issues let alone the really obviously damaging self-sabotaging performance/visual ones which undermine anyone's love of ED and turn off new and old players alike is wearing me down.
Last edited:
I feel your pain. 4+ months is just not acceptable. This should have been fixed BEFORE they released Trailblazers, which has only made things much worse.
Yeah. I was doing the CG earlier today and it was really hurting combat. In an asteroid field where everything used to be silky smooth.
I don't have the technical chops to even begin guessing what it is and I don't use/look at Reddit so I'm hoping the link to the issue tracker made it over there and those folk are contributing.
I'm just glad I opened a ticket!
I don't have the technical chops to even begin guessing what it is and I don't use/look at Reddit so I'm hoping the link to the issue tracker made it over there and those folk are contributing.
I'm just glad I opened a ticket!
I disagree with the closure of that other thread. As you state, the fact that this thread is down in the PC sub-forum means a lot of people who might have experienced the issue would not have known about this if they didn't frequent the PC sub-forum. Having the issue raised in a much more visible area should be applauded, not closed-down.
Yep, I've felt that pain in the last week. It's really annoying when you're trying keep a target close and in your sights for frag cannons. It's also just plain annoying... makes you feel like there is something wrong with your computer.Yeah. I was doing the CG earlier today and it was really hurting combat. In an asteroid field where everything used to be silky smooth.
I don't have the technical chops to even begin guessing what it is and I don't use/look at Reddit so I'm hoping the link to the issue tracker made it over there and those folk are contributing.
I'm just glad I opened a ticket!
I've been attempting to keep an eye on the game threads during stuttering episodes. It has taken me several attempts to catch it in the act, but I've now managed to take screenshots during and after an event.
The upshot is that one of the two main threads seems to climb very close to 100% utilisation (shown as 12.5% of CPU time on my 8-thread CPU) and the other drops dramatically. (This could mean that the busy thread is unable to cope with its workload - so a CPU with more headroom might behave differently - and that in turn might be unloading the other thread, or the other thread could be waiting for something like I/O; it's all too dynamic to capture it with Process Explorer, so I might consider using Process Monitor instead.)
Afterwards, things return to normal, which for my system means that both of the 2 main threads are a little under the max (at 10% ish).
[edit: am belatedly noticing that all of the lightly-loaded (2-3%) threads also show much lower utilisation during the stuttering]
(Note the thread IDs in the pics.)
First snapshot during the stuttering:
And a few seconds later, things look normal:
Might be interesting to see the same from someone with a much faster CPU than my 7700K - e.g. a 7800X3D or better. (I had the Process Explorer update speed set to 1 second. If my machine could cope I'd probably have gone with 0.5 second...)
It's all fun and games with the guesswork but I'm still inclined to think that FD know exactly what's wrong.
Meanwhile, it's interesting that GeForce Now doesn't exhibit the issue. Maybe they have a different game client...
The upshot is that one of the two main threads seems to climb very close to 100% utilisation (shown as 12.5% of CPU time on my 8-thread CPU) and the other drops dramatically. (This could mean that the busy thread is unable to cope with its workload - so a CPU with more headroom might behave differently - and that in turn might be unloading the other thread, or the other thread could be waiting for something like I/O; it's all too dynamic to capture it with Process Explorer, so I might consider using Process Monitor instead.)
Afterwards, things return to normal, which for my system means that both of the 2 main threads are a little under the max (at 10% ish).
[edit: am belatedly noticing that all of the lightly-loaded (2-3%) threads also show much lower utilisation during the stuttering]
(Note the thread IDs in the pics.)
First snapshot during the stuttering:
And a few seconds later, things look normal:
Might be interesting to see the same from someone with a much faster CPU than my 7700K - e.g. a 7800X3D or better. (I had the Process Explorer update speed set to 1 second. If my machine could cope I'd probably have gone with 0.5 second...)
It's all fun and games with the guesswork but I'm still inclined to think that FD know exactly what's wrong.
Meanwhile, it's interesting that GeForce Now doesn't exhibit the issue. Maybe they have a different game client...
I feel this issue has become much worse over the last couple of days
Indeed, really bad for combat players. Needs fixing ASAP but I ain't holding my breath.I feel this issue has become much worse over the last couple of days
Maybe because of the Easter hols where more people are playig.