Tango777

First of all, before I forget to write it here, there are no Mods in my DCS install. It doesn't matter if I run DCS or DCS MT (both are stable versions and not beta), it always hangs at the "Waiting for Pool Tasks" - 1 stage (I hope I got the name of the stage right). It did load a mission once out of 6 hangups - or crashes - whatever term you want to use. I cannot even take a screenshot. It was running great 24 hours ago. I have ran Repair DCS World twice, once with the Check modified files setting, and once for the Check all files setting. It finishes both times and it says that DCS has been repaired successfully. I have rebooted the PC twice (after running DCS Repair) and that does not help, DCS still crashes at the same stage. My specs are: i7-13700F - 32GB DDR5 RAM - NVIDIA GeForce RTX 4060Ti 16GB - 2TB NVMe SSD - Windows 11 I don't know what to do. So help would be greatly appreciated. DCS log is attached. dcs.log.old dcs.log

SharpeXB, Thank you so much! I did what you said and everything works now, and the FPS are smooth as glass! Tango777

Thanks for the replies here, they helped somewhat. I have dialed many settings way down and I am getting a type of stuttering effect, and I do not know why. I am still in the F-18, so it is not like a graphics hog like the F-14. I am attaching my settings a screen shot of my settings. This is a new pc and it is light years ahead, and has so much more "horsepower", of my old pc and my old pc did not have this stuttering type effect: i7-13700F - 32GB DDR5 RAM - NVIDIA GeForce RTX 4060Ti 16GB - 2TB NVMe SSD - Windows 11

So it chooses to blur when outside the airplane but not blur objects from inside the airplane? Why do the fps take a massive hit when DLSS is turned off? I am attaching a screenshot.

I just did and it is set to Quality which is the lowest setting.

I have the majority of the settings set pretty high compared to where they were set at after I installed DCS, but even though my computer handles DCS or DCS MT without any hit to the FPS regardless as to how high the settings are with DLSS turned on, things still look blurry (similar to heat blur behind the engines) UNTIL I zoom in or get close to an object. This also happens in the cockpit because if I zoom in on some instruments, then the blurry effect almost goes away. When I turn DLSS off the blur goes away if I am in the cockpit but the FPS takes a huge hit. All graphics from inside the cockpit are great, but when I switch to an outside view the graphics are horrible except the airplane as the airplane looks great. But the ground and sky from an outside view are as if I have all graphic settings set to the lowest possible setting possible and the FPS are still getting hammered as if I have every setting turned to the max. I have tampered around with the settings the best I know how and I cannot get this annoying visual problem figured out. If anyone can point me in the right direction as to what is causing this, I would be very grateful! My specs are: i7-13700F - 32GB DDR5 RAM - NVIDIA GeForce RTX 4060Ti 16GB - 2TB NVMe SSD - Windows 11

Do you happen to have a ballpark as to when the next stable DCS update is scheduled?

This is a very different problem. The previous problem was DCS hanging upon mission loading at World Preload 1/60. That problem was fixed in the latest stable DCS release. This problem causes DCS to hang just before the F14 hits the water. I don't know how I could get a log when DCS has hung.

I now have the latest stable version of DCS that updated today and when the F14 crashes DCS hangs. The screen remains in the current view, in my case the cockpit. There isn't 1 key on the keyboard that makes DCS respond. Escape key on the keyboard does not do anything, even if I let DCS sit there (looking at the instrument panel in my case) for 5 minutes. Technically I do not witness the crash. DCS hangs just before the F14 splashes and explodes. I am just in the cockpit looking at the water outside the front of the canopy. Ctrl + Alt + Del does work, but it takes a little while for the task manager to populate, and then from there it shows that DCS is not responding. Click on end task and that is the only way to close DCS.

@Naquaii Thank you.

