Jump to content

Recommended Posts

Posted

Hi Guys,

I just received my Odyssey + and followed the instructions I could find in these threads.

 

 

I tried everything I could but the image is fuzzy all over. The cockpit panels are fuzzy and all switches.

 

 

 

I thought only the text would be an issue but so far no fix.

 

 

My system I7 ASUS Rogue HeroIX overclocked, vid card 1080 oclocked.

 

 

Shimmering I can understand and the text not fully clear but I'm troubled by the fuzzy panels.

 

 

I'm on the verge of returning but I need to make sure I checked all the issues.

 

 

Cheers

Posted (edited)
Hi Guys,

I just received my Odyssey + and followed the instructions I could find in these threads.

 

 

I tried everything I could but the image is fuzzy all over. The cockpit panels are fuzzy and all switches.

 

 

 

I thought only the text would be an issue but so far no fix.

 

 

My system I7 ASUS Rogue HeroIX overclocked, vid card 1080 oclocked.

 

 

Shimmering I can understand and the text not fully clear but I'm troubled by the fuzzy panels.

 

 

I'm on the verge of returning but I need to make sure I checked all the issues.

 

 

Cheers

 

Hi Catseye,

 

Go to your Windows Mixed Reality VR driver folder in Steam and then to the Settings folder

 

