Major bug. Uh oh. Anybody else getting this or just me on PS4?

My friend earlier was exploring and using the FSS. I interdicted him to give him a fright and when we dropped into an instance he couldn't input anything at all via his controller. Nothing except the pause menu would respond. He had to log and relog to resolve this. Combat Logging is about to go through the roof!

Later tonight I've just used the FSS, tracked a High Grade signal and dropped in... Same thing. Zero controls. Pause only. Entering pause makes my ship thrusters kick in. I saw this pause causing thrust with my friend earlier too.

This is serious for anyone being interdicted. They will be sitting ducks and will probably start combat logging out of principle. Most certainly this one needs looked at urgently.

Posting here incase this is rare or PS4 only.

Any others?
 
Last edited:
I have had this happen to me today on PC. I was jumping system and the game was still moving but my controlls wernt.

When i pressed esc to the menue my ship started moving again and when i went back to the game it stopped.

Like a boo from mario. So odd.

I logged off and back in and it was all good. Hasnt happend since but i imagine it will lol
 
I had something similar to this on the Xbox One. I was using the surface scanner and I got to close to the planet and it dropped me out of Super Cruise but I couldn't do anything, but steer inverted and in a weird camera angle. Had to dashboard and restart because I was about to crash into the planet surface.
 
Last edited:
Nope.

Been interdicted, fine.
Dropped into USSs, fine.

PS what's 'pause'.

The options menu, which most people would probably associate with a pause button menu.

I sincerely hope FD get on top of this one quick or we might have some very unhappy people who don't wish to be called combat loggers feeling forced to log until it gets fixed. Worst bug I've seen since Q4 update. Only other one was trying to zoom in on a star in FSS and it creating a duplicate tab like replicate of the same display. So if I zoomed 10 times despite it looking like it zoomed into the same picture, it would need zoomed out 10 times to undo. Strange little bug that one, but a bit off topic.
 
Lost control several times now. Once when re entering super-cruise after visiting a q09 anomaly. Once when changing to a fighter also after visiting a q09 anomaly but also with some crystal structures.

I believe both cases had me change control entities or locations with analysis mode on. However, I've dropped out and entered super-cruise many times with it on and not lost control as well.
 
Last edited:

Deleted member 115407

D
This is serious for anyone being interdicted. They will be sitting ducks and will probably star combat logging out of principle. Most certainly this one needs looked at urgently.

Or, just take some precautions when in discovery mode. No need to combat log, just think ahead.
 
Or, just take some precautions when in discovery mode. No need to combat log, just think ahead.

I never combat log. Before you mistake my emphasis and start off some of the hardcore here who like to send unpleasant PM's.

And what don't you understand? This happens outwith discovery mode. It can happen dropping out of SC into a signal zone and likely any other instance of leaving SC. You can only fix it by logging out. So pay attention. Are you saying you wouldn't log out to resolve this issue because you are one who think's ahead where a glitch like this is concerned. Nonsense.

Get a grip with that kind of response.
 
Last edited:
Happened to me three times today when entering a new system. Not fun when you can't steer and the ship accelerates towards the star.

I often adjust the throttle during the loading animation and maybe there is something wrong with the throttle key handler.
 
This happens to me (PC) if I scan something with the composition scanner, then don't switch back to combat mode before entering supercruise. Very annoying but manageable if you know the workaround.
(Known issue from Beta)

I've not yet had it on exiting supercruise, but I haven't yet been successfully interdicted in 3.3 - possibly being in combat mode would mitigate there as well?
 
Not sure how to triangulate this as some people are having it after jumping to another system too. This is definitely one I hope see's a patch within weeks at most.

Some poor sod thousands of light years out is going to be fried if this happens when they try riding a neutron cone.
 
Last edited:
This happened to me once so far. I'm on XB1. I interdicted an NPC and everything except the pause button was nonresponsive and throttle went to zero when I dropped out of supercruise.
 
Or, just take some precautions when in discovery mode. No need to combat log, just think ahead.

No need for the "Git Gud" post mate. The issue is that sometimes coming out of FSA or DiscoProbeDarts you end up totally unresponsive and require re-logging to be able to operate any more.
 
Back
Top Bottom