Stutter Stutter Stutter since 1.3 - near stations, asteroids, and pretty much anything that has a model and collision

I don't think this problem is directly hardware related, since the FPS are (at least for me) the same during the stutter. Even CPU und GPU Load remains the same, not spikes. Hence I think it's a client-server sync issue. For most people it seems to happen near a lot of objects, which conludes my theory. Has anyone checked the logs?
 
Its WAY better in 1.4. Therefore I do not understand why we are not having a release (without CQC) ASAP. It fixes a lot of stutter problems. And its pretty stable.
 
Its WAY better in 1.4. Therefore I do not understand why we are not having a release (without CQC) ASAP. It fixes a lot of stutter problems. And its pretty stable.

That sounds very promising. I hope its not too good to be true for my stuttering. If you don't mind me asking, when did you get stuttering before 1.4? At what times was it happening?
 
I've not noticed any micro stuttering but like everyone else I do get the stutter in supercruise when other CMDRs or NPCs enter my instance. Also, and this one might just be me, but I also get a significant and predictable stutter when entering hyperspace, fps will drop from vsynced 60 to 41fps for approx 1 sec and then again around 3 sec later, this also coincides with a spike in network activity.

Hopefully this is fixed in 1.4. Ive tried cqc but have held off jumping into the main game via the 1.4 stress test, I prefer to wait for the release proper. Fingers crossed though

+just for reference, I'm on a gtx 970
 
Last edited:
Hm. Roll on 1.4 then because my approach/depature* from any celestial body in SC is a spasms-filled ride of microstuttering. (GTX 760)

* Even when the body isn't in view, e.g., behind me, it still stutters.
 
Last edited:
microstuttering has been on the increase in 1.3 this week. Still sounds like 1.4 which is out on the 8th october will fix this

Every beta had improved it for me and every release it's worse. I think it's related to how many people are playing. It would follow as people hop back on in preparation for the release the main game gets worse the week prior. I've also noticed after release it's horrible, then I burn out and come back and it's better and nothing has changed on my computer.

This and after a recent move, with the exact same speed internet I get less stutter and I don't get dropped from the server anymore. I'm using the same router and provider.
 
It´s so annoying! They said they would investigate it but how about a solution? When is this stuttering thing finally gone???

I figured out that with every stutter the frames drops down from 120fps to 25-40fps and also the GPU usage drops down to 0-8% or something like that.
And now the strange thing... every time if i open the galaxy map it has the same effect to my fps. The frames drops down again for a short time and the GPU usage too!!!

I hope there is a FD QA who could clarify those stuttering issues which exists a long long to long time! Every single stutter kicks my immersion feeling down to the ground...
 
I'm guessing that this is related to network code. When you approach a station, the client has to manage many other ships around. Same with the map. The client will try to update the map to show you, for example, where any of your friends are. I have found from my own experience that the network stuff is tying up the graphic stuff. It shouldn't but it does. When your framerate goes down and your GPU usage drops, that's not because it's busy. That means something else is preventing the code to go to the GPU. I'm suspecting that this is the network layer. I don't know why Frontier designed it that way but it's really bad for your graphic performances. It's as if there is one main loop that is shared to update the graphics and keep a connection to the server. If the connection lags for any reason, the loop slows down and the graphics are not refreshed as fast as they could.
 
I'm guessing that this is related to network code. When you approach a station, the client has to manage many other ships around. Same with the map. The client will try to update the map to show you, for example, where any of your friends are. I have found from my own experience that the network stuff is tying up the graphic stuff. It shouldn't but it does. When your framerate goes down and your GPU usage drops, that's not because it's busy. That means something else is preventing the code to go to the GPU. I'm suspecting that this is the network layer. I don't know why Frontier designed it that way but it's really bad for your graphic performances. It's as if there is one main loop that is shared to update the graphics and keep a connection to the server. If the connection lags for any reason, the loop slows down and the graphics are not refreshed as fast as they could.

I've never had any problems with stuttering, however I downloaded a huge file yesterday while playing 1.3 and got drops to 20-40 FPS. I'll try to reproduce this and test again with 1.4, it really looks like FPS are tied to network performance.
 
I noticed doing a Hutton run that I got some really bad FPS and freezing, down to 20fps. I only made the one, so not sure if it was just a coincidence. I do play wireless too.

Edit : I should add I never had any issues in 1.3. Like many 1.4 seemed to be the start of the problem.
 
Last edited:
I hate to say it, but I've also noticed shuddering (larger pauses) in and around busy stations, esp in SC. - in all iterations of 1.4beta... and now in 1.3...

...and things used to be buttery smooth...

:(
 
Last edited:
I'm guessing that this is related to network code. When you approach a station, the client has to manage many other ships around. Same with the map. The client will try to update the map to show you, for example, where any of your friends are. I have found from my own experience that the network stuff is tying up the graphic stuff. It shouldn't but it does. When your framerate goes down and your GPU usage drops, that's not because it's busy. That means something else is preventing the code to go to the GPU. I'm suspecting that this is the network layer. I don't know why Frontier designed it that way but it's really bad for your graphic performances. It's as if there is one main loop that is shared to update the graphics and keep a connection to the server. If the connection lags for any reason, the loop slows down and the graphics are not refreshed as fast as they could.

yea... its almost as if, instead of the "rubber-banding" you see when other multiplayer games are latent with network packets, it just freezes rendering until the packet is processed
hmmm..
 
yea... its almost as if, instead of the "rubber-banding" you see when other multiplayer games are latent with network packets, it just freezes rendering until the packet is processed
hmmm..

Exactly! I've played a lot of dungeon quests in WoW with other real players and never ever experienced anything like I see in ED, which makes me think that the design they chose is not really good, at least for graphic performances.

- - - Updated - - -

I noticed doing a Hutton run that I got some really bad FPS and freezing, down to 20fps. I only made the one, so not sure if it was just a coincidence. I do play wireless too.

Edit : I should add I never had any issues in 1.3. Like many 1.4 seemed to be the start of the problem.

That would make sense because there were a lot of players around Hutton Orbital. That's to be expected somewhat but, somehow, FD has tied the graphic loop too tightly with the network loop. As soon as your connection degrade or that you get in the same instance than someone with a bad latency connection, your framerate drops tremendously. If you're doing 120+ fps, you might not notice it too much but if you're on an older machine doing 20-25 fps, dropping to 10-15 is very noticeable.
 
Exactly! I've played a lot of dungeon quests in WoW with other real players and never ever experienced anything like I see in ED, which makes me think that the design they chose is not really good, at least for graphic performances.

- - - Updated - - -



That would make sense because there were a lot of players around Hutton Orbital. That's to be expected somewhat but, somehow, FD has tied the graphic loop too tightly with the network loop. As soon as your connection degrade or that you get in the same instance than someone with a bad latency connection, your framerate drops tremendously. If you're doing 120+ fps, you might not notice it too much but if you're on an older machine doing 20-25 fps, dropping to 10-15 is very noticeable.

I restart every couple of months and around updates, the start system is so bad I have to jump out as quick as possible. It's always the most populated system.
 
I´m only play in solo mode... shouldn´t be network related!?

Would be nice if FD could take place here and give an update on this issue!!!
 
I´m only play in solo mode... shouldn´t be network related!?

Would be nice if FD could take place here and give an update on this issue!!!

Correct me if I am wrong, but does not Solo mode still receive and send data to the servers? It should be lower but it still has to sync system data, prices, missions, etc with open right?

It should be a lesser impact but not sure by how much or how often.
 
Back
Top Bottom