Search the Community

As the title says - set up a trigger on a static mig21 (also tried other aircraft) and added an "play argument" call. Running it alongside a smoke in a zone to make sure the trigger is working and the smoke pops but no change on the actual aircraft. I tested it with various aircrafts and selections nothing ever worked. I attached my mission file BrokenPlayArgument.miz

Orbit task through waypoint action does resume route when over, but orbit task through triggered action does not. .miz attached (2 AI F18, number 1 orbits 1mn at wpt 1 - wpt action - then resumes to wpt 2, number 2 orbits 1mn at wpt 1 - triggered action - then RTB instead of resuming to wpt 2) Test-orbit-resume-pushtask-vs-wptaction.miz

When you move your head around whilst using the PNVS there is a noticeable stutter in the image, compared to when using the TADS and the image is silky smooth throughout. The PNVS feed is smooth when you aren't moving your head so this looks more like the actual PNVS itself is stuttering as it moves through its motion. To Reproduce: 1. Use the PNVS 2. Move your head

OB 2.7.9.17830 SP Persian Gulf F-5E-3 with AI wingman Take-off from Shiraz #-key works on ground to trigger the comms menu, menu is working NWS button on joystick in flight does not trigger the comms menu (despite seeing the button pressed on the cockpit-stick). F-5E-3_with_AI_wingman_NWS_not_triggering_COMMS_menu_in_flight.trk

I was doing some CCRP bombing practice with BDU-33s and for some reason the drop cue will randomly stop functioning after a drop or two. I noticed that it seems to be consistent after a cold and dark startup and you start attacking a TGP markpoint. In my mission trk I did a few runs on a stored steerpoint, designated a markpoint with the TGP and suddenly it just stopped working. Seems to be following the TGP. Had a similar issue with CCRP and CCIP a month ago where high drag munitions at low altitude were inaccurate but didnt save a trk. Mission Setup: No Mods (Originally thought it was the issue) F-16 with BDU-33s Cold and Dark Start Client Spawn Specs: AMD R9 3900X RTX 2080ti 32GB RAM SSD for DCS 1440p for Display (windowed) Track IR I couldn't attach the trk here due to its size so I included a link to it. https://www.udrop.com/6DLH/F-16_CCRP_Drop_Cue_Behavior.trk

The 2.7 brought correct scan centering and Spotlight modes to TWS and the Spotlight in RWS is the same and works correctly (Spotlight=press TDC long and a narrow scan follows the TDC around). Strangely the RWS scan centering is not the same as TWS = the correct implementation, but a strange variant of Spotlight with no TDC X, it then scans for a while like a Spotlight and then times out to normal RWS scan parameters? Trackfile attached. 2021.04.16 F-18 radar RWS wrong scan centering .trk

Hi there, i was trying the new ACLS in the F18 and i tried to follow the video instructions found on youtube but when i press the a/p cpl mode instead of a p/r indication on the hud i have a hdg indication and after some correction the a/p indication in the hud disappear with a Master Caution ligh on, on the mfd a/p is still visible the plane glide out of course....from there i can only take control of the plane if i want to land, what am i doing wrong ? AL.trk

In the F-16C, the game crashes when you try to enter HARM codes that do not associate to a radar. Three users tried it (including me), and the game crashed for everyone. I also tested it without third party mods and it would still crash. I tried it with a cold start and with the aircraft already in the air, still crashed. Desktop 2022.05.19 - 21.46.08.05.DVR_Trim_Trim.mp4

Since the last BETA update, the event.dead isn't called, if a unit isn't immediately dead, see attached demo. The death is registered in the ME event log, but the API isn't called. Reported by dcs-online.de and [WP] Stingray in the Moose Discord. event dead test.miz

The carrier in Mission 2 doesn't have ACLS set up despite Case 3 recovery.

