jaz85

Complete error: Warning Login in progress. Please wait or press Continue to launch DCS with free modules only. Since the March 19, 2025 update, I get the above message when launching DCS when in offline mode AND when third party modules are in installed in my Saved Games/DCS... folder. The interesting thing is that pressing the CONTINUE button brings me into DCS and I seem to able to use free and paid modules as usual. Another bit to this is that I am unable to exit offline mode via the launcher, rather I simply have to exit out of DCS and then remove the offline.bin file from my Saved Games/DCS... folder. Anyway, I do not think this is a critical issue, but would be nice to have it fixed.

I have also noticed this in circular orbits and also with when the tanker is a carrier recovery tanker. I suspect this is not intended behavior. To be sure, the tanker will still fly a nominally circular orbit (or recovery tanker orbit) at roughly the same altitude, but there are many disturbances now that did not used to be there, for example: small right hand turns (though the overall orbit still is a left-hand turn circle) accompanied by nearly instantaneous acceleration of four or five knots, and also accompanied by a small but quick change in altitude (maybe fifty feet?). With something like the S-3B tanker with its short hose or the KC-135 (boom, not MPRS), it is nearly impossible to stay connected to the tanker when these happen. It is a bit easier with the KC-130 and KC-135 MPRS because their long hoses have more play in them. On first post-most-recent update test, a tanker on a race-track orbit (but not carrier recovery) does not seem to show these behaviors. So it seems, to me at least, that these happen on circular and recovery tanker orbits. I understand that circular tanker orbits might not be a thing in real life, but they can be helpful in DCS especially for newer digital aviators who might have trouble trying to end up at a good intercept position for a race-track orbit. But I think the recovery tanker orbit in DCS probably is not all that far off of what might be used in real life. Anyway, even if not particularly realistic, if the capability exists in DCS, I suspect everyone would like it to work well.

thank you for posting this; I have noticed the same thing.

During night approaches, the deck illumination on the Admiral Kuznetsov (2017, from Supercarrier) is not visible until the approaching aircraft is nearly on top of the deck. This is new behavior since either the 30 Oct 2024 or the 2 Nov 2024 update. Prior to this, the deck lights would be visible from at least 2km and usually 3km or more. Kuznetsov (2017) night lighting.trk

also similar to earlier reports, I see this in dcs.log: 2024-09-06 03:53:49.586 ERROR ASYNCNET (41860): Entering offline mode failed because server returned an invalid reply.

I am now also getting this error, after getting an authorization notice specifying the CH-47F is not available.

Closed -- fixed with the first of the 2.9.7 updates.

Since the second (or first?) 2.9.6 update, there is no communication with the Forrestal and Kuznetsov (2017) carriers. I have tried with various aircraft on the Forrestal including the Community A-4E-C, F-14A, and F/A-18C. I have tried only the Su-33 with the Kuznetsov. To re-create, simply launch from either the Forrestal or Kuznetsov, and then try to establish contact to request landing. \ -> F5 ATC -> either carrier results in only F11 Back and F12 Exit options. The US CVN carriers seem to be fine in this regard, with communications working correctly as they have for some time. I've tried this with and without any community mods with the same behavior. su33_kuznetsov2017_no_comms.trk f14_forrestal_no_comms.trk

Short answer: yes, we have the more powerful engines in DCS. Long answer: The Mi-17 is the export version of what in Russian service is called the Mi-8MT. The DCS Mi-8 is modeled on an improved version of the Mi-8MT (the Mi-8MTV2) with improved hot-and-high performance and other enhancements over the basic Mi-8MT.

And it was there in front of me! This works great, thank you for mentioning it. I think this can be considered solved or at least as having an adequate solution.

I have options.graphics.maxfps = "75" in my autoexec.cfg and until 2.9 it would limit fps to 75. Since 2.9, that setting seems to have no effect with fps often exceeding 150 or so. My machine is Windows 11, Ryzen 5 5600x, RTX 3070 (8GB), 64GB RAM, and I am currently running open beta v. 2.9.1.48335. To be sure, DCS runs very well on this machine, but with 1080p monitors at 75Hz refresh rate, I get no benefit from fps higher than 75. With fps limited to 75, my gpu also runs anywhere from 5*C to as much as 10*C cooler than it runs with uncapped fps. Additional info: I am running the multi-threaded application, and have not yet tried this with the single-threaded application. So far I use this only single-user, so no multi-player. Otherwise, I am very much enjoying 2.9.