Windows Mixed Reality for SteamVR

Windows Mixed Reality for SteamVR

View Stats:
JankeS Dec 28, 2018 @ 7:13am
New Samsung Odyssey Plus and DCS big issue :(
For a year I used Pimax 4K goggles without any problems. I use VR only when I fly on the DCS simulator. I used the promotion on Black Friday and bought new Samsung Odyssey Plus goggles. What was my disappointment when it turned out that practically everything works except for the DCS simulator. It could not be worse. After starting the DCS the image from the left screen does not coincide with the right one. The simulator becomes unplayable. The only way to run the game I found (described by Sparkam - thank you) - is to use the Revive program and its inject function. In addition, the name of the file has to be changed:
"c:\Program Files\Revive\Revive\x64\LibRemixed64_1.dll" to LibRevive64_1.dll

The simulator works, but unfortunately the resolution is very poor, it does not help to overclock the PD in DCS. In addition, motion vector reprojection does not work, so you can not fly in a smooth way. Now, on the one hand, I enjoy good brightness, super colors and 6DOF, but I can not fully use it in DCS, which I really care about.

I wonder what the problem is? Is this the fault of the Windows Mixed Reality for SteamVR application? I tried with the beta version but unfortunately it did not help. Is this some incompatibility of Samsung's goggles with DCS? I count on help in solving this problem. greetings
< >
Showing 16-30 of 64 comments
It would be the best if MS or Steam fix that on driver level, if is possible.
JankeS Jan 7 @ 3:54am 
That would be wonderful. The only thing that is strange is that some models operate normally, and some have this misalignment. I bought Samsung Odyssey Plus goggles at the same time with a friend and his ogogle work in DCS normally and I have this misalignment: / We checked the software version and it is the same. I have no idea why one of them is ok and the problem is on others.
Check IPD range in WMR portal, of your and his.
I noticed in mine IPD range is moved for a 2mm, and is starting from 63.
My IPD is 63 (measured by a doctor), but sharp settings on O+ are on 64-65, where it was 63 on acer vr.
I have also misalignment on DCS. Maybe it is corelated, worth to check.
Last edited by Kyokushin; Jan 7 @ 4:09am
JankeS Jan 7 @ 4:25am 
I have an IPD of 68mm, my friend is 69mm - in a mixed portal I have 68.01 (but that's changing - recently I saw 67,927). The focus is rather ok at the set value. This misalignment is quite large. The inscription INSTANT ACTION from the left eye overlaps with the inscription CREATE FAST MISSION from the right. After using inject in revive, everything is in place, but the resolution is lower.
What is the lowest value which you and your friend can set in wmr portal?
Last edited by Kyokushin; Jan 7 @ 6:02am
JankeS Jan 7 @ 6:41am 
The lowest IPD value in a mixed portal for me is 64.167 and the maximum is 72.447. A friend will check later because he is not at home right now.
Last edited by JankeS; Jan 7 @ 6:43am
sparkam Jan 7 @ 10:36am 
Here is some data from my HMDs.
In my original Odyssey misalignment is about 2 times smaller then in Odyssey +.
I wonder, is it related to projection matrix, which is calibrated for every headset?

Odyssey+
IPD range 63.308 - 72.559

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

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)

-----------------------------------------------------------------------------------------------------

Odyssey
IPD range 60.686 - 72.115

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

Device 0 - holographic.WindowsHolographic - Samsung Windows Mixed Reality 800ZAA by WindowsMR - HMD - generic_hmd
D3DAdapterIndex: 0
RecommendedRenderTargetSize: width=1913, height=2385
Left Projection: left=-1.237922, right=1.043325, top=-1.425516, bottom=1.420440
Right Projection: left=-1.046205, right=1.227448, top=-1.404709, bottom=1.421922
Lens Center: (0.000000, 0.000000), (0.000000, 0.000000)
Tracking universe: 95203499829100
JankeS Jan 7 @ 10:47am 
It's my 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)
JankeS Jan 7 @ 11:30am 
Here are the details for my friend:

IPD 62.72 - 72.21

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)
Tracking universe: 3337486618300

His goggles work with DCS
Last edited by JankeS; Jan 7 @ 11:33am
sparkam Jan 7 @ 12:43pm 
Interesting, 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

Is there no misalignment at all or it is almost unnoticeable?
Mine:

IPD: 63.208 - 72.412
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)
Tracking universe: 3641072771200
Last edited by Kyokushin; Jan 7 @ 4:58pm
JankeS Jan 8 @ 5:18am 
Originally posted by sparkam:
Interesting, 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

Is there no misalignment at all or it is almost unnoticeable?

A friend claims that there is no mis-alignment. In fact, his data looks very symmetrical.
JankeS Jan 9 @ 5:07am 
I received data from another Odyssey Plus user from ED Forum who claims that he has no misalignment in DCS, here they are:

Device 0 - holographic.WindowsHolographic - Samsung Windows Mixed Reality 800ZBA
by WindowsMR - HMD - generic_hmd
D3DAdapterIndex: 0
RecommendedRenderTargetSize: width=2017, height=2517
Left Projection: left=-1.233322, right=1.045476, top=-1.438242, bottom=1.416070
Right Projection: left=-1.044679, right=1.242383, top=-1.426025, bottom=1.424816
Lens Center: (0.000000, 0.000000), (0.000000, 0.000000)
Tracking universe: 240186017820200

As you can see, they are not so symmetrical, so it is uncertain whether these data affect the problem of misalignment.
Niceman Jan 9 @ 6:28am 
My Data. DSC and ETS (Truck simulator) not work correctly.

Device 0 - holographic.WindowsHolographic - Samsung Windows Mixed Reality 800ZBA by WindowsMR - HMD - generic_hmd
D3DAdapterIndex: 0
RecommendedRenderTargetSize: width=2014, height=2520
Left Projection: left=-1.227423, right=1.042052, top=-1.425747, bottom=1.407900
Right Projection: left=-1.045127, right=1.233649, top=-1.422889, bottom=1.428664
Lens Center: (0.000000, 0.000000), (0.000000, 0.000000)
JankeS Jan 9 @ 7:03am 
In your goggles, the calibration of the projection of the left eye for the top and bottom does not have symmetrical values. It would be useful to get more data from working goggles for comparison. It is not known whether these factory calibration values ​​affect the DCS misalignment, but it is puzzling that some models work without a problem - so maybe it actually has to do with some factory calibration.
< >
Showing 16-30 of 64 comments
Per page: 15 30 50