My video pretty much explains my and many other people's frustration. AMRAAMs are broken. There is also other missiles broken, but AMRAAM is worst imo. If someone tries to tell me its working good, please watch the video or tracks beforehand. And if u insist on telling that, please leave the thread. AMRAAM guidance logic has been broken since the INS update that came in late 2021. ED then said it is a new wip model : + It is broken. Definitely not working properly and you don't need many people to test it. Can be seen in 1 min of gameplay. - It's a wip feature. Thats why open beta exists + You released this to stable as well? - It's WiP and team is aware. More updates to come This what's been going on for months. I've made 3 quick tests. 1- Notching WITHOUT RWR. RWR was turned off, no datalink or radar contact, no labels. This one was for people who think RWR is to blame. Yes, RWR in DCS might be too perfect, agreed. But this is not the reason 120C-5 being too easy to notch. See my tracks and video for this. You don't need the precise bearing indication that your RWR gives you. In fact, you don't even need an RWR. 2- Notching with RWR, low altitude, hot aspect, flat terrain and short range. Pretty much explained this already. No terrain to hide behind or break LoS. Just an easy notch inside 5nm. 3- Notching with RWR, high altitude, hot aspect, and short range. This one was for people always saying it misses because of altitude. Here you go. 30K MSL, 8nm shot and an easy notch. I haven't been enjoying the time I spent in DCS for months, and that was a reson I gave a break and only playing for competitive matches. Everything buggy, everything is broken and I can't see anything changing. I was a supporter of ED for years, and still want the best for both ED and us. If nothing is going to change, there is no point of spending another penny for anything from DCS. Do something that makes sense. Give us a roadmap or state report about what's going on. Said before in another thread, repeating this : It was fine back in time. At least revert to late-2020 missiles if its possible. They were decent enough to enjoy. Meanwhile, devs could work on new missiles and if you need testing, theres many people would like to join CB and test it. But if you want to test something that is not worth to play, please do it in CB. Dropping my tracks and video (of tracks, for lazy people who do not want to dl the tracks and watch it in game) Archer out. As always, Im hoping for changes. And reminder : This is not a rant or insult to ED. As a customer, this is my critisism about something I've paid for, while wanting the best for ED and myself. lowalt NO RWR notch.trk lowalt notch.trk highalt notch.trk

With the latest (18th May) patch there's an error when making a TADs target store, and presumably a HMD store too.. The Target store identifier doesn't correctly show in the 'weapon inhibit field' (top of the TADS or HMD High action display)....it shows T01, T02 initially but then seems to rotate back to showing T02 or T03 constantly with every additional store. In addition the Target Store idents in the COORD page seem to increment by 2 each time....so T02, T04, T06 etc. These idents increment even though the 'weapon inhibit field' status shows T03 every time. This is probably related to the addition of the pre-planned threat rings feature. But it's messed up the target store procedure. Although the actual locations are correct and can still be slaved to, it's major source of confusion. In my track I removed all pre-planned SAM threats in the ME and I still get the bug. You get the bug with ME SAM threats as well though. TADS Target Store error.trk

Track here. Tacview here. Rough timeline of events: Before takeoff I set my HAD to target lists 1, 2, and 3 as I will be attacking a SAM-5. I start flying 45º into the SAM, to put it at around 20-30NM. SAM-5 targets and fires a couple times. My HAD detects the 5 tracking and slowly updates to PGM-3. Suddenly, the 5 goes cold on my HAD although my RWR has it tracking and firing. Nothing on the HAD for a long period of time although RWR keeps beeping. I change to all Threat lists, I restart the HAD, nothing... I start getting targets back on the HAD, but not the 5, although it keeps tracking and firing at me. I fire a couple HARMS to 19 and BB and they impact at PGM-2. The 5 never comes back up on my HAD.

Hi. I tried to look but could not find it reported. maybe its way back in this forum. idk. Anyway. I am running latest stable version (2.7.11.22211) and i like to report a bug with aim9 and rapid fire. If you load up 4xaim9 on your A10 and shoot them rapid, you'll see that the model of the aim9 is still on the left outer weapon station. I have also provided two tracks. one where i fire slowly and you will see everything is ok. and one where i fire rapitly and you see the aim model still visible. this bug only seams to happen if you loadup 4xaim9's and shoot them rapid. I have tried replicating the same using only missiles on left and right wing. but could not get the same behavioure as i get with 4xaim9's No matter how fast i tried to shoot with only 2 missiles loaded. its ok. but not when loading up 4x missiles. Ofc in real life you would probably never fire aim9 in this rapid secuence. but that dosent change the fact there is a bug when lanuching the missiles rapidly. If this bug is a known bug just delete this post MissileBug-SlowFire.trk MissileBug-FastFire.trk

