Jump to content

DCS and Odyssey+ cross-eyed!!


sandman330
 Share

Recommended Posts

Hello all, I have read and read and I have seen others with the same issue.. BUT no true fix (for me).

 

I have just received the Odyssey+ and I play DCS (Non Steam). As far as I know, the Samsung Odyssey and similar HMDs requre Steam VR. I have noticed that within Steam VR the visuals are clean and crsip. Within Windows Mixed reality portal, it too is clear and crisp. However when you load DCS, the vision becomes cross-eyed.. clear but cross-eyed. I have seen screen shots showing the misalignment in game of about 1 degree.

 

I am not 100% familiar with Steam, and only use it for VR as I have no other option to run the Odessey+. (I use to have Oculus.)

 

Is there a fix for this bug in steam? or a guide to help remove this issue? why does this happen when loading DCS (I see it also happens to other select programs too). I have tried the 'Revive 1.6.2' fix which uses Oculus home. (weird). doesnt work for me at least.

 

Is it a steamVR, DCS or the Odyssey+ issue..?

 

I have the latest Nvidia drivers as of this post, lastest windows update and all drivers.

 

My rig : ASUS ROG Maximus X Apex, 32GB DDR4 Gskill RGB 3000, i7-8086 @ 5.2ghz (water), Zotac GTX 1080ti OC, 1200wwwt PSU..

 

I would sincerly appreciate all your help, expertise and direction. :cry:

 

Thanks in advance.


Edited by sandman330
Link to comment
Share on other sites

  • Replies 130
  • Created
  • Last Reply

Top Posters In This Topic

You're not alone my friend. I have the Odyssey+ as well and even though your PC outclasses mine by a long shot I'm having the exact same issue. I've tried forcing ipd, turning settings down, everything. I don't have a fix for you but I want to let you know others are having similar issues!

Link to comment
Share on other sites

Same here.

I had the Samsung Odyssey (non plus) with a very big miss allingment.

So i sold it in Summer 2018.

 

Now i own the Odyssey Plus and still having the little missalingment.

I hope this will be fixed in the close future.

i7-8700K / 32GB RAM @3000 / 1TB M.2 SSD / Asus RTX 2080 Ti OC

VR- Gamer: Valve Index

Flight Gear: Thrustmaster HOTAS Warthog / Thrustmaster TPR / 3x Thrustmaster MFD / Jetseat

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

So you guys have measured your IPD and adjusted the physical roller on the headset to match that? In the mixed reality portal settings it will tell you the distance between center of lenses when you adjust the roller, which is meant to match your physical IPD which is a measurement of the distance between the center of your pupils when focused on something maybe 2-3 feet or further in front of you.

 

I got a pretty big head so the max IPD setting in mixed reality portal is like 71.808 with the original Odyssey and just barely wide enough for me with the widest setting but it's key to set that to match the distance between your pupils or you will feel crosseyed. From there I also adjust how the headset sits against my face to put my eyeballs in the vertical sweet spot, you know you're there when the picture is it's clearest, provided the IPD is correctly set on the headset.

 

 

Frankly, I didn't measure my IPD before realizing that adjusting the roller on the headset adjusts how far apart the lenses are from eachother. I just rolled it til the picture looked clear, with no double vision, which was the max width for me.

 

So either adjust the roller, or focus on your finger with your arm fully stretched and get someone to measure the distance between the center of your pupils in mm and that's your IPD"

 

the "Force IPD" setting in DCS world isn't the same thing.. it makes the world larger or smaller, personally I don't use it.

 

The physical roller to adjust the HMD IPD, at least on the non+ is on the bottom of the front of the headset in the middle. And it physically moves the lenses closer together or further apart inside the HMD.

 

In the screen snip below, those are the settings for WMR within windows, accessed by clicking the three dots on the bottom left of mixed reality portal and clicking "settings" then "headset display" in the new window. In WMR headsets without a physical roller to adjust IPD, you adjust the slider, which would be a software setting, where the Odyssey uses a physical setting, i think maybe in conjunction with WMR software.

 

IPD.thumb.JPG.509f0440ceb135f39111f15870b961b4.JPG

 

I'm not saying anybody who's posted hasn't tried this. So don't take it the wrong way. I don't tend to notice a difference in DCS vs other VR experiences.


Edited by Headwarp
Spoiler

Win10 Pro, 11900K turbo ratio from 5.1GHzto 5.3GHz  2080Ti,  64GB DDR4 3600/18,  all drives are NVME or SSD, Valve Index and a 32" 2560x1440 @165Hz monitor.  (Not listed as compatible but the freesync doth work)    

