FSS stutter/lag

..........d the lack of biological feature information after closing the zoomed-in scan.

........
I can see bio-pois as same as geo-pois after zooming in. So they are definitly there.
.............

I didn't express myself at all clearly, sorry - I have now stuck in a "closing" to clarify.

Yes I too see the information in the zoomed-in view, I meant that the biological features are not shown / listed / whatever away from that view. I am told that it isn't even passed to the journal so EDDiscovery can't show it. So geo features are shown elsewhere (system map, EDDiscovery etc) but other surface features are not. Well OK after mapping they are listed in NAV but before that you have to make a note of which bodies have what.
 
Having the same issue on PC although framerate is around 200-250 when in FSS mode. Especially in big systems with lot's of zooming and panning this is a pain...
 
I am still wondering if this is really machine power related.. I am on a brand new PC with some serious power i9 9900/1080TI and frame rate never drops below 60.. never observed any issue with FSS
 
^^^--- + rep, this is the explanation.

The jitter happens after you first start scanning landable planets and as varonica points out, the game client is doing some calculating in the background, working out where the Geo PoI's are going to appear on that body. It becomes increasingly noticable if you quickly scan a succession of landable bodies with geo PoI's.

You and Para point out exactly what I've deduced (Xbox). I've begun scanning everything (zoom in, zoom out), just dealing with the stutter, then checking what kind of volcanism the bodies have in the sysmap - instead of waiting the 25-30 seconds it takes per body for the sites to show up.

Interestingly, since the last update, biological sites are showing almost instantly...it seems they've all turned into Bark Mounds, but that's a different issue. :D
 
Interestingly, since the last update, biological sites are showing almost instantly...it seems they've all turned into Bark Mounds, but that's a different issue. :D
Nah, it's just that out of all the biologicals, bark mounds have the least restrictive criteria. If a region has a given biological type present, then odds are that they'll be present on most, if not all, possible candidate planets. (Mind you, there are cases when candidates are rare. Plus cases where the Codex doesn't report all the criteria.)

So, if you're fed up with bark mounds being everywhere you look, the best solution is to fly to a different region that doesn't have bark mounds.
However, many biologicals are tied to bodies with volcanism, so it's back to the spinning circle then.
 
Nah, it's just that out of all the biologicals, bark mounds have the least restrictive criteria. If a region has a given biological type present, then odds are that they'll be present on most, if not all, possible candidate planets. (Mind you, there are cases when candidates are rare. Plus cases where the Codex doesn't report all the criteria.)

So, if you're fed up with bark mounds being everywhere you look, the best solution is to fly to a different region that doesn't have bark mounds.
However, many biologicals are tied to bodies with volcanism, so it's back to the spinning circle then.

When I first tested out the new mechanics near the Bubble, I found brain trees, anemones, etc. without even consulting the Codex as to reported locations. Now I'm three sectors away, and nothing but bark mounds!! It wouldn't be so bad if there were different types of bark mounds, like there are brain trees...chocolate bark mounds, peppermint bark mounds...you get the idea. :D
 
Is there a ETA, when this stutter/lag in the FSS mode will be fixed?
I'm having the same issue, even though I average around 150-200 fps in fss mode...
 
For me it just slows down when I'm close to bodies. Certainly no stutter just it scrolls slower so I don't get any issues with over shooting.
 
I am on PS4 and it starts lagging when it detects these geological / biological signals on planets. I have to wait until it finishes these detection scans, otherwise the whole FSS starts lagging.
Would be nice if it can stop scanning for these geolocial / biological signals when I quit the zoom on the planet.
 
I wonder if this stuttering in it is the primary reason why the FSS causes me such bad eye strain.

I noticed that some of the low framerate scenes when watching Spiderverse caused exactly the same sensation, and resultant eye-watering and pain as the FSS does... Coincidence? Seems unlikely.

The backdrop whilst panning the camera in the FSS has that same "flickbook" animation feel to it which the film implemented as a stylistic choice. Going to guess it's not intended here. The panning itself however, remains mostly smooth, with only the odd freeze here and there, causing overshoot on a signal source, most of the jittery low and inconsistent framerate animation lies soley in the ever-present background animation.
 
Last edited:
For me, the stuttering appears after zooming in on a planet with geological sites and zooming out before they've loaded completely (in the upper right edge of the screen).
If i wait for them to appear, than i don't have any stutters in tge FSS mode. But if i go through the system quickly and just zoom very shortly in on icy bodies for example, then the FSS starts to stutter heavily the more planets i had in a row with geo-sites :|
 
Anybody else find that the FSS refresh rate sucks? Makes quick scanning a pain when you keep overshooting targets due to the screen freezing for a second while it refreshes. Solid internet. No other types of lagging issues. Solo past the core on the way to BP.

Anyone else?

YES!

I was wondering whether it was my system. I have it pegged as a potential audio issue, but because I have some custom audio drivers on my PC to allow me to fine-tune which output-device which App should be on and at what volume, I was wanting to first uninstall all that before raising a bug report.

My thinking is that every time you scan something in the FSS, some sounds get played, which have to be shoved onto the audio queue. When scanning things very quickly I'm wondering whether perhaps too many sounds are being added to the queue and some mutex comes into play briefly locking the UI update thread or something. Just wasn't sure whether it's an in-game issue or system issue.
 
YES!

I was wondering whether it was my system. I have it pegged as a potential audio issue, but because I have some custom audio drivers on my PC to allow me to fine-tune which output-device which App should be on and at what volume, I was wanting to first uninstall all that before raising a bug report.

My thinking is that every time you scan something in the FSS, some sounds get played, which have to be shoved onto the audio queue. When scanning things very quickly I'm wondering whether perhaps too many sounds are being added to the queue and some mutex comes into play briefly locking the UI update thread or something. Just wasn't sure whether it's an in-game issue or system issue.

No really, see post #12, that's the real explanation. tl;dr the game is generating the geo/bio PoI's on the planet in the background, which is nabbing CPU time and possibly GPU render time in order to populate where these locations will be. This is happening even if you zoom out from a body with geo/bio PoI's.
 
No really, see post #12, that's the real explanation. tl;dr the game is generating the geo/bio PoI's on the planet in the background, which is nabbing CPU time and possibly GPU render time in order to populate where these locations will be. This is happening even if you zoom out from a body with geo/bio PoI's.

Unless you have access to the source code or a developer confirmed this, it's as much of a guess as mine. Also doesn't explain why only the Geo POIs are slow; all other POI types show up near-instantaneously.

Although should be easy to test - I'll try to find a (large) system without landables, and see if I can get stutter. If I can, it's not (solely) POI-related. If I can't, it most likely is.


EDIT: Reading @varonica's post, they do mention it's only due to Geo POIs, not Bio ones. So that makes more sense. Still, my impression was that it seemed related to audio; I could easily be wrong and as I said, it's easy enough to test given a suitable test system (which again, should be easy enough to find using EdDiscovery).
 
Last edited:
The FSS has always run pretty smoothly for me. Does anyone have video of the stuttering they're seeing? I'm curious.
 
Back
Top Bottom