All Activity

I would say all three could use a serious update: NTTR - could more like Afghanistan Caucasus - could be more like CWG Persian Gulf - could be more like Syria Also, I'm sure most players would also pay a modest fee for such upgrades if they were actually agreed to by ED.

And part of pressurization system no doubt

What you buy depends on what you want out of your simulation experience. I happen to like "closest-to-real" equipment to what I'm flying. I've been using Thrustmaster since the early '90s. Currently, I'm using the Thrustmaster AVA base with the latest F-16 stick, but the old Cougar F-18 stick. You swap them out on the same base. I've been flying the F-16 for decades, but the last 5 months have switched to the F-18 and have the F-18 stick mounted. It only takes seconds to swap the sticks out. I'm also using the TM Viper TQS (Throttle Quadrant System - has a small panel with knobs and switches on it), but its quality has been questionable. In addition, flying a two engine aircraft with only one throttle is a little awkward, but not a real problem for me. The generic sticks and throttles have the advantage of having more buttons on them to program.

Hi everyone, I just wanted to post a quick update. I've been taking a break from working on this mod for the last few months, playing other games and doing some things IRL. I'll be diving back into it soon for the Su-25 and push towards a 1.0 release, and wanted to provide a bit of a timeline for that: Roadmap 2025 Sept/Oct: v0.5 Su-25 Basic Support v1.0 Animate all major clickable elements (gear levers, canopy click points, etc) to accurately follow the cockpit model Update Su-25 to work with new version, when ED releases it Late 2025-2026 v1.1 Look into animating visible switches and knobs in FC cockpits -- Many currently have animation, but do not use it General bugfixing and compatibility updates as needed In the meantime, if you're itching to fly the Su-25 the original CLICKABLE-FC3 mod should still work fine

Hello It seems like the non XR IR image in the Sniper is a little too fuzzy in non XR modes. Could you please look into this? Here is a screenshot of a T80 tank column at 10 nm. nullHere's a comparative video - pilots state that their seeing "breakout" at 11nm - note that they do *not* appear to be in XR mode. null

I haven't had any problems doing that, this is news. Can you give me the name of a mission that doesn't work with?

Buddy-lasing for another type from ka50 probably won't work, since it's been changed and nobody knows the code(or if it's even a NATO PRF code anymore),I guess buddy-lasing now works only between ka50s. But for now 1113 still works for su25t. If u want an answer from dev about ka50,maybe u can try Ru ka50 sub-forum using a translator,looks like people who actually did the coding sometimes answer questions their.

Hi, not seen this one before, but please ensure the OH6GunnerExport script is removed. Run a slow repair of DCS or verify if steam version. thank you

Not even the Spiffy? Because in comparison I find the Corsair rather tame compared to that bird

dcs.log-20250904-135002.zip

Windshield ventilation / anti-fog would be my guess.

well a lot of us have been fine using the G2 so at least that much lol (in other words it far worse in the g2 vs the super)

How are you connecting the Quest 3 to VD? Do you have a dedicated access point? Look into connecting your Quest 3 directly via an ethernet cable to see if the problem still exists.

If your controls allow, you can also make turns on the ground by splitting the throttles. Similar to how a tank turns; Leave one propeller at idle while powering up the other propeller. Hope this helps.

also with the FPS counter, it says CPU limited ... what it means is not really that the CPU is limited; rather DCS just can't use any more CPU processing power... which is different, it will likely be the case that some CPU cores will still not be fully utilised, faster individual core performance will help some... but ultimately you will as @Hiob says be limited by something... a couple of things that *WONT* change the CPU limited status, is making sure that DCS does not use core 0/1 (which is what windows uses by default) and the same with other DCS performance related processes like your VR stack or voice attack , beyond that other than a CPU with faster cores not much can be done by us

Well, I agree with you, didn’t wanna “argue in the contrary”, we’re here for the same goal. It’s just that sometimes people consider bugs things that are not bugs (not just in the Corsair, in all modules). Opening (yet another) thread saying this thing flies 200mph at max power and is severely underpowered is not gonna help anyone, devs are just gonna disregard it. It is frustrating because I would also love this module to shine, not just because I’ve paid for it…but because I truly love this aircraft. And to be clear, I also think it flies slower than it should.

Да его уже никто не даст, так что на этом можно только поставить точку

Any idea what the highlighted portion is?

No, we weren't using DCS. We used FS2024 or 2020. Whilst I tried a variety of manoeuvres, all just felt a little slow in their reaction speeds and as a result, felt less natural. As mentioned, with the cost, space issues and required tweaking involved, taking the risk that it "might" be possible to dial it in seemed a bit of a jump too far. In addition, I know someone who had a DOF3 and eventually sold it on.

Я думаю он имел в виду игровую опцию, которая позволяет при холодном старте сразу иметь выставленную инерциалку. Т.е. при включение ИКВ и НАВИГАЦИЯ будет стразу готовность навигации.

Why be so dramatic? They are not abandonware. Persian Gulf, Caucasus, NTTR are all feature complete but still receive tweaks and bug fixes. thanks

Regarding headlights, the problem is more complicated than that: In a war zone, an armored column traveling at night will primarily use NVG or infrared devices to avoid turning on their headlights, which would make them visible from miles away, especially when faced with aerial reconnaissance vehicles (drones, helicopters, planes, etc.). It is therefore normal for columns to travel with their lights off on DCS. Outside a war zone, however, they would turn on their headlights normally. Also, it might be more interesting if ED added an adjustable "Lights on at night" option: true/false (default: false). Regarding brake lights, I believe some vehicles have them (but probably not all models). However, I find that this is clearly not a priority for ED; I would still prefer if they added many new units. At ED, you have a model with 2 animations: "intact" and "destroyed". The explosion allows you to make this transition between the 2 animations (this hides the texture change) A ship can sink in 10 hours. A ship can sink in 2 hours. A ship can sink in 18 minutes, like the Lusitania. By convention, in most video games, when a ship is destroyed, it sinks in 1 minute. It's true that it might be interesting to extend this duration of the sinking for rescue operations, for example. Perhaps add a slider option to define the sinking time? Or something relative to the damage ? We can already adjust that. There's an option to adjust the dispersion time during an attack. Personally, I often set the dispersion time to 3 seconds, so it looks like everyone is swerving (panic), then pulling themselves together and continuing on the road without stopping.

PG, Caucus, Normandy (all of them), NTTR: all abandonware. ED specifically said that NTTR will never get an update.

I've done that with VAICOM Pro, but again this is dependent on the mission. Sometimes Jester is happy to "set map marker 1 to fixed point" and other times he just plain ignores you. v6, boNes