Jump to content

Glide

Members
  • Posts

    1421
  • Joined

  • Last visited

Everything posted by Glide

  1. This is not implemented. The Sidewinder has more fidelity now. It will switch tracks if a friendly flies in front of it. It will track missiles. It will lose track if the sun is low on the horizon. I watched an Su-34 dodge my 9x from 1.7 nm out! Lucky bum! Man this game is fun!
  2. I have changed my entire view of performance after this thread. I have tried MSAA with SSAA, in fact I'm running MSAA x2 SSAA x2 and SSLR, and DCS is the best looking I have ever seen it. Smooth and sharp. With my 2d system at 4k, you must have at least 30 fps, but any more than that is a waste. For example, if you are turning down your quality settings to get 60 fps, you are wasting 30 fps that can be put toward quality settings. He's right. Crank up the beauty settings until you get a solid 30-40 fps. Leave off the fps counter. Just when you think it's perfect, it gets more perfect.
  3. The Radeon 6800 XT with 16GB of VRAM looks like the best deal for new hardware if you can get them. You can run all the DCS maps with that.
  4. Correct. Max Frame Rate = 60 in the NCP, but be sure to turn OFF vsync and gsync for that test. One other long shot, turn off Shader Cache in NCP. This will eliminate any disk issues. However, your load times will increase the first time you fly a map. Pro tip: if you want a quick way to tell if a setting has cleaned up the stuttering, use Ctrl+Z to speed up time. This makes the stutters much easier to see. Try this on Caucasus with vsync/gsync OFF, MSAA OFF, SSAA OFF, and Shader Cache OFF. I think that is the smoothest I've ever got it.
  5. There's a little more information on setting up each axis and axis tuning in Chucks guides.
  6. I think we know that DCS can't sustain 120 fps with any kind of quality on today's hardware. @Fakum the only thing left to try is a different monitor.
  7. Thank you for making me think. BTW, we didn't say they don't go together, we said they eat up FPS like candy when then are together. I had an interesting experience with your settings. I had been getting 60ish FPS with FAST, and I flew your settings without the FPS counter on. DCS never looked better. It was smooth as silk. Then I turned on the FPS counter and saw 40ish FPS. My cognitive bias kicked in, and I switched back to my previous settings. After all, 60 is better, right? But, I've said 30 should be enough, so I decided to eat my own cooking. I would fly your settings without the FPS counter to see if I could notice anything. I tried vsync ON first, and that synced at a solid 30fps. However, there were moments when it felt like the world was slowing down. Then I tried FAST again, and it was perfection. I'm leaving the FPS counter off for a week with your settings to see if my card can sustain this through a couple dozen dogfights on PG and Caucasus. Thanks for testing. https://en.wikipedia.org/wiki/Cognitive_bias
  8. I'm afraid to run Syria map with High Textures and High Terrain Textures is too much for our 11GB VRAM cards. Drop these down and you can just fit Syria into the dedicated gpu memory and have no stutters. I have put Syria on the shelf until I can upgrade my card. My card gets 70-80 fps as well. Right now I am running NCP Vsync = FAST, and I'm trying SSAA 1.5 and MSAA x2. My card will stay very close to 60 fps on Caucasus and PG with these settings. For me, that's perfect.
  9. So, you are back to getting 120 fps? Stuttering happens when Windows swaps Dedicated GPU memory with Shared GPU memory. This happens when your card runs out of dedicated VRAM. You can watch them happen on the Task Manager performance window for your GPU. You will see copy activity when you experience a stutter. As for where to test. Always test the same mission or set of missions. They can be instant action missions depending on how large. Syria map missions can easily use over 11GB of VRAM from the start. I also have certain textures and views that I always check when I make a change. For example, the seam on the nose of the TF-51D when you add Anisotropic filtering stands out much sharper. Those split second stutters are scattered around the map. There's one right as you pass the fork in the river at Poti on Caucasus. Once upon a time, there was another flight sim with a famous stutter. I was working with the "devs" on the AI changes, and since we had the advanced AI implemented, I developed a technique to replay a mission exactly the same way each time. That's when I discovered the stutters happen in the exact same place, but in a flight sim this was very hard to pin down. The devs could now pinpoint a stutter and begin diagnostics. No more stuttering. Patch #3 , if I recall.
  10. Try Vsync = FAST now in the NCP. This should push your FPS as high as they can go with Vsync on.
  11. @FakumThat's even lower than my performance. My point about vsync and alt+enter is that if you enable vsync in DCS it works both windows and full screen. If you enable vsync or gsync in NCP, it only works in fullscreen mode. Alt+enter toggles fullscreen mode. This makes perfect sense because the card can't know which app to sync with in windowed mode. This is why our fps goes up and down with Alt+enter. Let me know when you test vsync/gsync off completely.
  12. This is why @Fakum gets the better frame rates. Nvidia may have a trouble syncing when DCS is not in fullscreen mode. But, DCS vsync works no matter what.
  13. Nice work! I had forgotten how much I love vsync, so I have traded SSAA and SSLR for vsync. Super nice and smooth. Thanks for testing.
  14. @Fakum @silverdevil I would like you guys to run this test. Turn off vsync/gsync. Turn off MSAA,SSAA,and AF. Water to medium, terrain object shadows off. This is the baseline. Then in the NCP set Max Frame Rate = 90. Then test on Caucasus map. I can't do this because it's way over my specs. This should be just as smooth as vsync ON, but I suspect it will be better because your card has a better chance of hitting 90 than 120. My card can't keep up to that.
  15. Just ran an interesting test. My card does ~70-80 fps on the runway in PG with vsync OFF. When I enable vsync in the NCP and press Alt+Enter, it toggles vsync on and off. ie. it goes from 60 solid fps, to 70-80ish fps and back again. When I enable vsync in DCS settings and press Alt+Enter, it doesn't toggle. Stays at 60fps for both. I tried this with both Full screen selected and deselected.
  16. Huh, I just did a rebuilt. Looks like I guessed right this time.
  17. I was just coming to this. Don't know which settings you can change on the fly in NCP. I always exit DCS, change NCP, then start DCS. Clean slate. No worries, these are not related. I was going to ask if you have the latest Nvidia driver installed. Click the system info button.
  18. This is normal. Its fine to run DCS lower than the desktop resolution, but goes bonkers when you run DCS higher than the desktop resolution. Also, always change only one thing at a time. So, turn off Gsync, leave Vsync off, and test without SSAA or MSAA, Water = Medium, Terrain Shadow's off. This should be your baseline for testing. Then toggle Vsync by changing the Vsync setting in DCS, and compare. I don't see any change, by my card is 3 years old now. I'm going to test with vsync and see.
  19. Turn off all SSAA and MSAA in DCS. You have high resolution, so this should be tolerable. Turn off Terrain Object Shadows to save a bunch of FPS. Turn water to medium to save some FPS. That is a pretty lean setup, and great for testing. Fly like that for a week. Then add back any SSAA or MSAA you feel you need. So glad it's better!
  20. Super High End. To Drool For. I think only the 3090 tops it. @Fakum, if you are still using Gsync, then you are still using the G version of vsync. Have you tried turning off Gsync?
  21. I just noticed that TrackIR samples at 120 fps. @Fakum @silverdevil You both have 120hz native monitors. I wonder if something really strange is going on there. Can you force your monitors to refresh at 100 or 60?
  22. That's great. Not sure what's going on there, but the herring is not so red after all.
×
×
  • Create New...