It looks like some of the posts are saying that the latest update to DCS stable version has fixed the F-14 freeze when the mission is loading. I have the latest version of the stable version and I have ran the Repair DCS World. I can only fly the F-14 once, and if I try to fly it again DCS still freezes up at World Preload 1/60. DCS not only freezes but Windows 10 64-bit still locks up so badly that Task Manager or anything else is not even clickable. I have to Ctrl+Alt+Delete and click on sign out of Windows in order to prevent me from having to hold down on the computer's power button for a hard shutdown. If I want to fly the F-14 again, which I do, I have to close out of DCS and re-start DCS. This does not happen with any other airplane.

@Flappie, When I say that DCS hangs, I mean that it makes Windows lock up so bad that Task Manager or anything else is not even clickable. I have to Ctrl+Alt+Delete and click on sign out.

I read in another thread that DCS might not hang on the F-14 if you do not fly the same mission again, or do not fly the F-14 back to back. I tried that: I flew 1 mission in the F-14, and then a few missions in the F-18, and then I went back to the F-14. Right at World Preload 1/60, DCS hanged and I had to restart everything. So in my case it does not matter: I can only fly the F-14 once and then restart DCS if I want to fly the F-14 again. This is single player with DCS Stable version 2.7.2. in Windows 10 64-bit up to date and all drivers, including NVIDIA video driver up to date. And yes, I have ran the DCS Repair and it does not fix the problem.

Glad to hear that they are working on it because it happens to me every time when I go to fly another mission. I fly a mission, end it, and go to fly again. It then locks the computer up right at World Preload 1/60 every time. Windows locks up so badly that Task Manager or anything else is not even clickable. I have to Ctrl+Alt+Delete and click on sign out. Never happened before the latest update on the stable version.

So when I re-spawn or start a different mission in a different F-14, why is the damage still active?

Shouldn't the request repair function be something that works?

Has anyone experienced the following types of problems? The following was in the F-14B model and I am running the latest stable version of DCS. I landed back at Nellis after a successful mission (downloaded mission) and took no damage. I exited the mission and selected another mission out of Nellis, after takeoff the slats retracted and the 2 most inner flaps also retracted, but the rest of the flaps did not retract. I turned around and landed back at Nellis, I cycled the flaps toggle many times but the "main" flaps would not retract. The wings were not swept back and set to auto mode, the reset button did nothing. I asked for maintenance after both engines were completely shut down, and maintenance said 'Roger', so I assumed they were on their way. The countdown every 10 seconds for the maintenance crew was not popping up on my computer monitor. I waited several minutes and they never showed up. I asked for maintenance again and they said 'Roger', but never showed up. I exited and chose another mission out of Nellis and the flaps in a different F-14B had the same problem with the flaps. The other thing that I have noticed is that on every mission that starts on the runway, or whenever a mission starts with the engines running at mission start, the compasses (whiskey and computer) become uncalibrated throughout the mission. On the HUD, VSD, or NAV display will all show a heading of 340, but thankfully for the map (F10) I am actually flying South on a 170 or 180 heading and not Northwest. Nellis is a blue (friendly) airport in all cases here. None of this happened before the release of the latest release of DCS stable version.

The following was in the F-14B model and I am running the latest stable version of DCS. I landed back at Nellis after a successful mission (downloaded mission) and took no damage. I exited the mission and selected another mission out of Nellis, after takeoff the slats retracted and the 2 most inner flaps also retracted, but the rest of the flaps did not retract. I turned around and landed back at Nellis, I cycled the flaps toggle many times but the "main" flaps would not retract. The wings were not swept back and set to auto mode, the reset button did nothing. I asked for maintenance after both engines were completely shut down, and maintenance said 'Roger', so I assumed they were on their way. The countdown every 10 seconds for the maintenance crew was not popping up on my computer monitor. I waited several minutes and they never showed up. I asked for maintenance again and they said 'Roger', but never showed up. I exited and chose another mission out of Nellis and the flaps in a different F-14B had the same problem with the flaps. The other thing that I have noticed is that on every mission that starts on the runway, or whenever a mission starts with the engines running at mission start, the compasses (whiskey and computer) become uncalibrated throughout the mission. On the HUD, VSD, or NAV display will all show a heading of 340, but thankfully for the map (F10) I am actually flying South on a 170 or 180 heading and not Northwest. Nellis is a blue (friendly) airport in all cases here. None of this happened before the release of the latest release of DCS stable version.

