Jump to content

Glide

Members
  • Posts

    1194
  • Joined

  • Last visited

Everything posted by Glide

  1. So, I am not sure how the label issue came back, and I have not reproduced it yet. However, I cleared the Environment Data in Mixed Reality Portal and it went away.
  2. I can report this issue is present in the non-MT version. It is not related to Hyperthreading as I first thought because I have HT off. I have not isolated it yet. It is not related to NCP (my mistake), nor is it related to OpenXR Toolkit.
  3. You don't require anything from the NCP, but many have Threaded Optimization ON. You need to add the bin-mt folder if you want to have settings for the MT version (I assume, but I can't really tell the difference). Every time I tried to add the DCS.exe from the bin-mt folder, the NCP just assumed I was trying to add the existing DCS.exe entry until I added the folder. You could also delete the current Black Shark entry in the NCP and then add the new bin-mt verion (I haven't tried this). It's also a good idea to Restore defaults (global and program specific) and re-apply your settings if you think the NCP is not picking up your changes.
  4. See my post here: You were in OpenXR. Just launch Windows Mixed Reality Portal, leave it running, then launch DCS. Glad it's working.
  5. Is there a key I can map to increment and decrement the waypoints?
  6. Try uninstalling SteamVR. You can always put it back if you use it for other VR apps.
  7. Try turning off all AA, AF, Shadows, AO, and SSLR. Also try with Terrain Textures Low. I find even with MSAA x2 the terrain has a constant tick tick while banking.
  8. The only settings I use now in the NCP are Low Latency = Ultra and threaded optimization ON. I have also turned off all shadows and set terrain textures to Low.
  9. I have the G2 as well. I have the Omnicept version with the pupil distance slider. This slider I leave all the way to the left, and I set the pupil distance in OpenXR Toolkit (leave the in game IPD setting at 1.0). I also change the field of view to 90% in the OpenXR toolkit. I believe this improves the focus in the G2. My personal settings are all AA off, AF off, All shadows off, no sharpening in the OpenXR Tookit, and Turbo mode on in the OpenXR Toolkit. I also set OpenXR Custom Resolution in the OpenXR tools to 75%. This is perfection for my 3080Ti. Edit: Just an update, I can hold 60fps with 100% OpenXR Custom Resolution, and no Turbo Mode with the above in game settings. Even MSAA x2 causes the terrain to tick tick as you bank in my PG Dogfight mission (16 plane furball).
  10. I disabled Hyperthreading in my BIOS to clear this up. Also, shadows are a bit funky with the new lighting when the sun is low on the horizon. I have all shadows off (I fly at dusk and dawn usually, so I don't really miss them).
  11. The issue where labels only appear in one eye. As for HT, it is a know fact that timeslicing adds latency. That's why process lasso improves performance.
  12. I had it. I disabled HyperThreading in my BIOS. Cleared up the issue. HT is not required for MT to work.
  13. One technique we used at MSFS is to spawn in with a specific plane at a specific airfield and measure response time. You could choose a canned mission for the Su-25 or TF-51D on the Caucasus map, for example.
  14. The Toolkit merely changes the OpenXR settings. From the guide: Motion reprojection (only with Windows Mixed Reality): Enable overriding the Motion Reprojection mode. Default means to use the system settings (from the OpenXR Tools for Windows Mixed Reality). Lock motion reprojection (only with Windows Mixed Reality, when Motion Reprojection is forced to On Disable automatic motion reprojection adjustment, and lock the frame rate to the desired fraction of the refresh rate.
  15. Tested the AH-64 again, with working controllers, and I could get wobbles if I look up at the clouds with the IHADS displayed. Workaround: turn off clouds.
  16. So, MR unlocked worked like a charm in the f-16 and I did not notice any rotor wobble in the ah-64 as I was struggling to get it airborne (something up with my controllers, I think). This is because with my settings I can maintain 60fps in VR, so very low probability of bad prediction frames. Another easy test, enable the OpenXR toolkit FPS counter. With MR disabled, panning the headset back and forth, you will see double vision in the letters. With MR enabled, it's perfect.
  17. Well, in my case, with my headset set to 60hz, it expects 60fps. If I lock MR at 30fps, then it will create 30 prediction frames to go with the 30 "real" frames. So, the probability for missed targets is high. If I could lock the headset at 30hz, and lock the MR at 30, the probability of a "bad" prediction frame goes way down. I am going to retest MR and try the Unlocked option.
  18. I still run 60hz monitors. Try the sunglasses setting in the OpenXR Toolkit. I saw another member of the community said that helped with the flicker.
  19. There are a lot of variables at play here. In my G2, if I turn up the Shaking Reduction, the wobbles get worse. I suspect this is because the motion vectors that are used to predict the missing frame are not as accurate. I have the Omnicept version, which has more sensors than the standard G2. So, although I can get MR working pretty good at 60fps, it may not be the same for other hardware.
  20. The toolkit just modifies the OpenXR settings. If you have Turbo Mode on it will disable MR. Or, you leave it set to Default in the toolkit and Disabled in OpenXR. Try turning off shadows and anti-aliasing. Turn Anisotropic filtering to x16 to help with the jaggies. Low Terrain Textures and "lower" View Range helps too.
  21. If I set the headset to 90hz, I can get 70-80 fps on my PG Dogfight mission with the above settings. However, the extra frames are not really noticeable.
  22. Here's mine. I have found that even MSAA x2 causes a slight stutter in the ground, so I have ALL shadows off, AA off, SSAO off, SSLR off, Anisotropic Filtering x16 (to help with the jaggies), and Turbo Mode ON in the OpenXR Toolkit. Upscaling creates color banding in the sky textures, so I have it at 100% (no scaling) with Sharpening to taste. At 60hz I am getting a solid 60fps with my G2 and 3080Ti. Also, Low Terrain Textures helps quite a bit.
  23. Enable the advanced OpenXR Toolkit FPS counter. It makes it very easy to see the GPU and CPU frame times.
  24. HT is not required for MT. I have mine disabled, and it's fine. Disabling it fixed the missing labels for me.
×
×
  • Create New...