BS2 1.2.x bugs and glitches thread (not CTD/BSOD)

I've had trouble getting my LWS reset button to work since latest update. Anyone else?

Works OK on my end. Just flew an hour-long mission and no problems.

Thanks msalama,

I'll look into it further. I note I had trouble using all methods of operation of the button and I get the same results. I don't do much combat lately to see the results there.

If I do the LWS test procedure, the button will not shut off the lights after the test. I have to toggle the LWS power to get them to turn off.

I have to toggle the LWS power to get them to turn off.

That's weird because it works 100% correct here, tests and all. Are all your LUA scripts original and unmodded?

Thanks. It was a Helios binding issue. The Helios binding pushes the button, but it does not work. I used the same button in Options after deleting the Helios binding to fix the problem.

No, actually I found this to be caused by toggling my mouse cursor in DCS. If I hide the mouse, the button does not work. If I enable the cursor, the button works. Odd.

I cannot say from which version it start, but the Collective brake stopped working correctly for little adjustment in height (below 100m, as stated in the manual).

In other words it not bypass the collective dumper (20% Authority) any more, forcing me to overcome the dumper authority before obtain any variation in height.

The height assign function have no problem btw.

- Fuel gauge needle frozen when fuel switch is off

As mentioned previously in this thread, and as odd as it seems, this is normal behavior and not a bug.

Alpha, weird or not, i was thinking about it yesterday. and Then you came, confirming my thoughts. :)

It's somehow a poor feature, fuel stealers love that, don't they ? hehe !

Flanker, no, i do not forgot you. Need some investigations first.

- Zebra light missing when rotor RPM set to Low (RAlt Numkey Minus(-) ) as described last line page 10-11. - Active v7570(JG14_Smil)

The "zebra" light for low rotor RPM starts flashing at 83% rotor RPM. Some parts of the manual say that the light should flash at 83% while other parts of the manual say that it should flash at 85%. When the Free Turbine switch is placed in the "Low" position, the rotor RPM decreases to 84%.

Whether the game is wrong or the manual is wrong, I do not know. Either way, I would rate the chances of a fix to be very near zero, but I'll submit it anyway.

Not sure if it's new but with 10201 the IFF switch no longer moves. I hear a click when pressing LAlt-LShift-I but the switch doesn't move.

When pressing LAlt-LShift-LCtrl-I the IFF switch cover does open/close though.

No, actually I found this to be caused by toggling my mouse cursor in DCS. If I hide the mouse, the button does not work. If I enable the cursor, the button works. Odd.

I've had the same problem, although with the mouse cursor visible. I think it generally clears if I press the button several times though.

yes, same here. It is an odd one.

You do know we are wasting our time by finding bugs that will never be fixed. I haven't noticed the IFF switch. There is no real need to switch it.

yes, same here. It is an odd one.

 

You do know we are wasting our time by finding bugs that will never be fixed. I haven't noticed the IFF switch. There is no real need to switch it.

Yeah, even the mouse view not working after exiting Briefing with either of the buttons hasn't been fixed yet and that's a major deal as it pretty much forces you to abort the mission.

Are you sure there's no need to switch the IFF? It seems strange they'd assign a keyboard shortcut for it if so.

The illumination knob on PVI800 does not work but the knob for general lights on the back panel do modifies the PVI800 lightning power and, ofcourse, not for all the lights as it suppose to do.

The SAI is a bit unreliable accumulating very fast errors that renders it useless, especially if it is a backup and should be available anytime... is it OK to be like this?

- IFF on black shark is not implemented. And will not be in near future

Link

So, don't worry about this glitch.

Anyway, the switch still works for me.

- Zaelu is right. the general light does modify PVI800 illumination. Imho, this is a minor glitch too.

- SAI accumulates errors very fast. I saw that from the beginning, that would be great if someone confirm this thing, because, i must admit i rely on it only first minute of flight.

- Zebra Light : Roger that Alpha.

