Search the Community

So I'm bin having some trouble with the radios for the last months : They stop working after a couple of minutes. Yes, I'm using easy communications. At the strat of a (self made) mission, yyou can contact ATC, tankers or AWACS, no problem what so ever. Yet after a X amount of minutes, the radios, or communications stop working : you still hear yourself call ATC, tankers or a AWACS but there is no response. Is anyone here familiar with this problem, and maybe know a sollution ? (For your information, I'm using a lot of mods in DCS)

As per title, the Hud has become unreadable: Using the rheostat to decrease brightness make things even worse: Suggestions? Best regards. dcs.log

I'm running into a weird intermittent issue with the MiG-15bis. Some days I can click the radio and ARK-5 controls just fine and others neither will respond to any mouse or keybound inputs. The mouse changes when hovering over the knobs, dials, and switches but clicking right or left mouse or scrolling does nothing and I cannot for the life of me figure out what's going on. Is there something somewhere in the aircraft I'm missing half the time or is this a bug?

Hello, I've been having this issue since the 2.9.7 update even though no one else seems to be noticing it, or maybe it's just my pc for some reason. Anyway, enemy AI reacts to Fox 2 missiles in BVR fights unrealistically, dumping flares as soon as the missile is launched (again, beyond visual range), even though they could not be possibly aware of the launch. For those who have been here for some time this is nothing new, it's a recurrent issue that some DCS builds have. This bug basically renders the R-27ET useless in a PvE environment. Is anyone else experiencing this problem? If it's a widespread problem it'd be nice to have it resolved swiftly (as ED did multiple times) as it's a pretty bothersome nuisance. I could provide a .trk but I'm pretty sure you are all familiar with the problem. Thank you and keep up the good work!

I get taken out by a soldier in 1 hit sometimes https://www.facebook.com/photo/?fbid=1001492965496903&set=a.385080860471453&__cft__[0]=AZXswtIjPiS_2I_ddkVtFb5TgSwWpfHUQpNPntY7NwE4AZP2O9wMwPJASFKC6MRHF-SMKDAhUIUvDg33W1NdV_EwiDilBvopTTJOvZUmLeOMQkE1mpPwzoXL4TI3zxDSkLZRBPuokxCilIof6WgeKXgMJQ35r493OihcMyBh2Qo9vIDmkpDijvAg_VxeLntpsXFqdvwGW_pZFB5HSucUCiwNIyIaw032-w3cYC5XPfkr-PPY2ITiBMJdtGNZnliKT6c&__tn__=EH-R

There is a big performance hit when TADS is underlayed on the pilots MPDs, for example on weapons. I usually get 15-20 FPS, which is not great, but flyable. With the video I get around 12 FPS average, at times dropping to 2-3FPS randomly, for a few minutes even, then going back up to 10. Measured with the FPS indicator (right ctrl+scroll lock, or something like that), but feels more like 1 frame every 2 seconds while flying through the mountains northeast of sochi. When turning the video back off it's fine again. Windows 10 AMD Ryzen 5 1600 Radeon R9 380 32 GB, 4x8GB, dual channel, 3200MHz DCS running off M.2 SSD, saved games on normal HDD

The time it takes for su-27 pilot to release from the eject seat is very random compared to F18 and other jets. In F18 the pilot releases from the seat in about 2 seconds and this time is very stable (+- tenth of seconds depending on the initial seat orientation in space) On the other hand su-27 pilot can release from the seat in a couple of seconds, in about 10 seconds, or occasionally fly down in the seat for minutes and only then release. It created difficulties in proper handling of eject events in certain scenarios. Probably its fair for other red planes eject seats too. I hadn't the possiblity to test. Please check.

Hi, I noticed a few updates back, the big wing tankers have got really twitchy in the turns - rocking side to side and not flying smoothly at all..... They also seem to randomly decide to retract the basket during hook up attempts..... I wondered if this was planned to be addressed?

I'm pretty sure ED is already aware that very few vehicles will allow AI infantry to embark, but as it really limits mission design is this being prioritized?

When adding sortie name, situation or tasks etc to briefing, only the added images stay when the mission is saved. All the typed text just disappears

f4 phantom shrikes all way fall short lofted or direct, i have watched many videos on how to do it, shooting under 10mines following the lights for lofting, with tracking and yes the right head on. (SA6 hunting ), but they all ways land very very short like a run way plus short. It has gotten way past 30 shots and no hits, so i think it is now a bug in the game

When saving a mission objects that were not there before would appear; when reloading a save there was a stinger in a place where it never originally appears; this was also the instant action medium

CCRP doesn't work on the instant action medium difficulty, not sure when it does work; when using shkvl and laser with ccrp, when the bombs are supposed to drop there is a tone, but nothing ever drops; reverting to the old update fixed it

in the mission F-14A_IA_Caucasus_Quals_supercarrier.miz, when you salute to get taxi'd to the cat, your wingman immediately starts taxiing, and rams into you. only tried it in the caucusus mission, but I suspect its happening on all of them including the F14B and persian gulf map.

Hello, As written in the title I am experiencing huge freezes and stutter for a period between 10 and 30s, when the radar starts to operate (F16 is the worst, F4E is bad for 10s, F14 is in between the 2 others). I am a DCS veteran (2009) and very good at optimizing the game (and you know how difficult it is to optimize this game... ). But since roughly a year or so, I am struggling with some modules having a radar. it took me a while to figure out that my issue was only related to the radar as I was not playing with many modules. After a looooong period of testing everything (all the optimization tips found everywhere: w10 defender, fxo, metashaders, core affinity, pagefile, preload radius, lod, etc etc etc...), I found that the freezes/stutters where occuring when the radar starts to operate (wheels up after take off). I make sure my game is evenly spread on all cores (affinity set) and the game is capped at 60fps (for TIR5 smoothness) whilst it has the potential to run between 80 and 110. When I can, I maintain the radar switched off until I am high enough in height to give a little bit of room for CPU/GPU. But this is not a proper fix. Did anyone found a trick to sort this out ? (for the F4, settings the radar CPU to low in special settings doesn't change anything unfortunately)

Issues with RB-15F tracking when not using waypoints, how come it either nose dives into the water or just flys past the targets? Desktop 2025.03.09 - 21.20.40.02 - Trim - Trim.mp4

My red air forces which were previously in the mission they disappear After I assign player mode to the f-18 I've done some testing and that is the situation that comes up in probably causes many of the other problems that people are reporting Because I've noticed for instance if I add red forces after I assign the f-18 to player A lot of illogical things start to occur

Attaching a screen shot that shows the situation. In it the viewer can see that my throttles are set above the Afterburner thresh hold hash mark and that the engines are at 100% RPMs but that both nozzle pos gauges are not in their after burner positions and in the pit there was no afterburner roar noise. The problem was simply solved in-flight by pulling the throttle back below the afterburner hash mark and pushing it forward. Not sure if this is a bug or intended behavior?

As topic. Even though the last update seems to have solved the stuttering problem, but F5E remastered still stutters in my game, especially in VR mode. I regret buying it. Now I just switch back to the original F5e to play the game. I wish it can be solved as soon as possible.

What happened: Flying in multiplayer server against AI F5 with Aim9P5 missiles. Took them straight into the Vertical flying directly into the Sun so they wouldn't be able to get a lock with their IR missles. They were directly in my 6 so not only should they have been visually blind (Another issue...), their missile seekers should have been saturated. They were able to launch a tracking IR missle against me which I wasn't able to defeat with flares either. Completely ruined immersion. I suspect its a whole AI / Missle issue rather than just an issue with the P5? Fix: AI unable to launch IR missles into the sun, (Bonus fix: Lose SA on your AC when flying into the Sun/Cloud/Behind terrrain..)

Hi ED, Creating this post whilst I try to create a reproduction case but as this has happened twice now in 2 days under similar circumstances it maybe faster for you to review the crash dump file to see the codepaths etc. It seems to be when missiles explodes near a unit whilst it's rearming and it's destroyed registering a self-kill (possibly a close by intercept) Both are crashing in the same method: 2024-06-08 00:18:47.337 INFO EDCORE (Main): # -------------- 20240608-001848 -------------- 2024-06-08 00:18:47.337 INFO EDCORE (Main): DCS/2.9.5.55918 (x86_64; Windows NT 10.0.20348) 2024-06-08 00:18:47.337 INFO EDCORE (Main): C:\dcs\server\bin\Weapons.dll 2024-06-08 00:18:47.337 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff8b41175c8 00:00000000 2024-06-08 00:18:47.337 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\dcs\server\bin;', symOptions: 532, UserName: 'sdcs' 2024-06-08 00:18:47.337 INFO EDCORE (Main): OS-Version: 10.0.20348 () 0x110-0x3 2024-06-08 00:18:47.337 INFO EDCORE (Main): 0x00000000001175c8 (Weapons): wStowage::stopRearm + 0x1738 2024-06-08 00:18:47.337 INFO EDCORE (Main): 0x000000000014898a (Weapons): woMissile::doExplode + 0x22A 2024-06-08 00:18:47.337 INFO EDCORE (Main): 0x000000000011824d (Weapons): wWeapon::getDescriptor + 0x99D 2024-06-08 00:18:47.337 INFO EDCORE (Main): 0x0000000000116807 (Weapons): wStowage::stopRearm + 0x977 2024-06-08 00:18:47.337 INFO EDCORE (Main): 0x000000000001c71e (edObjects): DamageInfo::GetDamager + 0x72E 2024-06-08 00:18:47.338 INFO EDCORE (Main): 0x00000000000189b4 (edterrain4): ITerrainImpl4::EventHandler::~EventHandler + 0x1CA4 2024-06-08 00:18:47.338 INFO EDCORE (Main): 0x00000000000177c0 (edterrain4): ITerrainImpl4::EventHandler::~EventHandler + 0xAB0 2024-06-08 00:18:47.338 INFO EDCORE (Main): 0x0000000000014efb (edterrain4): landscape4::lRoad::getStartParam + 0x407B 2024-06-08 00:18:47.338 INFO EDCORE (Main): 0x0000000000014f37 (edterrain4): landscape4::lRoad::getStartParam + 0x40B7 2024-06-08 00:18:47.338 WARNING LOG (8760): 10 duplicate message(s) skipped. 2024-06-08 00:18:47.338 INFO EDCORE (Main): 0x000000000001e505 (edterrain4): ITerrainImpl4::querySceneObjectsCB + 0x275 2024-06-08 00:18:47.338 INFO EDCORE (Main): 0x000000000001c55f (edObjects): DamageInfo::GetDamager + 0x56F 2024-06-08 00:18:47.338 INFO EDCORE (Main): 0x000000000000cad0 (edObjects): viObjectManager::GetSegmentList + 0x1300 2024-06-08 00:18:47.338 INFO EDCORE (Main): 0x0000000000116ff2 (Weapons): wStowage::stopRearm + 0x1162 2024-06-08 00:18:47.338 INFO EDCORE (Main): 0x000000000010f8ef (Weapons): Ammo::add_and_get_ref + 0x1C6F 2024-06-08 00:18:47.338 INFO EDCORE (Main): 0x000000000013fb57 (Weapons): woMissile::Control + 0xDA7 2024-06-08 00:18:47.338 INFO EDCORE (Main): 0x000000000014484a (Weapons): woMissile::InitExhaust + 0x29A 2024-06-08 00:18:47.338 INFO EDCORE (Main): 0x00000000000045ab (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x3EB 2024-06-08 00:18:47.338 INFO EDCORE (Main): 0x0000000000004bc2 (World): wSimCalendar::DoActionsUntil + 0x262 2024-06-08 00:18:47.338 INFO EDCORE (Main): 0x00000000008c8f99 (DCS_server): SW + 0x407E49 2024-06-08 00:18:47.338 INFO EDCORE (Main): 0x00000000008c8c71 (DCS_server): SW + 0x407B21 2024-06-08 00:18:47.339 INFO EDCORE (Main): 0x00000000008ebb71 (DCS_server): SW + 0x42AA21 2024-06-08 00:18:47.339 INFO EDCORE (Main): 0x00000000008a8874 (DCS_server): SW + 0x3E7724 2024-06-08 00:18:47.339 INFO EDCORE (Main): 0x00000000008a9fad (DCS_server): SW + 0x3E8E5D 2024-06-08 00:18:47.339 INFO EDCORE (Main): 0x00000000004a1c10 (DCS_server): (function-name not available) + 0x0 2024-06-08 00:18:47.339 INFO EDCORE (Main): 0x000000000280cd0f (DCS_server): AmdPowerXpressRequestHighPerformance + 0x13A1D0B 2024-06-08 00:18:47.339 INFO EDCORE (Main): 0x0000000000cf70ee (DCS_server): SW + 0x835F9E 2024-06-10 18:50:15.361 INFO EDCORE (Main): # -------------- 20240610-185016 -------------- 2024-06-10 18:50:15.361 INFO EDCORE (Main): DCS/2.9.5.55918 (x86_64; Windows NT 10.0.20348) 2024-06-10 18:50:15.361 INFO EDCORE (Main): C:\dcs\server\bin\Weapons.dll 2024-06-10 18:50:15.361 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff8c08e75c8 00:00000000 2024-06-10 18:50:15.362 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\dcs\server\bin;', symOptions: 532, UserName: 'sdcs' 2024-06-10 18:50:15.362 INFO EDCORE (Main): OS-Version: 10.0.20348 () 0x110-0x3 2024-06-10 18:50:15.362 INFO EDCORE (Main): 0x00000000001175c8 (Weapons): wStowage::stopRearm + 0x1738 2024-06-10 18:50:15.362 INFO EDCORE (Main): 0x000000000014898a (Weapons): woMissile::doExplode + 0x22A 2024-06-10 18:50:15.362 INFO EDCORE (Main): 0x0000000000119cb8 (Weapons): weaponInitRandomSeed + 0x1A48 2024-06-10 18:50:15.362 INFO EDCORE (Main): 0x000000000007ceb2 (edCore): Mail::Reader::stream + 0x1462 2024-06-10 18:50:15.362 INFO EDCORE (Main): 0x0000000000b4a9b3 (DCS_server): SW + 0x689863 2024-06-10 18:50:15.362 INFO EDCORE (Main): 0x0000000000b6e913 (DCS_server): SW + 0x6AD7C3 2024-06-10 18:50:15.362 INFO EDCORE (Main): 0x0000000000b64c5e (DCS_server): SW + 0x6A3B0E 2024-06-10 18:50:15.362 INFO EDCORE (Main): 0x00000000008eba20 (DCS_server): SW + 0x42A8D0 2024-06-10 18:50:15.362 INFO EDCORE (Main): 0x00000000008a8874 (DCS_server): SW + 0x3E7724 2024-06-10 18:50:15.362 INFO EDCORE (Main): 0x00000000008a9fad (DCS_server): SW + 0x3E8E5D 2024-06-10 18:50:15.362 INFO EDCORE (Main): 0x00000000004a1c10 (DCS_server): (function-name not available) + 0x0 2024-06-10 18:50:15.362 INFO EDCORE (Main): 0x000000000280cd0f (DCS_server): AmdPowerXpressRequestHighPerformance + 0x13A1D0B 2024-06-10 18:50:15.362 INFO EDCORE (Main): 0x0000000000cf70ee (DCS_server): SW + 0x835F9E 2024-06-10 18:50:15.362 INFO EDCORE (Main): 0x0000000000014de0 (KERNEL32): BaseThreadInitThunk + 0x10 And in both cases, the last event was a self-kill bda event 2024-06-08 00:18:47.307 INFO Scripting (Main): event:initiatorPilotName=Hawk tr,target_coalition=2,linked_event_id=0,targetMissionID=1001926,target_ws_type1=2,initiator_object_id=17197569,target=Hawk ln,target_object_id=17196545,targetPilotName=Hawk ln,type=bda,target_unit_type=Hawk ln,t=10942.348,initiator_unit_type=Hawk tr,event_id=3344,weapon=MIM-23K Hawk,initiator_ws_type1=2,initiatorMissionID=1001930,initiator_coalition=2, 2024-06-10 18:50:15.334 INFO Scripting (Main): event:initiatorPilotName=Tor 9A331,target_coalition=2,linked_event_id=0,targetMissionID=1002815,target_ws_type1=2,initiator_object_id=17409537,target=Tor 9A331,target_object_id=17409537,targetPilotName=Tor 9A331,type=bda,target_unit_type=Tor 9A331,t=25576.864,initiator_unit_type=Tor 9A331,event_id=9485,weapon=9M330 Tor (SA-15 Gauntlet),initiator_ws_type1=2,initiatorMissionID=1002815,initiator_coalition=2, dcs.log-20240608-001848.zip dcs.log-20240610-185016.zip

Civilian airplanes cannot be placed with waypoint 'Takeoff from ramp'. The error pop-up mesage reads "error set to airfield. No free airport." I tried this with A330, A320, while KC-135 and E-3A work perfectly. Additionally, AI traffic does not land on Bodo. Instead they divert to Andoya. This was tested with F-18, F-15 and F-16.

It seems that naval units does not respect "late activation".

Multiple cockpit components have 100% gloss material applied. This kind of material property has no place in a realistic cockpit, even on cockpit gauge glass, let alone on non-glass parts of the cockpit. Even Soviet oil paint doesn't give gloss anywhere near 100%. Examples: control stick emergency cockpit glass hammer cockpit indicator frames probably even the radar control palm rest adding additional items to the list: generic metalic chromium air spherical nozzles even the grey knobs have a metalic gloss to them the right hand adjustable flash light with coiled cable The use of such material properties additionally lead to graphical artifacts on object edges manifesting in white-ish lines that require heavy anti-aliasing. But the unrealistic look is a more serious issue here. Independent of hardware configuration, or in-dcs settings. EDIT 2025-02-20: Multiple examples uploaded, added ugly metalic components to the list as I see no point in starting a separate thread. https://1drv.ms/f/c/66cf2646234394fc/EtaGgsCLk8BNsDRTeFpxXlYBp4UqyIerOMj-QTnctB2Yfw?e=Luya4g An additional remark: To be confirmed (best at the radar controls and the control stick) - the affected surfaces reflect light without obeying occlusion as seen by unnatural pronounced gloss even in the shadows.

I just downloaded and installed the new CH-47F. I could do a startup but I ran into some issues. 1: I put the Eaps to on but the EAPS fail stayed on for both on the WCA. No matter what I tried! 2: After the startup was complete I wanted to take off. Being in the air I got a very unstable A/C and it looked like uncontrolled input. Since the AFCS was on both it should be stable in the air. 3: After playing for a while the screen suddenly went to black. When I turned the cam a bit it came back. That wasn't workable. Also when I pressed F2 and turned around the screen switched from entire black to visible and back to black. Had to shutdown the game with CTRL+ALT+DELETE. It became unresponsive