NightMan

I have just tested version 2.8.1.34437, and this hasn't yet been corrected. But that's OK, as it was reported just this week.

I have just tested version 2.8.1.34437, and this hasn't yet been corrected.

There are too many incongruences. For example: There are: - "Gyro/Mag/Manual heading - down"; - "Gyro/Mag/Manual heading - up". Ok, that's bearable. But there are: - "UV-26 Change dispensing board - next"; - "UV-26 Change dispensing board - prev"; - "UV-26 Change dispensing board - LEFT"; - "UV-26 Change dispensing board - BOTH"; - "UV-26 Change dispensing board - RIGHT". Please; standardize things. Either: - ALWAYS use "next/prev" and "up/down", as in the Gyro/Mag new method; - ALWAYS use "next/prev" and "up/down" combined with all the other possible settings, as in the "UV-26 Change dispensing board..." method. Mixing methods becomes VERY confusing and difficult to setup.

There are too many incongruences. For example: There are: - "Gyro/Mag/Manual heading - down"; - "Gyro/Mag/Manual heading - up". Ok, that's bearable. But there are: - "UV-26 Change dispensing board - next"; - "UV-26 Change dispensing board - prev"; - "UV-26 Change dispensing board - LEFT"; - "UV-26 Change dispensing board - BOTH"; - "UV-26 Change dispensing board - RIGHT". Please; standardize things. Either: - ALWAYS use "next/prev" and "up/down", as in the Gyro/Mag new method; - ALWAYS use "next/prev" and "up/down" combined with all the other possible settings, as in the "UV-26 Change dispensing board..." method. Mixing methods becomes VERY confusing and difficult to setup.

I have just tested version 2.8.1.34437, and this hasn't yet been corrected.

I have just tested version 2.8.1.34437, and this hasn't yet been addressed.

I have just tested version 2.8.1.34437, and this hasn't yet been addressed.

I have just tested version 2.8.1.34437, and this hasn't yet been corrected.

I have just tested version 2.8.1.34437, and this hasn't yet been corrected.

I have just tested version 2.8.1.34437, and this hasn't yet been corrected.

I have just tested version 2.8.1.34437, and this hasn't yet been corrected. Instead ED changed the existing control to cycle forward/up/next and added another control to cycle in the opposite way. This is a good enough solution, but not ideal: 1 - it requires dozes of controls to be remapped; 2 - either do it for all the cyclable controls or for none of them, and simply restore the previous behaviour --- standardization is always the best way. And, once again, there is nothing about it in the ChangeLog: https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/

I have just tested version 2.8.1.34437, and this hasn't yet been corrected.

I have just tested version 2.8.1.34437, and this hasn't yet been corrected.

I have just tested version 2.8.1.34437. It appears this has been corrected, but, once again, there is nothing about it in the ChangeLog: https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/

As you say, "...to the very end of the shutdown procedure.". I like to just fly and use the aircraft for other than just kill tanks. So I landed, shut everything down and went for a snack. When I came back the flashlight wasn't working, although I knew I had turned it on. So I tried to start the systems in the dark using keyboard controls, and when I turned the battery on the flashlight came on also. That's how I found out.

Very well; The version is 2.8.0.33006. And the track goes here. I changed the title of the track to "Confirmed bug..." because I replayed it and it confirms what I say. Confirmed bug - A-10C II - Flashlight only works when battery is on.trk

Like the title says, in the A-10C/C II the flashlight only works when the battery (aircraft battery) is on. As far as I know, flashlights use AA or AAA batteries and don't depend from the aircraft's batteries. Is this behaviour correct or is it a bug?

I have an idea; how about giving some credits, or extra miles as ED calls it, for each valid bug or problem a member reports?

For me it is working exactly the same. I have it assigned to MOUSE_BTN3.

The problem is transversal to all models.

Make sure you redefine it for each aircraft. There is a global control and one for each aircraft. These take precedence over the global one. It worked for me.

The light changes suddenly, going from shadow to lit and back to shadow, as if God is flipping a switch on the wall. It's very annoying. It is most noticeable when we are looking down into the switches, because it appears something has exploded nearby and the cockpit is being lit by the flash. It is somewhat disruptive. Transition should be progressive.

The light changes suddenly, going from shadow to lit and back to shadow, as if God is flipping a switch on the wall. It's very annoying. It is most noticeable when we are looking down into the switches, because it appears something has exploded nearby and we are seing the flash. It is somewhat disruptive.

Like the title says, it appears the front right panel is open, as if for ventilation, like those old car windows. See the screenshots.

It doesn't look like you destroyed anything. There should be a KILL event.