Are these bugs or is there something wrong with my install?

[Rangoon]

I realize with something this complex, things are going to inadvertently get derailed during updates, even though the actual Black Shark aircraft simulation is several years old, but I'm wondering if these are bugs or if something has gone wrong with my installation.

 

1. Cockpit switches are broken, keybinds reset themselves, disappear, etc. For example (and there are several), the back panel lighting switch doesn't work regardless of what you set in the keybindings. No keypress will activate it, only a left mouse click. This is the same for the IFF switch. Cover works fine, but not the switch. Sometimes I can get a function to work by assigning it a non-default keybind, but other times not.

 

2. Cockpit lighting brightness/PVI panel brightness. The PVI brightness knob doesn't do anything, and the cockpit panel light only affects the PVI panel (not the cockpit lights).

 

3. Comms seem to break if you interrupt someone (or maybe change channel?). For example, if you speak to the ground crew, and then change the channel (or maybe ask them again...need to retest this as it's happened various times/situations/ATC/ground crew) then you will never hear from them again. I have My intercom on, channel set to ground crew, and I can see them doing things (ground power on/off), but they don't speak to me. I even tried this with the cockpit door open, so that no radio/intercom problems could be interfering.

 

4. ATC at Mozdok clears me to runway 09 even though the winds are 270ish at 2 m/s (both what ATC said and what PVI says). I realize that is a very light wind, but wonder if Mozdok would put me on 27 evne if the wind was 270 at 10m/s?

 

5. Hover check is unavailable from ATC after requesting taxi to runway even though the manual references more than once that you request taxi, taxi, then request hover check, hover check, then request takeoff, takeoff.

 

6. Changing the inverter switch doesn't affect the light (contrary to manual).

 

7. During hydraulic system test, turning off main hydraulic system power illuminates the back panel lights but no EKRAN message appears (contrary to manual).

 

8. When checking the fire extinguishing system, lights on the wall panel function, but there is no fire light on the forward panel (that light functions fine in a lamp test) (contrary to manual).

 

9. When performing a Rotor RPM readjustment check, the RPM changes but the zebra light doesn't flash (contrary to manual).

 

10. When performing an EEG GG test, the warning lights illuminate, but no voice messages are heard (contrary to manual).

 

So is my DCS install borked? Just some bugs that need to be reported and/or worked out? Or am I doing something wrong here?

[msalama]

The last I flew the Shark several months ago (more of a Huey man myself nowadays) at least points #6, #7, #8, #10 still worked OK IIRC. But I don't have the foggiest about how it is now - or whether you've done something wrong - since I'm not really current in the Ka-50 anymore. :helpsmilie:

 

But that was how it was last August(ish) or so anyway.

[King_Hrothgar]

I can't comment on the test functions as I never bother with those but can comment on the other parts.

 

1) The key assignments thing sounds an awful lot like the file is set to read only and thus any changes you make in game are not actually saved. Find the file and check its attributes. If set to read only, set it to read and write for all users. If that doesn't work, you may need to simply use mouse clicks. Honestly I've never tried assigning the cold start functions to keys. I've always clicked them. So this may not be new or limited to you.

 

2) The brightness knobs for the instruments and panels never worked. I don't know why as other planes have them working, but in the Ka-50 they've never done anything as far as I know. All switches and instruments are lit, but there are a few switches to get them all.

 

3, 4 and 5) Helicopter pilots do not care what ATC thinks. They are not worthy to speak to us. As for the interruption thing, don't interrupt the AI. It's like that with all the planes and the AI loves to spam comms.

[Rangoon]

1) The key assignments thing sounds an awful lot like the file is set to read only and thus any changes you make in game are not actually saved. Find the file and check its attributes. If set to read only, set it to read and write for all users. If that doesn't work, you may need to simply use mouse clicks. Honestly I've never tried assigning the cold start functions to keys. I've always clicked them. So this may not be new or limited to you.

 

I found "Keyboard.diff.lua" in G:\Users\*\Saved Games\DCS\Config\Input\ka-50\keyboard, and its properties were not Read Only. If that's the correct file, then something else is going on unfortunately.

 

Of course it can be argued that I shouldn't care too much about some of this, but the whole spirit of DCS is the study sim. The high level of systems detail is everpresent throughout the documentation and the aircraft at the very least, and something which clearly ED takes pride in, so when things don't work, especially this many years after release, it's either overburden/complacency on ED's part, unintended consequences from other updates which haven't been noticed, or else my install is uniquely messed up. What's happening with the keybinds seems really fishy.

[Yurgon]

