Getting my Rift today!!!

[Lensman]

Thanks guys. Yep, I've mapped the Reset VR View to button on my quadrant. My aircraft of choice is the Spitfire and the default viewpoint seemed spot on for me. Compared very well to a recent experience of sitting in a Spit at the Hendon RAF museum. If I want to 'lean back' a tad I find you can lean forward, tap the reset view button, then sit back.

I'm also very pleased that the controls and switches of my 'nearly scale' Spit cockpit come to hand/finger very well. All that's missing is a view of my hand!

Good advice about turning the FPS counter off.

Cheers for the welcome to the VR Club!

[vortexringstate]

Just found out about the VR Zoom feature. I have it mapped to my pinky button on Warthog so I can keep it pressed while I use the mouse.

 

Set up a hat switch (shifted) to move the view "cockpit camera" up, down, front, and back.

 

As I'm still setting up my PC system, i haven't yet got my Rift working... (despite it teasing me from its box beside me!) I'm trying to get ahead of things so I can correctly configure my Rift when my system is built.

 

I'm trying to understand the above comments... why do you need to VR zoom? Isn't that the whole thing with VR...? Just lean in? Similarly , why the need for the bindings on the hat switch?

 

With the VR zoom bound to a button, does the mouse scroll incrementally 'VR zoom'? Iv read on other posts VRZoom is just on or off (in or out).

 

I'm sure all my Qs will be answered when I actually get my rig operational but it's helpful to get my head around 1st.

 

Cheers

[some1]

I'm trying to understand the above comments... why do you need to VR zoom? Isn't that the whole thing with VR...? Just lean in? Similarly , why the need for the bindings on the hat switch?

 

 

Cheers

 

Because the Rift/VIve resolution is poor and you will have a lot of difficulties spotting and discerning targets otherwise ("is that black smudge in the distance a bomb hole, a tree, or another tank?"). It also sometimes helps to read some smaller gauge or display in the cockpit without repositioning yourself. But zooming also distorts the cockpit perspective, so it's not very pleasant and I try to avoid it.

 

Also because sometimes pilots in real life fly with binoculars and it works a bit like them.

 

VR zoom is a momentary shortcut, it zooms as long as you hold a button and returns to normal view when you release it. All other zoom functions/shortcuts are disabled in VR, this is the only way, so you want to have it in some easy to reach place on your hotas.

[Scooternutz]

As I'm still setting up my PC system, i haven't yet got my Rift working... (despite it teasing me from its box beside me!) I'm trying to get ahead of things so I can correctly configure my Rift when my system is built.

 

I'm trying to understand the above comments... why do you need to VR zoom? Isn't that the whole thing with VR...? Just lean in? Similarly , why the need for the bindings on the hat switch?

 

With the VR zoom bound to a button, does the mouse scroll incrementally 'VR zoom'? Iv read on other posts VRZoom is just on or off (in or out).

 

I'm sure all my Qs will be answered when I actually get my rig operational but it's helpful to get my head around 1st.

 

Cheers

 

I use the shifted hat switch to adjust my up/down front/back view. It would be exactly like adjusting the seat in the A/C and that is what it feels like. The VR zoom just brings in some detail when you need it. I don't use it often.

[vortexringstate]

Wooohoo. Got my PC and Rift up and Running. AWESOME experience and will always remember that buzz of being in VR for the first time! As someone else here has said..."Iv been waiting 25 years waiting for this !" Technology is making my dreams come true.

 

Iv cleared up several of my questions and concerns now and am in the tweaking mode of getting the best out of the settings.

 

trying to get Oculus Tray Tools to function properly but having trouble...

[simo1000rr]

Wooohoo. Got my PC and Rift up and Running. AWESOME experience and will always remember that buzz of being in VR for the first time! As someone else here has said..."Iv been waiting 25 years waiting for this !" Technology is making my dreams come true.

 

Iv cleared up several of my questions and concerns now and am in the tweaking mode of getting the best out of the settings.

 

trying to get Oculus Tray Tools to function properly but having trouble...

 

I wouldn't recommend using Oculus tray tool with DCS , it works with other games but with DCS leave it without it . Why you use the tray tool to begin with in DCS ??

[vortexringstate]

I wouldn't recommend using Oculus tray tool with DCS , it works with other games but with DCS leave it without it . Why you use the tray tool to begin with in DCS ??

 

Naieviety....?

 

I have a new i7 CPU with GTX1060 and 1920x1080 monitor. Iv only played using Track IR on another PC prior to this build, so I am unsure what good/acceptable frame rates are to be expected in VR...?

 

I thought the HUD overlay function was good to see Performance adjustments. Im not very conversant in the world of GFX settings: AWS, Super sampling, Pixel Density etc are things I have yet to fully understand esp in relation to each other for in game experience.

 

I also bought the USB3 PCI expansion card which some are having difficulties with. I read somewhere the Tray Tool solved those issues (not that I was having issues yet). Is there known issues with the Tray Tool it or is it an un-necessary performance tax?

 

 

