crua9
C
I've said it before, and I'm going to say it again. They need to fix the map for VR users.
Absolutely.
I know drkaii made that doc about how to use the map without the mouse, but it still doesn't work for me (at least not with my mappings). I have no problems moving around or finding systems (i can use voice attack to type). It's the process of actually selecting the target system and the 'plan route' button.
I know drkaii made that doc about how to use the map without the mouse, but it still doesn't work for me (at least not with my mappings). I have no problems moving around or finding systems (i can use voice attack to type). It's the process of actually selecting the target system and the 'plan route' button.
Selecting the system is a pain, until you get used to the perspective. Zoom in, and spin the view overhead a bit, and you'll spot how off your placement of the cyan puck can be. Liberal use of zoom is also a good way to make life easier and quicker. It's all about getting the puck over where the line from the star intersects with the plane.
Last edited:
crua9
C
I think what happens is the thing is it's line up with one eye, and it's trying to guess where you're going to look.
Yeah, shove the mouse pointer somewhere out of the way and ignore it- it's actually really misleading on the map in VR. Learn to use the bindings and UI pane selection, or lose your mind
Last edited:
With default bindings on an X52 I actually don't find the map any more difficult to use with the Rift than on monitor (apart from typing, of course). Just needed a bit of time to figure it out. Follwoing drkaii's explanation definitely helps. I don't really see much to be fixed there.
Don't use the mouse at all! A 2D mouse in a stereoscopic 3D map spells disaster.
Don't use the mouse at all! A 2D mouse in a stereoscopic 3D map spells disaster.
Except not everyone has all the buttons/switches of an x52.
A simple 'route to target' button in the navigation panel would do wonders.
yeah, i agree, it's to complicated. it needs to be more easier, a bit like the targeting on the gimbaled weapons.
I think the text inside the system map is definitly way to hard to read when using the OR. The problem though is that this might all change when CV1 get released with better screen resolution and tech. So I don't know if Frontier going to bother with it .
crua9
C
I agree with the text being a pain. I have a 970 with a DK2, so I know it isn't my system.
Although I agree there is certainly room for improvement and certainly a virtual keyboard wouldn't go a miss, but I certainly don't struggle with it.
I do have a X52 pro but don't use it for the galaxy map, I stick with the good old fashioned keyboard and mouse option and happen to think it works quite well for me
I do have a X52 pro but don't use it for the galaxy map, I stick with the good old fashioned keyboard and mouse option and happen to think it works quite well for me
I have never found this so bad.. Peeping between rift and nose I can even hold typed conversations.. What I am finding a huge drag is the route calculation times near the core, 5+ minutes..!
the key to working the map in vr is that you have to set at least one joy axis to a gmap crosshair movement command. you then navigate the map with the mouse, put the blue crosshair on the star you want and the slightest movement of said axis will highlight the nearest star and bring up the sub menu. It also really helps to set a joy hat to menu nav and your trigger as the "select" command. I hooe this helps those of you who were like me, slowly moving your head and the mouse to hopefully get the damn star to highlight..
P.S. I bound the joy Z axis to the crosshair up/down command so that a slight twist highlights and brings up the sub menu. life is sooooooooooooo much easier now
P.S. I bound the joy Z axis to the crosshair up/down command so that a slight twist highlights and brings up the sub menu. life is sooooooooooooo much easier now
Last edited:
yup.. i had that too.. it was brutal on the return trip. it doesnt seem to speed up again until you get to the 18,000ly mark. It had me thinkin i'd burned up a card or something.
crua9
C
Check your RAM. I'm finding this game can use every bit of 20 GB of RAM during times.
Well I figured I would try going around it.. Glad I started to do so, 1kly straight up, found huge blocks of Neutron and Non-Sequence systems, absolutely jammed full, so skirting along the upper layers of the Milky Way until I get above the core then driving down. Routing is much quicker up there, less to process..
makes sense.. plotting through the center of the center takes quite some time..I've made fresh coffe and burned one and still had to wait to complete the route. you think adding more RAM would help? I currently have 16gb @1600 xmp..
The map is fine in VR - you just need to tweak your controls.
Under "Galaxy Map" in "Controls" -
1. Bind translate plane up, down, left, right, foward, and backward
2. Bind camera tilt to your HOTAS flight stick
3. In the galaxy map, there is a setting for "Grid Mode" - ***turn this on***
Now when you enter the galaxy map, pull back on your stick a bit to get the camera out of the inital plane. The systems project little red dots on to the grid, and you can navigate a circle on screen to select those red dots using the translate keys you just bound.
I don't miss M&KB on a monitor at all - this is perfect.
Under "Galaxy Map" in "Controls" -
1. Bind translate plane up, down, left, right, foward, and backward
2. Bind camera tilt to your HOTAS flight stick
3. In the galaxy map, there is a setting for "Grid Mode" - ***turn this on***
Now when you enter the galaxy map, pull back on your stick a bit to get the camera out of the inital plane. The systems project little red dots on to the grid, and you can navigate a circle on screen to select those red dots using the translate keys you just bound.
I don't miss M&KB on a monitor at all - this is perfect.
crua9
C
Some people don't have the money or game selection for a HOTAS. But, thanks for the heads up.
Last edited by a moderator: