Driving me nuts! Galaxy Map

Ok so I've read numerous points about the galaxy map in VR but not found the one thing I need to know.

I can move around no bother. I can select menus no bother.

When the blue cursor is over a planet why won't it bring up the context menu so I can select it and plot a route?
 
  • Make sure grid and object markers are in the map settings. (right most tab)
  • first thing to do when using the map is to tilt the view a bit so you can see the grid and the grid markers.
  • Manouver the center grid marker to the marker left by systems to to select and find the context menu.
  • Mastering the zoom binds are key. You need to zoom out to get large movement and zoom in to find the markers.

It takes some getting used to but I don't miss the mouse at all in galaxy map.
The system map is honestly worse. But at least with it you have the list for interactive objects.
 
Last edited:
  • Make sure grid and object markers are in the map settings. (right most tab)
  • first thing to do when using the map is to tilt the view a bit so you can see the grid and the grid markers.
  • Manouver the center grid marker to the marker left by systems to to select and find the context menu.
  • Mastering the zoom binds are key. You need to zoom out to get large movement and zoom in to find the markers.

It takes some getting used to but I don't miss the mouse at all in galaxy map.
The system map is honestly worse. But at least with it you have the list for interactive objects.

Thanks I'll give that a go but have a workaround below.

I've managed to enable the context menu switch in controls. I can now switch between planet selection and the menu on the left using the mouse to either look away and hit the mouse button, or look at the left menu and hit the mouse button. Took me over an hour to sort it. I use the joy sticks to move around. Aaaaaaaarrrrrrrrrrrrrrrggggggggggggggggghhhhhhhhhhhhhhhhh!

I've not seen any mention of the center grid marker or the context switch option. Just loads of vague rubbish about setting up controls. Thanks again!
 
Step 1, stop using a 2D selection device in a 3D space.. use the 3D cursor the game gives instead of a mouse. it magnaticly locks onto stars when you get near, never had an issue ever selecting anything.
 
Step 1, stop using a 2D selection device in a 3D space.. use the 3D cursor the game gives instead of a mouse. it magnaticly locks onto stars when you get near, never had an issue ever selecting anything.

Nope doesn't lock onto anything unless your focus is away from the menu. I had to actually use the mouse to change the focus then I can lock on. Which setting I'm missing so I don't have to use the mouse currently escapes me.
 
Last edited:
Nope doesn't lock onto anything unless you're focus is away from the menu. I had to actaully use the mouse to change the focus then I can lock on. Which setting I'm missing so I don't have to use the mouse currently escapes me.

Have you enabled 'Show Grid' from the below place in the Galmap?

UfHA
 
Not sure if this is the problem you're having but when I first started using the joystick to control the galaxy map (since trying to do it with the mouse in VR is basically impossible) I too found that I couldn't operate the little context menu. Basically my problem was that I was using the little hat stick on my joystick (Thrustmaster T-Flight HOTAS) to move laterally around the map and this was conflicting with the fact that the hat stick was also bound to UI navigation. I changed the galaxy map bindings so I had to press the hat stick in combination with another "shift" button to get lateral movement and bingo, I can now do everything I want in the galaxy map using only the joystick. If it's any use I wrote up some of these early findings in "the bad" section over here ...

https://forums.frontier.co.uk/showt...and-the-ugly?p=4591413&viewfull=1#post4591413
 
Not sure if this is the problem you're having but when I first started using the joystick to control the galaxy map (since trying to do it with the mouse in VR is basically impossible) I too found that I couldn't operate the little context menu. Basically my problem was that I was using the little hat stick on my joystick (Thrustmaster T-Flight HOTAS) to move laterally around the map and this was conflicting with the fact that the hat stick was also bound to UI navigation. I changed the galaxy map bindings so I had to press the hat stick in combination with another "shift" button to get lateral movement and bingo, I can now do everything I want in the galaxy map using only the joystick. If it's any use I wrote up some of these early findings in "the bad" section over here ...

https://forums.frontier.co.uk/showt...and-the-ugly?p=4591413&viewfull=1#post4591413

I have exactly that set up, I'll change the mappings when I get back to my rig.

Once I can replicate and correct the issue I'll post it up for posterity.
 
I have exactly that set up, I'll change the mappings when I get back to my rig.

Once I can replicate and correct the issue I'll post it up for posterity.

OK cool, fingers crossed.

As an added tip, I actually now use all 4 buttons that sit alongside my thumb on the throttle as "shift" modifier buttons. So, for example (and outside of the galaxy map) with none of them pressed my hatstick operates my vertical and lateral thrusters, with the top button pressed my hatstick does the pips, with the second button pressed it's targetting (next/prev ship and next/prev subsystem), with the third pressed it opens my HUD panels and with the fourth pressed it does misc' functions (lights, galaxy map, FA off and silent running). That's 20 separate functions on the hatstick alone. By using lots of "shift" modifier buttons (that simply alter the behaviour of other buttons) you can easily quadruple the number of functions you can bind to the stick.
 
I use an Xbox Controller and have absolutely no issue with navigating the Galaxy Map nor have I ever had, it felt a bit different from flatscreen at first obviously but I got used to it very quickly thereafter.
The only issue I'm seeing is the Trade Routes don't always show up for each System, they seem to load for some systems but not for others and when checking back on the monitor it's working as normal, so somethings screwed there.
 
these threads about galaxy map should get a sticky and a faq... or a fix pass by the devs.

The trick is to use ui navigation to move between the left menu and the planetary menu and having them separate from the movement. Takes a while getting used to. Basically what Alec said.
 
When I show people Elite in VR, copies of the game are absolutely sold until they go into GalMap / SysMap. Then I either have to do it for them on the monitor or talk them through the process with mouse and KB. Neither makes the game more appealing.

GalMap / SysMap need to be sorted for VR use. An on-screen keyboard is also a must. They have it on PS4 definitely.
 
Last edited:
Since it's sort of on-topic, I thought I'd ask here before starting a new thread...

I have the galaxy map sorted (I think), but I'm having issues with the system map. Namely, using the mappings that I have for the galaxy map, I can pan left and right (roll on the joystick), I can zoom in and out (a hat on my throttle that does zoom in galaxy map), but no up or down either by using the direct up and down control that works in galaxy map (the other part of the hat that does zoom), or the pitch on the joystick. Yaw on the joystick, which rotates the galaxy map also does nothing, but that sort of makes sense in the more two dimensional system map.

Any thoughts as to what I am missing, as it makes navigating the system map a bit fruitless.

Thanks

Other than that, I have to say VR is a game changer! :)

Edit: Hmm, Ok, I figured it. It's the axis that I use my throttle for in galaxy map that moves up and down in system map, so I think I'm good to go... :)
 
Last edited:
I don't actually think they have sorted this yet, there was some input sensitivity bug with axis and the maps.
In short if you bound a panning function to an axis, you wouldn't really get full speed, it would simply register a partial input.
Binding this to an actual button made panning about twice as quick.

Especially noticeable in the system map, but then again, the panning speed in the system map is atrociously slow
 
Back
Top Bottom