Jump to content

Glide

Members
  • Posts

    1198
  • Joined

  • Last visited

Everything posted by Glide

  1. 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.
  2. 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.
  3. Enable the advanced OpenXR Toolkit FPS counter. It makes it very easy to see the GPU and CPU frame times.
  4. HT is not required for MT. I have mine disabled, and it's fine. Disabling it fixed the missing labels for me.
  5. Make sure you disable Motion Blur. It's not working right now.
  6. 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.
  7. Just some clarity, CPU bound only means your CPU is working harder than your GPU. It does not mean there is something wrong. Ideal conditions are for your GPU frame times to be just a bit lower than your CPU frame times, but never higher. A good test is to cycle Vsync in 2D and watch it switch from GPU to CPU bounded. With Vsync ON the GPU doesn't have to produce as many frames, so it coasts. If you are CPU bounded you should increase your graphic settings until you are see GPU and CPU bounded cycling back and forth (almost equal). This is the same principle as using GPU-z to get your GPU Load to as close to 100% as you can but never over.
  8. 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.
  9. 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.
  10. For the AH-64, MR is not required with these G2 settings: 60hz, OpenXR 75% Custom Resolution, OXRTK 75% NIS (or FSR your choice), and Turbo Mode ON. Solid 60 FPS in combat. Not saying these are THE BEST, but this combination is very nice.
  11. MR is really fussy when the FPS are lower than your target. The more frames it has to create (to fill in) the more chance it will miss the mark and create a wobble. So, at 60hz (G2), if I can maintain 60fps, I won't generate any frames. Results vary depending on the aircraft. The rotors on the AH-64 still cause the HMD to wobble. The prop on the TF-51D is good.
  12. I recall Wags saying in one of his demo videos that there's absolutely no reason to turn on SSAA. Perhaps it's deprecated now.
  13. I added the bin-MT folder to the control panel for testing so it wouldn't conflict with my normal settings.
  14. 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.
  15. 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.
  16. Getting excellent results with my G2 set to 60hz with NIS 75% in OXRTK. I was getting a solid >50pfs in my test missions without MR, so I decided to test it again. I noticed just a couple of artifacts without NIS, but adding a bit of NIS bumped my performance enough that I did not see any in the last mission. 3080Ti. EDIT: Just tested the TF-51D and the AH-64 with these settings, and they were excellent!
  17. Disabling HT in the BIOS did not change this issue. It might be related to the angle of the Sun behind those mountains because after getting on the river, the affect seems to be gone.
  18. I disabled Hyperthreading (HT) in my BIOS, and no more missing labels. BTW, MT ran great with HT disabled.
  19. Confirmed on the non-MT build as well.
  20. Confirmed in the non MT beta. One of my AI groups had this on their wingman (#2 in group).
  21. Seems to be related to Motion Blur. Disabled Motion Blur, and mission launches as normal.
  22. Same results with the F16 Free Flight on Syria. Mods, if you can change the title of this thread, much appreciated.
  23. Strange screen on loading the mission. First I tried a custom Caucasus River Racing mission with the TF-51D, then the canned Instant Action Mission. G2, 3080Ti, high end pc.
×
×
  • Create New...