is it now a nvidia related issue or amd too?
It affects players with both cards.
is it now a nvidia related issue or amd too?
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.
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
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.
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..
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.
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´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!!!