Note, my knowledge of the Ka-50 startup and its systems mostly comes from the

video(s), so I can only comment on what the manual says where I specifically looked stuff up to answer your questions.

 

4. ATC at Mozdok clears me to runway 09 even though the winds are 270ish at 2 m/s (both what ATC said and what PVI says). I realize that is a very light wind, but wonder if Mozdok would put me on 27 evne if the wind was 270 at 10m/s?

 

I've observed this kind of behavior on some airports. My guess is that they're programmed to only allow take-offs and landings in one direction. Some runways only show skid marks on one end, though Mozdok isn't one of them.

 

5. Hover check is unavailable from ATC after requesting taxi to runway even though the manual references more than once that you request taxi, taxi, then request hover check, hover check, then request takeoff, takeoff.

 

AFAIK it's always been like that. The DCS ATC is rudimentary at best.

 

Some time ago, a major ATC overhaul was announced but then got pushed back and I haven't heard an update on the issue in a long time.

 

8. When checking the fire extinguishing system, lights on the wall panel function, but there is no fire light on the forward panel (that light functions fine in a lamp test) (contrary to manual).

 

I can't confirm that, it works for me, always has. For each of the 3 groups, I get a flashing FIRE indication on the forward panel.

 

Do you keep holding the "fire warning sensors BIT" buttons down for the duration of the test?

 

9. When performing a Rotor RPM readjustment check, the RPM changes but the zebra light doesn't flash (contrary to manual).

 

I think it's always been like that, and IIRC the Leading Edge Training video also mentions that the zebra light may come on, but doesn't necessarily do so.

 

10. When performing an EEG GG test, the warning lights illuminate, but no voice messages are heard (contrary to manual).

 

Where does the manual say there should be a voice message for the GG test?

 

So is my DCS install borked? Just some bugs that need to be reported and/or worked out? Or am I doing something wrong here?

 

I think you're doing just fine. This looks to be the way Black Shark has worked ever since 1.0.1. I don't think ED is going to fix any Black Shark-specific problems, however we'll hopefully see ATC improvements in the future.

[Rangoon]

Do you keep holding the "fire warning sensors BIT" buttons down for the duration of the test?

 

Yurgon, you are right about the Fire Extinguishing System check. I wasn't holding down the button, and indeed now when I do the Fire light illuminates. Thanks!

 

Where does the manual say there should be a voice message for the GG test?

 

On page 9-15 it says "Slowly move the throttle levers from the IDLE position until the “n ст ПРЕД ЛЕВ ДВИГ” (LEFT ENG PT OVRSPD) and “n ст ПРЕД ПРАВ ДВИГ” (RIGHT ENG PT OVRSPD) lights illuminate. This should occur at rotor RPM around 86%. Simultaneously, a “Раскрутка турбины левого двигателя” (Left engine power turbine over-speed) and “Раскрутка турбины правого двигателя” (Right engine power turbine over-speed) voice message will be heard."

[Fakum]

Just throwing this in the mix,,,

 

http://forums.eagle.ru/showthread.php?t=138575

[Yurgon]

On page 9-15 it says "Slowly move the throttle levers from the IDLE position until the “n ст ПРЕД ЛЕВ ДВИГ” (LEFT ENG PT OVRSPD) and “n ст ПРЕД ПРАВ ДВИГ” (RIGHT ENG PT OVRSPD) lights illuminate. This should occur at rotor RPM around 86%. Simultaneously, a “Раскрутка турбины левого двигателя” (Left engine power turbine over-speed) and “Раскрутка турбины правого двигателя” (Right engine power turbine over-speed) voice message will be heard."

 

This works fine in my installation.

 

You previously talked about the Gas Generator test, however the above quote is from the Power Turbine test. If you mix these two, I imagine the results will be something unexpected. :smartass:

 

AFAIK the Gas Generator test shouldn't result in a voice message, but the Power Turbine test definitely should ("Left Engine Turbine Overspeed, Right Engine Turbine Overspeed" or the other way around, depending on which throttle you raise).

 

Again, I recommend the Leading Edge Training video, it shows the practical application of these tests and I think it will clarify things for you.

 

As far as I can tell, there's nothing wrong with the tests and nothing wrong with your installation, either, it just sounds like a little mix-up. :)

[ShuRugal]

I can't comment on most of your problems, but one I have noticed within the last few months (not sure when it cropped up) is that rotor RPM decreases with airspeed increase, even if the rotor is completely unloaded. If i start from sufficiently high altitude and dive at a steep angle with 0 collective, the rotor RPM will drop down as low as 70%.