Oculus Rift and DCS World Discussion

[ReviZorro]

once again ' date=' sorry for broken weekend ( bad idea compile something on friday night )[/quote']

It almost fixed now :)

Big thx!

Спасибо!

[Kegetys]

once again ' date=' sorry for broken weekend ( bad idea compile something on friday night )[/quote']

 

It runs now but it seems only slightly improved from the version in the beta; The image still does not cover the entire visible area and it looks like the render target is not scaled to the correct size.

 

Also the IPD seemed wrong, and I tried adjusting it from the Oculus config utility but it seems to have no effect on it - I guess it is using some static IPD?

[Alex Okean]

IPD is given by Rift API as warping data too

[Frusheen]

I think the IPD might be correct but the images are still not filling the rift display (black borders). The presence of these borders may be causing the perceived IPD issue as the two images are not rendering on the full screen.

 

Alex it's really close to being perfect. Warp and scale look good and only minor yaw drift on DK1. It needs tweaking to have the image fill the rift screen. Is it also pulling this info from the rift API?

[Alex Okean]

I am not sure about what you means as "black borders" cause they will always be there because of lenses presence. May be you setup wrong lenses which does not correspond with rift settings

[SkateZilla]

The First Devkits have a Different Aspect Ratio than the other Kits.

 

Can you take a screenshot of the image, then draw a line depicting what you see and what's bordered?

[Kegetys]

The difference is visible here (DK1):

http://junk.kegetys.fi/oculus_dcs.jpg (DCS beta with the new visualizer.dll)

http://junk.kegetys.fi/oculus_tuscany.jpg (Oculus SDK Tuscany demo)

 

There is a large black border in the DCS image - It looks like the required scale factor is not applied to the render target, or the warping parameters are not right.

 

edit: I had a look with GPA and it looks like DCS is using a 1280x800 rendertarget which is not right - The needed scale factor for DK1 is something like 1.7 so it should be around 2176x1360, I guess that is the problem.

Edited April 8, 2014 by Kegetys

[ReviZorro]

The difference is visible here (DK1):

http://junk.kegetys.fi/oculus_dcs.jpg (DCS beta with the new visualizer.dll)

http://junk.kegetys.fi/oculus_tuscany.jpg (Oculus SDK Tuscany demo)

 

There is a large black border in the DCS image - It looks like the required scale factor is not applied to the render target, or the warping parameters are not right.

I have similar picture, but I don't see any borders. Strange.

 

Upd: My Tuscany demo looks less wide - and I don't see any borders...

 

And how to make a screenshot in DCS with OR? (standart method (SysRq) gives only a copy of desktop).

Edited April 8, 2014 by ReviZorro

[Kegetys]

Upd: My Tuscany demo looks less wide - and I don't see any borders....

 

Are you using the demo from the latest SDK version? Under samples\OculusWorldDemo\Release\OculusWorldDemo.exe. (Oculus website seems down now but I downloaded mine just a few days ago and I dont think there has been any updates to the public SDK for a while).

[Alex Okean]

recomended scale factor has nothing with black borders cause borders is conected with recomended FOV , installed lenses and nose-to-screen distance . scale factor is intended for optimal pixel density in the screen center

[Kegetys]

recomended scale factor has nothing with black borders cause borders is conected with recomended FOV ' date=' installed lenses and nose-to-screen distance . scale factor is intended for optimal pixel density in the screen center[/quote']

 

The scale factor is taken into account by the distortion shader, so if the scale factor is not applied correctly it will render a smaller area (see section 5.5.3 "Distortion scale" in the SDK docs). When you apply the scale factor correctly the image fills almost the entire screen, as also shown in the docs images (I guess it also makes the required FOV wider though?).

[Alex Okean]

guys i am under NDA , but we use a slightly newer SDK than you can find , where core things are changed

[ReviZorro]

Are you using the demo from the latest SDK version? Under samples\OculusWorldDemo\Release\OculusWorldDemo.exe. (Oculus website seems down now but I downloaded mine just a few days ago and I dont think there has been any updates to the public SDK for a while).

You're right, I used an older version. Picture from SDK 2.5 is similar to your screenshot.

 

What type of lenses (A, B. C) do you use? What is the distance to the OR screen (far or close)? Do you wear a glasses? (My case - lenses B, close to screen, no glasses).

[ReviZorro]

BTW, it is still possible to get 6DOF with Opentrack and Razer Hydra.

Edited April 8, 2014 by ReviZorro

[SkateZilla]

You're right, I used an older version. Picture from SDK 2.5 is similar to your screenshot.

 

What type of lenses (A, B. C) do you use? What is the distance to the OR screen (far or close)? Do you wear a glasses? (My case - lenses B, close to screen, no glasses).

 

BTW, it is still possible to get 6DOF with Opentrack and Razer Hydra.

 

I guess you missed the part where he said N...D...A...

[blksolo]

So WITH the new .dll added I realize that when I said my rift was working fine earlier that it wasnt. It definitely works now,scale is perfect,totally awesome experience. All we need is better definition on Oculus part and this will be insane!! Btw the frosted side window on the Huey should be removed,you cant see out of it in the rift.

[KaspeR32]

I guess you missed the part where he said N...D...A...

 

I'm pretty sure they are having a conversation about the SDK THEY(not Alex) are currently using.

Edited April 8, 2014 by KaspeR32

[ReviZorro]

I guess you missed the part where he said N...D...A...

Ok, question was asked for Kegetys (I know, what this name meant to community, but, AFIK, he is not in ED team).

 

And as for the Razer Hydra - it was not a question, but a statement ) So I'll use the Hydra for 6DOF with native OR support.

[SkateZilla]

Ooops, Sorry, My mistake... proceed as normal.

[KaspeR32]

I actually still get just a black screen when I try to run DCS with "Auto Detect Oculus Rift" setting enabled. If I un-check that, I can put the monitor settings to "Stereo" and I get a picture on the screen (although it's all skewed)

 

Does the new .dll fix that also, or just the skewing?

[blksolo]

Not sure,but the new dll definitely fixed immersion and scale for me.

[blksolo]

So I dont know if any of you guys have tried this,if you havent shame on you!!! I just put on my trackir 5 and rift and guess what. I got 6DOF!!! I'm talking readible instruments and everything!!! Now the bad news,I never could get trackir to work right,jitters all over the place,loses track etc. But I'm thinking one of you guys with a good profile/environment could give it a try and provide some feedback.

[average_pilot]

Been there, done that. :) You should look at this blog: http://thecodinglove.com Maybe you'll find it as funny as I did...

I don't remember the last time I laughed so loud for so long. It feels great :thumbup:

[Frusheen]

For those of you wishing to read the radio menus while in the rift don't forget to check out this fantastic mod from PeterP: http://forums.eagle.ru/showthread.php?t=76225

 

I have configured my radio menu to 170% and it is now in the centre of the rift screen (set vertical offset to 300 and horizontal offset to -350). You can also click on the commands rather than use the keyboard. All credit to Peter for this fantastic mod. As this is a beta rift implementation it is not advised to install mods. I have found no issues with it so far but use at your own risk!

[blksolo]

I just did a bombing run and looking behind me and watching the bombs explode was unreal!!