fjacobsen

Did the Carrier move ?

Hmmm... Like the dogfight scene in Top Gun against Mig-28's :megalol: I have seen Behind enemy lines - nice action though, but still Hollywood.

The transition from forward flight to hove must be done gradually. In hollywood movies You will see alot of quick stops - forget that. pitch back on the cycle to reduce speed and lower the collective inorder not to climb. Monitor descend rate and decceleraion. Once You get slow - add som rudder to counter torque induced yaw. Most important - monitor descend rate and keep it within safe margin. Controlling the Gazelle near hover means alot of small corrections and focus on descend rate. Learn to anticipate in what direction to control before required. Be patient and wait forYour control input to take effect. The helicopter will always lag behind You control input, so stop controlling just before start going in the opposit direction. There is no substitute from practicing - practicing. Don´t compare to the KA-50, UH-1D ot MI-8 ! This is a small light helo and very agile.

Not sure what You did - but there is no 8 x FXAA. FXAA is a post process that can either be On or Off and not 2, 4 or 8 x. FXAA will remove the jaggies, most noticable at the cockpit edges. But it´s not perfect, so You will have some shimmering landscape and objects.

Data link is broken - Reported and Devs are aware.

Reemember "Finger Lifts" + Throttle forward inorder to set Aferburners.

And here are my settings: Only addition is FXAA set to On in the Nvidia Control Panel.

Nvidia driver is fully uptodate. Apart from having set FXAA in Nvidia control panel instead of using ingame MSAA, everything else is set to default. Maybe DCS is doing something that the Nvidia drivers doesn´t like

BIGBEWY... Here is a crash lock with the AV-8B on the Persian Gulf map using mavericks and GBU-12: https://forums.eagle.ru/showpost.php?p=3498940&postcount=3

Thats also my experience. Seems that the PG map still needs alot of tweaking and optimazion. Maybe the new "texture unloader" is not put into use on this map yet. NTTR, Caucasus and even Normandy runs much smoother than the Persian Gulf, though both NTTR and Caucasus ere bigger and at least Caucasus alot mor diverse in terrain features and objects. + NTTR is 366.000 square kilometers, mostly desert plus Las vegas. + Caucasus is 250.000 square kilomters with alot of forrest, open land and smaller towns. + Normandy is 92.916 square kilometers with alot of trees and small villages + Persian Gulf is 200.000 square kilometers and mostly desert, though have some big towns.

Also got a crash in the Persian Gulf. Log: dcs.log-20180527-081432.zip

And where do You find the axis filters ?

I get the same... NTTR and Caucasus runs smooth, but Persian Gulf is stuttering and freezing with much higher memory consumption.

When adjusting radar brightnes knob, it doesn´t rotate, but is "only" an animation bug.

Not sure on this but... Try to restart DCS after deselecting "Easy comms". I think to remember a restart is necessary for the change to take affect. Data link does still not work - so no need to test.

Tanks for checking... With "Easy Comms" Off it works again. So now the most major bug on the KA-50 is the INOP Data link .

Sure.... KA-50_Radio menu bug.trk KA-50_Cau.miz

I do use "easy comms" and have tried both "/" and "ALT+/" (SPU-9 PTT). Makes no difference. Menu entries are white, indicating that I´m on the right frequency. I can f.ex select "2. Wingman", but then an empty comms menu appears from where I cannot get out off with an "Exit" option in the radio menu. Only the radio in use is indicated on the top of where the list of commands should have been shown. Note that I have also tried to un-install, cleanup and re-install the KA-50. 2.5 stable works fine.

[REPORTED]KA-50 Easy comms radio issue New bug in 2.5.2.... Openeing the radio menu and selecting any of the options: 1. Flight. 2. Wingman. 3. ATC etc..... And I get an empty menu, just telling what radio is used at the top. So now I cannot test wether the data link bug has been fixed, cause I cannot issue any command to my flight / wingman.

When I open the radio command with Ralt+/ and select any of the options, I just get to an empty comms menu - so no way I can give my wingman commands. Thois has happend after the DCS 2.5.2 update.

And how aboiut the KA-50 Data link also not working in stable and OB ? It has been reported both via ticket system and in the forum, but no feedback so far !

It doesn’t work in DCS 2.5 stable either. I send a ticket regardong this issue for 2.5.2 OB and recieved an answer that it was beta. I then send a ticket for the same issue with 2.5 stable and got the answer it had been fixed in the beta. So kind of running round in circles

Seems to have been fixed with the 23rd may 2.5.2 update.

Not fixed with 2.5.2 - 23rd may.

Good find. Just wonder what then had to be changed in the .dll file. One problem though... I had 2 x IRMV and 2 x TVMV. Once both IRMV where fired, I still got a frozen IR image on the MFD from the last fired IR-Maverick. I ahd to push some switches and buttond to initialise the TVMV MFD, but cannot remember the sequence to do so - seems like a bug. FinnJ