104th_Money

@Rudel_chw A quick update, I deleted the fxo and metashaders files after the roll back and it fixed the issues with the FPS. But it appeared the rollback itself caused numerous BSOD crashes at the most random times. In the middle of this issue I also unparked the CPU cores which appeared to have no effect on FPS, reverted the unpark back to original which I believed at the time I might have not reverted correctly, installed a windows update and upgraded my CPU to a i9-13900k. I literally couldn’t figure out what the different BSOD crashing issues were with all of the changes. I tried so many different things, using DDU to clean uninstall the Nvidia drivers then reinstalled the previous drivers, cleaned and repaired registry, reseated CPU/cooler and even reinstalled W11 OS while keeping my apps and files and none of it helped at all. In the end I accidentally found that I had left my Asus overclock on from the previous CPU. So I turned that off and then I decided that maybe I should install the latest Nvidia drivers and delete the fxo and metashaders files again to see if that helped. Doing those 2 things solved all problems and everything is back to normal again. What a stressful weekend it was. The moral of the story for anyone reading is to do one thing at a time so you know what that it broke something and save yourself the wild goose chase lol.

Rudel, this fixed 99% of the issues especially the highly fluctuating fps numbers. Thank you so much for responding. TOViper, thank you also for responding. I checked and all settings were still as they were supposed to.

On saturday I updated to the latest Nvidia drivers. I was previously using April 18th version. Opening up DCS I immediately noticed that I was getting major stutters where as before everything was perfectly smooth. It almost seemed like Vsync stopped working as I also get spikes up to 80fps and down to 35fps. Today I rolled back the drivers, or downloaded and reinstalled previous drivers to be exact. However this did not do anything for the problem. When the major stutters start happening, CPU usage is normal at about 35-40% and temps at around 50deg c, ram is between 28-33gb out of 64, GPU usage is at approximately 60% with temps around 50deg c. I am stumped as to what might have changed and why it did not fix itself after the driver rollback.

The Rotorheads MP server has a script that gives coordinates for downed aircraft and actually spawns a soldier at that location for pickup. You have to land and pick up the soldier then it despawns as if he entered the helo. Not sure if it works for AI but it definitely works for player flown aircraft so I dont see why it wouldnt work for AI.

The AI OH-58D damage model shows external damage when hit but takes a significant amount of damage to down aircraft. When aircraft does crash, it doesn't die. Triggers that should activate when the OH-58D is damaged or dead do not work. Retested same triggers with AI UH-60A and the damage/dead triggers work as intended. Also when the aircraft is descending nose down, both rear doors and the left side rear compartment door opens and closes again when climbing nose up.

So just found this by accident...Its in the rear right cockpit of the Mi-26. It looks more detailed that the whole cockpit lol.null

Thanks for the tip Hector, I will try that when I get home from work. I’ve been loving all the extra detail and clarity with the 3090. Overall it’s been performing way above expectations. Just finished retuning gpu fans through Precision X1 and Asus Armory Crate for the cpu to keep the temps at around 50c deg. It’s crazy how much better the trees look, having shadows from objects, visible draw distance at extreme and the cockpit global illumination on. Really increases the immersion level for me. I’ve found only one instance of an issue at Incirlik air base in the Apache. I get some stuttering/fps drop when I’m looking towards the buildings but I think that might be from the Military Aircraft Mod planes textures which I have multiple statics near that area causing it. Another thing that I’ve noticed, and I’m not 100% convinced that what I am experiencing is directly attributed to this but it really seems as though my control inputs seem a bit smoother with a few different aircraft. Almost like having better fps is giving a more condensed or higher control input count allowing just a bit more precision if that makes sense. I noticed it mildly in the F-16, F-18 and the OV-10 Bronco mod but it is definitely more noticeable in the Apache for sure, especially during landings.

Ok so got settings dialed in for custom fan curves and then started maxing out DCS settings. This thing is a beast. I think the only 2 I dont have set to max is the 2 top right dcs settings. Those are at like 80%. Then I couldnt stand the lack of anti-aliasing so I went into the Nvidia control panel and set power to maximum performance and anti-aliasing to 8x. This took care of pretty much everything, no jagged edges like before but couldnt push those settings with the 2080Ti. I am Vsync'd at 60fps and it doesnt budge from there. In the FPS counter I see it saying GPU bound in green with theoretical fps between 145 and 240 fps. Havent tried to uncheck Vsync yet to see if I get screen tearing. So far its been worth every dollar, DCS just looks amazing now!

