jumphigh

I'm afraid nobody will fix the errors in the older version if there is a paid upgrade available. Eagle Dynamics is lacking the manpower to support every revision of every module. They're hunting a moving target and do not look back. It's the same as Windows 11: Fake improvements and a kick in the ass for everybody not willing to sacrifice his needs on the altar of hipsters for the sake of change. NOT GOOD! By the way I hope Eagle Dynamics will provide a Linux port in 2025 for the same reasons...

Please stop this BS! I don't want more graphical nonsense when GPU prices are that high. I got over 50 FPS with my RX 570 on 2560x1440 before the advent of DCS 2.7, now with 2.7.9 it's down to 40 FPS. The Marianas map with higher poly counts aren't looking really good but are shown with even lower FPS. Stop that useless eye candy when playability is ruined! Fix the whole crap first or provide LTS versions! When I bought a module I was able to run it on my machine. I don't want to lose my invest with silly "improvements". Nobody will be flying better if bolts are "updated" from textures to polygons!

You're probably right. I have a far inferior system, playing with a RX 570 4GB and resolution 2560x1440. I use the Huey free flight mission in the Caucasus to check my frame rates. With my settings I was able to get 50+ fps. With the advent of DCS stable version 2.7.7 something seems to be broken. I can change my graphic settings to whatever I like – the lowest is looking ridiculous and worse than a game from the 90ies – but I can't get above 40 fps anymore. It's reported already.

Ask yourself: How do you evenly distribute 40 frames on 60 frames of the monitor? Nobody can do that! So when running a 60-Hz-monitor with V-Sync you can have 60 frames or 30 frames of the same length, nothing between. You need a new monitor supporting variable refresh rates (VRR, Adaptive Sync), e.g. a FreeSync (AMD) or G-Sync (nVidia) model. Most of them support rates as low as 40Hz (40 FPS). Some decent Samsung TVs have a range of 20Hz up to 120Hz.

Bohemia Interactive tries to sell expansions and DLCs for ARMA 2 and much more for ARMA 3. It isn't that different to DCS. And I remember how I got into DCS: I bought a disc copy of UH-1 in Germany from Koch Media in 2014. I didn't know that DCS even existed that days – the disc copy looked like a stand-alone sim. To my surprise I got a free Frogfoot on that – and never played it. So I wonder how many enthusiast out there are getting into DCS just with the free base module? I took me several months until I realised that you can fly trough trees. Since then I always thought, WTF, it's a helicopter sim, isn't it? I took years until version 2.0 to change that ridiculousness. There are users inside the UH-1 subforum willing to pay for a new UH-1. I say: Eagle Dynamics, get the job done for the old one! Collision boxes on the ground are another point of ridiculousness. Every iteration something breaks or is worse than before. I lost all trust in the devs.

I don't know. I remember the benchmarks inside of ARMA 2. One of them showed single-digit FPS. Now, 10 years later, decent CPUs and GPUs don't change that much. Nobody trashed the game because of that. As a low level heli pilot sometimes I think the graphical details of DCS are worse than that old gem. I know the maps are huge and you can't compare to hand crafted maps, but especially towns and villages aren't that sparse and empty in reality. Even the new Marianas are looking empty. So I really don't know why DCS is so slow.

They should make a automatic benchmark including log with the free Frogfoot on the Caucasus and Marianas maps. That will deliver standardised and repeatable measurements to the devs. Requesting tracks, FPS and frame times from customers is a big mess...

Like others said you won't get any module update. You can stay on the older version not more than one year because after that you will loose authorization and you have to update if you want to play again. I wanted to stay on 2.5.5 with my old RX570 4GB but this March I ran out of authorization and was forced to upgrade. No way to stay on the older version. DCS might be a moving target but they can't expect that their customers are always able to upgrade hardware if they raise the toll. So without LTS versions my pocket remains closed – I do not buy stupid DRM-crippled SW any more. With my old RX570 card I suffered FPS losses from 2.5.5 to 2.5.6. I got over 60 FPS with 2.5.5. That went down to between 50 and 60 FPS on 2.6. With the 2.7-track I managed to get 46 FPS average. But now with this "stable" version 2.7.7 it won't go higher than 40 FPS. Every revision measured in UH-1 Free Flight mission. I'm playing in 2560x1440 and all settings Low/Medium or off. 4GB VRAM isn't a problem, it stays below 3,7GB on the Caucasus map. But even with going deeper to low textures, shadows off and tree and theatre density to 0.1 DCS is capped below 40 FPS!? Everything is looking bad, worse than games from the late 90ies. Ridiculous! CPU (i5 10400) stays at 10% and RAM is below 12GB. What the hell are they doing???

