Frusheen

Heliking I think you should try Skatezillas method. I removed and redownloaded my 1.5beta twice as I had a very early beta installed which would not show in the rift after updating. When reinstalling it pulls a lot of files from my 2.0 install rather than redownloading them. Both times the rift was still not being detected. When I copied and converted my 1.5 release version to beta it finally worked. I suspect something is different in the oculus implementation between 1.5 and 2.0 which is not being updated by the installer or is being installed incorrectly.

I am having the same problem. Grass is flashing and ghosting at low level in VR. This is not the same as the texture flashing in the peripheral of the rift FOV. It's in the entire field of view and clutter/bushes has to be set to 0 as a result or else it makes low level flying in helicopters etc very nauseating in VR.

Never suffered from it but the best advise I've seen is to NOT try and play through it. Play in short sessions and take a break. If you get really bad sickness from VR even the thought of putting on the headset can make you sick the next time.

00031.214 ALERT LUACOMMON: Error: GUI Error: [string "./MissionEditor/modules/Options\Data.lua"]:384: attempt to index field 'VR' (a nil value) GUI debug.traceback: stack traceback: [C]: ? [string "./MissionEditor/modules/Options\Data.lua"]:384: in function 'getVRChanged' [string "./MissionEditor/modules/me_options.lua"]:97: in function 'onChange' [string "./dxgui/bind/Button.lua"]:22: in function 'callback' [string "./dxgui/bind/Widget.lua"]:310: in function <[string "./dxgui/bind/Widget.lua"]:305> Looks like you added the lines to the wrong file or saved it in the wrong place.

What does your log file say?

Sounds like you are adding them wrong. Are you using notepad++ to edit the lua file? Have you checked your log file under saved games/logs to check the cause of the crash?

Having really weird issue with my 1.5 beta install. 1.5 release and 2.0 work fine in VR. Yesterday I uninstalled my beta version due to a corrupt update (I still had the separate multiplayer icon for some reason and my rift was not being detected unless I launched from that icon). I uninstalled and removed all traces of the beta from my program files and saved games folders. I downloaded the latest beta installer. Installed the beta and it still does not detect my rift! I tried repair several times. The sim runs fine. Shows the latest version number but my rift stays off (yes VR is enabled in options and the options lua has been fixed). I think it must be something to do with files which are being pulled from my 1.5 or 2.0 installations. Both of those have no mods enabled and run VR fine yet I can't think what else could cause this. Is there a way to install 1.5 beta so it does not pull files from existing installs and downloads the entire thing clean? Or is there anywhere other than program files and saved games where remnants of the old installation could persist after uninstalling?

The problem is due to missing parameters in the options.lua. The fix was posted yesterday by SkateZilla in the relevant thread. http://forums.eagle.ru/showthread.php?t=169019 Guys let's use the VR bugs section to post bugs. Everything mentioned here has its own specific thread in that area of the forum. This thread should be closed.

Skewed tracking caused by corrupt values in Views.lua The VR headtracking is off in the latest beta. The cause seems to be values other than zero introduced into the default view section of the views.lua file for each aircraft. Editing the views.lua corrects the issue. Similar issue posted by trackIR users.

The terrain clipping issues which are listed as fixed in the open beta changelog persist. I still have textures popping in and out on the periphery of my vision.

The fix is given in this thread. You need to add a few lines to your options.lua file. http://forums.eagle.ru/showthread.php?t=169019

It is not working in the beta yet. Use joy2key or similar as a work around for now. Edit: my mistake. The recentering key is now working. It is in the UI assignments menu and is no longer num5.

We have a new VR bugs section for the beta. A fix for the issue is posted here: http://forums.eagle.ru/showthread.php?t=169019

Derek see here for a fix to the view tracking. http://forums.eagle.ru/showthread.php?t=169026

edit: wrong thread.

I have a clean install Skate so this issue seems to be introduced by the beta update.

Can confirm editing the Views.lua for the gazelle has fixed the issue I was experiencing with it in the rift.

You can get around it. Read back a few pages. It's working fine for me now.

VR request following today's beta update: - please make the crosshair disappear when it is not over an active switch or click spot when using head as pointer.

Reported the tracking issue here while we wait for a VR bugs section: http://forums.eagle.ru/showthread.php?t=169026 It seems the issue also exists for trackir users

Same issue in oculus rift. Causing serious nausea.

Thanks SkateZilla. My issue with beta and VR pre dates the latest beta release. I reinstalled tonight and the issue persists. After reinstalling (I didn't redownload the installer) I get two beta icons one standalone, one multiplayer. VR will not work with the standalone icon but it does with the multiplayer icon. I have no issues in 1.5 release or 2.0 alpha. Didn't 1.5 do away with the multiplayer icon? I think I need to redo beta from my 1.5 release version.

Headtracking is no longer 1:1 with head movement. It's hard to tell if it's a warp issue with the rendered image or if there is crosstalk in the head movement axis. Either way it results in the view appearing to distort as you look around in cockpit. Very noticeable when looking left and right in the gazelle (the view also moves up and down). I need to test with other aircraft yet.

I can't get the open beta to run in VR mode at all. Currently reinstalling. Check the previous page for a link from Skatezilla for issues with today's beta release.

I was joking :music_whistling: Exiting the VR menu in non VR mode cause the screen to go black. I have to kill the application.