Jump to content

Recommended Posts

C6_lefuneste
Posted (edited)

Hello,

I purchased some time ago an HDK2 in order to support the opensource approach.

Despite some tracking problem I used it without trouble in DCs world and War thunder, with SteamVR.

So I was really happy to be able to get back to IL2BOS. All was OK in the hangar, but  I was very disapointed to see that, when in cockpit, the view was deformed (all object have a vertical size far greater than it should be) and also that when turn my head along X axis (the virtual axis going from your head to the screen) the image is shifting instead rotating...

Why this kind of problem occured only with IL2Bos ? Did you implement VR in a other way than DCS or WT ?

Edited by lefuneste
  • Upvote 1
Posted (edited)

I am also experiencing this issue with the HDK2. The apsect ratio is incorrect. The image is compressed in the horizontal axis so turning your head skews the image dramatically which is extremely disorienting. It's not playable at all. It's sad because otherwise the performance is great. Head and shoulders above DCS.

 

I have tried both today's SteamVR build and the beta build. I also have up to date GPU drivers and device firmware. Running in direct or extended mode makes no difference with the issue. Other SteamVR titles are working just fine.

 

System:

AMD R7 1700 4Ghz

AMD RX 470

16GB DDR4 3200

Win 10 x64

Edited by bejeavis
  • Upvote 1
Posted

Please note I am having the same issue on my Pimax 4K which is essentially recognized/the same as a DK2 from my understanding. This effect is most pronounced with vertical head movement there are severe distortions of clouds and cockpit frame when doing this. I thought to myself it appears like the FOV/ head position is wrong. Hopefully the fix is obvious and easy since this effect will probably be near impossible to catch on camera. 


 


I completely agree with both above it is unplayable currently. I have confirmed no such effect at all is DCS 109K. Fix this soon please as the performance does seem much better than DCS. 

Posted (edited)

1CGS for VR utilizes Open VR currently for running BoS in both the officially support Rift CV1 and HTC Vive.

 

Official support by Oculus for the Rift DK2 ( Developer Kit ) ended in March 2016. As time progresses more and more VR games are going to be tougher to run in the DK2 if at all. I see it more and more over on the Oculus forums. Many are trying to find and keep older runtimes just to get the device to work with some more current games.

 

Pimax uses Open VR as well for the software to run their device, same software 1CGS uses for BoS in VR.

Obviously it works in some other games, so it can work. Not sure if users have to do any configuring of their own to get it to run for them or not.

But I am not sure this would really be on 1CGS. They wrote their software to run on Steam VR. Obviously it does run well for the most part.

 

I could be looking at this wrong, but it would seem to me to perhaps be more in Steam VR's court, or maybe even Pimax.

I know with the Rift at times there are some game updates through Oculus software that brakes the game in VR, and Oculus goes in maybe along with developer to get it addressed and resolved...

 

Have you also checked to make sure you have the latest firmware for the Pimax?

Edited by dburne
Posted (edited)

Confirmed this distortion is showing in both HMD and on Standard PC window screen while in game. Here is the steam mirror capture. 

 

 

 

Since its showing this distortion outside of headset I am sure it should be fixed without too much problem. Elite Dangerous, Project Cars, DCS, etc all working flawlessly on latest FW of Pimax. 

Edited by LonnyEnds
Posted

I tried it today. Works with Oculus DK2...But....My head is about two-feet outside (above) of the cockpit. How do I get back inside the cockpit it reset the viewpoint?

 

Basically to get it working in DK2:

 

Turn on computer.

 

Make sure Oculus is plugged in.

 

Launch Oculus software

 

Click '"Settings"

 

Click "General"

 

Click "Allow other sources"

 

Launch Steam

 

Click on the Steam VR tab

 

Click set up room

 

Go through the onscreen setup

 

Steam VR should then turn green and say ready.

 

Launch BoS

 

Go into settings/graphics and then click turn on VR HDM

 