Sim hardware - VKB MCG Ultimate with 200mm extension, Virpil T-50CM3 Dual throttles.   Blackhog B-explorer (A), TM Cougar MFD's (two), MFG Crosswinds with dampener.   Obutto R3volution gaming pit.  

 

Link to comment
Share on other sites

I hve adjusted my IPD, wich is roughly on the lower end of the scale(62,8mm)

I also set the figures from the wmr into die "DCS IPD".

 

 

But the thing is, in other games like project cars 2 and elite dangerous everything is propper.

Only DCS is a little missaligned...

 

But i can deal with it, hoping that it will become like in the other games.

 

And @Headwarp, every discussion is helpful :-) so I personaly dont get your post wrong.

i7-8700K / 32GB RAM @3000 / 1TB M.2 SSD / Asus RTX 2080 Ti OC

VR- Gamer: Valve Index

Flight Gear: Thrustmaster HOTAS Warthog / Thrustmaster TPR / 3x Thrustmaster MFD / Jetseat

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

I have heard that setting the display to 60 hz instead of 90 hz may fix the issue, but may also cause you to become nauseated. I won't be able to test until the weekend but I will keep digging and if I find a solution, will post. I've adjusted the IPD wheel all the from left to right and all the way across the board I'm getting the cross-eyed effect. Seems it has something to do with the engine and our hmd not playing nice.

Link to comment
Share on other sites

i7-8700K, Z370, 32GB DDR4-3000MHz, RTX 2080 Ti, FSSB R3L, TM Warthog HOTAS, CH Pro pedals, 2x MFD's, Windows 10 Pro, HP Reverb

 

DCS: F-16C, F/A-18C, F-14B, F-15C, AV-8B, M2000C, F-5E, A-10C, AJS-37, Su-27, Su-33, MiG-21bis, MiG-29, Spitfire LF Mk. IX, Bf 109 K-4, SA342, UH-1H

Link to comment
Share on other sites

 

 

that's a good news!!

 

 

TomMicrosoft [sviluppatore] 20 ore fa

 

Hey all we are aware of the issue and determined that the DCS team will need to make changes to fix it. We reached out to their team and will work with them to fix this in an upcoming DCS release.

 

 

 

:thumbup::thumbup::thumbup::thumbup:

  • CPU : Intel i7 8700k@5.0ghz cooled by Noctua NH-D15 / Motherboard:Asorck Z370 Taichi / RAM: 32GB GSkill TridentZ @3600mhz / SSD: 500GB Nvme Samsung 970 evo+1 TB Sabrent Nvme M2 / GPU:Asus Strix OC 2080TI / Monitor: LG 34KG950F Ultrawide / Trackir 5 proclip/ VIRPIL CM2 BASE + CM2 GRIP + F148 GRIP + 200M EXTENSION /VKB T-Rudder MKIV rudder /Case: Fractal Design R6 Define black

Link to comment
Share on other sites

That's good to know that ED is "on the hook" to help improve the O+ experience in DCS. :thumbup:

 

(Would be nice to get some official word from ED as to when, and maybe even, what is needed in DCS for this kind of change)

PC: AMD Ryzen 9 5950X | MSI Suprim GeForce 3090 TI | ASUS Prime X570-P | 128GB DDR4 3600 RAM | 2TB Samsung 870 EVO SSD | Win10 Pro 64bit

Gear: HP Reverb G2 | JetPad FSE | VKB Gunfighter Pro Mk.III w/ MCG Ultimate

 

VKBNA_LOGO_SM.png

VKBcontrollers.com

Link to comment
Share on other sites

In the discussion on the steam forum https://steamcommunity.com/app/719950/discussions/0/1742229167208813376/?ctp=2, we analyzed data from several Odyssey Plus goggles - including for comparison with goggles on which DCS normally starts. We used the vrcmd application in the folder:

 

c:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\win64>vrcmd

 

This application generates such data:

 

Device 0 - holographic.WindowsHolographic - Samsung Windows Mixed Reality 800ZBA by WindowsMR - HMD - generic_hmd

D3DAdapterIndex: 0

RecommendedRenderTargetSize: width=1687, height=2107

Left Projection: left=-1.246544, right=1.040488, top=-1.439158, bottom=1.418004

Right Projection: left=-1.047278, right=1.232865, top=-1.418372, bottom=1.425465

Lens Center: (0.000000, 0.000000), (0.000000, 0.000000)

 

This is just the data from my goggles that have the effect of misalignment in DCS.

 

For comparison, data from goggles that do not have this problem:

 

