All Activity

Have you checked your dcs.log file for any errors? The DCS Discord channel has a feature that allows you to upload and analyze the dcs.log file for any errors and will give recommendations for fixing or optimizing your setup.

THANK you for that, this makes so much sense now!

Hi, I am new to DCS and have started running an f16 which I find to be great but im very unskilled. I have installed opentrack with a delanclip head set but although its very good I cannot seem to reduce the HUD size and it bleeds over the screen. It seems related to the forward/back movement and I have to lean right in to get anything like a decent capture of a target. Has anyone experienced this? Any guidance would be appreciated Thanks

Cheers. I guess since i only play pvp i have less trouble with tracks/replays not working, whereass pve does create issues. My guess is that ai still can pull off some stuff regular players can not hence there is discrepancies later in the track? There are few dedicated mp dogfightservers for mp only which could be used for testing. But it kinda appears the flightmodels sorta could be the root? Or PvE respectively.

You must uninstall and disable the maps in the module manager inside the game, (or launcher?). Just deleting them in Windows File Explorer will of course just download them again, because that's how the system is designed, and the system thinks you still want them to be installed. Cheers! Sent from my SM-A536B using Tapatalk

Yeah, I think the audio cue went off fine. But the SA6 launched on my wingman when he was 21.5nm away, and that missile impacted him when he was around 12.5nm away and still outside what I was seeing in-game as the threat circle on the SA. Not sure if that'd be a mission-specific issue or something with DCS itself, just thought I'd flag it. If the SA6 had targeted me instead I would have blown up somewhere where the voiceover was telling me I was still out of range. Tacview to make it easier to see Tacview-20250903-185232-DCS.zip.acmi

What do you mean? At the production time it was very competitive. Still flies for some air forces today but of course not comparable to 5th and next gen.

Yeah, kept his job, mishaps happens all the time! Blood pressure, indescribable? [emoji28] Pretty shure HP didn't exactly invoice until all was fixed. Nice of the backup guys to actually have done their jobs. [emoji1303] EDIT: This was like close to 25 years ago. Everyone learned something that's for sure. And I've never heard anything like it ever since! Sent from my SM-A536B using Tapatalk

The ECM is modeled very primitively. In reality, it may not always interfere with the air defense system.Moreover, there are many interference guidance algorithms. The Tor M2 has an optical guidance channel, it doesn't care if you use the EСM or not.

The EF mods don't work on the latest version of DCS. I run 2 versions an old one for the EF and the latest for everything else. That's why I'm trying to find a player that is using V 1.0.7. Yes, the original Modders have stopped working on it...but there must be other EF fans with the mod. I need one of them to share their mod.

Thought so. But then you might want to change the header to have it a little more descriptive. [emoji6] Just click and edit it. Cheers! Sent from my SM-A536B using Tapatalk

got feedback...at least 1 of those 4 PC's had it again. No need to say it's the most important of those 4, Murphy's law always strikes when you need it least. Sigh, nada I can do but watch disaster happen.

Indeed, that tops it all, LoL. Has he kept his job ? just curious What was that guys blood pressure once he realized what he'd done ? I guess "Off the scale!" Sh!t happens...LoL

I just tested it. I wasn't aware of it. It's a start. Great! Thanks for the tip.

Even if the Mission flown in the Track does not have any Mods in it? The Track is only two F-15Cs fighting on the Syria map-

Dows anyone know if there is a QF-4 livery for the F-4E with a pilot disable draw argument in the custom_args section so the cockpit will be empty?

this is a fairly common error i think. really no good solution. do you have WinWing MFDs? if so do you have vsync or gsync enabled? turn those off and retry.

It despawned because the parking spots are too small for it. So in that sense that is the expect behaviour as designed.

