Jump to content

Glide

Members
 View Profile  See their activity

  • Posts

    1421

  • Joined

  • Last visited

 Content Type 

Everything posted by Glide

  1. Glide
    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.
  2. Glide
    See my post here: You were in OpenXR. Just launch Windows Mixed Reality Portal, leave it running, then launch DCS. Glad it's working.
  3. Glide
    Is there a key I can map to increment and decrement the waypoints?
  4. Glide
    Try uninstalling SteamVR. You can always put it back if you use it for other VR apps.
  5. Glide
    OpenXR Toolkit 1.3.0 is out.
  6. Glide
    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.
  7. Glide
    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).
  8. Glide
    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.
  9. Glide
    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.
  10. Glide
    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.
  11. Glide
    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.
  12. Glide
    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.
  13. Glide
    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.
  14. Glide
    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.
  15. Glide
    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.
  16. Glide
    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.
  17. Glide
    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.
  18. Glide
    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.
  19. Glide
    HT is not required for MT. I have mine disabled, and it's fine. Disabling it fixed the missing labels for me.
  20. Glide
    It looks to me like the new lighting as been added to the other maps, and when the sun is low on the horizon, it can do strange things with reflections.
  21. Glide
    I leave the VR settings in Game at defaults. Also, I have ALL shadows turned off in this test with Ambient Occlusion and Light Reflections ON. I also have Low Latency Mode = Ultra in the NCP which should take the heat off the GPU a bit (prevents the card from buffering frames, just like Framerate Limits do). And, I had to add the bin-MT FOLDER to the NCP so it would not conflict with the default DCS.exe settings.
  22. Glide
    Just to clarify your setup, you have OpenXR which comes with Windows, and you have OpenXR Tools from the MS Store to allow you to change your resolution. And you have OpenXR Toolkit (Github) for all the goodies it brings (I have it set to 75% CAS in this shot with no Turbo Mode). I tested 75% OXR/75% NIS with Tubro Mode ON and got a solid 60fps. When I bumped it up to 80/80, it was getting ~55 fps in the AH-64D. So, my sweet spot with the 3080Ti is 75/75. Note the numbers may be different for your hardware. Just to make the math simple, if you have 100 pixels, and you set OpenXR to 75%, it's like running a 4k monitor at 3k (75 pixels). NIS 75% tells the card to render at (.75 x 75) 55.5 pixels, and scale up to 75 pixels. Play with the numbers until you get the best results.
  23. Glide
    I added the bin-MT folder to the control panel for testing so it wouldn't conflict with my normal settings.
  24. Glide
    Create a shortcut with these parameters for the MT exe. Put the shortcut on your desktop or a DCS Repair may delete it. My G2 is working great with the MT build. I am even getting great results with Motion Reprojection. I have my headset at 60hz, and I'm getting 60fps in VR on my PG Dogfight mission. I've added 75% NIS scaling in OXRTK, nothing more. Low Terrain Texture resolution in game settings helps.
  25. Glide
    Is there any reason to test Nvidia Control panel settings in MT? Does the MT build have the new graphics pipeline? Edit: sorry, didn't notice this was an F-14 thread. Should go in main feedback.
×
×
  • Create New...