[REPORTED] latest update - Oculus Rift Issues

[eaglecash867]

Sorry to disagree, but, yes you can know for sure you have completely removed a mod. Do you know how OvGME works? It backs up the files replaced by a mod when enabling, and reinstates them when disabling.

Before doing any DCS update, my standard procedure is run OvGME, disable all mods, run repair (just to check), run update, run DCS to check how things are running, then run OvGME and enable all mods.

Now, in the case of the shaders mod, things are more complicated. There are a couple of additional steps, i.e. emptying the dxo and metashaders2 folders as well as renaming the DCS folders within the mods\terrains\xxxx\misc\metashader folders, but it’s all set out in the readme file.

 

Actually, it looks like we're in agreement. You still have the same issues with yours that I do, right? I hadn't been following "standard prodecure" with previous versions of the Beta, and never had issues. The only thing I had ever had to do, was repeat the steps for INSTALLING the mod AFTER the update. Never had to remove it prior to an update. That may be wrong, but regardless of that, it had never caused problems. Also, if the shaders mod requires extra steps, beyond using OvGME. that says, right there, that OvGME, in fact, does NOT get everything. :smilewink:

 

Anyway, as I stated in my previous post, this was a logical troubleshooting step for me, since I had been forced into a situation where it had to be attempted. It didn't work, and I informed everybody of my findings. I have the problem, you have the problem, lots of others have the problem, we're all scratching our heads.

 

The thing that seems to be working for all of us, including you, is to revert to a previous version. That's something that I haven't done yet, but I also have the release version installed, so I just went back to playing that until the Beta gets fixed. Flew a Persian Gulf mission on the release version last night, and it worked beautifully.

[eaglecash867]

With ASW on, I get of course the swirly gun-sight recticle and also blurring of planes ( like double image) as they fly by. With ASW off I do not get that, even if fps is down to 45. I can not explain why that is, it is just a better experience for me.

 

Now after this past week's update, I assumed ASW is not working for me either - I did some testing with ASW on, and while my fps would be locked at either 45 fps or 90 fps as one would expect it to be with ASW on, I did not get the blurring as planes flew by or squiggly gun-sign recticle. But it was still smooth for me.

For whatever reason on my particular system, I seem to have a better experience overall with ASW set to off. I have been running it that way for quite some time.

 

Don, just curious. How many sensors do you have for your Rift? Just wondering because, up until a few weeks ago, I only had one, but now I have two. Just throwing that out there as a possibility.

[dburne]

Don, just curious. How many sensors do you have for your Rift? Just wondering because, up until a few weeks ago, I only had one, but now I have two. Just throwing that out there as a possibility.

 

I have two sensors.

[eaglecash867]

OK, well, I guess that rules that out. Thanks Don.

[Raven (Elysian Angel)]

I just tested 2.5.3.21153. Same problem still: everything's blurry and flying around is nauseating.

 

Thank you ED, for the speed at which you push out Hotfixes, but I'm afraid there's still work to do...

[imacken]

Also, if the shaders mod requires extra steps, beyond using OvGME. that says, right there, that OvGME, in fact, does NOT get everything. :smilewink:

 

As I said, the shaders mod requires some extra steps to enable/disable. All described in the readme.

If you don’t disable the mod, you’ll have some redundant folders at best, e.g. your renamed folders during the mod install, and replacements for them during the DCS update.

What you said was we can’t be sure that ‘removing a mod is getting all of it’. I’m saying yes you can, and OvGME is a great tool that ensures that any files you changed are replaced with the originals when you disable the mods.

Just because you don’t see any problems by not disabling mods before an update, doesn’t necessarily mean it’s the right thing to do. By ensuring you disable all mods before any DCS update is good practice, and ensures you have a clean install to update.

[slyly666]

I just tested 2.5.3.21153. Same problem still: everything's blurry and flying around is nauseating:(:(:(:cry::cry::cry: please to fix soon for oculus rift thank you

[RePhil]

I still have same issues as before Hotfix 2 so back to my no fly zone

[eaglecash867]

As I said, the shaders mod requires some extra steps to enable/disable. All described in the readme.

If you don’t disable the mod, you’ll have some redundant folders at best, e.g. your renamed folders during the mod install, and replacements for them during the DCS update.

What you said was we can’t be sure that ‘removing a mod is getting all of it’. I’m saying yes you can, and OvGME is a great tool that ensures that any files you changed are replaced with the originals when you disable the mods.

