bandit648

I suspected no issue with overcast so thanks for confirming. For now I'll be using dynamic weather. I just learned that CombatFlite can also generate dynamic weather conditions and it's super easy to use.. great work-around until ED fixes this. https://www.combatflite.com/ Does anyone know if there's a way to control the cloud base level with dynamic weather? The default seems to be around 8000 ft and I haven't found any way of changing that yet.

Adding some more test results. The issue is reproducible in the "Stable Release" version 2.5.3.24984 also so I suspect this has existed for some time. Here is my test flight in F/A-18C over SOH map. Static weather clouds set to level 8. Flight time is 7 minutes.

I tested this as well and didn't get any stuttering until I added static weather clouds at level 5 to 8. I didn't test full overcast. So, the problem appears to be with the clouds. For some reason the same clouds added through dynamic weather run perfectly fine.

This guy did a fantastic tutorial on how to create custom dynamic weather profiles. It's a pain but it's worth it for the performance difference.

It's kind of shocking the difference dynamic weather makes. The problem is that configuring it is not as easy as it should be. I recommend people setup a few different dynamic weather profiles and save them for use in place of static weather. The other thing that annoys me is how the cirrus clouds are programmed to fade in and out every few minutes. There are some simple things like that could easily be fixed. The addition of some hi-res cirrus cloud textures would improve the look of the sim at the same time.

When it comes to stuttering in DCS there can be a million different causes but one thing is for certain - static weather causes stuttering and dynamic weather does not. I know this has been mentioned on the forums before by others so I decided to test it for myself. Here are the results- I setup a simple mission on the SOH map with 41 units present. I'm cruising in the F/A-18C at 25000 ft for approximately 7 minutes over heavy cloud cover. I turned on FPS logging in MSI Afterburner and observed the results. In the first test, I had static weather settings with clouds set to 8 with rain on and winds at 10 knots. Many stutters were recorded with the worst dip was from 60 down to 40 fps. These are major stutters. In the second test I used a dynamic weather profile I setup that has heavy clouds, winds and rain. The results speak for themselves. I'd like the dev's to recognize this as an offical bug and hopefully fix it. I bet a lot of the complaints about suttering are because of this.

Yes exactly.. this used to be not so much of an issue since everyone was gaming on 1080p @ 60fps with v-sync on. Now many more people own high refresh-rate displays with VRR in the mix as well.

Glad it works for you! I'm thinking we should ask the ED dev's to fix the in-game limiter so we can all just use that. Technically the in-game limiter should offer the best performance but the DCS one is broken.

I'm not sure why some insist on acting like this issue doesn't exit. I've tested TrackIR on two different systems and in four different sims and they all do the same micro-stuttering unless locked at 60 fps. I know that you and Goa tried to find a solution for this as well. There may not be one but I've opened another case with NaturalPoint to see what they say.

Maybe we should take the discussion over to guru3d forum and see what the folks over there say. I'm saying that capping my game at 60 fps while running at 144hz does not disengage G-Sync as you are claiming. You are absolutely right that capping at 58 fps on a 60hz panel is ideal for G-Sync.. No argument there. Is 58 fps ideal for TrackIR? Not in my experience. Most people who have G-Sync have 100hz or higher monitors so advice that 58 fps is one size fits all setting is not good advice.

So this thread is really to discuss the best method of fps locking. In my tests, NVInspector "Limiter V2 - All Off" gets the best results and maintains the best lock on 60 fps. RTSS fluctuates a lot, especially under load in heavy missions. RTSS supposedly has lower input lag but no one has tested Limiter V2 so we don't know. And really, who cares? This isn't CS:GO we're playing here. 30mikemike, I think you mean NVInspector as NVCP doesn't have those options. I'll try the v-sync @ 1/2 refresh rate and report back. Thanks.

You're running an older Nvidia driver, that's why. Limiter V2 was introduced in a more recent driver, not sure when.

I just use the base/global profile since I don't play many other games. But, if you just want to affect DCS choose the "Digital Combat Simulator: Black Shark" profile. Then modify the following: Frame Rate Limiter: 60 FPS Frame Rate Limiter Mode: "Limiter V2 - Force Off [Enables Limiter V1 (Less Input Lag)] Click Apply Changes

So correct me if I'm wrong, but isn't the blurbusters recommendation to cap 3 fps below your refresh rate based on if your fps is expected to exceed your refresh rate. You can run G-Sync perfectly fine at 60hz, but if your fps goes to 61 or above then you will experience tearing without v-sync enabled.

Yes, VSYNC will act as a frame limiter and cap your fps at 60. I think this interferes with G-Sync though as it didn't perform well for me. For me, the best results were leaving v-sync off in NVCP, capping fps at 60 with NVInspector "Limiter V2 - All off" option, and running my monitor at 144hz with G-Sync on in Fullscreen mode. The other thing I found that messes things up is the in-game fps limiter. In the graphics.lua file there is a line "maxfps = 180;". I leave it disabled by simply commenting it out (just put -- in front of it). Technically the in-game fps limiter should be the best since its capping the frames at the source. However, the DCS one is terrible. If I lock at 60 with "maxfps" I get terrible results compared to RTSS or NVI. That thing should just be disabled by default.

I can't, I modded textures from an addon I own for another sim to work in DCS. However, it would not be hard at all for a talented texture artist to make new cirrus clouds for DCS. If I can find the time I'll try to make my own that I could release as a mod. Maybe we can talk someone who is good with textures into making some for us :music_whistling: Maybe someone like... oh, I dunno... Mustang??? :helpsmilie:

