Frank Murphy

You did not get the point [emoji4] It is just you said the Ka-50 cannot be equipped with S-13T then you say you performed some tests using S-13T, that's all [emoji6]

No contradiction here ? [emoji6]

I have trained to some sling load on Ka-50 after a long time not practicing. However I could figure out the indicator which shows the location of the cargo to hook and how the cable is stretched (or some data related to altitude if I can remember well) does not work anymore in 2.5 (nothing moves on it). Same issue for anyone ? Thanks

I confirm the fix passes IC.

Hi Nicolas, Thanks a lot [emoji4] I am gonna try that fix asap. I was performing some tests during a night flight tonight and it seems to me the lights were kind of weird...

So if you are perfectly happy, I am so happy too [emoji4]

I did not say anything else... It is up to you if you prefer not to be able to perform night missions just because ED do not care anymore about making the module evolve to the existing night version (I do not ask for a Ka-52) [emoji846]

Hi, Depending on time, HMS may be automatically replaced by NVG as helmet feature. You still have the choice to choose one or another by asking the ground crew. As for the Skhval, as said before it is a day optic sight. There have already been many discussions about that point but it seems ED will not offer a Ka-50 N (or Sh in Russian) version. I use a mod kindly developed by a user which increases the maximum contrast (as far as I remember) of the Skhval. It allows to get a kind of FLIR view and it is quite efficient (when you can manage to lock the target...).

I have found what was wrong. I just had to correct the path of campaign files (.cmp) in "logbook.lua" because I had an extra "EN" sub directory that does not exist anymore in 2.5 path (only the SA342 campaign path did not change for me). I just deleted that directory in the path in each "campaign" node and all went right. I can now correctly see the achieved, in-progress and not-yet-started campaign in 2.5 GUI and go on from my 1.5 status for each campaign.

Same here. Copied logbook.lua from 1.5 to 2.5 and all my Ka-50 campaigns in progress are now set to inactive. But strangely the only SA342 campaign is in active status and progression has been kept.

Thanks a lot Nero :-) I will test asap.

Hi Nero, I do not know how to make it clearer than Arkroyale048 did... But let's try again :-) When Shkval is caged, the upper part of the HUD shows a heading indicator (as shown in red on Arkroyale048's screenshot). When Shkval is uncaged, that indicator is replaced by another one centered on 0 degree with 30 degrees left and right (I guess but not sure). Would it be possible to get the heading indicator still be displayed when Shkval is uncaged ? I do hope the explanation is crystal clear that time :-)

+1 It would be useful when a wingman has spotted a target and tells you its heading (instead of having to use HSI). Thanks !

Same behaviour for me

Do you mean you are still running the good old standalone BS 1.0.0 ? Nice :) I can only give you configuration tips about DCS World (I have updated to 1.5.5 last night). I have created a "Ka-50.lua" file in "[DCS Home Directory]\Config\MonitorSetup" and selected it in "Options - System - Screens" in DCS menus (or something like that, I have a French GUI). You have to select max resolution proposed by DCS GUI in "Options - System - Resolution" (choose the line before the last line because the last one cause some display issue). Your configuration file should content those lines : Viewports = { Center = { x = 0; y = 0; width = 2560; height = 1440; viewDx = 0; viewDy = 0; aspect = 1,777777777777778; } } Shkval = { x = 2560; y = 0; width = 640; height = 1024; } ABRIS = { x = 3200; y = 0; width = 640; height = 1024; } There will probably have some adjustments to do but it should be a good basis.

Please tell us on which monitor you want to display main view on one hand and Shkval + ABRIS on the other hand (with correct resolution of each monitor).

Hi, I think you mistook between left and right monitor resolution when I read your config file (height 768 is your right monitor as you specified). If you just switched monitor resolutions, your ABRIS x coordinate should be 512.

Hi, I have used LED switching yesterday but not directly with script, GUI only (and I have not checked out the generated script). But I can see that you use PULSE action in your script whereas LEDs only work with PRESS (switch on) and RELEASE (switch off) actions. Hope it helps