All Activity

This statement is accurate when it comes to exaggerating visual/audio feedback for the pilot to make up for lack of physical feedback from flying, which is entirely necessary when pushing an aircraft to the edge of its envelope. However for general, cosmetic items that do not function as flight envelope feedback exaggeration is unwarranted. As a modeler myself, I also disagree with exaggeration in that context but that's a different discussion altogether.

The ATP is not as easy as the previous pod. Was our Litening pod simply unrealistically good in terms of optics/laser/etc? I kinda thought so. Perhaps reality is just more difficult? -Ryan

We'll look into it, thanks!

DCS 2.9.17.12034 - 24.07.2025 Mission 02 "First Sortie" - Fixed incorrect voice-over in food small talk dialogue. Mission 05 "Convoy Hunt" - Fixed radio presets. Mission 10 "Finland CAS" - Fixed decorative infantry walking on taxiway. Mission 11 "Sam Hunt" - Fixed decorative infantry walking on taxiway. Fixed active Game Master slot. Fixed "Skip Briefing" function not stopping briefing voice-over. - Fixed floating elevated platform at roadbase. Fixed cryptic ATIS subtitle. Changed wingman skin. Mission 12 "Alakourtti" - Fixed decorative infantry walking on taxiway. Mission 13 "Greyhound" - Fixed decorative infantry walking on taxiway.

After today's update I experience exactly the same thing. Devastatingly long loading times and even launch screen pops up super slow. When I start the DCS the fan speed goes up slightly then almost goes sleeping. Usually the fans should have been spinning fast. What I noticed, even the video in launch screen runs with stutters, I am not even mentioning the game; my FPS dropped from 72 solid to 20 max.. I did numerous methods, thx to Chatgbt, but the problem still exists. Then I read this forum and disable the Hyper Threading, unfortunately also this did not help. Since yesterday I had no issues at all... Let me know if anyone has an idea

Except you didn't break anything, you just did it wrong

Why does this update require an OS restart?

It's my understanding this has been possible in the A-10C (and also A-10C II) module and what you're describing as a bug would have been a bug for a long time. It's also my understanding that other friendly aircraft, particularly E-3 AWACS, can serve as a gateway between SADL and Link 4/Link 16. So the only bug, as I understand it, is that the gateway works even without such an asset present in the mission. But frankly, that whole datalink thing is a bit of a mess and has been for basically ever, where A-10C players can currently see AI Hornets and Vipers, but not player controlled ones, yet player controlled Hornets can see player controlled A-10Cs on their SA page. It's all work in progress, AFAICT. I'm not saying you're wrong, but this doesn't look like something that would be easy to address, nor does it make a lot of sense to me to fix this particular issue without addressing the bigger picture.

TMS aft seems to be a fix. Problem: In either IR mode, you can't see the bandit, save for a slight blur. In TV mode, the bandits jet exhaust is inky black, so you can't even make out wings. -Ryan Fair enough, I'm just better at breaking things than the testers. -Ryan

You are welcome, and consider next time leaving out the shot at our testers, they work hard on this stuff, and as you can see with a couple of your reports already its easy to miss a step or misunderstand something. Thanks.

The fuel tank selector rotary, and magnetos switch are still + or - . The gunsight brightness is finally an axis. The correction to drag with loadouts are nice, it doesn't wallow as bad anymore.

Double-tap EXP on your stick to go into XR.

You guys want videos ahead of time, it means in many cases he is using pre-release builds that are still being heavily tested and possibly changed, while it doesnt happen often, something may change between his video and release. While I understand you are kidding, he works hard to get you guys ready for release so you can enjoy right away, lets not dump on him too much please.

So, in order to do what Wags does in the videos, I should not do what Wags does in the videos. -Ryan

If I understand correctly, yes. Only eprls systems can be present in a SADL net and in our case in the TAD. For the A10C2, with the proper implementation of the arc-210 and the gateway for the L16(TNDL) IA and human L16 equipped aircrafts (15,16,18,A10C2) as you said, can be present in the TAD. Prior to the arc-210 upgrade (and the TNDL WiP) I don’t remember to have in the A10C (not the C2) a picture in the TAD with other airframes different of the A10C (no E3, 18…) So I presume that it’s more a “core bug” due to the partial implementation of the TNDL that conflicts with the old EPRLS implementation.