In the past I have only used them on rotary-wing aircraft and not fixed-wing aircraft.

I see. The reason I would use them as a last resort was because I saw some tutorials on the matter on youtube.

In the A-10C, I used to be able to take out an air threat with a Maverick's onboard camera if I were to be out of my Aim-9s. In the A-10C II, I can lock onto the air threat without a problem just like in the A-10C. But the problem is that in the A-10C II, the Maverick's camera does not remain locked on to the airborne target after I fire it. Instead the Maverick just continues to fly straight, and then it pitches down and into the ground.

Thank you!

I have been trying to install it via the Module Manager, but unlike the F-16 and F-14 trial, DCS gives me an error. I am attaching a screen shot.

When I mentioned what the F-16s look like on my end during a mission, I meant that they all look like this no matter what airplane I am flying: https://www.mutleyshangar.com/reviews/sean/dcsa10/data/thumbnails1/ai_f16.jpg Regardless of what mission I download from DCS, or what mission DCS auto-generates, the majority of all AI airplanes have a very low resolution which is fine. For whatever reason unknown to me all helicopters though have much higher textures than AI airplanes, but with the exception of the rescue chopper Sea Hawk that flies alongside the starboard side of the Stennis. If the AI airplanes are on my fighter wing in the mission, then those are the only airplanes that have normal high def textures. draconus, no complaints here just questions and opinion. Developers usually have a rig that blows the average gamer's rig out of the water, no pun intended. A developer e-mailed me their specs of their rig and I was blown away because it is in the thousands of Dollars. So whenever a developer tests something for the creation of necessary required specs, I assume they are testing it on their rig they use for design and development? If that is the case, then of course they are going to say that their development of the Supercarrier in this case has little to no slideshow effect or fps hit. A couple of posts here in this forum are saying that 16gb RAM or 20gb RAM is considered minimum or behind the times already. I searched this forum and more than a few Viggen owners had the exact same fps problems that I did, and this was only a year ago. I checked their rig's specs and some had specs that really overshadow my specs. But now the Viggen works great on my rig regardless of altitude, weather, and the amount of action going on in any given terrain and mission. Heatblur must have figured that something on their end needed to be optimized for fps reasons. So the release from Heatblur that DCS put out in a beta update in February last year fixed the low fps and stuttering problems for powerful rigs and my rig. The Viggen was released to the public in 2017, DCS 2.5 probably had something to do with it, and the Viggen fps issue fix came out more than a year after release. Before that release the likely problem was some calling my computer a low spec computer, and boy am I glad that was 100% wrong. All that to say this: It would be interesting if Heatblur is able to do the same to the F-14 as they did to the Viggen. If the F-14 will always be such a demanding module on computing power, I wonder if this is a turning point or a new normal to upgrade (not just more RAM or a new video card) or buy a new computer every couple of years as to what is to come? It was not too long ago that I was told that my computer was a pretty nice rig here in the forums.

As soon as everything loads when using the F-18 on high settings when other modules are around the fps are great. But the F-5s and F-16s you reference load instantly because their exterior model looks like a sim from the early 1990s. No different than what B-52s or F-117s look like in current DCS missions. Once everything loads on the current Stennis, the F-18 runs just fine as other F-18s that are not part of the mission are for some reason dark and have a very rough look just like the B-52s or B-1s. The F-18s that are active in a mission do have the same external details as mine and when they are in play my fps takes a bit of a hit but for no more than 45 seconds, by that time they are in my GPU's memory. Please read what I said about Heatblur's Viggen. What I will add is that the Viggen was not fun to fly for a long time until they released a big update on it last year. I do remember reading a "zillion" of complaints about it. Immediately after that update though, the fps improved from 0 to 10, no more stuttering, and no more cockpit re-draws. I was told over a year ago, after I purchased it, that the Viggen was a module that demanded a ton of computing power. But now I fly it often on the same computer I had at that time, the same computer that I have now. I am running the latest version of DCS.