Jump to content

Sparkam

Members
  • Posts

    35
  • Joined

  • Last visited

Everything posted by Sparkam

  1. Checked before and after slow repair, removing metashaders2, fxo, mods, disabling antivirus. No difference.
  2. Hi, Every time when I attempt to start multithreaded DCS with steamVR (--force_enable_VR --force_steam_VR) it crashes on loading to main menu. With OpenXR no crashes. I usually play with reprojection and 180% SteamVR resolution (1944x2424 per eye). OpenXR is too stuttery even with hiher FPS. I run DCS on i7 8700K, 1080TI, 32GB, SSD, Odyssey+. I also checked performance without VR with my current settings: Average CPU, GPU load on the same track (used low resolution in DCS settings 1280x768 for game window) no MT, no VR 180 fps CPU 33% GPU 80% ----- MT, no VR 180 fps CPU 40% GPU 60% dcs.log-20230311-114320.zip dcs.log-20230311-105022.zip
  3. Similar. Most of the time I see flickering 'CPU bound (rendering thread)' in MT VR OpenXR i7 8700K, 1080TI, 32 GB
  4. Found this some time ago. Fujairah runway mark lines are under the runway surface. ${1}
  5. It's a bummer... Without stereo_mode_use_shared_parser far-away objects (mountains, trees) look incorrect. Part of a mountain may be absent in one eye even with long rendering distance. Tough choice between deck crew and far away objects.
  6. Hi, you don't need to calculate average values. Just copy/paste values as explained here. https://forums.eagle.ru/showpost.php?p=3843193&postcount=109
  7. After step 3, there are two files (renamed file and file with last save). I combined the data from two files into new file (copy of the last save) in notepad++. Copy/pasted numbers from block EYE_RGHT of the first file into block EYE_LEFT of the new file. Then copy/pasted numbers from block EYE_LEFT of the second file into block EYE_RGHT of the new file. If you dont want to mess with files, you can just swap values with sliders, however values will be rounded. It's not critical. You probably won't notice the difference. With this method i just wanted to swap exact default values.
  8. My final settings from Samsung Windows Mixed Reality 800ZBA.lua EYE_LEFT = { L_OUT =1.239822, L_IN =1.045044, L_TOP =1.419550, L_BTM =1.431158, } EYE_RGHT = { R_OUT =1.237106, R_IN =1.043276, R_TOP =1.439004, R_BTM =1.414056, } Just swappled data for EYE_LEFT and EYE_RGHT in the file. Direct copy of my settings will not work for you. You need to swap your numbers. My data before modification EYE_LEFT = { L_OUT =1.237106, L_IN =1.043276, L_TOP =1.439004, L_BTM =1.414056, } EYE_RGHT = { R_OUT =1.239822, R_IN =1.045044, R_TOP =1.419550, R_BTM =1.431158, } Here is how i saved my default settings in file: 1. In the vr debug tool press reset projections, then move any slider for left eye and press save. In Samsung Windows Mixed Reality 800ZBA.lua file you will get unmodified data for right eye; 2. rename Samsung Windows Mixed Reality 800ZBA.lua to something; 3. Open DCS. In the vr debug tool press reset projections, then move any slider for right eye and press save. In the file you will get unmodified data for left eye; 4. combine data from two files (swap numbers for EYE_LEFT and EYE_RGHT).
  9. It seems that if I swap all left/right values (OUT, IN, TOP, BTM), then it solves misalignment for me. Need experiment more with OUT, IN settings in order to adjust convergence distance of projections. Ability to lock OUT, IN or TOP, BTM sliders would be helpful in order to move them at the same time. Apparently, you can workaround slider precision issue. You can drag border between left/right settings and enter value you want if you play around with sliders and border position.
  10. Копирование помогает в значительной степени но не окончательно. Мне помогло полностью устранить расхождение не копированием, а сменой местами настроек. Значения для левыого глаза (верх, низ) идут в правый глаз, а значения для правого глаза идут в левый. https://forums.eagle.ru/showpost.php?p=3783554&postcount=62
  11. Я отключаю каждый раз как запускаю WMR.
  12. Copy from left to right or vice versa helps but not completely. Experimentally I found that vertical misalignment is gone entirely when I swap top bottom values. L_TOP goet to R_TOP, and R_TOP goes to L_TOP. Same for L_BTM R_BTM. Alex, could you make sliders more precise, so we can enter exact values for swapping? Here is example of my settings. Default No misalignment swapped values: Best 1: Best 2: Edit: It seems that if I swap all left/right values (OUT, IN, TOP, BTM), then it solves misalignment for me completely. Need to experiment more with OUT, IN settings in order to adjust convergence distance of projections. Ability to lock OUT, IN or TOP, BTM sliders would be helpful in order to keep aspect ratio constant. Apparently, you can workaround slider precision issue. You can drag border between left/right settings and enter value you want if you play around with sliders and border position.
  13. Новый тест по проблеме Одиссея https://forums.eagle.ru/showpost.php?p=3782971&postcount=53
  14. Great! Will test in a couple of hours.
  15. Привет, здесь инструкции https://forums.eagle.ru/showthread.php?p=3734199#post3734199 https://forums.eagle.ru/showthread.php?p=3745425#post3745425
  16. Я переставил с первого одиссея и сделал подставки из ткани в двух местах. К жесткой накладке не привык, слишком на лоб давит. Можно попробовать чем-то перетянуть накладку о+ в районе лба. Думаю, поможет в какой то степени. Эффект раздвоения можно заметить, если держа голову ровно, смотреть вдаль на HUD и нажать громкость+- на шлеме. Цифры громкости будут расходятся вертикально или по диагонали, если смотреть на игровой мир. Или игровой мир будет двоиться если сфокусироваться на громкость. Можно нажать win на контроллера, чтобы стало видно контроллер и игровой мир. Поместить контроллер рядом с чем-то из кабины (например с РУС или на кресло). Контроллер должен выглядеть так, как будто он часть игрового мира. И можно нормально сфокусироваться на часть кабины и рядом соящи контроллер. Он не должен выглядеть как-то странно (как будто в аквариуме) или двоиться. Еще можно включить границу перемещения в vr и смотреть на ее углы.
  17. Привет, заметно ли вертикальное расхождение картинки, если нажать громкость +/- на шлеме в DCS? Судя по данным оно примерно 0.58 градусов.
  18. Я пока разницы не заметил с этой опцией. Где именно, в DCS плотность пикселей, SteamVR Application Resolution 200% или "renderTargetScale" : 2.0 ?
  19. Logs with my HMDs. Both have this issue. In Samsung Odyssey+ misalignment is bigger compared to original Odyssey. Samsung Odyssey+ 2019-01-18 18:21:22.998 INFO VISUALIZER: OpenVR Projection///////////////////////////////////////////////////////////// 2019-01-18 18:21:22.998 INFO VISUALIZER: OpenVR Projection Bounds Eye 0: 1.23711,1.04328,1.43900,1.41406 2019-01-18 18:21:22.998 INFO VISUALIZER: OpenVR GetProjectionMatrix(0,150000,0.02) result: 0.87705,0.00000,-0.08500,0.00000 0.5f,0.00000,0.70100,-0.00874 0.5f,0.00000,0.00000,0.00000 0.5f,0.00000,0.02000,0.00000 2019-01-18 18:21:22.998 INFO VISUALIZER: OpenVR Projection Converted to DCS: 0.87705,0.00000,0.00000,0.00000 0.5f,0.00000,0.70100,0.00000 0.5f,0.00000,0.08500,-0.00874 0.5f,-0.00000,1.00000,0.00000 2019-01-18 18:21:22.998 INFO VISUALIZER: OpenVR ed::makePerspectiveForHMDProjection result : 0.87705,0.00000,0.00000,0.00000 0.5f,0.00000,0.70100,0.00000 0.5f,0.00000,0.08500,-0.00874 0.5f,-0.00000,1.00000,0.00000 2019-01-18 18:21:22.998 INFO VISUALIZER: ------------------------------------------------------------------------------------- 2019-01-18 18:21:22.998 INFO VISUALIZER: OpenVR Projection Bounds Eye 1: 1.04504,1.23982,1.41955,1.43116 2019-01-18 18:21:22.998 INFO VISUALIZER: OpenVR GetProjectionMatrix(1,150000,0.02) result: 0.87533,0.00000,0.08525,0.00000 0.5f,0.00000,0.70158,0.00407 0.5f,0.00000,0.00000,0.00000 0.5f,0.00000,0.02000,0.00000 2019-01-18 18:21:22.998 INFO VISUALIZER: OpenVR Projection Converted to DCS: 0.87533,0.00000,0.00000,0.00000 0.5f,0.00000,0.70158,0.00000 0.5f,0.00000,-0.08525,0.00407 0.5f,-0.00000,1.00000,0.00000 2019-01-18 18:21:22.998 INFO VISUALIZER: OpenVR ed::makePerspectiveForHMDProjection result : 0.87533,0.00000,0.00000,0.00000 0.5f,0.00000,0.70158,0.00000 0.5f,0.00000,-0.08525,0.00407 0.5f,-0.00000,1.00000,0.00000 2019-01-18 18:21:22.998 INFO VISUALIZER: /////////////////////////////////////////////////////////////////////////////// 2019-01-18 18:21:22.998 INFO VISUALIZER: LAUNCH IN VR : OpenVR : Samsung Windows Mixed Reality 800ZBA Samsung Odyssey 2019-01-18 18:38:43.236 INFO VISUALIZER: OpenVR Projection///////////////////////////////////////////////////////////// 2019-01-18 18:38:43.236 INFO VISUALIZER: OpenVR Projection Bounds Eye 0: 1.23792,1.04332,1.42552,1.42044 2019-01-18 18:38:43.236 INFO VISUALIZER: OpenVR GetProjectionMatrix(0,150000,0.02) result: 0.87671,0.00000,-0.08530,0.00000 0.5f,0.00000,0.70275,-0.00178 0.5f,0.00000,0.00000,0.00000 0.5f,0.00000,0.02000,0.00000 2019-01-18 18:38:43.236 INFO VISUALIZER: OpenVR Projection Converted to DCS: 0.87671,0.00000,0.00000,0.00000 0.5f,0.00000,0.70275,0.00000 0.5f,0.00000,0.08530,-0.00178 0.5f,-0.00000,1.00000,0.00000 2019-01-18 18:38:43.236 INFO VISUALIZER: OpenVR ed::makePerspectiveForHMDProjection result : 0.87671,0.00000,0.00000,0.00000 0.5f,0.00000,0.70275,0.00000 0.5f,0.00000,0.08530,-0.00178 0.5f,-0.00000,1.00000,0.00000 2019-01-18 18:38:43.236 INFO VISUALIZER: ------------------------------------------------------------------------------------- 2019-01-18 18:38:43.236 INFO VISUALIZER: OpenVR Projection Bounds Eye 1: 1.04621,1.22745,1.40471,1.42192 2019-01-18 18:38:43.236 INFO VISUALIZER: OpenVR GetProjectionMatrix(1,150000,0.02) result: 0.87964,0.00000,0.07971,0.00000 0.5f,0.00000,0.70756,0.00609 0.5f,0.00000,0.00000,0.00000 0.5f,0.00000,0.02000,0.00000 2019-01-18 18:38:43.236 INFO VISUALIZER: OpenVR Projection Converted to DCS: 0.87964,0.00000,0.00000,0.00000 0.5f,0.00000,0.70756,0.00000 0.5f,0.00000,-0.07971,0.00609 0.5f,-0.00000,1.00000,0.00000 2019-01-18 18:38:43.236 INFO VISUALIZER: OpenVR ed::makePerspectiveForHMDProjection result : 0.87964,0.00000,0.00000,0.00000 0.5f,0.00000,0.70756,0.00000 0.5f,0.00000,-0.07971,0.00609 0.5f,-0.00000,1.00000,0.00000 2019-01-18 18:38:43.236 INFO VISUALIZER: /////////////////////////////////////////////////////////////////////////////// 2019-01-18 18:38:43.236 INFO VISUALIZER: LAUNCH IN VR : OpenVR : Samsung Windows Mixed Reality 800ZAA
  20. Hm, it's logical. Logs only for OpenVR, not Oculus api.
  21. Новый шлем, это точно...)) Потенциальный фикс для Одиссея не помог. Здесь разработчик DCS попросил логи, чтоб понять лучше проблему. https://forums.eagle.ru/showpost.php?p=3763716&postcount=28
  22. I wonder, how numbers in log will change if you open DCS through Revive inject?
  23. Hi Alex, judging from logs above, I calculated misalignment with method described here https://steamcommunity.com/app/719950/discussions/0/1742229167208813376/?ctp=3#c1742231069940351286 Vertical misalignment of your Odyssey is relatively small. It's only 0.41994205°. My original Odyssey has 1.2° and I didn't realy noticed it until I knew how to see it. Here on Russian forum I described how to see misalignment https://forums.eagle.ru/showpost.php?p=3736445&postcount=17 There is also partial workaround of this problem. Inject function of Revive. Instruction here https://forums.eagle.ru/showpost.php?p=3734199&postcount=7 I will attach logs for both my Odyssey headsets later.
  24. Как я понимаю, это каждый окуляр калибруют на заводе и где-то в шлеме записано.
×
×
  • Create New...