Oh dang, you are right! I felt like something was off but I had been using the Auto Dock since the last patch. I am going to investigate further but I do have the same issue. The comms about where your assigned pad is and all the "300m to touchdown" or "approach vector is good" etc. seem GONE.
For my exploration build thrusters are set to priority 2 in case of a defective power plant (reduced output). And although this problem (reset to 1 after each jump) is less problematic than the change of all priorites (which is fixed), it indicates, that I can not rely on the priority list anymore für exploration purposes. If still (after the patch) the priorities will be changed by the game itself (even if it's only one), the whole priority list is useless. If we saw this this time and it's still not totally fixed, I will never again use priorities for a decent build if I'm out in the dark far away from home.
I have my Thrusters on Priority 1 one but I tried changing it while auto undocking... it was messed up: I could hear the left/right sound effect but the priority would stay on "1" then suddenly become "5", then "2", then "1" (for some reason never "3" or "4"..) but without being a coherent change, sometimes it would become "1" and stay there then become 2, then 1, then 5, then 2, then 5, then 1.. you get the idea.
I have the same. I already wrote about it here some days ago. Unfortunately it's not only changing during auto undocking (which is really messed up 1-5-2-1) but also after hyper jump.
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.
That's my experience also, I tested it with signals just over 380kls away and 100kls away. The first one, the 380kls one I just SC'd up to 20kls away, slowed down and the FSS worked fine. The second I tested at various distances, 60kls, 40kls and 20kls, both 60 and 40 failed but at 20kls the FSS worked fine on a signal that was otherwise impossible to scan. Yes it's not always the same distances, but I suspect it is distance related and also related to the layout of the signals in the area we are trying to scan. Normally a signal to close or hidden by another body would simply "fail to resolve" and you would need to move to clear the obstruction so I think this is related to both the target signal layout and distance.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?).
and add engineering for mining equipment
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.
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.
Oh, didnt know that. Thank you for explaining
(Makes some sense now btw!)