Device 0 - holographic.WindowsHolographic - Samsung Windows Mixed Reality 800ZBA by WindowsMR - HMD - generic_hmd

D3DAdapterIndex: 0

RecommendedRenderTargetSize: width=1687, height=2105

Left Projection: left=-1.225003, right=1.041945, top=-1.414402, bottom=1.415475

Right Projection: left=-1.039288, right=1.240635, top=-1.423776, bottom=1.421235

Lens Center: (0.000000, 0.000000), (0.000000, 0.000000)

 

What you can notice is his top/bottom values are pretty close (symmetrical) to each other. Unlike other Odyssey+ headsets.

 

top=-1.414402, bottom=1.415475

top=-1.423776, bottom=1.421235

 

It is possible that this is a clue that will help in removing the problem.

 

Here are the next data from the two odyssey goggles plus with the same problem in DCS:

 

Device 0 - holographic.WindowsHolographic - Samsung Windows Mixed Reality 800ZBA by WindowsMR - HMD - generic_hmd

D3DAdapterIndex: 0

RecommendedRenderTargetSize: width=1913, height=2388

Left Projection: left=-1.237106, right=1.043276, top=-1.439004, bottom=1.414056

Right Projection: left=-1.045044, right=1.239822, top=-1.419550, bottom=1.431158

Lens Center: (0.000000, 0.000000), (0.000000, 0.000000)

 

Device 0 - holographic.WindowsHolographic - Samsung Windows Mixed Reality 800ZBA by WindowsMR - HMD - generic_hmd

D3DAdapterIndex: 0

RecommendedRenderTargetSize: width=2065, height=2581

Left Projection: left=-1.241200, right=1.041525, top=-1.444395, bottom=1.412439

Right Projection: left=-1.052791, right=1.237553, top=-1.431514, bottom=1.432223

Lens Center: (0.000000, 0.000000), (0.000000, 0.000000)

i7-8700K, Z370, 32GB DDR4-3000MHz, RTX 2080 Ti, FSSB R3L, TM Warthog HOTAS, CH Pro pedals, 2x MFD's, Windows 10 Pro, HP Reverb

 

DCS: F-16C, F/A-18C, F-14B, F-15C, AV-8B, M2000C, F-5E, A-10C, AJS-37, Su-27, Su-33, MiG-21bis, MiG-29, Spitfire LF Mk. IX, Bf 109 K-4, SA342, UH-1H

Link to comment
Share on other sites

In the discussion on the steam forum https://steamcommunity.com/app/719950/discussions/0/1742229167208813376/?ctp=2, we analyzed data from several Odyssey Plus goggles - including for comparison with goggles on which DCS normally starts. We used the vrcmd application in the folder:

 

c:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\win64>vrcmd

 

This application generates such data:

 

Device 0 - holographic.WindowsHolographic - Samsung Windows Mixed Reality 800ZBA by WindowsMR - HMD - generic_hmd

D3DAdapterIndex: 0

RecommendedRenderTargetSize: width=1687, height=2107

Left Projection: left=-1.246544, right=1.040488, top=-1.439158, bottom=1.418004

Right Projection: left=-1.047278, right=1.232865, top=-1.418372, bottom=1.425465

Lens Center: (0.000000, 0.000000), (0.000000, 0.000000)

 

This is just the data from my goggles that have the effect of misalignment in DCS.

 

For comparison, data from goggles that do not have this problem:

 

Device 0 - holographic.WindowsHolographic - Samsung Windows Mixed Reality 800ZBA by WindowsMR - HMD - generic_hmd

D3DAdapterIndex: 0

RecommendedRenderTargetSize: width=1687, height=2105

Left Projection: left=-1.225003, right=1.041945, top=-1.414402, bottom=1.415475

Right Projection: left=-1.039288, right=1.240635, top=-1.423776, bottom=1.421235

Lens Center: (0.000000, 0.000000), (0.000000, 0.000000)

 

What you can notice is his top/bottom values are pretty close (symmetrical) to each other. Unlike other Odyssey+ headsets.

 

top=-1.414402, bottom=1.415475

top=-1.423776, bottom=1.421235

 

It is possible that this is a clue that will help in removing the problem.

 

Here are the next data from the two odyssey goggles plus with the same problem in DCS:

 

Device 0 - holographic.WindowsHolographic - Samsung Windows Mixed Reality 800ZBA by WindowsMR - HMD - generic_hmd

D3DAdapterIndex: 0

RecommendedRenderTargetSize: width=1913, height=2388

Left Projection: left=-1.237106, right=1.043276, top=-1.439004, bottom=1.414056

