Apologies. I normally don't assume that people have a HOTAS, but I honestly didn't think you could play in VR without one.
The advice still works - just don't bind to a HOTAS. Safe flights.
Apologies. I normally don't assume that people have a HOTAS, but I honestly didn't think you could play in VR without one.
The advice still works - just don't bind to a HOTAS. Safe flights.
If you are playing a flight-ish game like ED in VR without a HOTAS, that's going to turn out badly, by definition. VR requires tactile control cues for complex control schemes. It's hard to see how someone could afford a machine powerful enough to run ED in VR without being able to spring for one, frankly, it's like complaining that tyres for your Ferrari are too expensive.
Meanwhile, mapping the galaxy map controls to an old wired XBox 360 pad or similar is a cheap and effective way to make the map easy to navigate, if you don't want to map those particular controls to a HOTAS.
I use WASD and still can't figure out how it's done,
i want headlook integration, and i want it NOW!
i want headlook integration, and i want it NOW!
Damn the poll closed already? Any way I would have been a 'No' the map works fine if you set up your HOTAS correctly. No need for any changes.....Just take some time and set up the options properly it can be done with or without a HOTAS, just don't use a mouse for it.
Last edited:
Yep, this. It's hardly rocket surgery to do, and there are plenty of resources to help if people are finding it difficult.
People keep saying this, but again, not everyone has a HOTAS setup, and some of us have a budget HOTAS which doesn't have enough bells and whistles for all this mapping.
Anyway, the navigation in the map has never been an issue for me. People keep saying "don't use the mouse", and I'm not sure why. I keep my mouse to the right of my stick. In the map I just reach down and use it for moving around, zooming in/out, navigating the menus, etc. It works perfectly fine for this.
The only thing that's ever been problematic for me is actually selecting a system and it's sub-menu items. The pointer just doesn't line up where you think it is. It took some playing around, and now I've found the 'sweet spot'. Basically I have to get fully zoomed into a system, then bring the up/down blue arrows up a couple inches above it (what looks like a couple inches), then clicking between the blue arrows above the star selects it and brings up the sub menu.
Maybe I'll try grabbing a screenshot tonight to show this.
Last edited:
see my post on the first page... yes, I say the word hotas but the idea is the same. I suspect that any other control bind would do the same as long as it's not a mouse/kb bind. If a mouse/kb combo is all you have for this game then i suspect you are ill equipped to play adequately...no matter how good you are.
crua9
C
I was wondering. Why can't this be working out of the box?
Since the game already knows we are using a VR headset, why can't it work out of the gate. Or are VR users a sub users and not good enough
it does if you use one of the joy model profiles...at least they did early on.
Actually, I'm now using a PS4 controller and the Galaxy Map is perfectly fine. Make sure you're using Grid Mode and you should be good to go. I find it VERY easy to navigate with a controller. Keyboard, not sure. I would assume it's the same thing...but who the hell uses a keyboard in VR? lol
Last edited:
Did you read my original post fully?
This is exactly why:
Last edited:
So is that why it grinds to a halt when calculating routes near the core? runs out of memory and has to use the disk? I only have 8GB in my system and going anywhere near the core is painful
I don't have huge issues with the map TBH.
The one thing that was a real pain was selecting a destination system as I couldn't work out how to line up the cursor - as in, I'd search for a system, the map would zoom to it but I couldn't get the cursor over the system to select it as a jump destination. I'd move the cursor toward the system and then would lose context by the time it reached.
I got round this by yawing on my stick which seems to have the effect of pinning the system info for the duration. I could then move the mouse to the system and select it.
The one thing that was a real pain was selecting a destination system as I couldn't work out how to line up the cursor - as in, I'd search for a system, the map would zoom to it but I couldn't get the cursor over the system to select it as a jump destination. I'd move the cursor toward the system and then would lose context by the time it reached.
I got round this by yawing on my stick which seems to have the effect of pinning the system info for the duration. I could then move the mouse to the system and select it.