ACFT is showing a negative static roll characteristic at the 100-120 roll mark, causing the ACFT to want to roll upside down during CMF. ACFT is neutral static during this roll. Request this is updated. Occurs even when cyclic is re-centered to neutral (hence negative static tendency). Additionally, ACFT does not appear to have a “nose tuck” tendency in the >30 degree roll. The Apache, much like most helicopters, displays a weather-vane effect and will tuck into the left or right turn at this angle with no aft cyclic or thrust increase. Current characteristic has ACFT conducting essentially a translation slide in the turn instead of a heading change towards the ground.

Hello, for the longest time I thought this was a real life feature. However I can not find it documented in any real world literature, and after consulting with others believe it may be a bug. I have recorded a track. First I enter active paused, reset trim, test controls in each axis. Then try moving pedal with full back cyclic, left pedal is limited. I then hold in left pedal while moving my cyclic around, and you can see the pedal deflection change as cyclic position changes. I then turned off the pedal dampener and did the same test to verify it wasn’t the dampener. I hope this is helpful, thank you very much Rear cyclic limits left pedal.trk

Occasionally, in RWS a bugged target is lost and while attempting to reacquire, the elevation setting on the cursor is frozen into its previous range. Sometimes either the target altitude or one of the the radar elevation numbers is also stuck on the screen where the target was, a ghost of sorts. I’ve learned that the only way to resolve this is to switch into TWS and back. I’ve only experienced this in multiplayer so far, no track available. Side note but perhaps related, shouldn’t the azimuth and elevation be centered on a bugged target through any maneuvering? I’ve noticed this is not always the case, and I need to manually adjust while doing crank turns.

Hi I noticed this. The FPAS page shows Tacan 10 when actually I'm on Tacan 73? Is that a bug? Scren shot added. (F18 cockpit)

ATFLIR will continue to show the Designation reticule (diamond) despite there not existing a current designation. 1. Designate using the TPOD 2. Go to SCENE mode 3. Undesignate: notice the reticule reverts to the designation reticule, not the INR crosshair DesnotINR.trk

ATFLIR will enter INR SCENE erroneously. EDs manual defines INR SCENE as: INR SCENE. The ATFLIR enters this mode when the pod is slewed while in SCENE mode. The ATFLIR will enter SCENE mode again once slewing is complete. However in DCS it will be shown when in normal INR mode and attempting a slew. 1. Designate with TPOD 2. Go to SCENE mode 3. Undesignate: TPOD goes to INR mode 4. Slew: TPOD goes to INR SCENE, despite it not attempting to acquire a SCENE track. INR SCENE.trk

When engaging LST from VVLSV, the pod LOS will remain fixed at the point the VV was facing at the time of LST activation. Deactivating the LST will make the pod display the video pointing at that location, but will continue to show VVLSV symbology in the display. 1. VVLSV the pod2 2. Enter LST 3. Move the jet 4. Exit LST: Observe the Pods orientation relative to the VV VVSLV LST.trk

It seems since the recent update in open beta, when you ignite the rato system, you get a half a second of boost and there's an animation where you see the smoke leave the cannisters, not connected to the plane rather than the 7 seconds or so of boost to the plane.

Hi, I noticed helicopters are not having exhaust heat blur in latest open beta DCS 2.7.12.23362. Heatblur effect is present for fixed wing jets though. Is this a known change?

I found trying to access the rearm menu before you are in a airfields rearm radius causes a bugs with rearm dropdown menu and stays bugged for the rest of the session. This happens with Gazelle, Huey and Harrier from quick tests (I assume all modules are affected) Recreate: In mission editor place a client aircraft with the option "Take off from ground hot" outside a FARP/Airfield rearm radius. Fly the mission and when in the pit try to individually select weapons on each station, each weapon category is empty. (the bug) If you then fly to and land on the FARP/airfield each weapon category is still empty. You can still rearm from pre-set loadouts. Track is provided but not sure if you will see the effects on the rearm menu. If you repeat this process but only open the rearm menu after you land in a rearm radius it works as intended and the bug can no longer be reproduced. server-20211010-144758.trk

Trying to learn ccrp bombing. No way I get the instructions: The voice is drowned in engine noise, and the mission overview text is in russian. If I could get the text in English, I'd be good. But how?