Right Projection: left=-1.045044, right=1.239822, top=-1.419550, bottom=1.431158

Lens Center: (0.000000, 0.000000), (0.000000, 0.000000)

 

Device 0 - holographic.WindowsHolographic - Samsung Windows Mixed Reality 800ZBA by WindowsMR - HMD - generic_hmd

D3DAdapterIndex: 0

RecommendedRenderTargetSize: width=2065, height=2581

Left Projection: left=-1.241200, right=1.041525, top=-1.444395, bottom=1.412439

Right Projection: left=-1.052791, right=1.237553, top=-1.431514, bottom=1.432223

Lens Center: (0.000000, 0.000000), (0.000000, 0.000000)

 

 

13WELT_JankeS, Ok so ran this "VRCMD" from the file ext you posted but where do i get the info it generates sorry I am not finding it. Currently I have no eye misalignment in the O+ it appears to be even. But I would like to help. Thanks!

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

You must run these applications in the command line window. The easiest way is to click on the magnifying glass and enter CMD. Then open the folder containing the vrcmd applications and drag it to the command line window and press Enter. Thank you for your help.

i7-8700K, Z370, 32GB DDR4-3000MHz, RTX 2080 Ti, FSSB R3L, TM Warthog HOTAS, CH Pro pedals, 2x MFD's, Windows 10 Pro, HP Reverb

 

DCS: F-16C, F/A-18C, F-14B, F-15C, AV-8B, M2000C, F-5E, A-10C, AJS-37, Su-27, Su-33, MiG-21bis, MiG-29, Spitfire LF Mk. IX, Bf 109 K-4, SA342, UH-1H

Link to comment
Share on other sites

I ran my Odyssey+ that is confirmed to have the problem after running vrcmd my details are below

 

Device 0 - holographic.WindowsHolographic - Samsung Windows Mixed Reality 800ZBA by WindowsMR - HMD - generic_hmd

D3DAdapterIndex: 0

RecommendedRenderTargetSize: width=2015, height=2517

Left Projection: left=-1.240856, right=1.041081, top=-1.432307, bottom=1.417400

Right Projection: left=-1.047061, right=1.234631, top=-1.419297, bottom=1.430691

Lens Center: (0.000000, 0.000000), (0.000000, 0.000000)

Tracking universe: 69102031649400

Link to comment
Share on other sites

Thank you very much for your data. We are still waiting for the fix from Eagle Dynamics.

i7-8700K, Z370, 32GB DDR4-3000MHz, RTX 2080 Ti, FSSB R3L, TM Warthog HOTAS, CH Pro pedals, 2x MFD's, Windows 10 Pro, HP Reverb

 

DCS: F-16C, F/A-18C, F-14B, F-15C, AV-8B, M2000C, F-5E, A-10C, AJS-37, Su-27, Su-33, MiG-21bis, MiG-29, Spitfire LF Mk. IX, Bf 109 K-4, SA342, UH-1H

Link to comment
Share on other sites

I've tried everything. The IPD setting in the game affects the size of the cockpit, but does not change the setting of the left eye image relative to the right. These images are not only that they are offset horizontally, but one is much higher than the other. This can be seen immediately when uploading the game via SteamVR when the loading window with three bars is super clear, and when the DCS menu is shown the image is very distracted. It can not be seen anymore because the eyes hurt.

i7-8700K, Z370, 32GB DDR4-3000MHz, RTX 2080 Ti, FSSB R3L, TM Warthog HOTAS, CH Pro pedals, 2x MFD's, Windows 10 Pro, HP Reverb

 

DCS: F-16C, F/A-18C, F-14B, F-15C, AV-8B, M2000C, F-5E, A-10C, AJS-37, Su-27, Su-33, MiG-21bis, MiG-29, Spitfire LF Mk. IX, Bf 109 K-4, SA342, UH-1H

Link to comment
Share on other sites

As per the links posted, it looks like you'll have to wait for ED to address it. If you take the MS developers word.

hsb

HW Spec in Spoiler

---

 

i7-10700K Direct-To-Die/OC'ed to 5.1GHz, MSI Z490 MB, 32GB DDR4 3200MHz, EVGA 2080 Ti FTW3, NVMe+SSD, Win 10 x64 Pro, MFG, Warthog, TM MFDs, Komodo Huey set, Rverbe G1

 

Link to comment
Share on other sites

Has anyone checked the DCS Open beta update? Added possible fix for Samsung Odyssey crosseyed picture.

 

