goon3r

Thanks, that was it! As a point of feedback here, this looks like an opportunity to improve the mission description and maybe simplify the trigger a bit. It feels like this is far too specific of an action for what is something as arbitrary as a fly-over. I would recommend there is either a clear explanation of what is needed, or loosen the conditions a bit.

Having similar issues as the OP. Looking for a little help. I've "Completed" the very first mission 3-4 times and so far unclear what the problem is for me to actually move forward in the campaign. I'm flying over the airbases roughly 1500ft (AGL), eventually I turn towards WP7 and I destroy all of the practice targets myself or let my wingman finish them off before we return to the carrier. Notes: I've never seen the skip refueling option in the menu. Should that be available after flying over Senaki ? Is the expectation to destroy all of the practice targets ?

ED Team, is there any eta on when we might get a fix for this ? I feel the A10C module should receive better support for this type of issue. I realize the solution might not be trivial but its been several months with no updates.

Could you update the thread title as well to reflect the problem it addresses ? It might make it clearer rather than just the description of the solution.

Thanks! Super happy as I wasted countless hours trying different things this past week and nothing was making any sense.

So, I've validated that the problem here is my setup and the Seagate Firecuda 520 drive. I tried a replacement unit of the same model drive and found the same issue persisted. I was finally able to resolve by replacing with a Samsung 970 NVME drive. This is without having to touch any bios, windows, or DCS settings.

No, I haven't tried this since most of the reading I've done suggests I should enable that. Whats the purpose of that setting anyway ?

I'm not using VR but I see its set to 1.0. My resolution is 3440 x 1440. Also here's a comparison of what I see as far as disk usage when running on the nvme drive vs the sata drive: Notice the spikes on the faster drive and continual disk access vs on the slower drive. Also, notice the transfer rate difference. NVME SATA

Updated bios, and checked a few settings related the onboard controllers and nvme settings. Reset the to defaults as well. As I mentioned this is a clean build so Chrome, and dcs are the only things installed apart from basic drivers. I also am confident the NVME drive isn't overheating. At least I haven't seen signs of throttling even in benchmark tests. Is this just an issue with DCS ? Anyone with a similar setup ? Just to remind, I am on stable build - 2.5.5.

So, my suspicion of this being a storage related issue is confirmed, running the same graphical settings on a 5 year old Sata 2 drive works perfectly for DCS on this new build. I also ran another test where I installed Windows on the SATA drive and DCS on the NVME drive and the stuttering was there again. At this point, this looks to be some type of issue with issue with how DCS is running in that name drive. I'm not sure of a solution at this point.

On the Ryzen 9, I think this is called SMT. I tried it with no difference. I'm not sure about this. This same GPU performed fine with the same graphics settings and resolution on a Sata II drive. I have a gysnc monitor and it's always worked fine. I just tried forcing vsync in the nvidia settings but that didn't make a difference.

This is a clean install of OS and Game.

Hi All, Looking for a little help with a weird issue on a new build. I've been testing out the new build and noticed bad stutters in DCS. I've tried OB/Stable and different modules and maps with the same result. Also tried uninstall/reinstall as well. These are all new parts except the GPU however other games I've testing have worked fine. I've tried full/window and max preload radius, v-sync on/off. My previous build was on a Sata SSD with a 4790k and ran perfectly. Specs: R9 3900x ASUS x570 Pro FireCuda 520 1TB NVME GTX 1080TI 32GB DDR4 W10 Pro I made a short video of the issue. It's easy to see if you look at the buildings in the center of the screen. Is there a setting in windows or DCS that I should be looking at ?

Thanks for insight Frederf. Unfortunately, I've been using the same install for a few years and honestly can't remember the history of my installs. My DCS install folder has mushroomed to 150gb which is almost half of my ssd. I cant imagine having 2 installs! I wish the instructions to do this worked as described in the thread i linked to. In theory, this should work fine. I will need to be mindful of updates I guess. I've had 2-3 cases recently where the a few bugs in the beta build broke the game for me. I was hoping for a quick opt out of beta.

Hi All, looking for a little help with release versions. I would like to stay on the release branch. Following the instructions here: https://forums.eagle.ru/showthread.php?t=114030 I ran this command and downgraded back to release branch: DCS_updater.exe update @release However, having done this I still get regular prompts for the beta. Is this expected ? My assumption here was that this was a permanent switching of my install to release branch and I would only get release updates. Can someone please clarify ?

Hi All, looking for a little help with release versions. I would like to stay on the release branch. Following the instructions here: https://forums.eagle.ru/showthread.php?t=114030 I ran this command and downgraded back to release branch: DCS_updater.exe update @release However, having done this I still get regular prompts for the beta. Is this expected ? My assumption here was that this was a permanent switching of my install to release branch. ****Apologies for posting this here, I should have been in the DCS world 2.5 section...

Has this actually been reported/acknowledged as a bug ? I just reverted back to 2.5.3.23225 and the elevation control works fine again.

Thanks for this. I am suspecting this mission puts some serious strain on the machine. This is my first time playing the huey campaign. I started mission 6 just when I got this new card so I immediately became concerned.

Thanks for this. I tried changing settings to match yours 1 step at a time. The only one that made any impact was water. Dropping that down to medium got be almost 30fps at the mission start, was 20fps previously. I have everything else back to high/max except water.

So I can get the performance up by dropping the textures down but I haven't bothered with reducing the resolution. I am starting to think this is just the sim because the card and my machine performs flawlessly in other games/situations/benchmarks. I am not sure if anyone with similar specs and resolution is able to test, but at 1440p all high preset I cannot pass 20fps. When the mission starts, there are about 6 different AI helicopters around the player all starting engines and or taking off. Its a huge amount happening at this point. Someone commented earlier about getting 40-60fps but they were running 1080p. I was hoping to be able to game with the 1080TI comfortably at 4k but now I am leery of investing in a new monitor if the card is choking at 1440p.

So, I was doing a free flight over Vegas in 2.xx and was able to get my FPS from well up over 100 by turning off Vsync. Previously it was capped at 60. The same vysnc change doesn't work on 1.5x. I see no difference. Here are my Control Panel settings: Starting to wonder if I should consider a reinstall of DCS 1.5x.

Starting to wonder the same myself.. Yep, you can also access them from the main menu, under missions and browse to the campaigns folder :

Did this, but DCS performance is around the same. Performance in other applications seem fine. Ran some 3Dmark tests and Cinebench so I think the drivers and hardware are fine.

Do you mind loading up that mission with the "high" preset settings and report back ? I'll try to get the control panel screenshot once I'm back home.

I've played a few other missions and things seem mostly fine, I usually average in the ~60 range. I'll need to try a few more situations and see if there is another module you can do a similar test with.