Tips & Suggestions: 'Galaxy Map' with OR

Is there some trick to selecting things in the galaxy map with the dk2?

I'm having a heck of a time selecting systems in the galaxy map. It seems to depend on where you're physically looking with the rift, but the clicky part with the mouse is very unreliable for me regardless. Is there some trick or feature I'm missing? I'm hoping it's something obvious that I've overlooked :).
 
My advice would be to map your HOTAS (if you have one) for use in the galaxy map.

Pitch is especially important, as you wont see the selector due to it being in the same plane your eyes are in when it loads up.

Others report that using an xbox controller worked for them.

Considering how often this is brought up, I'm really thinking about doing a tutorial video on the subject.
 
I have just finished mapping my Hotas back from the controller. It did seem a little strange, but I think pitch and yaw are very important in the visualisation of looking around. Set up a good view of where you want to go before selecting it.
 
I can pitch around using the mouse, but cant "translate x,y or z" at all even though I have even mapped wsad keys for that. they don't work, nor does select.

I don't have an xbox controller (using hotas).

Its had me stumped since I got my dk2.
 
I can pitch around using the mouse, but cant "translate x,y or z" at all even though I have even mapped wsad keys for that. they don't work, nor does select.

I don't have an xbox controller (using hotas).

Its had me stumped since I got my dk2.

Maybe the mouse control overrides these functions?
I use the yaw and pitch stick. Then to position my blue (think it is) cursor using roll for X, throttle for Y and zoom on the paddle on the front of the throttle. That's for T-flight. Tried other ways but got mis-binds.
 
My advice would be to map your HOTAS (if you have one) for use in the galaxy map.

Pitch is especially important, as you wont see the selector due to it being in the same plane your eyes are in when it loads up.

Others report that using an xbox controller worked for them.

Considering how often this is brought up, I'm really thinking about doing a tutorial video on the subject.

A tutorial would be really useful. I use a controller but it would be cool to use my HOTAS instead. Having said that I would recommend anyone with a rift get a controller. FPS games like half life and Alien Isolation work much better with a controller than mouse/KB in the rift
 
Map the galaxy map controls to your hotas. You'll need all of them.Pitch and Yaw are necessary to get a proper view of the selection plane, as you invariably start looking edge on to it. Pitch up or down and you'll be able to see the blue selection reticle.Translate X and Y move the selection reticle on the selection plane. This behaves exactly the same way the radar does - every system has a vertical line going from it to it's 2D position on the selection plane. It's the 2D position you want to target with the reticle - don't try to select the system itself! Then you click whatever your UI select button is, and the target is set; the selection plane will recentre onto the system.If the system is too high or low for there to be a line from it to the selection plane, then use the controls you mapped to Translate Z to move the plane up and down until there is.Using the menu is the same as the UI menus in the cockpit; look towards it to give it focus then use your usual UI controls to navigate it.
 
Galaxy-Map and Station-Board in Oculus Rift / Idea for better reading

Hi,

I would like to make an suggestion: Is it possible to drag & drop the information-board in the galaxy/system-map from the far left side and the three different station boards independently in Oculus Rift for better reading? My idea would be, to drag & drop them with the mouse to bring the informations right in the middle of the screen. And: If we then could make them bigger or smaller like on a smartphone too, it would be perfect.
What do you think? It would solve a lot of "unreadable"-issues.
Thanks.

olipilot
 

Sir.Tj

The Moderator who shall not be Blamed....
Volunteer Moderator
My advice would be to map your HOTAS (if you have one) for use in the galaxy map.

Pitch is especially important, as you wont see the selector due to it being in the same plane your eyes are in when it loads up.

Others report that using an xbox controller worked for them.

Considering how often this is brought up, I'm really thinking about doing a tutorial video on the subject.

If you do, let me know and I'll add it to the new faq.

This goes to anyone who thinks of something that can go in there. :)
 
A tutorial would be really useful. I use a controller but it would be cool to use my HOTAS instead. Having said that I would recommend anyone with a rift get a controller. FPS games like half life and Alien Isolation work much better with a controller than mouse/KB in the rift

I prefer 2 sticks, my thumbs are no more so young to be that precise with a pad plus I need 3 axes on my right hand.
If you bind the voices in the Galaxy map section in the controls plus the Selection on the UI section, you should be free to navigate inside the Galaxy/System Map with any issues.
 