There is no physical evidence. The report mentions "provisions for GM1", but doesn't specify which tank was installed "instead of the FuG 16" - the 115l Zusatzbehälter or the 85l GM1 tank. Negative. The R11 Rüstsatz did not include GM1, but it did include some more advanced IFR equipment. RLM projected a run of 200 airframes, supposed to be built by AGO under the designation A-8/R4. GM1 was later cancelled by RLM for the use on the 190, though, as performance with GM1 was less than the 109's performence with the DB605D without GM1. GM1 was cancelled altogether by August '44 due to lack of necessity. Acc Rodeike only a few R4s supposedly are known to have been flying with 10./JG 11 around the op Bodenplatte timeframe. GM1 wasn't, as clearly stated in your travel-report Bengelmann: "Dieses ist um so zweckmäßiger, als die Aussicht besteht, daß auch für Fw 190 mit 801D Motoren die GM1 Anlage noch zum Einbau kommen wird." So on 04 FEB '44 a mock up of the 801TH GM1 device was shown, which would have an 80g/s nozzle, according to required specs. Fw proposed the use of the same device which was already designed for the 801D, as this design was prospectively to be used in the future. See above how this worked out. Approval by Rechlin or an OEM's test-bench doesn't include kits ready for shipment and modifications starting at the front units or even serial production in all branched-out factories. As we can see, GM1 was earmarked for some 200 AGO airframes only. Final approval by RLM is a different matter altogether. That's because you're busy reading things into stuff that's not written there. It's not "we're checking into it", but "the following solutions can be offered on short'ish notice". Seems you're not understanding we're dealing with a centralized planned economy here, where changes aren't just incorporated because some test or general approval make it seem favorable. Changes are incorporated into specificly ordered blocks, which at times may not happen for several months.

F-16? I don't think so. At high speed - if you can call it that - lets say 250kt, the nose sways all over the place

Wind does not influence the choice of runway for aircraft takeoff and landing. Aircraft consistently use Runway 27 for takeoff and Runway 09 for landing, or vice versa.

We will try and reproduce soon, but if you get a chance, share a track of this issue if you have it. Thanks.

Foreword; Used both executables (bin and Bin MT folders). Tested in the Caucasus map, single player on a windows 11 rig. As of July 23rd, 2025 The latest update (DCS 2.9.18.12722) I did a little experiment as I Also experience significantly long load times. If you're running a 13900k or 14900k you'll find this interesting. - Two updates ago I got super long load times and stuttering in DCS... Disabled Hyper-threading in the BIOS, POOF! Problem solved, no issues and everything was butter smooth - Today, out of curiosity, I updated to the latest DCS, ENABLED hyper-threading in the BIOS and tried DCS again. Stuttering gone but Stupid long load times to the point where I get the windows blue circle thingy on the mouse and asked to close the program or wait. If I wait, DCS works but I have to wait a long time. Sooooo I - DISABLED hyper-threading again and checked... All back to smooth, regular short load times, no lagging, no stuttering. All good. BTW, Windows 11 is fully up to date but I think that fixed the stuttering but not the long load times and lagging. I don't know why this is hapenning but it seems to be the new norm for me. Hyperthreading on, games run like crap. Hyperthreading off, games run smooth as butter with no issues. Has anyone noticed this as well?

I don't understand your point, so let me try and clarify if I get it right: a player controlled A-10C (not A-10C II) should not be able to see any F/A-18C on the TAD. Is that what you're trying to convey?

That may be it. I will check. This may be what Wags said to "Press TMS long" in the video.... Thanks! -Ryan

If you are not in A-A MT mode, you need to press TMS Aft-Short to slave the ATP to the bugged target after manually slewing the ATP away. If you are in A-A MT mode, the TMS commands change so the pilot can actively hunt for targets. If you slew the TGP away from being slaved to the bugged FCR target, you must deselect MT and press TMS Aft-Short to slave back to the bugged FCR target. We'll add a blurb in the manual that TMS Aft can be used to return the TGP to SLAVE mode to get back to the bugged FCR target. Let me know if that helps, if not post back and I can take a closer look. Thanks!

~350mph (~315 knots) is attainable starting with a shallow dive and WEP off. Speed can be maintained with gentle care.

You get the best picture you need to be in TV NARO XR mode. In this screenshot you are not.