I told you the FSS would continue to be an unqualified success...
IIRC this was the original behaviour during the beta testing and it was changed prior to release due to the complaints so it zoomed out while maintaining focus on the body just scanned.EDIT : also when FSS seems to work, zooming out from a group of bodies or a body recenters on the parent body, making it very annoying when scanning bodies spread around a gas giant. It always recenters and you have to move the mouse even further away, very frustrating and counter-intuitive.
Finally came across the FSS corruption bug; the objects in question were orbiting a star 464,000 Ls away. Decided to fly towards it and mark of every 50,000Ls starting at 400,000Ls. Once I was within 350,000Ls I could scan successfully, so the distance the bug stopped happening for me was somewhere between 350,000-400,000Ls.
This is interesting since the user from the video I posted had the issue at 280,000Ls, while I never had come across the issue until now. Seems distance related, but it isn't always the same distances that this occurs at
EDIT: Should of read MatYNWA's comment better (sorry!), could well be not related to distance (Certain angles of scan in relation to the primary star and the one your scanning...who knows?).
fix the bloody Dolphin!
and give us small seismic charges
EDIT : also when FSS seems to work, zooming out from a group of bodies or a body recenters on the parent body, making it very annoying when scanning bodies spread around a gas giant. It always recenters and you have to move the mouse even further away, very frustrating and counter-intuitive.
The odd thing is that while I remember this being reported when the FSS was first available, I'm almost certain I never experienced it myself at the time. I put it down to one of those weird bugs that only happens with certain combinations of GPU / controller / custom settings. Maybe I was wrong. Maybe it got "fixed" as I was learning the FSS ropes and I just assumed I'd got better with the controls.IIRC this was the original behaviour during the beta testing and it was changed prior to release due to the complaints so it zoomed out while maintaining focus on the body just scanned.
Same here, been that way since the April Debacle. It also hangs for me when trying to relog to the Main Menu, which is really annoying because that is a standard procedure for re-instancing the game in various scenarios.Game still hangs when exiting to desktop. I have to manually end the task with the Windows 10 task manager.
The "Repair all" not fixing paint is intentional and was implemented after initially fixing up Paint as well automatically.
Some like (me included btw.) having those "scars of long hauls" on many of their Ships, so blame folks like me for the current state of having to manually fix the paint.
Or allowing players to use an optional module that would allow greater level of selecting their tools to carry out eploration. Have ADS as an optional module.Re-reverting it back to the way we liked it pre-April-patch shouldn't be too difficult
that supposed to been fixed!!Hi, is somebody here, who could be so kind and enter an issue into the issue tracker for me? I gave up. Issue tracker not working for me, neither does the ticket creation and did I mention this ridiculous google-captcha-thing? Kind of an illness these days. I am trying since days to enter an issue to indicate the problem of the lost priority on thrusters (the others are fixed with the patch). I already thought of buying a ticket and visit frontier directly (although I didn't try a dove, maybe ).
You could try it out before entering an issue. Just set the priority to 2, jump into another system and have a look. I think it would be a good idea to have this one as well in the bug list for future patches.
It is not for thrusters, if they are set to other value than 1. All other modules are fixed.that supposed to been fixed!!