Request for official statement from ED for Oculus Rift CV1 to run

[TOViper]

Hi ED,

 

 

which version of Oculus software does 2.5.6. officially need?

I personally can provide Oculus Home 1.3 and 1.7, but nothing higher.

What do you need me to install in order to get 2.5.6 running?

 

THANKS and kind regards,

TOViper

[Magnatilla]

+1000

 

I have a slow internet connection, downloading the latest patch each time only to find it won't pick up the CV1 and then rolling back is a bit of a labour of love.

 

An official statement on this would mean I can wait to see if there's a fix or just not bother with 2.5.6 on wards.

[fitness88]

I'm running 2.5.6 on:

 

Oculus App Version 13.0.0.280.463 (13.0.0.280.463)

[Magnatilla]

Thanks for chipping in fitness88, but I think what we're trying to establish from ED is if they have switched to only supporting the new API for Oculus.

 

If they have switched to a new API, users like me are stuck at nothing newer than 2.5.5. (so no new modules that are not backward compatible to 2.5.5) :mad:

 

If it's a bug we can look forward to enjoying the future of DCS when it's fixed. :thumbup:

[dburne]

Thanks for chipping in fitness88, but I think what we're trying to establish from ED is if they have switched to only supporting the new API for Oculus.

 

If they have switched to a new API, users like me are stuck at nothing newer than 2.5.5. (so no new modules that are not backward compatible to 2.5.5) :mad:

 

If it's a bug we can look forward to enjoying the future of DCS when it's fixed. :thumbup:

 

I may be missing something in this statement, but is not the Rift Software using the same API across the board whether one is using Rift or Rift S?

[Magnatilla]

Hi Don, my thoughts are that maybe the new runtimes for newer versions of Oculus (home) have a matching newer SDK/library linked when the DCS code is written/compiled.

 

That's all I can think of as the headset is not detected in any way, even when forcing VR on the DCS command line, I would expect head tracking to work if the display is not enabled (from previous coding on Oculus stuff, admittedly a while ago).

 

But nothing. hope that makes sense?

 

I really do hope it's a bug but only ED can really let us know on this.

Edited February 25, 2020 by Magnatilla
spelling

[A2597]

why can you not update Oculus?

I use CV1, never had an issue?

[Baldrick33]

why can you not update Oculus?

I use CV1, never had an issue?

I think they want to run an older version that doesn't load Oculus Home or simply not want to upgrade it for other reasons
Edited February 25, 2020 by Baldrick33

[Magnatilla]

why can you not update Oculus?

I use CV1, never had an issue?

 

https://forums.eagle.ru/showpost.php?p=4216284&postcount=12

 

Also saw the threads on Oculus firmware update bricking your headset if you're on Win7.

 

:(

[TOViper]

I think they want to run an older version that doesn't load Oculus Home or simply not want to upgrade it for other reasons

 

True. Windows 7 and Oculus 1.30 mini-version here.

I am currently trying to finally find the heck out which version of Oculus runtime is needed for DCS 2.5.6 to run.

That's all I wanted to know from ED, but so far NO WORD of them!

[Goblin]

True. Windows 7 and Oculus 1.30 mini-version here.

I am currently trying to finally find the heck out which version of Oculus runtime is needed for DCS 2.5.6 to run.

That's all I wanted to know from ED, but so far NO WORD of them!

 

Using Win7 you are below the recommended system for VR... Why not upgrade to Win10 and newer Oculus runtime?

[Svsmokey]

I too was reluctant to switch to win 10 , as i really liked the win 7 layout , and was concerned about win 10 data collection . However , i find win 10 pro offers all i need to control privacy settings and updates , and i have adjusted to the 10 gui . And it allows me to fly the Rift :)

[TOViper]

I too was reluctant to switch to win 10 , as i really liked the win 7 layout , and was concerned about win 10 data collection . However , i find win 10 pro offers all i need to control privacy settings and updates , and i have adjusted to the 10 gui . And it allows me to fly the Rift :)

 

Thanks for your kind words.

A few days ago I decided to switch to Windows 10 pro.

 

Generelly speaking now, everything is working, but in DCS the picture is wobbling around when frames come down (the real frames) in the area of 45. I never saw that in W7, and the VR picture is not that clear as it was in Windows7. Artefacts here, wobbling there ... you know.

I miss the clear picture of W7, but on the other hand ASW works pretty fine under W10, and it produces the same "smootheness feeling" with real 45 frames, than it was in W7 with "original" 90 frames (in W7 I only had 90 frames with the Tiger, on a more or less empty maps.

 

So, yes, I am on Windows 10 now.

Honestly speaking I was impressed of the updater program. After updating, everything (100%) on my desktop was like in Windows 7. That is stunning, and I have to agree that Microsoft has done a good job on this.

Edited March 24, 2020 by TOViper