DerekSpeare

This is a good fix for the "dancing and shimmering" trees. I still have a few that have not been fixed, but most of them look much better :thumbup: Does ED plan to fix this? The hit to the frame rates is :( and :music_whistling:

Using the following resolutions/Pixel densities: 1.0 = 2160 x 1200 1.5 = 3240 x 1800 2.0 = 4320 x 2400 You would be rendering: 2,592,000 pixels = 1.0 5,832,000 pixels = 1.5 10,368,000 pixels = 2.0 Even with three screens at 5760x1080 you're only rendering 6.22 million pixels. I'm finding that 1.5 gives me the best performance in SP with minimal ghosting.

If Oculus knows what's good for them they will have their shelves filled with ample supply in order to meet the holiday demand that's coming... Congrats to those who are receiving their CV1's! :thumbup:

I'll take it anyhow! :thumbup:

Works like a champ - I didn't know this was possible to turn it off. Thank you! It would be cool in the future to have the cockpit mouselook feature to OFF and external cams to ON if that can happen.

I have discovered some oddness in planes without clickable cockpits. It seems that if we want to turn off the mouselook from within the cockpit we then loose that function in external views as well. This is not the best way to do it, in my opinion. The two features should not be mutually exclusive. I want to keep my mouselook-with-zoom for external views but I don't want it in planes without clickable cockpits.

Dat's a hellagood hw combo...what's your Oculus pixel density?

Thank you :D :thumbup: It does work and it does make a difference. I get a HUD that's almost "crisp" to read with 2.0 but the hit on frame rates is too much for me. I run it at 1.5 and live with the balance.

It appears to be evident in all of the birds. An improvement would be to resize the box to the space necessary to accommodate whatever text is being indicated. It would be prudent to enlarge the text to a degree to make it more legible and use a font/color which has a greater contrast.

I use Notepad++ to edit the LUA files, FWIW.

I'm finding that my saved eyepoint positions are not getting saved when I exit out of DCS and start a new session. This was in v2 and in the v1.5 beta. I do not have the issue with the other v1.5 version.

Another VR REquest: Please make the tooltip text larger and automatically resize the box in which it appears automatically resized to the amount of text contained within it.

Is this accomplished by using the method I describe here: http://forums.eagle.ru/showthread.php?t=164892 If yes, how do we hold the views to the left and right when making the adjustments? If no, where do we change the camera angles? Thank you!

I am getting this exact same issue with the SU-25T.

Update for the head tracking in VR: The head tracking works fine for the out-of-cockpit views. Get in the plane and lateral and forward/backward views are not right. The much larger VR text for radios is MUCH appreciated!

Update for the head tracking in VR: The head tracking works fine for the out-of-cockpit views. Get in the plane and lateral and forward/backward views are not right. The much larger VR text for radios is MUCH appreciated!

Cheers, Bast! That's a great workaround! +1 rep to you! I don't know where to look to decouple the mouse from the view...I need to hunt for it.

What exactly are the files to be edited and where precisely are these files located? I do not know all the places DCS files are stored. The mouse look REALLY must be decoupled from the cockpit view for non-clickable planes using VR. It's REALLY disorienting.

It's in my post here: http://forums.eagle.ru/showthread.php?p=2821108#post2821108 Thank you :thumbup:

I doubt that...especially after the press attention it is getting. They'd lose serious face by admitting such a mistake, more face than they've lost all along...though they may not care any longer. I don't it's an error...strange way to do it, though...they could have gotten positive press by saying, "you know guys...we love you...we see that it's not the best for our fans to be so restrictive...so we killed that and here you go...aren't we great!"

BUG 1 Clicking the gear and then the OK button when making the changes to the graphics and all menu interfaces are gone. Running a bare installation of the Beta just installed new today. BUG 2 Front-to-back head tracking is borked in the SU25T in the cockpit. Issue not evident in the v1.5 stable release or alpha. Issue is not present in the menu/hangar screen. I can supply whatever you need. Logs.zip

I am. It's a bug...I want to change the settings and click ok but doing that causes the menu to vanish entirely. Head tracking is off as well in the plane.

Thx Enduro and SkateZilla - rep inbound! The v1.5 beta VR menu interface is seriously FUBARed - click the gear and then the OK button when making the changes to the graphics and all menu interfaces are gone. Front-to-back head tracking is borked in the SU25T in the cockpit. Issue not evident in the v1.5 stable release or alpha. Issue is not present in the menu/hangar screen. More bugs to come when I find them.

Is there an easy way to copy all of my controller settings from the v1.5 Stable Release to the Open Beta v1.5 release? I am just installing v1.5 beta today...been using the stable version all along. BTW, I'm getting a sweet 85mb/s d/l speed so hopefully this will keep quiet for another few mins :D

News??? It may be that Oculus removed the HMD verification check from the latest runtimes: https://github.com/LibreVR/Revive/releases/tag/0.6.2 http://arstechnica.com/gaming/2016/06/oculus-reverses-course-dumps-its-vr-headset-checking-drm/ It would mean, then, that ReVive runs again with the Oculus Store. If this is the case, and it appears it is, then that means that this Razer HDK2 may work with the Oculus store and other Oculus titles...with work, of course. My biggest concern for the Razer HMD is that it has to have some type of ATW for it to be even worth considering for my own use.