G-Sync is supposed to work UP TO the refresh rate of the monitor, not less than. Maybe on some monitors this is an issue, hence the recommendation to cap fps lower then the refresh rate. On my monitor, I can run at 60hz/60fps with no tearing and I can also run all the way up to 144hz with no tearing. As far as TrackIR is concerned, I don't know why some people say it's smooth for them with variable fps while others like myself only see smooth tracking at a locked 60 fps. TrackIR updates at 120hz so according to NaturalPoint you should only expect smooth tracking at 30/60/120 fps. That's exactly what I observe as well. If you make quick jerky head movements back and forth you don't notice it, it's only with slow movement that the microstutter/jerky movement is noticeable. I liked my XB321HK also but the artifact glitch was something that bothered me from day one. I didn't just read about it in the forums, I saw it with my own eyes. Then I went to the forums and found other people saw it too... and Acer was doing nothing about it. For me, that was too much given the high cost of the monitor so I demanded my money back.

My guess on the game is a recently released flight "combat" game for Playstation 4 :thumbup: I think back in 2017 Wag's said they were working on a new weather engine for the 2.5 update. This got me really excited about 2.5 but sadly here we are in 2019 without even a single WIP screenshot of new weather. There has also been no mention of work on a new weather engine so I'm suspecting that work has been shelved for now. That being said.. I'm not sure why a 3rd party developer or mod team couldn't make some improvements to the look of the current weather. I've played around with adding HD cirrus cloud textures and it's pretty easy to do and looks much better then the stock ones. Modding the cumulus clouds appears to be a little more tricky however. Here's what it would look like with 2048x2048 cirrus cloud textures...

I encourage you to do your own testing on this subject. You should be able to run G-Sync at 60hz / 60 fps just fine. TrackIR is certainly smoother at 60 fps. Download the Nvidia Pendulum demo and do some tests and see what works and what doesn't. My Monitor, runs G-Sync perfectly at 60hz. I have the LG 32GK850G 32-Inch 1440p/144hz G-Sync Monitor. https://www.nvidia.com/coolstuff/demos#!/g-sync I suspect advice on sites like Guru3d is geared towards the masses playing first person shooters and not guys running flight sims with TrackIR in the mix. You can setup logging in MSI Afterburner to track your fps. Just go to settings, monitor tab and select a location for your log file. Then setup hotkey's to turn it on/off. How do you like your Acer XB321HK? I used to have that monitor. I owned it for around 6 months before forcing Acer to give me my money back on it. The monitor has this intermittent artifact glitch that Acer apparently had no interest in fixing. Lots of discussion about it on the Acer forums.

Alright gentlemen, I did some benchmarking tests with a mission I made on the Caucasus map. The mission has 145 units total. I flew for 5 minutes with heavy action and saved the recording to use for the test. The total time of each test was 5 minutes. In my experience, 60 fps locked with NVInspector is the smoothest. The test results also show that NVI maintained a better lock on 60 fps than Rivatuner. Rivatuner 58 fps lock with v-sync on in NVCP didn't work well for me. 60 fps appears much smoother. You can open the attached files with MSI Afterburner for graph view, or just view them as a regular text file. rivatuner_60fps_lock_144hz_vsync_off.txt NVI_LimiterV2_60fps_lock_144hz_vsync_off.txt uncapped.txt

The problem is TrackIR. Many of us that use it see microstuttering when running at anything other than 60 fps. I'll record fps with Uncapped vs Limiter V2 vs Riva and post the results. Of course if I fly around on an empty map then Riva can maintain a pretty solid lock. The problem occurs when under load in a heavy mission.

I just gave 58 fps lock a quick try and it didn't seem as smooth to me as 60. I'm curious what others will report if they try this. I also get a lot more fps stuttering with rivatuner then I get with NVInspector Limiter v2. I have a heavy test mission where a large number of Russian armored units are advancing on Tbilisi. There's also MRLS positioned on the hills to the North so there's lots of smoke, explosions, etc. When running this mission, I've found that uncapped, I never dip below 60 fps. If I cap with riva, I get stuttering because fps fluctuates a few fps below the cap. NVI Limiter V2 seems to do a better job of hold the fps at whatever I lock it to.

Right, anything above 60 fps on a 60hz monitor will result in screen tearing unless v-sync is enabled. That's the only reason to leave it on, as I said before. I don't believe the Guru3D advice is based on running DCS with TrackIR. As myself and many other forum members have observed, TrackIR in DCS runs the smoothest at 60fps. As far as input lag goes, blurbusters said they hadn't confirmed what the input lag is with the new LIMITER V2 option in NVInspector. As of Nvidia Profile Inspector version 2.1.3.6 and Nvidia driver branch R381 or later, a new “Frame Rate Limiter Mode” dropdown has been introduced with a “Limiter V2 – Force Off” This option claims to reduce the limiter’s input lag; exactly by how much, and with what combination of settings, remains to be determined. I'll try the 58 fps advice and report back. I'll set my 144hz monitor to 60hz, Enable G-sync Full screen mode, Enable V-sync in NVCP, and cap fps with rivatuner at 58 fps. Not expecting the smoothest TrackIR experience but who knows...

What I read on blurbusters was that the NVInspector Limiter V2 was supposed to have lower input lag, but they hadn't confirmed it because they didn't test it. In the testing they did do, rivatuner had the lowest. What I'm saying is that riva doesn't hold a solid 60 fps lock very well. NVInspector "Limiter V2 - All Off" option appears to be doing a much better job at that then riva.

That is nonsense. All you have to do is turn on the G-sync indicator in NVCP to see whether or not it's working. How does v-sync kick in when it's forced off in NVCP?