Teamasian

DCS was stuttering more because of the e-cores rather than the unparked cores issue.

It turns out that a simple edit in registry editor was insufficient to unpark the cores, and that using e-cores caused stuttering in DCS. I managed to fix that with process lasso, so the problem is gone now. Thanks for the help!

Both of these were correct as solutions. Editing parking/unparking cores through registry editor didn't actually change anything, but I'm able to force it through process lasso. Additionally, forcing DCS to use P-cores only within process lasso removed the stuttering entirely, even on large missions. Thanks for the help y'all!

The cleanup of the input folder seems to speed up loading times quite significantly, which is extremely helpful. Thanks for the help on that! The stutter to crash issue remains, but if it helps at all, the game will continue to stutter in the main menu and worsen in the encyclopedia after quitting a mission (launcher is disabled, so no problems from there).

For the last few patches, I've noticed that the game is starting to become more and more plagued with horrendous stuttering issues. The last patch, 2.9.11.4686 has turned the game into an actual powerpoint presentation as I now have to click to advance exactly 1 frame in DCS during freezes. So far, I've been able to conclude that these issues have nothing to do with my graphics settings, as the game occasionally still manages to stutter itself to death in the main menu with low or high presets. During gameplay, it seems like the stutter occurs during takeoffs/landings or when approaching a mass of vehicles, but is not always consistent. This stutter often escalates into a freeze for 10-20 seconds if no input is made. Clicking my mouse alleviates the problem for a stunning 1-2 seconds before the game freezes again. Specs: Intel® Core™ i9-14900KF, NVIDIA GeForce RTX 4080, 32 GB RAM I've attempted to solve this issue using just about everything I have come across in the forums, bar changing mouse polling rate. I'm out of ideas at this point, so any help is appreciated. Note: this issue is only really prevalent in medium to large missions, but still happens in missions with 2-4 units if they are destroyed close enough. dcs.log

Unparking cores seems to be ineffective, and the severe stuttering is still sometimes present, especially if I run DCS as administrator. Selecting a slot in a mission sometimes crashes the game as well. I have attached a new log in case there are additional problems that can be addressed. dcs.log

After additional testing, I've managed to partially solve this issue by deleting a third party antivirus, then re-adding both DCS Saved Games and install folders as exceptions. Regardless, using DLSS still freezes and occasionally crashes the game at the start of a mission. Additionally, stutters and freezing for 10-30 seconds still occur ingame, including the main menu. The freezing can be temporarily fixed by clicking anything every time the freeze occurs, but often freezes again immediately afterwards.

For the past 2-3 months, I have been unable to run semi-large missions within DCS that are generated by liberation, retribution, or DCC. All missions containing more than 100 units will stutter after a few minutes of gameplay, escalating into a crash within minutes of the stuttering. Current PC specs: CPU: Core i9-14900KF GPU: RTX 4080 Memory: 32 GB Before the forced integration of multithreading, I was able to run large (400+ units) liberation missions on my old PC with a 2080ti, 32 GB RAM, and a significantly degraded cpu, which leads me to believe that this is an issue with DCS. I have attempted slow repair, clearing fxo and metashaders, log analyzer's recommendations, removing all mods, turning off hardware accelerated GPU scheduling, turning off core isolation, and various adjustments to the game's graphical settings, and reinstalling the entire application from scratch. I attached one of the missions for testing if needed. dcs.log dcc_mission.miz

It seems like the Stennis is not accessible for me in multiplayer servers as well. I don't even have the option to occupy a slot. Requesting to land prompts the response "You are not authorized to land," which is the standard response for SC to non-SC players.

As the title says, I am unable to takeoff, land, or even ramp start both the F/A-18 or F-14 modules on the carrier. This applies to both the self-made missions and premade missions that came with the modules. I've already removed all my mods and run a repair and cleanup of DCS. Selecting the options "takeoff from ramp", "takeoff from runway", and "takeoff from parking hot" all result in an air start. Additionally, the way the aircraft hooks pass directly through the wires lead me to believe that this issue stems from Supercarrier somehow. dcs.log

When spawning in the back end of the Stennis, the F14 sometimes bounces vertically into the air, causing the landing gear to collapse. Its probably just a multiplayer issue, but it might be worth looking into.

I can't even see my own carrier group on max gain lol

Although its probably due to user error, I am completely unable to see ships using the AG radar. Is there something specific I’m supposed to mess around with in order for it to work?

I can no longer take off from carriers when spawning on one. This problem didn't exist on 2.5.5

AAR is near impossible in the Refuel Fight Recover mission due to several issues. In the Refuel Fight Recover mission, the tanker will accelerate, decelerate, dive, climb, and sometimes oscillate wildly without warning, sometimes clipping my nose in the process. The probe also falls out of the basket randomly when I'm flying straight and level by the tanker. This pertains more to the AAR practice mission, but I've noticed that trying to refuel with a KC-135 sometimes causes the plane to sometimes pitch up wildly without input. I know that Heatblur has done a great job simulating wake turbulence, but the oscillations I see seem to be more of a bug. It could have something to do with the probe being around a KC-135. Lastly, I'm not new to AAR, so the fact that all of these problems are occurring only with the F-14 is kind of strange, however, it could just be that my equipment is straight up garbage.

Is the A-10 supposed to be really easy to bring down? Because after 10 experiments with AA vehicles, tanks, and BMPs, it seems like even a single 30 mm shell rips off a wing or tail every time.

Autopilot is not available when spawning on the non-supercarrier Kuznetsov

After several weeks of this bullcrap, ED still shows no intention of fixing any problems related to FC3. All missions, as well as multiplayer, are impossible to play with the Su33. I'm starting to want a refund.

The Su25's top and left mirrors freeze when you look at them. EDIT: This problem is also on the Su25T, and I just realized that there is another thread of the same issue. Sorry for my ignorance.

ED doesn't have much of a choice other than to make Russian equipment obsolete. Most sources on semi-modern Russian equipment are heavily censored, making it near impossible to simulate missiles and planes at their true capabilities. It is not speculation. Its real and nobody but Russia can do anything about it.

ED likes making money, not fixing bugs. Russian FC3 aircraft are heavily neglected, so the chances of it ever being fixed are somewhat low.

Please continue. There is a lot to be said.

Following the recent update, it is now impossible to start the Su33 on a carrier unless you turn off electrical power. This makes any missions very annoying to complete. Although some have stated that this has already been reported, absolutely nothing has been done about it. Apparently, ED only has Open Beta available for fun, and doesn't actually use it to identify and fix bugs.

You are completely wrong. There are sometimes mistakes in the mission editor that makes the tanker frequency different from the frequency stated in a briefing or on a custom kneeboard. Please use that empty head of yours before you criticize people in that manner.

Thanks dude. I got it to work, but seeing targets other than aircraft parked in airfields are near impossible.