Ok so I pulled the trigger on the 3090 today, found a brand new in box unopened EVGA RTX Nvidia 3090 FTW3 Ultra for $800. Hoping this will be a beast for me at more than double the Vram from the 2080Ti, faster memory and PCIE 4 instead of PCIE 3. About to head into DCS and start moving up the settings. I'll post back with settings updates later... Thanks again for the input from you all!

I appreciate the input from all of you. My current screen resolution is 2560x1440. My current DCS settings with 2080Ti are not bad at all but I really want to bump up the sliders as well. I am also leaning toward going VR in the very near future as I now have access to an Oculus Quest 2 to try out for free. Im curious to know what CPU you guys are running as well.

Diego, Thanks for the response. Prices are similar for a 3090 Ti to a 4080 but there is something about that 24gb vram vs 16gb vram that has me wary of pulling the trigger on the 4080 when the 3090 or 3090 Ti may or may not be a better choice.

Just asking the question again since I didnt get any feedback...

Hi brain_delay, The used 3090 market prices are really coming down now but my main concern is not really getting a used/new card. I just want to get the best card for DCS but not sure if the 4080 is better than the 3090 solely for DCS. im just not willing to put up the cash to get a 4090 yet and need a short/medium term interim card to hold me over for 6-8 months. If either the 3090 or 4080 satisfy me with good fps/eye candy I doubt I would even want to upgrade to the 4090.

Thanks unlikely_spider, not quite sure why I said 12gb. Maybe its all the numbers and specs getting tossed around in my head over all the possible graphics cards...Went through the same thing before pulling the trigger to buy my new pc parts, took 2 weeks to clear my head from that mess lol.

Just recently put together a new pc build and I would like to upgrade my video card now but the 4090 is just a bit too far out of reach. My 2080Ti just isn't quite keeping up with the new i7-12700k/64gb ram. I have read more than I care to about the 3090 vs the 4080 and by all accounts and every other game out there, the 4080 has newer technology that compensates for the 50% less Vram and makes it the better choice. But I only have my pc to fly DCS and we all know that its a different beast than all others. So my question is, for DCS specifically... Will I benefit more from the 3090 with its 24gb of vram or the newer tech 4080 with its 12gb vram? Thanks for any input!

Predator, I just had this problem occur in the last week. I would open the trackir software and it might last anywhere from 5-45 minutes but the software would always freeze. I tried many things to no avail and finally figured out that my powered USB 3.0 hub was the cause of all the headaches. Plugged directly into the rear I/O and all problems went away. I would suggest moving the plug from the current usb port to another one to see if it corrects the problem.

I updated DCS last night then turned computer off. Booted up awhile later and Windows Defender in Windows 11 Pro flagged this file as a virus. Trojan:Win32/Wacatac.B!@ml. Its a Combined Arms file. At first I didnt catch that it was from DCS and seeing that WD was saying its severe I isolated the threat. After booting into DCS I got a Combine Arms not available message. I turned off WD and repaired my installation and now CA is working properly but it keeps triggering a WD warning even though WD is now turned off.

Try resaving mission in 2.8, although I havent had any issues with pre 2.8 missions myself.

It appears that most of the mods equipped with dispensers have a weapon system lua created that corresponds with powering up the system. The A-29 mod has countermeasures working with no power on, i tried to edit it for another mod but could never get it working.

I tried to edit the pylon locations in the weapons loadout lua file before. It doesnt seem to work. I think it additional changes are needed in the aircraft .dll file.

@Flanky83 You should not need your internet providers permission to port forward. This is something that is done on the router at your home through the settings. About 10 years ago I did have a router from my internet provider that I had to log in online to accomplish the port forwarding but with any modern router you should be able to do it just fine.

I have seen that happen myself, the terrain is just too steep and takes an abnormal approach to land. I get around it by changing the wind direction so they land on the other side.

Back in 2018 I ran DCS on a 2013 Mac Pro trash can using bootcamp and windows 10. It was the 8-core 3.0ghz model with 32gb ram, dual D700 6gb graphics cards and 1tb SSD. It didnt struggle at all with 1080 resolution. I was able to use the latest comparable AMD video drivers since Windows was running natively.

What is your approach and touchdown speed? Sounds like you are coming in too fast. Aerobraking is the standard way to slow down in the F-16. It prevents the wheel brakes from getting too hot. You need to be at least 13 deg for max aerobrake effectiveness.

Im willing to bet that the wobbling during startup has to do with the rigidness of the landing skids or lack of. It seems like they are flexing too much allowing the body of the helicopter to sway everything stabilizes.