Certain modules - A-10C (I and II), Harrier, F-14 and Mirage 2000 - lighting axes don't start until 50% rotation on knobs

[speed-of-heat]

On 10/5/2022 at 3:30 PM, imacken said:

INST PANEL LIGHTS BRT in the Harrier.

 

[Flappie]

Yep, that one is already in my list.

I need the broken ones for F-14 and A-10C I/II because I couldn't find any issues with these planes.

Edited October 23, 2022 by Flappie

[imacken]

28 minutes ago, Flappie said:

Tested with a TM Warthog HOTAS. I recognize the issue affects both M-2000C and AV-8B. Regarding the F-14 and A-10C, I need a hint: what precise light control axis commands are you talking about?

F-14 Pilot

• HSD Brightness: 0-100%
• HUD Brightness: 0-100%
• VDI Screen Brightness: 0-100%
• VDI Screen Contrast: for some reason, only a small part of the screeen changes between 0-50%. The whole screen contrast starts changing in the 50-100% range. Issue or art? I also noticed the constrat is not changed at all in night mode. I'm not sure this is an issue, though.

F-14 RIO

• DDD Brightness: 0-100%
• DDD Erase: 0-100%
• DDD Pulse gain: 0-100%
• DDD Pulse Video: 0-100%
• ECMD Brightness: 0-100%
• TID Brightness: 0-100%
• TID Contrast: 0-100%

A-10C I / II

• Flashlight BRT Control: I could not get the flashlight to lit up.

AV-8B -> affected

• CONSOLE LIGHTS BRT: 50-100%
• EDP BRT CONTROL: 50-100%
• FLOOD LIGHTS BRT CONTROL: 50-100%
• Formation Lights Knob Axis: 50-100%
• HUD BRT CONTROL: 50-100%
• INST PANEL LIGHTS BRT: 50-100%
• VIDEO BRT CONTROL: 50-100%
• VIDEO CONTCONTROL: 50-100%
• WARN/CAUT ANNUNC BRT CONTROL: 0-100%

M-2000C -> affected

• Caution/Advisory Lights Knob: 50-100%
• Console Panel Lights Knob: 50-100%
• Dashboard Panel Lights Knob: 50-100%
• Dashboard U.V. Lights Knob: 50-100%
• HUD Brightness: 50-100%
• PCN Brightness: 50-100%
• Red Flood Lights Knob: 50-100%
• Refuel Lights Brightness Knob: not implemented yet?
• RWR Lights Brightness Control: 50-100%
• White Flood Lights Knob: 50-100%

 

Thanks for that. Sorry, the axis commands for the F-14 and A-10Cs are injected by Quaggles mod, so you won't see them.  Still, they are the same issue as you can see in the Harrier and M2000.

[Flappie]

M-2000C and AV-8B issues reported.

I'll get in touch with Quaggles about the F-14+A-10 bit.

[imacken]

Thanks a lot for this.  I have attached the A-10C and F-14 commands that I use in Quaggles mod.  There you will see the problematic 'Lighting Panel' commands, which behave in the same way as the Harrier and M2000.  (You'll also see some of the commands I put in myself, but it's just lighting commands you should look at.)

I've also attached Quaggles mod that I use.

InputCommands.zip DCS-Input-Command-Injector-Quaggles.zip

[Flappie]

Thank you. I chatted with Quaggles, and I understand what his mod does, now.

But I'm not script-savvy enough to understand what's going on with the F-14 and A-10C. Sorry. The best I can do is wait for RAZBAM to fix their isues, then ask them what's it's about.

[imacken]

Thanks for your help on this!

[imacken]

On 10/24/2022 at 6:23 PM, Flappie said:

Thank you. I chatted with Quaggles, and I understand what his mod does, now.

But I'm not script-savvy enough to understand what's going on with the F-14 and A-10C. Sorry. The best I can do is wait for RAZBAM to fix their isues, then ask them what's it's about.

A few months on with this and no change in Razbam modules or Quaggle's mod. Any news?

[skypickle]

Not to derail this topic, but i think ED has to expose a variable to the user that it presently does not: the center point. Regardless of whether an axis is designated a slider or not, we really do not know how this number is being applied.

We think the reading of a ‘slider’ cranked all the way left is zero and the control assignments window may indicate this, but the control in the jet may still be based on a range where the midpoint of the controller is calculated (the center point) and used as zero. And when you check the slider checkbox, it puts the calculated midpoint as the start position. Another example where this is a feature and not a bug is in the special options for the F5E where there is a selection for the pitch axis to be:

linear

non linear

FFB

 

These choices change the center point of the axis so that the plane flies straight and level with different deflections. So when you fly with the FFB setting, the stick has to be pushed forward for level flight. But you as well as dcs recognize the controller is pushed way forward. We never really know where the center point (zero point) of the jet is until we fly it.

If we knew the zero point, then i would know where to put the stick ahead of time. Similarly if i knew the zero point of these axes that are misbehaving, the bug would be immediately apparent.

[imacken]

I take your point, but I think it's OT for the subject of this thread. Start another one maybe?