So I have both my surface scanner & detailed scanner set up in a fire group (1 to primary & 1 to secondary fire) but when I try to use either one I get an error message "incorrect cockpit mode, press not bound to switch." Well I have no idea what is going on and I'm getting super frustrated as I have no idea where this "not bound to switch" is. I'm playing this game mainly to explore, but so far the help is very vague for what i'm trying to do.
Having problems w/surface scanner operation (user error most likely)
- Thread starter TSgtMatt
- Start date
I'm playing on a PS4
should be same thing, check control configs.
problem is the combat/scan mode . and if you cannot switch you will get stuck often
cannot shoot in scan mode but all passive modules are active.
Combat mode, guns active and combat modules and some scanners. non combat modules dont fire.
Should be a switch mode somewhere, most likely with FD after an update, it will require a binding to some button control combo etc
should not matter if on PC / Xbox or PS , sounds like that mode switch isnt bound, or if it is check what it is bound to ,control config setting somewhere no doubt
problem is the combat/scan mode . and if you cannot switch you will get stuck often
cannot shoot in scan mode but all passive modules are active.
Combat mode, guns active and combat modules and some scanners. non combat modules dont fire.
Should be a switch mode somewhere, most likely with FD after an update, it will require a binding to some button control combo etc
should not matter if on PC / Xbox or PS , sounds like that mode switch isnt bound, or if it is check what it is bound to ,control config setting somewhere no doubt
Thanks a ton, now I'm all set up (for the most part...) and have already scanned a few systems.
FYI, the "not bound to switch" message is it saying that the binding to switch is not bound. If you see that same message now, having assigned a binding to switch modes, the words "not bound" will be replaced with the actual binding. You see this in other places where there are missing key bindings but it shows them all anyway, it could have been handled better in the message I think.
Yea, it took me a little bit to figure that out. I'm more used to seeing "not assigned" and the "not bound to switch" threw me for a loop.