Restart BoS.

 

Place on Oculus

 

Enjoy

 

 

Looks great and very impressive, especially watching burning aircraft as you fly past them

 

Had an issue with BoS not recognising my joystick, seems it was setting my Simpeds as Joy_0 and all my config for the Cougar is Joy_1. So been a pain reconfiguring the joystick. Now the issue is BoS won't recognise the full range of the throttle....So frustrating!

 

Anyway, Oculus is very impressive....But BoS controls and interface are doing my noodle in a bit

 

Cheers, MP

Posted (edited)

Thanks for that clear input could you comment if you had this distortion before you did the room setup? I will see if these steps work with Pimax. 

 

Re set up my room no difference. 

 

Here is PC screen capture: 

 

 

Edited by LonnyEnds
Posted

I tried it today. Works with Oculus DK2...But....My head is about two-feet outside (above) of the cockpit. How do I get back inside the cockpit it reset the viewpoint?

 

 

Have you assigned reset VR View to a button?

 

It is listed as " Default VR View" under the Pilot Head Control tab.

C6_lefuneste
Posted

Official support by Oculus for the Rift DK2 ( Developer Kit ) ended in March 2016.

 

I'm not using an Oculus DK2 but an OSVR HDK2...

I had the following lines in startup.cfg:

 

    or_enable = 1

    or_height = 1920

    or_hud_rad = 1.50000

    or_hud_size = 0.75000

    or_ipd = 0.06300

    or_width = 3456

 

I did not understand the values _height and width. I tried to change them, but it does nothing and they went  back to their values...

Do you have the same lines ? Are they the same for Rift or Vive ?

Posted

I'm not using an Oculus DK2 but an OSVR HDK2...

I had the following lines in startup.cfg:

 

    or_enable = 1

    or_height = 1920

    or_hud_rad = 1.50000

    or_hud_size = 0.75000

    or_ipd = 0.06300

    or_width = 3456

 

I did not understand the values _height and width. I tried to change them, but it does nothing and they went  back to their values...

Do you have the same lines ? Are they the same for Rift or Vive ?

 

Here are mine. I am running the Rift CV1.

 

or_enable = 1

 or_height = 2384

 or_hud_rad = 1.50000

 or_hud_size = 0.75000

 or_ipd = 0.06539

 or_width = 2000

Posted

Here are mine. I am running the Rift CV1.

 

or_enable = 1

 or_height = 2384

 or_hud_rad = 1.50000

 or_hud_size = 0.75000

 or_ipd = 0.06539

 or_width = 2000

 

 

Mine with Pimax 4K 

 

or_enable = 1
or_height = 3328
or_hud_rad = 1.50000
or_hud_size = 0.75000
or_ipd = 0.06400
or_lens_offs = 1.00000
or_width = 1872
 
So at least for my case it looks like the aspect ratio is way off/ is in Portrait mode somehow. There was a similar issue with DCS at one point I will try changing these values and investigating further this weekend. 
Posted

Ok guys after some investigating I have made a bit of progress. It appears the startup.cfg Is getting its values from Steam VR. If you change supersampling level and start IL2 then exit the numbers in startup will change. My numbers above make sense since I had Supersampling set to 1.3. The native resolution being 2560x1440. This solves the mystery of why changing the startup file has no effect. The question is now, is there a way to manually configure Steam VR resolution/ change the aspect ratio. In my case I am at 16:9 which I wouldn't think would be so distorted but it is. I am going to try some different versions of Pimax software to see if I can get better results. Unfortunately supersampling affects both width and height equally. If we could set a custom resolution or set supersampling for each separately we could correct this issue.   

Posted

I submitted a ticket through Steam under SteamVR's page. Hopefully they will take a look at it. OSVR is listed as officially supported for this title so they should. Other folks having this issue should also submit tickets.

  • 3 weeks later...
Posted

Was anybody able to sort this out?

  • 1 month later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...