- Still has no mouse problem doveman :huh: (and i won't complain)

- IFF on black shark is not implemented. And will not be in near future

Link

 

So, don't worry about this glitch.

Anyway, the switch still works for me.

 

- Still has no mouse problem doveman :huh: (and i won't complain)

Hmm, strange as JG14_Smil confirmed it. So if you're in mission, press Esc, click on Briefing and then click either the Back or Fly buttons, you can still toggle between mouse cockpit and mouse view with Alt+C? For me, I still have the mouse cursor to click on switches but when toggling to mouse view, it no longer works. Only if I exit from the briefing by pressing ESC is it OK.

I didn't realise that IFF wasn't even implemented. Strange that they bothered to make the switch moveable and assign a keyboard shortcut in that case! The switch works for me if I click on it, just doesn't move when I use the keyboard shortcut but hey ho :)

You're right, i'm just clicking it too, only for the fun :)

Anyway, unlike Falcon 4 which had a IFF recognizer or something (EtherealN explained it well elsewhere), in DCS we have the F10 fog of war. (which is absoluteley too powerful and unreal imo)

About your mouse problem, i tried briefing, esc, alt-c, fly, in every combinations, everything possible. my cursor is always here when i'm calling it.

I have really no clue how to help you right now.

Don't get me wrong, i do not wish this bug on our machines, but if no-one (maybe JG now) has it, how could ED resolve it ? that's the main problem.

About your mouse problem, i tried briefing, esc, alt-c, fly, in every combinations, everything possible. my cursor is always here when i'm calling it.

I have really no clue how to help you right now.

Don't get me wrong, i do not wish this bug on our machines, but if no-one (maybe JG now) has it, how could ED resolve it ? that's the main problem.

OK, thanks for testing. Seems it only affects some people then.

Doveman, I may add one thing :

I play in Windowed Maximized (1 screen out of 2)

Auto Disable Aero

The only thing i have, is when i'm in view mode (mouse controlling view) if i press briefing, then back or fly, my mouse turn back in view mode (invisible) but i can't look around. View mode is stuck. Alt-C call my mouse back on screen though. The only solution to resolve this is to call briefing without view mode activated. (mouse already visible)

Maybe it will help you.

Otherwise, i use TrackIR, and taking a look at the briefing while flying, is a thing a rarely do.

Doveman, I may add one thing :

 

I play in Windowed Maximized (1 screen out of 2)

Auto Disable Aero

The only thing i have, is when i'm in view mode (mouse controlling view) if i press briefing, then back or fly, my mouse turn back in view mode (invisible) but i can't look around. View mode is stuck. Alt-C call my mouse back on screen though. The only solution to resolve this is to call briefing without view mode activated. (mouse already visible)

 

Maybe it will help you.

 

Otherwise, i use TrackIR, and taking a look at the briefing while flying, is a thing a rarely do.

Ah thanks, so maybe the bug is universal and the mouse view mode doesn't work after entering Briefing with it active and then exiting Briefing with either Back or Fly. I didn't note whether I was in mouse view when testing but I'll check.

So we only have to remember never to open Briefing with mouse view mode active and not to close Briefing with either of the buttons. :music_whistling:

Hopefully this is something that can be fixed then.

I use Full Screen mode and don't disable Aero.

Hmmm. Once again, it seems like 1.2.4 doesn't really care about our dear ka50. The change log for blackshark is extremely quick to go through with nothing mentionned in the bug list. Always makes me sad eventhough I should be used to by now. Granted the 1.2.4 was in the tester's pipe before this thread was really noticed. I have some hopes though about carrier operations since the take off from ramp bug was mentionned in the DCS world part. Also mentionned is the choppers (AI) sinking on carriers. So maybe it will have an indirect impact on the drifting bug?

You can add "Doppler NAV System not repairable".

I still find the format with all the colors and nomenclature quite confusing.

And cut-off levers are not working as expected when sending value 0 and 1 to the Engine Interface, as described below. (posted as ED support ticket, so they are probably aware - will post if I get any news on the subject)

Problem description:

When sending value 0.0 or 1.0 to Engine Interface (cockpit_device_id = 4) to switch 3009 or 3010 (left or right engine cut-off valve) the switch will changes state regardless of current state.

 

Expected behavior would be that sending value 0.0 always rendered the 3010 in either down or up position and vice versa for sending value 1.0.

 

Example code for controller setup (located in: "...\Saved Games\DCS\Config\Input\ka-50\joystick\Joystick....lua"):

{combos = {{key = "JOY_BTN18"}, }, down = 3009, up = 3009, cockpit_device_id = 4, value_down = 0.0, value_up = 1.0, name = "Cut-off-valve left", category = "Engine Interface"},
{combos = {{key = "JOY_BTN19"}, }, down = 3010, up = 3010, cockpit_device_id = 4, value_down = 0.0, value_up = 1.0, name = "Cut-off-valve right", category = "Engine Interface"},

 

Thanks to MadCat for pointing out this issue.

Another finding regarding this problem.

 

When adding these lines:

{down = 3009, cockpit_device_id = 4, value_down = 0.0, name = "Cut-Off Valve Left Engine Close", category = "Ins Engines start-up control panel and levers"},

{down = 3009, cockpit_device_id = 4, value_down = 1.0, name = "Cut-Off Valve Left Engine Open", category = "Ins Engines start-up control panel and levers"},

 

and same for the right valve with "3010".

 

With 4 seperate buttons set for those new commands, I found some interesting things.

 

First off, I can now move BOTH levers at the very same time with the Warthog's top 2 toggle switches, together with using TARGET.

Previously always one valve didn't move, as if there was a delay from Warthog->TARGET->game, and only one of the 2 commands got recognized when flipping them simultaniously.

Like that a lot !!!

 

But now to the interesting finding:

The original purpose of seperate commands for valve open and closed still doesn't work, it moves both ways with the same command.

 

BUT:

when I manually get the lever "out of sync" with the mouse, say the lever is in the open position, with the mouse I move it to the close position, all is fine.

If I then place the switch on the throttle in the down position and thereby send the command to close the valve, as said, it moves up again in the open position.

However the clickable box for the mouse doesn't move with the lever, instead it is set/remains at the closed position.

 

So the clickable box to actuate the lever with the mouse actually does move according to the seperately set commands for open and closed valve positions.

The visual model and the actual function of said valves however, does not.

 

Just found it and thought to share this, sorry for the rather long post :music_whistling:.

 

MadCat

1.2.4 and so it goes...

Another update, another BS system lost. I am probably the only one that even cares about this one :)

ABRIS\GNSS menu, CALC no longer accepts Airport codes. I know this worked in 1.2.3. I was in a MP mission, so I'll look further into this and see if it works in SP. Hopefully, this is just a matter of getting pointed back to another lua file that has the GNSS data.

While the routine for the CALC ran in the past, I doubt it even did anything as ABRIS location has been porked since earlier updates.

I love BS, but after paying for it three times, I really miss each feature we lose! I just cannot see paying any more money to ED until something is done about bug fixes. Fix the bugs and I'll buy every single thing ED makes.