I checked on my goggles and unfortunately after the last update DCS 2.5.4.26368 nothing has changed :( I still have crosseyed picture .It is comforting that steps have been taken to solve the problem.Thank you for your work and I keep my fingers crossed hoping for a quick solution problem.


Edited by 13WELT_JankeS

i7-8700K, Z370, 32GB DDR4-3000MHz, RTX 2080 Ti, FSSB R3L, TM Warthog HOTAS, CH Pro pedals, 2x MFD's, Windows 10 Pro, HP Reverb

 

DCS: F-16C, F/A-18C, F-14B, F-15C, AV-8B, M2000C, F-5E, A-10C, AJS-37, Su-27, Su-33, MiG-21bis, MiG-29, Spitfire LF Mk. IX, Bf 109 K-4, SA342, UH-1H

Link to comment
Share on other sites

  • ED Team

Hello guys , I definitely cannot reproduce this issue with my headset Samsung Odyssey 800ZAA ,

Do you have any workaround ? Is it related to original Odyssey headset or reproduced only on Odyssey+ , can it be reproduced for other vendors ?

any other info will be helpful

sigpic2354_5.gif
Link to comment
Share on other sites

Somewhat better

 

The most recent open beta which downloaded today for me, is somewhat better. I can now put the headset on and fly in dcs for about 5 minutes before my eyes become too strained due to the cross eye feeling.

 

The cross eye effect is still there, when you takeoff the headset it takes about 10 minutes to straighten your eyes out so to speak.

 

I hope they fix this issue completely very soon, this is such a pita...

 

Again using a new Samsung Odyssey + with Steam for WMR HMD

Link to comment
Share on other sites

The problem concerns only WMR sets from Samsung: Odyssey and Odyssey Plus. For me, after the last update, nothing has changed. But I received information about further work on solving the problem:

 

TomMicrosoft writes:

 

"Hey all we are working with DCS to confirm that we have a DCS update - it is not a WinMR update, but we should have a better idea soon. a full grasp on the fix we'll be reaching out to additional devs (iRacing, Euro Truck Sim) "

 

I think that they will be able to fix it soon.

i7-8700K, Z370, 32GB DDR4-3000MHz, RTX 2080 Ti, FSSB R3L, TM Warthog HOTAS, CH Pro pedals, 2x MFD's, Windows 10 Pro, HP Reverb

 

DCS: F-16C, F/A-18C, F-14B, F-15C, AV-8B, M2000C, F-5E, A-10C, AJS-37, Su-27, Su-33, MiG-21bis, MiG-29, Spitfire LF Mk. IX, Bf 109 K-4, SA342, UH-1H

Link to comment
Share on other sites

Thanks everyone for your valuable input. Sorry for my absence in the posts. I have tried almost everything bar sending it back for a refund. I did try the latest update and I too experienced the same as 13WELT_JankeS. IL2 works well, no cross eyed effect there. Seems to be selective.

 

Although I find it very interesting that there are people out there that have the Odyssey + and have no misalignment with DCS. How can it be. I have 2 rigs. The one I mentioned on my original post (in Hong Kong) and my other is essentially the same but with 2 GTX 1080ti in SLI (in Japan). Everything is underwater and overclocked. I am still getting the same issue on that rig as well. :huh:

 

Thanks again. :thumbup:

Link to comment
Share on other sites

Hello guys , I definitely cannot reproduce this issue with my headset Samsung Odyssey 800ZAA ,

Do you have any workaround ? Is it related to original Odyssey headset or reproduced only on Odyssey+ , can it be reproduced for other vendors ?

any other info will be helpful

Hi Alex, thank you for your input. My Odyssey + is 800ZBA. I have read that it also has occurred on the Odyssey. WMR and Seam VR applications are all clear and not misaligned (well for myself anyway) I only have flight sim stuff on my rigs, But IL2 is clear smooth and aligned.

 

For me when DCS (non steam DCS version) starts, the menu looks clear, readable, and nothing to much out of shape, as with in game, there is something not right and you can feel it in the eye, but on a visual standpoint, it is fine...as your brain adjusts for the misalignment.... However, when I take the headset off after say 5 mins, I am cross-eyed.

 

The HMD seems ok, as it works in other apps. Seems its a software/driver/compatibility/conflict issue. I am no software expert and therefore relying on the wisdom of professionals like yourself who are skilled in these areas.

 

Thanks again.

Link to comment
Share on other sites

It's got to be a difference in eye's, I can tell it's there, but not by any direct visual cue in the goggles. It's mainly when they are remove after a time in DCS my eyes see it. Usually the right eye is a bit out of focus until it re-adapts. For now limiting exposure, there's other flight sims.

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

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