HR-Crumble

Hi all, As per the title since the most recent update March '25 the AI set to the following makes them launch at you : Reaction to threat = evade fire ROE = Weapon hold Scenario 1: 2x Red Hind set as above to cruise through the blue area but not engage. When they see a blue player move towards them they start firing at blue. Scenario 2: 2x Su-24 set on border patrol with aim of 2x player F/A-18s to come up along side them an intercept. No locking of any systems, just pull up alongside in a classic intercept and follow. As soon as the Red Air visually sees the blue they break and start shooting. Reaction to threat = evade fire ROE = Weapon hold used to never elicit a response. Have been using this setting for years in mission making and they have only just started shooting back?

Hi all - is there a valid D/L link? The one provided just takes you to some broken pages and the file isnt there. Tried to find the discord link in case the D/L link is in there - Discord link is invalid as well. Can anyone kindly shed some light? Many thanks.

Is this based on the Super Hornet displays and avionics etc?

Hi all, Not sure what is going on here as I have never had this issue before. Syria map using Ramat David on bluefor I select the aircraft I want to be available on MP as dynamic spawn but they don't all show up? Anyone who joins our server can only see SOME of the aircraft I have selected as INFINITY amount. As it happens it looks like its only module that ME AS THE ME has installed that actually show in the game. This is also the case when I click Hide Not Flyable? So how do I get F-15E S4+ for example to be a dynamic spawn in the MP game even though its selected as INFINITY amount in the miz file? In the image below you can see all the jets I have ticked - but in the server for the whole group the guys can only see what modules I have installed???

JCAG (Joint Combined Aviation Group) is a helicopter unit operating three aviation companies with OH-58D, AH-64D, and CH-47F aircraft. We have recently opened our public discord to offer both helicopter and fixed-wing modules. We are actively recruiting for our public missions, which are free and open to everyone every Thursday at 1930 UK time. These missions follow a mini-campaign format, with 3-5 connected missions per campaign. We fly for two consecutive Thursdays, take one off, and provide an open PvE server for practice in between. While we are always looking for dedicated helicopter pilots for our main group, you don’t have to be one to participate in public missions. We offer a variety of fixed-wing roles every week. Public Modules in rotation: OH-58/AH-64D/CH-47F/Mi-8/Mi-24/KA-50/A-10C/F-16C/F/A-18C/F-4E/F15C/Mirage F1/Viggen/F-14/Mig-29/SU-27/SU-25 (more added and rotated all the time) If you’re looking for a laid-back, ‘milsim-casual’ group with a friendly atmosphere and engaging missions, feel free to send me a DM to join in. For those who prefer more structured missions and are experienced helo pilots, we also welcome you to transition to the JCAG side, where you’ll experience full milsim operations with real-world procedures and tactics. Cheers - Crumble

Hi all, It’s 2025 and I’ve just got the Hind. Like everyone else it seems my initial experience of the AP yaw SUCKS. Damn aircraft keeps auto trimming itself and the heading hold won’t let me pedal turn. So I did some research and came across this awesome thread and have fixed my issue by taking the following advice written in here: - Trim types is centre after release - Yaw pedal auto move - OFF - Auto Microswitch OFF as Y (bound to a rocker switch so AP head is always OFF and damp is now always ON) Almost 99% better for me. Now my question is the Pedal trim - most of you use the above settings also and most of you have No pedal trim - why? How do you straighten out the Hind when it flies with some crab? In all other helo modules I use pedal trim with force trim so I can pedal adjust the helo so it’s flying straight then save that trim with Force trim. Are you guys not trimming your Hind to fly straight?? Or do you fly with a constant bit of pedal in (seems like hard work and unnecessary when you can just trim and lock it in and take your feet off?) Am I missing something?

How would one get a ‘Truck and pan movement’? I’m trying to achieve a move where I can almost ‘move around a point’ on an aircraft but rotate around it. Im trying to truck left or right and then pan as the camera is locked on a certain point or area like a missile tip for example. At the moment I am RCTRL+F2 and then CTRL + *or / to scale in/out. Then I truck slow with CTRL+W or D and then turn my head using TiR or the mouse but they create a jerky pan. Am I missing a better way?

Hi all, Im trying to work out how to do the following camera movement: - Sliding left or right whilst also tracking a fixed spot so it looks like you are turning around a point subtly. - I can do it by using RCTRL+F2 and then using my mouse or TiR to follow a certain point but its a jerky movement so I'm looking for a key combo or clever way to do it smoother. Thanks all.