Just because you don’t see any problems by not disabling mods before an update, doesn’t necessarily mean it’s the right thing to do. By ensuring you disable all mods before any DCS update is good practice, and ensures you have a clean install to update.

 

So, semantics aside, are you having the same problems with blurriness in the Beta as most of us, or aren't you? :music_whistling:

[Zarma]

Did you guys try to delete the FXO and Methashader2 folders ?

[imacken]

I just tested 2.5.3.21153. Same problem still: everything's blurry and flying around is nauseating:(:(:(:cry::cry::cry: please to fix soon for oculus rift thank you

 

Really disappointing. I had high hopes for hotfix 2. Never seen an update on a Sunday before!

[dburne]

Really disappointing. I had high hopes for hotfix 2. Never seen an update on a Sunday before!

 

Yeah kudos to the team for at least trying to get something out over the weekend.

I am grabbing it now - I have not had these issues so hopefully that will still be the case for me after this hotfix2. Will know soon.

 

Edit: Just checked the posted changelog, it really doesn't say anything about the VR issues in this hotfix2.

[Aries]

Tried in .21153, still blurry when looking right on ground or objects and rolling aircraft...

 

GTX1070, Oculus Rift

[eaglecash867]

Yup, Zarma, did that too. While testing the latest beta to see if I had the same problems as everyone else, I even ended up screwing something up so badly that I had to completely remove the 2.5.3 beta and do a fresh install from the DCS download page. Even with a fresh install and clear fxo and metashader2 folders I still have the issue. I also noticed that the first time I tried running the updated beta, before the reinstall, SteamVR was somehow getting triggered to start up. I haven't used SteamVR in months because I currently don't run anything in it. But, for some reason, when I'd start DCS, it would try to load. I have since removed SteamVR altogether, and still have the feeling of being drunk in the cockpit. GUI and mission planners seem to be fine, its just when you enter the cockpit that things go screwy.

[eaglecash867]

Yeah kudos to the team for at least trying to get something out over the weekend.

I am grabbing it now - I have not had these issues so hopefully that will still be the case for me after this hotfix2. Will know soon.

 

Edit: Just checked the posted changelog, it really doesn't say anything about the VR issues in this hotfix2.

 

Don, should the latest hotfix be trying to download and install when I start DCS like usual? Mine doesn't seem to be doing that.

[imacken]

Don, should the latest hotfix be trying to download and install when I start DCS like usual? Mine doesn't seem to be doing that.

Try using Skatezilla's Update Utility. Much better at getting updates than the standard DCS startup I have found.

[imacken]

Yeah kudos to the team for at least trying to get something out over the weekend.

I am grabbing it now - I have not had these issues so hopefully that will still be the case for me after this hotfix2. Will know soon.

 

Edit: Just checked the posted changelog, it really doesn't say anything about the VR issues in this hotfix2.

I couldn't resist trying it anyway, and yep, no change. Still all the same issues. Back to 2.5.2!

[dburne]

Just had a nice flight over Normandy in the Spit, all seems to still be well on my end so far with Hotfix2.

[yeager]

No ASW so getting the multiple vision thing when moving my head, and my computer locks up now when trying to exit the game.

 

The game does not seem to respond to any of the Oculus keys for ASW, control 1, 2 or 3.

 

 

Does anyone still experiencing such VR problems?

[AcroGimp]

Tried latest hotfix and still same issue for me, even setting menu to lowest possible resolution.

 

Gets halfway through loading page, Core 11 goes to 100% and then hung, Ctrl-Alt-Del only way out.

 

VR is completely INOP.

 

Latest Oculus Beta Core, patched Thursday/Friday, latest Nvidia drivers.

 

Could ED have accidentally used an older Oculus API?

 

'Gimp (DISCO vVMFA-122)

[Ala12Rv-Tundra]

Waiting, waiting. Time to read manuals lol

[imacken]

Does anyone still experiencing such VR problems?

 

Amongst others https://forums.eagle.ru/showthread.php?p=3614476#post3614476

[D4n]

100% core load, sounds like race-condition/memory-leak in the VR-mode-code.

[yeager]

Really disappointing. I had high hopes for hotfix 2. Never seen an update on a Sunday before!

 

Same here. Grounded for now.

[D4n]

Why, the game is NOT crashing, so it IS "playable", right?