Dauntless 7

When flying the F-4U in MP, the aircraft is impossible to get above 200 knot indicated. A check of the external view of other player F4U's shows the landing gear extended on all of them. This is despite the gear appearing up on the players own F2 view as well as according to cockpit instruments. Suspect that the sim is seeing player landing gear as down and thus limiting maximum speed.

Any damaged AI warbird, when considered "killed", will go into a left or right level turn at roughly 400 knots and will stay that way indefinitely, even when their engines are no longer operational.

Seems all missions have both fuel and ammo set to unlimited. This seems really unnecessary given the parameters to achieve success in each task/instance and that tasks are all immediately repeatable via the F10 menu. Personally, would prefer not to have unlimited fuel and ammo since all that weight degrades aircraft performance. Trying to dogfight even an F-5E is pretty nuts with two AIM-54's always on the belly.

Per your suggestions: 1)Game Mode and HAGS were already off. 2)Removed mods, ran repair. Had ran several repairs in the past two weeks, but not with mods removed. Put mods back on after repair. 3)Disabled Core Parking in Registry. 4) Turned off Core Isolation. Ran DCS and utilized ALT+TAB to go back a forth from DCS to Discord and an open Edge window reference multiple time and have not yet encountered the problem again so far. In fact DCS is running smoother now on this Win 11 PC I have only had for a couple of months than it has so far. I suspect Core Parking was the primary culprit. Thanks for the assist.

Have begun to have severe graphic stutter, freezing and even CTD's whenever using ALT+TAB in Win 11 v 24H2 to tab move from DCS to another window, such as Discord, and open Edge reference page, even task manager window and back to DCS. The stuttering, freezing, etc. begins anywhere from a few seconds to up to 30 seconds after ALT+TAB back to DCS. Operating DCS is very smooth by itself, or even with a window open behind it, unless you ALT+TAB out of DCS and back in. I use DCS in Full screen mode. Have tried with mouse confined to monitor and not. I use only one monitor. Since it only began in last two to three weeks I suspected a Win update, NVIDIA update, or DCS update that occurred during that timeframe. First noticed the problem on or about 15-16 March 2025. Here are my system specs: Processor Intel® Core™ i9-14900K Processor (8X 3.20GHz + 16X 2.40GHz/36MB L3 Cache) Memory 96 GB [48 GB X2] DDR5-6000MHz Memory Module - Kingston Fury Renegade Video Card NVIDIA GeForce RTX 4070 Ti SUPER - 16GB GDDR6X (DLSS 3.5 – AI-Powered Performance) MSI VENTUS 3X Black OC Motherboard MSI MAG Z790 Tomahawk MAX WiFi - WiFi 7, ARGB Header (3), USB 3.2 Ports (2 Type-C, 8 Type-A), M.2 Slot (4) Power Supply 1000 Watt - CORSAIR RM1000x - Cybenetics Gold ATX 3.1, Fully Modular Primary Storage 4TB Kingston Fury Renegade M.2 PCIe Gen 4 NVMe SSD -- Gen 4 Read: 7300 MB/s, Write: 7000 MB/s Sound Card Creative Labs Sound Blaster Audigy FX [PCIE] -- 5.1 Channels, 192KHz/24-bit Operating System Windows 11 Pro w/ Windows Recovery USB - (64-bit) Log Attached dcs.log

I have identified a location on the Afghanistan map where a small town is drawn, but should be empty desert. The location is where an allied coalition Forward Operating Base was located during the Global War on Terror. I know this from real world experience. I assume the town was drawn there based on the remnants of the FOB that are visible on satellite imagery after 2012. The remnants are still visible on the most recent Google Earth imagery. This village is located at N31 38'40" E64 57'17" on the Afghanistan Map west of Kandahar Airfield on bearing 279 at 46 NM. If the village was erased from the Afghanistan Map and replaced with the local desert terrain texture, it would be possible for someone like me to recreate the FOB that was there. I have attached an image of what it looks like.

Would like to see a 2 meter tall T-Wall addition. Were used on a lot of FOB's in Afghanistan. The 3 Meter ones are two tall for an accurate reconstruction. We also need Container Housing Units usually referred to as "CHU's" by those that lived in them.