(("Whatever drive you have steam on":\Steam\steamapps\common\MixedRealityVRDriver\resources\settings)

 

Open up the default.vrsettings file and make sure it shows 2.0 in "driver_Holographic"(it's the first item). Most the time it shows 1.0 and you will have a horrible image.

 

Like this:

 

"driver_Holographic" : {

// Increase back buffer size so that larger superscale values do not get a resolution reduction

"renderTargetScale" : 2.0

 

 

Also, you might want to check your Video Application resolution in the Steam VR settings:

1. Click on the little drop down in the steam VR window

2. Click on settings

3. Then click on Video and check the resolution.

391486323_SteamVRimage.PNG.857201ef43b4de8b21a4da55d4127804.PNG

39910322_VRsettings.PNG.2865714077c4ed67a8142e6db16e99ba.PNG

Edited by walleye62
Posted
Hi Catseye,

 

Go to your Windows Mixed Reality VR driver folder in Steam and then to the Settings folder

 

(("Whatever drive you have steam on":\Steam\steamapps\common\MixedRealityVRDriver\resources\settings)

 

Open up the default.vrsettings file and make sure it shows 2.0 in "driver_Holographic"(it's the first item). Most the time it shows 1.0 and you will have a horrible image.

 

Like this:

 

"driver_Holographic" : {

// Increase back buffer size so that larger superscale values do not get a resolution reduction

"renderTargetScale" : 2.0

 

 

Also, you might want to check your Video Application resolution in the Steam VR settings:

1. Click on the little drop down in the steam VR window

2. Click on settings

3. Then click on Video and check the resolution.

 

 

Hi Walleye62,

 

Thanks for the feedback.

 

I'm using the beta version and following your info checked that "renderTargetScale": is set to 2.0 (looks like that is a fix already set)

 

 

I have the resolution set to 200.

 

 

So the one thing that I did not have set correctly is the PD. That is the software PD not the physical dial in the HMD.

 

 

Thanks for the tips. I'll try it out tomorrow.

 

 

Cheers

Posted (edited)
PD ? Adjusted for sweet spot ? ASW-or-whatever-WMR-calls it ?

This thread may help

 

https://forums.eagle.ru/showthread.php?t=228658&page=3

 

Hi Svsmokey,

 

 

I Think that the PD might be the issue. I'm going to try 1.5 and see what happens. Most seem to recommend 1.0.

 

 

 

Also, I read Skatezilla's post on what the difference means between the physical wheel that moves the lenses and the ingame Force IPD distance that will change the FOV. I need to look into that - it's currently set to 100.

 

I now have the following:

 

pd ingame 1.0 going to try 1.5

steam ss 200%

rendertarget 2.0

no ingame aa

steam wmr beta

ASUS gtx1080

odyssey 1 hmd

wmr very-high (beta) in windows control panel

 

Thanks for your help.

 

 

Cats . . .

 

 

ps: I have to say though, that even not fully clear is blows you away looking at 3D. I almost puked rolling and looking out the side of the cockpit. (Inner ear balance thingy.)

Edited by Catseye
Posted
Hi Svsmokey,

 

 

I Think that the PD might be the issue.

I read Skatezilla's post on what the difference means between the physical wheel that moves the lenses and the software PD that will change the FOV. It was set at 63.3 and the cockpit looked rather small. :)

 

I guess you just keep changing the numbers until the FOV looks right? or is there a proved PD?

 

I now have the following:

 

pd ingame 1.0

steam ss 200%

rendertarget 2.0

no ingame aa

steam wmr beta

ASUS gtx1080

odyssey 1 hmd

wmr very-high (beta) in windows control panel

 

 

I'll work with the steam software PD tomorrow.

Thanks for your help.

 

 

Cats . . .

 

 

ps: I have to say though, that even not fully clear is blows you away looking at 3D. I almost puked rolling and looking out the side of the cockpit. (Inner ear balance thingy.)

 

You may be confusing PD (pixel density) and IPD (inter-pupillary distance) I think the Steam SS amounts to the same thing as PD , so you should probably leave the in-game PD at 1.0 .

9700k @ stock , Aorus Pro Z390 wifi , 32gb 3200 mhz CL16 , 1tb EVO 970 , MSI RX 6800XT Gaming X TRIO , Seasonic Prime 850w Gold , Coolermaster H500m , Noctua NH-D15S , CH Pro throttle and T50CM2/WarBrD base on Foxxmounts , CH pedals , Reverb G2v2

Posted
You may be confusing PD (pixel density) and IPD (inter-pupillary distance) I think the Steam SS amounts to the same thing as PD , so you should probably leave the in-game PD at 1.0 .

 

Steam SS has absolutely no effect for me, but PD definitely does. So I'd recommend he gives adjusting PD a go and see what effect it has. For me, with a 1080ti, I have PD on 1.4 and MSAA on x2.

 

And yeah, you don't need to touch the ingame IPD unless you're having issues with scale in the game (i.e. everything feeling too big or too small) - the default should be fine for most people. The headset IPD you should set to your physical IPD (literally the distance between the middle of your pupils) - it'll either be on your glasses prescription or you can just measure with a ruler and a helpful assistant (or you can just trial and error till you're not cross-eyed).

Posted

Also check out this thread, https://forums.eagle.ru/showthread.php?t=228586 I am blind in one eye and it made a difference for me. :)

The first time you started DCS with the O+ attached you must have seen this window. I got my image to be clearer by playing with the different sliders. Try it and if you have already done it just delete the Samsung lua file in Saved Games\DCS

AMD RYZEN 7 2700 / 32GB / RTX2070 / 500GB M.2 with Windows and DCS / 2 - 500GB SSD / Rift S/ TM Warthog with F18 stick and Virpil WarBRD / Foxx Mounts/ MFG Crosswind rudders + 3 MFD's | Now enjoying VR with PointCTRL controllers + Gamematrix JetSeat

Posted (edited)
Hi Walleye62,

 

Thanks for the feedback.

 

I'm using the beta version and following your info checked that "renderTargetScale": is set to 2.0 (looks like that is a fix already set)

 

 

I have the resolution set to 200.

 

 

So the one thing that I did not have set correctly is the PD. That is the software PD not the physical dial in the HMD.

 

 

Thanks for the tips. I'll try it out tomorrow.

 

 

Cheers

You may also want to make sure all your other settings are up to at least 1.0 (or 100% in steam)in Pixel density or "resolution" for steam.

 

My Pixel Density/resolution settings are:

1. DCS(in game): 1.5

 

In Steam VR settings:

Under Video

2. Aplication resolution: 200%

Under Applications (You will see a dropdown)

3. Steam VR: 100%

4. Steam VR Home: 100%

5. Windows Mixed Reality: 100%

6. DCS: 150% (you can only see this though when DCS is running)

 

Also, the Forced IPD in my DCS is unchecked. It caused nothing but problems for me. And as Svsmokey said, PD (pixel density) and IPD (inter-pupillary distance) are two seperate things. The only thing I mess with for the IPD is the little wheel on my headset.

 

Cheers!:thumbup:

Edited by walleye62
Posted
Steam SS has absolutely no effect for me, but PD definitely does. So I'd recommend he gives adjusting PD a go and see what effect it has. For me, with a 1080ti, I have PD on 1.4 and MSAA on x2.

 

And yeah, you don't need to touch the ingame IPD unless you're having issues with scale in the game (i.e. everything feeling too big or too small) - the default should be fine for most people. The headset IPD you should set to your physical IPD (literally the distance between the middle of your pupils) - it'll either be on your glasses prescription or you can just measure with a ruler and a helpful assistant (or you can just trial and error till you're not cross-eyed).

 

 

Thanks backspace340,

Working on this today.

My prescription is 65mm and that is set.

So now to check out the in game IPD setting to see what it does to the in game scale. Right now it looks too far away and fuzzy. I did notice that when I physically moved forward things became clearer so I'm wondering if a closer scale will begin to resolve the clarity.

 

 

Gonna' be a fun day guys. I really don't want to return this. Also, I have a small bucket on my lap. ;) :)

Posted
You may also want to make sure all your other settings are up to at least 1.0 (or 100% in steam)in Pixel density or "resolution" for steam.

 

My Pixel Density/resolution settings are:

1. DCS(in game): 1.5

 

In Steam VR settings:

Under Video

2. Aplication resolution: 200%

Under Applications (You will see a dropdown)

3. Steam VR: 100%

4. Steam VR Home: 100%

5. Windows Mixed Reality: 100%

6. DCS: 150% (you can only see this though when DCS is running)

 

 

 

Cheers!:thumbup:

 

 

I checked out 1 - 3 and they are as you show.

I need to plug the HMD in and see 4 - 6 settings.

 

 

Thanks again.

Posted

Yeah with the IPD, in theory it should change world scale (and it does). It also made things clearer on my rift when messing about with it (which in theory it shouldn't).

New hotness: I7 9700k 4.8ghz, 32gb ddr4, 2080ti, :joystick: TM Warthog. TrackIR, HP Reverb (formermly CV1)

Old-N-busted: i7 4720HQ ~3.5GHZ, +32GB DDR3 + Nvidia GTX980m (4GB VRAM) :joystick: TM Warthog. TrackIR, Rift CV1 (yes really).

Posted

Steam SS to 100%

 

in game PD to 1.3 (you will need MSAA to 2x)

 

OR

 

in game PD to 1.4 (no MSAA)

 

anything higher than any of those settings and the Odyssey+ will start to look fuzzy and unclear.

 

You also need to make sure your IPD is set correctly for your Eyes and the lenses are positioned on the center of your eyes vertically.

Strike

USLANTCOM.com

stepped_with_391_new_small.png

i7-9700K OC 5GHz| MSI MPG Z390 GAMING PRO CARBON | 32GB DDR4 3200 | GTX 3090 | Samsung SSD | HP Reverb G2 | VIRPIL Alpha | VIRPIL Blackhawk | HOTAS Warthog

 

Posted

I found setting the in game ipd to my actual ipd put the cockpit at proper scale. I used a ruler and kept raising and lowering the visor while I held the ruler up in front of me aligned with the hsi. When the gauge was the right size as per milspec the ipd was a match for my prescription.

All of my posted work, ideas and contributions are licensed under the Creative Commons - Attribution-NonCommercial 4.0 International (CC BY-NC 4.0,) which precludes commercial use but encourages sharing and building on for non-commercial purposes, ©John Muldoon

Posted
Steam SS to 100%

 

in game PD to 1.3 (you will need MSAA to 2x)

 

OR

 

in game PD to 1.4 (no MSAA)

 

anything higher than any of those settings and the Odyssey+ will start to look fuzzy and unclear.

 

You also need to make sure your IPD is set correctly for your Eyes and the lenses are positioned on the center of your eyes vertically.

 

 

 

 

SE,

Thanks for the details on PD/MSAA. I wondered if MSAA could be run with an HMD.

Posted
I found setting the in game ipd to my actual ipd put the cockpit at proper scale. I used a ruler and kept raising and lowering the visor while I held the ruler up in front of me aligned with the hsi. When the gauge was the right size as per milspec the ipd was a match for my prescription.

 

 

Interesting about the cockpit scale being correct if you set the in-game ipd to one's actual ipd.

 

 

I'm lucky in that I wear eye-glasses and my prescription shows it as exactly 65mm.

 

 

I'll start there and make small adjustments along with the others of which I am very grateful.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...