@Flappie just wanted to give you a little testing update that I have done for the black screen flicker. I have managed to find some new evidence and I believe the culprit to be anything smoke/or particle physics related. NB * I saw the same vertical ‘saturns rings’ and black half screen flicker on the new patch on 4YA last night so the patch hasn’t stopped the flicker or artifacting. Here is my testing: 1. Modules tested on and verified same issue occurs - Apache, Kiowa, Phantom, A-10Cii, Hornet, Viper, Fulcrum A+S, SU-25A, Chinook, P-47, P-51, Combined Arms. 2. Maps tested and verified same issue occurs - all terrains tested except for Kola and NTTR. Worse on Syria and Iraq. 3. I have worked out how to replicate the issue - originally I thought it was just the new fog, but now it occurs in testing with dust cloud set at any range and thick cloud settings. I have ALSO now worked out via testing that it happens when using smoky engines and you look at an aircraft which had smoky engines especially from front on or rear on - namely I can force the issue when looking the F4, Mig-29 and seen it on the SU-25. If I put any one of those elements listed above in a miz either on their own or together then I can reproduce the black screen issue. If I turn off fog/dust/heavy cloud and choose a less smoky engine then I cannot reproduce the issue. My parameters: 5600x/7800xt 16Gb/64Gb/SSD/Win 11. I have verified the issue also happened on Windows 10 and then under a fresh install of DCS and Windows 11. Items I have eliminated as a baseline: - no over clocking. - operating temps within manufacturers and board parameters. - Ample PSU wattage. - Tried a different monitor at 1080 instead of usual monitor at 1440p. - GPU and mobo drivers up to date including bios. - Nuked meta and shader folders. - No mods installed. - No image enhancement overlays. - checked Windows power settings/eco settings. - Only happens under DCS. - MP and SP. - Have tried all DCS graphics settings and effects set to off and low where possible. - 2D with TiR - I do not use VR. Finally I always ask others in my group if they see the same issue as that’s always a decent indicator as it’s platform agnostic - answer, yes they do I hope that helps - please feel free to DM if you need more details etc. Crumble.

Will do - I cleared out my trks last night as the folder was over 10gig and our mission last night no one had any flickering. Everything was the same as normal except fog was turned off. don’t know if that’s a clue for you and the dev team? Fog may be causing it. I know it causes a lot image issues for VR players also. I’ll try fog on again and then post a track.

Yes I’ve just seen the Saturn ring one reported and have read all 6 pages but no one mentioned the black flickering?

I am seeing this issue also but I’m also getting flickering black on the screen when taxing. Has anyone else reported flickering black as well as the Saturn rings?

Hi all, I have noticed that since I believe the above update I am seeing black flickering on half the screen of my monitor and also insane artefacts in game. Eventually they go. Black flickering is half the whole display. Attached is a photo of the artefacting taken today. I have had it verified that others in my group have seen the same artefacts recently as well. I have tested the following: - it happens in all modules - it happens on all maps - I’m using track ir - I have nuked and redone my drivers (AMD 7800XT) - have nuked DXO/Meta and tried reshade on/off - happens on both MSAA and FSR - have changed resolutions - black flickering mainly happens on the ground when taxiing and artefacting mainly in the air - issue persists after todays (5/2/25) mini update - have ensured W11 is up to date and has no GPU power management settings affecting it. - it happens with and without reshade. - it does not happen in other games. - have tried other monitors and cables just in case.

So you recommend MFAA in AMD software and MSAA X4 in DCS? Any sharpening? In DCS or AMD Software?

I could have mandella’d myself here but I swear there was an official ED video using Reuben and the Dark ‘What a wonderful world’ cover as the soundtrack?? I cannot for the life of me find it. Am I crazy?

Is there an export script to get the airspeed on a stream deck for the F4?

I fully concur with you on the MSAA shimmering. It’s so bad I had to move to TAA + FSR with scaling of 0.9 (doesn’t make any frame difference regardless of setting for me) and sharpening at 1.0. Those are the only settings on a 7800XT I can ever get remotely looking good and sharp. But it suffers with horrendous ghosting. Sent from my iPhone using Tapatalk

Thanks for your reply - interesting you haven’t had issues. I’m finding its worse on Syria map and the most lagging comes from using the multi select tool and copy and pasting. Even just a few units causes lag. If I restart DCS then the lag goes and then builds up again over time. There is nothing standing out in my logs.

I have noticed that on all maps and regardless of size of miz file that gets created, complexity or mods or not that over time (a few hours) the mission editor gets very laggy. Laggy to scroll, laggy to zoom, saving is laggy and copy 'n' pasta literally makes the blue wheel spin. Have confirmed with some squads mates this is the same across different systems. Anyone else?

I haven’t had a deep dive and retweak of my AMD graphics settings since the past few updates. About 6 months ago I made a jump from a 3070Ti to a 7800XT. Whilst the extra VRAM and sheer grunt was much appreciated I felt the DLAA on the nvidia gives a better image than the FSR AMD card. Has much changed in the recent updates or has anyone got any combo of AMD settings in game that can match DLAA better? For ref I have the following: 1440p monitor 7800xt 64Gb system ram Not touched the AMD driver app or settings. Everything on ultra in DCS and FSR set to 0.9 sharpening. Sent from my iPhone using Tapatalk

Sand storm only shows on Syria for me at 23000ft and above viz set on the slider. Anything set below that and no dust is shown. I also get random miz files where despite setting orret altitude of fog you do not get the fog. It feels like dust and fog is somewhat inconsistent or broken.

Hi all, Have noticed since the most recent update inconsistent or not working at all - no dust storm effects are working. Have tried 3 different desert maps - with cloud and without loud. Set dust to 984ft viz and 23000ft viz and the max 65000ft viz. No dust storm effects no show in game. No mods, no scripts. Fresh miz. No other weather. Anyone else?

Have come across this issue. Just building a standard AI SEAD mission - done the same way that has always worked for years. Issue is when the AI are set to take off from the boat they will not proceed to their next waypoint and then fly their route and launch harms. But if you set them to fly over point just over the boat they will carry on and execute the route and strike. Have tried different maps, new jets, new locations, new targets, new fuel states etc. trk attached. LastMissionTrack.trk

Damn that’s a shame. Sent from my iPhone using Tapatalk

Bump - did the last update resolve this? Sent from my iPhone using Tapatalk