Honk still gives bodies , so you know how many.you can then fly around until the beady eye picks them up.
What happened to the FSS ?
- Thread starter Deleted member 38366
- Start date
-
- Tags
- fss
You'd need a good beady eye to spot that ball-o-ice 20kls away never mind the one at half a million ls distant
Still doesn't see it as an issue, just a difference.
The other things seem annoying, but again, I'm hardly seeing these issues. There is some light flickering occasionally, which I can also cause to happen by fiddling with the VR headset (Oculus Rift). The FSS space has been well behaved otherwise.
I wonder if some of the graphics issues people are experiencing are due to outdated drivers, as as been suggested by others. I tend to update as new NVIDIA drivers come out, with the rare roll-back if something breaks. I run ED in VR, using 2 x Geforce GTX 1070 cards in SLI. The game generally runs well on Ultra, with about equal load on either card. I recently saw some frame rate drops near shards PoIs on planet surfaces. But whether that was normal (never saw them before) or an issue with the coinciding April Update, I don't know.
The centre-on-main-body feature of the FSS zooming could be an unintended change. Not sure if it is a regression though. Have FDEV actually said it was?
S
In my experience, entering FSS again will cure it momentarily, that is until you try to zoom in on the same spot things started to go south at first.
So far moving your ship a bit, preferably laterallly, keeps the bug at bay.
Still doesn't see it as an issue, just a difference.
The other things seem annoying, but again, I'm hardly seeing these issues. There is some light flickering occasionally, which I can also cause to happen by fiddling with the VR headset (Oculus Rift). The FSS space has been well behaved otherwise.
I wonder if some of the graphics issues people are experiencing are due to outdated drivers, as as been suggested by others. I tend to update as new NVIDIA drivers come out, with the rare roll-back if something breaks. I run ED in VR, using 2 x Geforce GTX 1070 cards in SLI. The game generally runs well on Ultra, with about equal load on either card. I recently saw some frame rate drops near shards PoIs on planet surfaces. But whether that was normal (never saw them before) or an issue with the coinciding April Update, I don't know.
The centre-on-main-body feature of the FSS zooming could be an unintended change. Not sure if it is a regression though. Have FDEV actually said it was?
Couple of thing to disect there.
Firstly, the graphics issues
The graphics issues could be many many things, and I wouldn't begin to assume I could even know the answers, it's a custom engine doing a lot of crazy and complicated things, all I can give is my own personal experience, which is that I updated my graphics card drivers a day after the new patch was released, and that the same graphical issues existed before and after said graphics driver upgrade.
However, my own graphical issues are vastly less problematic than some of the videos I have seen, I merely get all of the graphics being heavily over exposed (very very bright) after zooming back out of planets -sometimes-
And if I then exit the FSS while this is happening, this overexposure exists over the entire game output (UI, Background, ship cockpit, any objects like stations - it's over the entire screen so I would guess it's coming from the system which they use to "tone and colour grade" various parts of space, total guess, though)
I use an AMD card as opposed to Nvidia, and I think I've only seen videos of the entire UI overlay flipping round from people using Nvidia, though unsure on that.
However, that part is a pretty huge and obvious bug.
As for the centering issues -
No, FD haven't said "This is a regression" but they have said they realise there are problems with FSS and have passed them on to be resolved - and said this when the main complaint appeared to be the re-centering into the "wrong" position (the original message from frontier was in this thread in which the OP only mentioned the minor graphical problem that I sometimes get)
The reason I say it is a regression error, is because I played during the beta when the FSS was being tested, and before release, they got feedback from the playerbase wanting it to be changed, and then they changed it, and said this was the new design intent. (I personally see the merit in the way it worked before this change, but understand the want to have it not behave the way it is currently)
The current behaviour is exactly as it was during the beta (regarding the re-centering only)
This coupled with seeing many "regressions" after patches in the past (understandable with such a huge interlinked and complex code base) leads me to believe it is indeed a regression to previous behaviour which existed during the beta, and was then changed.
Last edited:
It's beginning to look like a versionitis issue! I don't actually remember the centre-position from the beta, only that we got a (better) method for exploring systems and a lot of whining about it.
I get the background flickering to lighter colours from time to time, within the FSS itself. It seems related to be zooming in and out near the main star, but it has been more a cosmetic issue than anything. The effect reminds me of smoke or steam rising from a vent in a setting with low sun, and the graphics engine getting a bit confused about where to place the shadow border. So I see shading flickering then, just like I see skybox background colour flickering in the FSS near a star.
It is starting to look like one of those things that affect different setups differently.
S
Yes indeed it does, and that is a method I have used to good effect allied with the instant scan of flying rapidly through the midst of a gas-giant sub-system, for example
Parallax exploring can be fun sometimes!
I have experienced it several times now, but each time it appears to happen only for objects at a far distance, the two instances I observed happened with secondary stars 100K+ls away. Remaining where I was and trying various things had no effect, the only thing that changed it was to approach the distant objects. I tried several time with the object just over 100kls away, slowing down at 60kls and testing, the same, 40kls and testing, still the same, but at 20kls away it worked as normal, so it appears to be something to do with the level of zoom not working for extremely distant object when they are obstructed or really close to another object.
With objects that distance moving laterally which I tried first is probably not going to affect it much, once I approached to around 20kls my angle of approach probably did exactly as you describe and moved the objects laterally enough to be distinguishable.
I have no doubt we will get a patch soon to fix it and the centering issue, that ones just annoying for most people but a real downer for players who suffer from motion sickness by the sounds of things.
Not good for VR players, then.
Im using the latest NVIDIA drivers and the FSS is unusable. Twisting graphics on zooming in, white screen on zoom out and moving the ship doesnt help.
I cant figure out how they manage to not only break something new with every patch, but how a bug this severe, which for me is in the game breaking category, managed to get past them.
Doesnt anybody test this stuff?
I will never buy another FD game, its just too frustrating to have ones ability to play randomly taken away due to sheer negligence and carelessness.
I cant figure out how they manage to not only break something new with every patch, but how a bug this severe, which for me is in the game breaking category, managed to get past them.
Doesnt anybody test this stuff?
I will never buy another FD game, its just too frustrating to have ones ability to play randomly taken away due to sheer negligence and carelessness.
It is starting to look like one of those things that affect different setups differently.
Definately, I've seen some videos of things that don't happen on my system at all.
It did do the centre of mass repositioning in beta, I remember that frustration well
I don’t agree that it is “better”, just a different way of finding the same information. It didn’t fit well with what I enjoyed about exploring, and so I didn’t like it, and still don’t, so I find ways around it like going back to parallax exploring. Although, it is less annoying to use than it used to be, and it makes total sense in a populated system for USS discoveries.
I didn’t realise that expressing a reasoned dislike of something was whining
I didn’t realise that expressing a reasoned dislike of something was whining
It's not. Non-constructive criticism is, however. And there was a lot of that.
S
And then we have this shiz...
How far away were the objects giving you problems, as I said in my post, if they are 40-60k+ls away moving the ship locally won't have much effect, try identifying the rough location of the object from the system map, basically see what's missing and point in that direction, if they are dierctly ahead of you they should appear that way in the FSS as well and move a lot closer if they are distant objects.
That's worked in both the cases I encountered while having the exact issues you describe.
Or alternately, instead of making up for FD's incompetence by performing some inconvienent gameplay contortion i could just play something else and never buy another Frontier game, which i think is the route im going to go.
Same problem. Point of entry into a cluster is the default position. Moving outwards from the point of entry to scan another body defaults back to centre on zooming outAfter this new Patch, my FSS is acting up badly.
Working a Gas Giant and its moons is currently rather disorienting. After zooming out, the FSS vector isn't where it's supposed to be but often somewhere else.
- instead of maintaining the exact zoomed vector after zooming In & back out from an FSS scan, it "auto-centers' on next nearest Parent/Higher Gravity Well (?)
- zooming in gives 1-2sec of severely discolored FSS display
Same with a distant B, C, D Sun etc, the FSS almost permanently has to be manually re-positioned with upto 2 zooms back out in order to re-target the correct body
Am I alone with that weird issue ?
Clearly, the ADS was inferior.
I returned from a quick overnight trip earlier today and scanned a few systems on the way home. I didn't get any folding or distortion but the barycentre behaviour was consistent. I would much prefer that my telescope zooms back out to the same position I zoomed into, it was a little disorienting to keep returning to the same spot multiple times and having it stay where I put it would be more intuitive. Hopefully this is just a regression bug & not another 'feature' no one asked for.