Interior lighting control issues/ inconsistencies

[MadKreator]

Other interior lighting issues-
- when you flip on the cockpit light switch, all the normal lights are at full brightness, but all of the knobs are still in the off position 
 

- chartboard key bindings do not work
 

-Chartboard direct input doesn’t work
             - when sending direct inputs to dcs via scripts such as through helios, none of the chartboard axes function ( theres 3 sets of chartboard axis definitions for the  knob, why is there 3?!?

- The remaining 4 cockpit lighting knobs only respond to encoder style inputs ( separate Command definitions for increment and decrement via direct inputs) when in reality they most likely should be standard, single command definitions ie. potentiometer style axes, just like the UV lighting adjustment (glow functions)— more of a nitpick.
 

It’s early access so I’m sure things will work out in the long run. These are minor issues.

- props to the devs for the well labeled and notated cockpit script files though! Love it. 

Edited June 21 by MadKreator

[ac5]

Indeed... Also the mouse wheel does not work when trying to adjust the  lights dimmers 

in the cockpit and gunsight light. (All other airplanes do, WWII or not).

A lot of keyboard Keybinds do not work also. 

Otherwise, amazing work, thank you and congratulations!

[felixx75]

 

[MadKreator]

So far anything that is an axis, knobs levers and all that need to be clicked and held then drag up and down with the mouse. Which is normal in every module but you can also use the mouse wheel. Mouse wheel control is non-existent in the F4u. I will be using my Helios profile to control these things BUT I think mouse wheel movement is very important for these types of controls when interacting with the in-game cockpit…. Not that my opinion makes any difference
-side note in the cockpit scripts.. the keyboard commands have different command ID’s then the Direct input does. It’s very odd that they don’t use the same definitions. Of course I’m not a programmer but every other module only has one set of device commands per control. Not sure why there is different sets for every control. No complaints if it works, just a totally different approach than other modules.

Edited June 21 by MadKreator