Shooting A20 bombers with and AIM-7 or AIM-9 will not kill an A20 bomber. Only tried this from F-14A Tomcat But if an AIM-7 or AIM-9 will kill fighter jet such as the F-14 or F-15 that is just as big as the A20 it should kill the A20!

Install instructions for: DEVRiM DCS MiG-29 Complete English Cockpit Mod v1.3c DCS Open Beta version 2.8.8.43704 (NOT STEAM VERSION!!!) Stand-alone FC3 MiG-29A/G/S only. (NOT THE FLAMMING CLIFFS ALL IN ONE PACKAGE!!!) Procedure works as of 19 September 2023 I only recently found and downloaded this mod for the MiG-29. I was having the same problems with getting it to work in the non-STEAM, Open Beta version of DCS with the stand-alone version of the FC3 MiG-29 that many were. After reading through all the comments and things people said worked for them, but did not work for me, I finally settled on one of the last fixes posted, which exchanged the word “English” for “default” in the files, but was vague and non-specific, and thus resulted in my changing things that did not need changing. Here is the step-by-step procedure for making it work if you have the same DCS and MiG-29 mod version that I do, as listed above. All of these changes are done in your “(X): / Users / (your name) / Saved Games / DCS folder”. Nothing needs to be done in main game program files folders. STEP 1: Download the DEVRiM DCS MiG-29 Complete English Cockpit Mod v1.3c Zip file and save it somewhere easy to access. (I used the desktop). Extract the contents to the same location using whatever Zip file program you like. (I used 7 Zip). STEP 2: Open your “(X): / Users / (your name) / Saved Games / DCS folder”. Look to see if you already have a “Liveries” folder at that exact location. (NOT inside another folder in that location.) If you do not simply create one there and name it “Liveries” (Capital L with no quotation marks). If you do have one, leave it there but make sure it is named the same way. STEP 3: From the DEVRiM DCS MiG-29 English Cockpit Mod v1.3c folder you just extracted, find the folders named: Cockpit_MiG-29A Cockpit_MiG-29G Cockpit_MiG-29S Inside each of those folders is a folder named “English”. Rename that folder, in each of the above listed folders, to be “default” (lower case d with no quotation marks. STEP 4: This part requires editing several lines of text in the “description.lua” found in the folders you just renamed to “default” in the Cockpit_MiG-29A and Cockpit_MiG-29G folders only!!! (NOT the Cockpit_MiG-29S folder). Take your time, pay attention to detail, and double check everything you did in each before saving and moving to the next one. Inside the “Cockpit_MiG-29A” folder you just created, Open the “default” folder you just renamed. Open the “description.lua” file using Windows Notepad. In the document you see there are several lines of text. Everywhere except the top line, where you see the word “English”, change the word to “default” (lower case d with no quotation marks.) When done, double check every line to ensure spelling and spacing are the same. Save the document and close it. REPEAT this EXACT same process for the “description.lua’ file, in the “default” folder, in the “Cockpit_MiG-29G” folder that you made. DO NOT edit the “description.lua” file in the “Cockpit_MiG-29S” folder!!! STEP 5: Run DCS in Non-Multi-thread mode first. Open the SETTINGS menu. Open the GAMEPLAY menu. Set the Avionics to “English”. Set the Units to “Imperial”. (The units may not matter but I use Imperial units always so I figure it is worth mentioning.) Open the SPECIAL menu and open the MiG-29 menu. The Customized Cockpit MiG-29A, G and S menus should all show “default”. Next, Jump in a mission in each version of the MiG-29 and verify that you see proper cockpit textures and that the labels and lights and HUD all have English text. If you see strange colored textures (in my case they were green) go back into the “description.lua” files you edited and make sure you did not miss a line or make a typo error. Next, try it out in Multi-thread if you like using multi-thread mode for DCS. It should work. And that should do it!!! This is the procedure that worked for me. Hope it works for you!

Perhaps there is already a method for doing this in DCs that I have yet to discover. If so forgive my ignorance of it. However in building missions I have found that it would be a great help, if there was an option to make an AI aircraft, for which there is a player module, able to be occupied by a player / client. For example, if a mission maker puts in a mission a flight of 4 x F-16's, there would be an option box that could be checked on or off, that would allow player/clients to occupy the aircraft slot and fly the flights assigned mission, instead of it being an AI flight. However if no player occupied the slot, then the AI would fly the mission as designed. I have seen this feature used in other high quality simulations and it gives the mission maker much more flexibility in designing missions that can be flown by one player or several players. And it can be used to allow a player/client to fly the same mission from many different roles and in different aircraft, without creating a different version of the mission. But it also allows the mission maker to exclude AI aircraft that the mission maker wants to be strictly AI flown from being occupied by a player/client.

Having same issue. Occurs after landing back at carrier, doing a hot refuel and rearm and launching again. Once airborne an attempt to change radio frequency on AN/ARC-182 (V/UHF 2) radio using jester menu causes DCS to stop responding as soon as I open the jester frequency selection page. But as already stated it only occurs after landing and rearming and launching again. I habitually put jester in "no talking" mode during a carrier trap approach, so he won't babble the entire time I am trying to hear carrier ATC instructions. Then put him back in talk mode after rearming. I Wonder if it has something to with that?

I have encountered the same problem in the F-14 and the P-51. Only occurs when padlocking an aircraft that is roughly between 5 and 7 oclock, maybe even 4 to 8 oclock position. And sometimes when an aircraft that is padlocked in the forward field of view passes to the extreme rear the view padlock view get stuck looking to the rear. Only way I have found to fix it is to unpadlock, which still sticks the view over the shoulder, but then I can use the POV hat to force the view toward the front, quickly hit padlock again which padlocks the view on a point in front of the jet, then unpadlock again, which returns the view to front centered. A really troublesome bug when you are in a hard turning fight or dodging missiles. Pretty sure its a DCS side issue and not an aircraft specific issue since it happens when flying various aircraft.

Thanks for the tips. Spent a couple hours practicing last night and I I am finding the groove again within the changes. I still struggle to get exactly on and stay on AoA and "On speed" but I am able to stay close enough that I am sticking the landing probably 80+ % of the time (When I remember to drop the hook. Forgot to a half dozen times last night). Mostly one and four wires but getting the two or 3 about 50% of the time I guess. Can definitely feel the difference from before the update. Just takes a good bit of getting used to I suppose. Thanks for the tips. Spent a couple hours practicing last night and I I am finding the groove again within the changes. I still struggle to get exactly on and stay on AoA and "On speed" but I am able to stay close enough that I am sticking the landing probably 80+ % of the time (When I remember to drop the hook. Forgot to a half dozen times last night). Mostly one and four wires but getting the two or 3 about 50% of the time I guess. Can definitely feel the difference from before the update. Just takes a good bit of getting used to I suppose. Thanks for the tips. Spent a couple hours practicing last night and I I am finding the groove again within the changes. I still struggle to get exactly on and stay on AoA and "On speed" but I am able to stay close enough that I am sticking the landing probably 80+ % of the time (When I remember to drop the hook. Forgot to a half dozen times last night). Mostly one and four wires but getting the two or 3 about 50% of the time I guess. Can definitely feel the difference from before the update. Just takes a good bit of getting used to I suppose.

"On speed" should mean "on AoA". But what I am finding is that to get to On AoA the jet has to be right at a stall at 120knots indicated, then I hit the wake turbulence that is now way more than it was before, and the jet falls like a rock, requiring full power to avoid hitting the back of the ship, which mean going around. At any speed above 120-130 knot I no longer am able to get the jet at the correct AoA. Even coming in at 140-150 indicated the jet falls almost too fast to save it when hitting the wake turbulence. But at that speed I cannot get the AoA indexer orange ball or the E down with the wings on the HUD. Forgot to mention all of this has been within the Instant Action CASE 1 landing missions. Maybe it is an issue with the mission parameters, like wind or carrier speed or both. But would not think so, since they all have wind of 10-20 knots and ship speed of 10-20 knots. Going to keep trying though. Eventually I will find the groove or break something trying.

Not sure if it was this Heat Blur Tomcat patch or the update to DCs version 2.7.whatever or installing the Super Carrier module, because I did them all within a few days of each other. But I am finding it VERY difficult to achieve On Speed AoA during landing now. Was challenging before but now it feels next to impossible without stalling the aircraft. Not sure if it was one of these updates / installs or if it is just me. Anyone else having the same trouble?

WORTH EVERY PENNY!!! Buy it and love it.