Map the galaxy map controls to your hotas. You'll need all of them.Pitch and Yaw are necessary to get a proper view of the selection plane, as you invariably start looking edge on to it. Pitch up or down and you'll be able to see the blue selection reticle.Translate X and Y move the selection reticle on the selection plane. This behaves exactly the same way the radar does - every system has a vertical line going from it to it's 2D position on the selection plane. It's the 2D position you want to target with the reticle - don't try to select the system itself! Then you click whatever your UI select button is, and the target is set; the selection plane will recentre onto the system.If the system is too high or low for there to be a line from it to the selection plane, then use the controls you mapped to Translate Z to move the plane up and down until there is.Using the menu is the same as the UI menus in the cockpit; look towards it to give it focus then use your usual UI controls to navigate it.

Spot on.
 
Please Do!


Well - you asked for it - it's not really good (sorry about the overall quality), but I hope it helps a little:


[video=youtube;cPNNBbe71v0]https://www.youtube.com/watch?v=cPNNBbe71v0[/video]

If you do, let me know and I'll add it to the new faq.

This goes to anyone who thinks of something that can go in there. :)

Thanks, but after watching it on YouTube, I think it's a little too bad for an official faq thread - but maybe someone picks the idea up and does a better one.
 
Last edited:
Thanks for this Catpain.

When you say "bind all the axis" - looking at your config you don't seem to have any of the axis (X/Y/Z) bound?

Would really appreciate some detail on the actual bindings you use.

Oh, and your English is great. :)
 
Thanks for this Catpain.

When you say "bind all the axis" - looking at your config you don't seem to have any of the axis (X/Y/Z) bound?

Would really appreciate some detail on the actual bindings you use.

Hmm - I dont really see the point - we likely use different controllers and I have it set up to something that makes sense to me - which doesn't necessarily mean it makes sense to anyone else.

But here you go:


I use a TM warthog with pedals.

  • My pitch axis is the joysticks Y axis
  • My yaw axis is on the pedals
  • Translating forward and backwards as well as sideways is mapped to the trim hat
  • Translating up or down is mapped to the hat underneath it (pushing it upwards or downwards)
  • Zoom in and out is mapped to the index finger coolie hat on the throttle


I navigate menus by using the mic hat on the throttle on my left hand thumb., to swap between riders, I use the throttles china hat. To select, I push the mic hat.


I could upload the ED binds file and my TARGET script if you like, but I doubt it would make sense to you even if you used the same controller.
I have a Cat (surprise) and it likes to jump on the keyboard when it needs attention, so I have rebound everything to CTRL/shift+keypress combinations in TARGET to keep it from boosting me into a wall (it did that once :D).
 
Thanks... that helped. :)

I've managed to get a rudimentary galaxy map working in the Rift. I can at least select things now, and look at routes. That's using a Saitek x52 non-Pro.
 


Hmm - I dont really see the point - we likely use different controllers and I have it set up to something that makes sense to me - which doesn't necessarily mean it makes sense to anyone else.

But here you go:


I use a TM warthog with pedals.

  • My pitch axis is the joysticks Y axis
  • My yaw axis is on the pedals
  • Translating forward and backwards as well as sideways is mapped to the trim hat
  • Translating up or down is mapped to the hat underneath it (pushing it upwards or downwards)
  • Zoom in and out is mapped to the index finger coolie hat on the throttle


I navigate menus by using the mic hat on the throttle on my left hand thumb., to swap between riders, I use the throttles china hat. To select, I push the mic hat.


I could upload the ED binds file and my TARGET script if you like, but I doubt it would make sense to you even if you used the same controller.
I have a Cat (surprise) and it likes to jump on the keyboard when it needs attention, so I have rebound everything to CTRL/shift+keypress combinations in TARGET to keep it from boosting me into a wall (it did that once :D).

Thanks for the video. I FINALLY got it working! I just need to see the setup on the controls page really. There are a few weird things that I've noticed however;

WSAD / Cursor keys don't work in the rift to "translate" the map, even though it lets you add them in the controls setup page.


Some controls are unique and cant be added multiple times even though this wont affect anything in game.

For instance, you can set JOY_Y and JOY_X to tilt and pan the galaxy map and they still work as your in-game flight stick, but when I map my warthogs Mic switch to translate Y for instance on the map, then it unmaps it from the in game UI controls where I want it as well.

This is odd.
 
Last edited:
Some controls are unique and cant be added multiple times even though this wont affect anything in game.

For instance, you can set JOY_Y and JOY_X to tilt and pan the galaxy map and they still work as your in-game flight stick, but when I map my warthogs Mic switch to translate Y for instance on the map, then it unmaps it from the in game UI controls where I want it as well.

This is odd.

It's not odd at all, actually. The game uses the same universal UI controls in the galaxy map and in the game, so if you remap your mic switch to translate in the galaxy map (I use the same for navigating UI menus) it unmaps it from UI controls since you would be lacking UI controls in the galaxy map.

So basically, you should be able to remap any button except the UI navigation buttons, since they're carried over between the map and the game.
 
Back
Top Bottom