Autopilot has the 3 modes Alt hold, Orbit, Straight. E.g. playing as the door gunner select Orbit and then activate the AP – the AP circles around the spot beneath you. So select the mode, than activate the AP and the AP will do what the mode says. Recently I stumbled across the same key binding issue on external cargo. There are "External Cargo Release", "Pilot Cargo Release" and "Copilot Cargo Release". Only the second and third can be bound to a controller, the first is restricted to the keyboard. That's somewhat logical, as pilot or co you have a dedicated cargo release button on your stick – use this instead of a generic keyboard binding. So for example the reasoning for "Look Down At Cargo" may be: Being on the stick move your head yourself. An other explanation may be, that they simply forgot to add a controller binding for those functions. With the advent of VR and multiplayer many members asked how to map the change of door gunner aiming mode (head tracking or mouse) to a controller button – you can't without editing a LUA yourself. Since the Huey doesn't get much love from the devs AFAIK the problem still persists. So it's up to you, there might be a solution on the forum. But the easiest thing you can do is to use your controller software and bind a controller key to the needed keyboard key. Don't bind that controller key inside of DCS. Pressing the controller key now should activate the keyboard restricted command like a direct keyboard key press does.

Of course – no reaction on right click in the column of any game device. I can change the default 'U' on the keyboard. Seems that stick buttons can only be bound to the specific Pilot or Co-Pilot Unhook command. Is it just me?

I can't assign a controller button on "External Cargo Unhook". It seems you only can use the appropriate stick commands for pilot or co-pilot?

Without DCS' style of force trim you need all the way on the cyclic with the Huey. Don't restrict maximum throw (saturation) on cyclic axes! At least on fast forward flight you have to push the stick almost all the way to the front – what you can't do with a saturation of 80% on the pitch axis.

Hello Forum, am I the only one who has this annoying behaviour? When flying the supplied Heli Ops mission and choosing the Huey task with sling loading supplies to the front line post I crash the cargo regularly. On approach to drop zone you get red smoke and the crew chief starts to make his call outs. Then I crash the cargo box to the floor and the crew chief's call outs continue forever. Even when miles away from drop zone you can hear e.g. "20 to front, 20 to right, 30 to ground". Many user complained about the fragile cargo that break easily but I do not find any report about the call outs. I'm on latest stable 2.5.6. [Sorry, wrong sub forum. Please move to "Bugs and Problems".]

I updated to 2.5.6 and login works again. But FPS are significantly worse than 2.5.5. I have to lower settings to get the same semi smooth game play than before. Not everybody out there owns a $2000-RTX 3090. There are reasons your customers want to stay at an older version!

I even don't understand why there's a need to shut off older versions? Of course you get no support but deactivating authorization to render it useless on customer's side? That's ridicules and in my opinion a violation of customer rights – at least in the EU. This is not an online service! On my side there would be no problem in upgrading if code quality is given. But my main module is the Huey and according to the forum, version 2.5.6 introduces more problems and faults with every update then it solves. As an owner of older modules I lost all confidence in newer DCS.

As I already wrote: Latest 2.5.5, Subversion 41371.1. I opened a support ticket and they told me: I can't remember, when and where I read about old versions going out of activation so I asked the forum. Maybe one of the members has more insight. One month ago, 2.5.5 activated flawlessly and allowed me to test modules during free trial, but now, it refuses to work without further notification? Am I the only one who is still on 2.5.5?

Hello, I'm running the latest 2.5.5. Last start was 2021-02-05, everything was working then. Now at start, every login attempt fails with "Invalid login or password", I have no authorization and all paid modules are disabled. But login to my user profile at ED's site works as usual and I can see all my modules. Integrity check and repair show no problems with my installation. I don't want to update to latest 2.5.6@stable because I'm inside the Huey campaign and I'm afraid that the latest changes to weapons effectivity may harm the old mission design. Especially the effect of the Gatlings on unarmored soldier groups seems worse in 2.5.6. Is this problem related to my old 2.5.5 or what's going on at the moment?

There is no indication that different weapons can be used at the same time. According to the description in the manual the flexible sight trigger does the same as the trigger on the co's cyclic stick. Since there is only one trigger on each cyclic stick the armament selector must be working for both sides. You have to coordinate weapons usage and someone has to flip the switch each time weapons change.

That's the way the Huey systems work. Only one weapon can be active at a time – for both sides. To prevent your Co from taking over control when ROE is set to Free Fire you have to disable flexible sight mode with the M-key. Or you set set Co's ROE to Hold, set flexible sight to Automatic, change from pilot position to co pilot via 2-key and do the shooting yourself while auto pilot driving around according to auto pilot mode.

Sorry, but you simply shift the problem from outside of DCS into it. If you have RUDDER LEFT and RUDDER RIGHT, what value win to set the single rudder on your plane if both half-axis are loaded? Best solution can be to calculate the mean of -LEFT and +RIGHT which allows a smooth handover from one pedal to the other. You'll get a centered rudder if both pedals are fully pressed. This calculation could be done outside of DCS with a suitable driver so a single RUDDER channel is still suitable. But I suspect most software coming with the input devices won't cover this case so the split inside of DCS may be the real thing.