Im finding it tiresome on the eyes tweaking all the variables to trying to benchmark what looks good vs perf! Should I simply be using FPS as a quantified way of tuning, or using the in game experience? I notice an uncomfortable 'shimmering' of light objects (such as building roofs) and power poles/towers. Id really like to tune this out/down.

 

Any tips or performance tweaks would be greatly appreciated!

[dburne]

Naieviety....?

 

I have a new i7 CPU with GTX1060 and 1920x1080 monitor. Iv only played using Track IR on another PC prior to this build, so I am unsure what good/acceptable frame rates are to be expected in VR...?

 

90 FPS is ideal, anything below 90 down to 45 and ASW kicks in ( will run at 45 fps and interpolates the frames). It works fairly well. Below 45 is not going to be good...

Oculus did a pretty good job with this ASW feature to allow the Rift to run on some lower spec pc's.

 

I thought the HUD overlay function was good to see Performance adjustments. Im not very conversant in the world of GFX settings: AWS, Super sampling, Pixel Density etc are things I have yet to fully understand esp in relation to each other for in game experience.

 

Pixel Density = Super Sampling. They are the same. Renders a better and higher resolution image, downscaled to fit the Rift's resolution. Nice feature but comes at a price of performance.

 

I also bought the USB3 PCI expansion card which some are having difficulties with. I read somewhere the Tray Tool solved those issues (not that I was having issues yet). Is there known issues with the Tray Tool it or is it an un-necessary performance tax?

 

Is that the recommended Innatek card? If so be aware you have to disable power management to the Fresco Logic USB 3 root hub on each clean boot or system restart. It will re-enable each time. Also make sure the power management is disabled for the Oculus sensor or sensors. These will be listed in device manager under Oculus. If you do not, you will have HMD disconnects and/or sensor dropouts from inactivity , and then it takes a reboot to get them back. Very frustrating.

That Oculus Tray Tool the guy did over on their forums, also can be set to run at startup and disable these items as well upon startup. You can also use the Tray Tool for Pixel Density settings per game, but best to use the in game GUI setting if the game has it, like DCS does.

There is no performance hit from using the Tray Tool.

 

Im finding it tiresome on the eyes tweaking all the variables to trying to benchmark what looks good vs perf! Should I simply be using FPS as a quantified way of tuning, or using the in game experience? I notice an uncomfortable 'shimmering' of light objects (such as building roofs) and power poles/towers. Id really like to tune this out/down.

 

Monitor your FPS in game at first. As long as it is 90 fps or 45 fps and does not drop below 45 fps, you should have a smooth experience. As long as it is smooth to you, you are golden. You certainly don't want any stuttering.

 

As far as graphics options, what I did in DCS menu was start very lean, and kept adding a little bit at a time, testing in between with the same flight. I kept working with it and tuning it till I got to where it was very smooth and I was satisfied with the image quality. Sure I would like it to be better, but the immersion outweighs that currently for me. Sometimes I am at 90 fps, but oftentimes I am at 45 fps - but it is still very smooth for me. I never see it drop below 45 fps or stutter.

 

Hope this helps,

Edited April 3, 2017 by dburne

[vortexringstate]

Anyone got a solution to not being able to click "OK, CLOSE or FLY AGAIN" in the mission debriefing window while using Rift?

 

My Vr settings are set to 'Use mouse'. I can click on everything in the startup menu but the briefing windows dont seem to work with the mouse clicks.

 

Frustrating!

[Cibit]

You need to drag your desktop taskbar to the right vertical as it conflicts with the lower buttons in DCS:)

 

Also the tray tool is great for determining your settings with the performance option showing you headroom for the system.

I have all the eye candy on and have 45FPS steady which is perfectly acceptable to me in NTTR and with the shadows on the world seems so much more real!

Edited April 11, 2017 by Cibit

[dburne]

Anyone got a solution to not being able to click "OK, CLOSE or FLY AGAIN" in the mission debriefing window while using Rift?

 

My Vr settings are set to 'Use mouse'. I can click on everything in the startup menu but the briefing windows dont seem to work with the mouse clicks.

 

Frustrating!

 

You need to be running in true full screen to be able to easily access all the clickable options in the menu.

At this time true full screen requires ALT+ENTER.

I always make a point to hit that first after launching DCS and getting to the menu screen.

[freehand]

I do not have a problem with menu options and do not use the ALT-ENTER anymore for me the performance is a little worse if I go full screen the manual way.

 

Not sure why but a dcs is good on the off now.

 

I have changed 2 things tho upgraded windows 10 creators edition and replaced my rog-swift monitor for another.

 

edit: I have never had a problem with the menu selections even before.

Edited April 13, 2017 by freehand

[Mango]

I've noticed that you need to look squarely at what you're trying to click. i.e. the mouse cursor should roughly be in the center of your view, otherwise clicks are not registered.

[vortexringstate]

You need to drag your desktop taskbar to the right vertical as it conflicts with the lower buttons in DCS

 

That did it! The task bar must have been screwing things up! Thanks a bunch!

[Kayos]

You need to drag your desktop taskbar to the right vertical as it conflicts with the lower buttons in DCS:)

 

Yes, this is very annoying. Hopefully they can fix this one day.