I tested the ALQ-184L jammer on the A-10CII against the TOR M2 [CH], the result is quite surprising since the ECM is able to break the SAMs' locks. (very interesting feature) The SAM also seems more susceptible to ECM in general as it reduces the engagement distance when compared to other SAMs. The TOR [ED] does not seem to follow this logic. I report this characteristic because it does not appear to be in line with the other SAMs in the game. The updated SAM is more susceptible to ECM than the previous version. Repro steps: I fly toward Tor M2 I wait for RWR to signal the launch. I turn on the ECM Result: The Tor M2 [CH] does not behave under ECM like other DCS SAMs. Jem_TM2_test.trk

Fresh bump, and updated post ^^

Fresh bump and updated post ^^

I stumbled upon this very thread after facing a similar issue multiple times with the MiG-29A, so I'll share all the data I saved here to keep everything in the same place. Flying a simple 1v1 dogfight between my MIG-29A and a M2000C, I found out that the track diverges very rapidly, to the point that there is nothing in common between the original flight and the replay. I've tested this multiple times, and the outlook of the combat sometimes changes dramatically. The AI in replays completely ignores the flight path and actions it took during the real flight, and develops a mind of its own. A coherent dogfight turns, in the replays, into a mess where my plane still follows the original trajectory, but is fighting against (and firing weapons at) thin air, whereas the target is now actively trying to get a shot out of my plane. This is repeatable for each flight/replay combination. I've seen multiple instances of the 2000C shooting me down in the replay whereas I won the fight during the flight. For testing purposes, I flew a 1v1, which voluntarily kept long to generate data, and won in the end to illustrate the change in outcome that often happens in replays. I saved a bunch of files for diagonistic: ORIGINAL_TRACK is the track saved immediately after the flight. Logically, it should show me winning the fight (it does not). REPLAYED_TRACK is the the track produced (and saved) by playing ORIGINAL_TRACK (it should show the issue, and have me not winning - but it's unreliable anyway). Because neither tracks can be trusted - that's kind of the problem - I also saved two Tacview files: ORIGINAL_FLIGHT_TACVIEW is the Tacview file produced during the original flight. Because of the track bug, it's the only file that is trustworthy when it comes to how the flight was actually performed. It shows me downing the 2000C at 095858. REPLAYED_TRACK_TACVIEW is the Tacview file produced during the replay of the flight. It has nothing in common with ORIGINAL_FLIGHT_TACVIEW save for my trajectory and weapon employment, and I can be seen fighting ghosts in it. At 095858, I'm shooting at nothing whereas the 2000C is closing in my 6, and tries to shoot me down at 095902. As one would expect, the longer the mission, the larger the difference between the replay and the OG flight. I've had very short dogfights (sub-30s) replay most the time the same, because errors and changes don't have the time to propagate. Still, even on such short flights, sometime the difference is massive (for instance, I had a frontal gun engagement turn from a complete 2000C destruction in the OG flight to a single flaperon loss in the replay. In that replay, the 2000C shot me down afterwards because I flew a straight line - there were no ennemies anymore to worry about in the OF flight at this point). Longer dogfights never replay correctly. As it stands, tracks are unusable as a mean to save a flight. Tacview is the only tool that can store trajectories and results in a reliable fashion. Yeah, the problem seems to be markedly worse when maneuvering. ORIGINAL_FLIGHT_TACVIEW.zip.acmi REPLAYED_TRACK_TACVIEW.zip.acmi ORIGINAL_TRACK.trk REPLAYED_TRACK.trk There you go. You now have two example of the issue. Note that this isn't Spit-specific, it's a sim-wide problem. I could replicate that with any plane and the two examples provided include the 109, the Mosquito, the 2000C and the MiG-29A.

Even with a larger page size, still the same issue. Also, changed the power settings to best performance (ie, no parked cores) Not sure if relevant, but I do get this message in the log around the time the freeze happens: "2025-09-06 12:17:41.781 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED" I would expect that the explanation be somewhat straightforward by looking at the ETL file (and see the stack traces) by someone who has access to symbols (that is, not me :-))

This is something to add on my "to do list" when mig-29a is released.