Bugs report (Noticed on 2.1.1)

[-IRRE-Rolluptito]

Hello there,

 

Here a small list of bugs I have noticed on 2.1.1 version of DCS.

 

1. Rudder trim isn't working (You already know this one)

 

2. Fixed sight isn't working (already corrected for the next update if I'm not wrong)

 

3. Radar antenna elevation is acting weird: with master mode selector in NAV position (so, not weapon dependant) it is acting differently depending on weapon mode selector position.

If I change the elevation with with radar in A1 (PPI) mode and weapon mode selector on RB75 for exemple it changes the radar scan zone from WIDE to NARROW instead of changing the elevation.

I have to go on IR/GUN-POD/or AIR mode on weapon mode selector to be able to change the antenna elevation.

 

Plus, the radar elevation indicator and index (on top of the radar screen) doesn't show except if weapon mode selector is on IR/GUN-POD/or AIR.

 

Finally, this indicator, when it's showing his ass, does not move at all even if I change the antenna elevation (The elevation change is visible with the ground showing differently on the radar screen but not on the indicator).

Is it a normal behavior? It seems way more simple on the manual. :book:

 

 

4.Some commands cannot be binded to controllers (exemple: seat adjustment or weapon mode selector) but only keyboard. Is it wanted by devs?

 

Thank you very much! ;)

 

Rolluptito

[amalahama]

Great idea -IRRE-Rolluptito!!! Trying to make developer's life easier gathering in just one post the community confirmed bugs :)

 

I would add:

 

5. Magnetic deviation knob doesn't visually change when rotated

Edited July 3, 2017 by amalahama

[Home Fries]

Here's a bug report on the new joystick and keyboard lua files (2.1.1 and 1.5.7)

 

The first seven lines under --Lights panel in each lua file need to be removed, as they are conflicting with the new commands.

 

In the keyboard lua file, the lines are 320-326, which read as follows:

{combos = {{key = 'L', reformers = {'LShift'}}}, down = 3001, cockpit_device_id = devices.LIGHTS, value_down = -1.0, name = _('Anti collision lights switch'), category = _('Lights')},
{combos = {{key = 'L', reformers = {'RCtrl'}}}, down = 3002, cockpit_device_id = devices.LIGHTS, value_down = -2.0, name = _('Navigation lights switch'), category = _('Lights')},
{combos = {{key = 'L', reformers = {'LCtrl'}}}, down = 3003, cockpit_device_id = devices.LIGHTS, value_down = -1.0, name = _('Formation lights switch'), category = _('Lights')},
{down = 3001, cockpit_device_id = devices.LIGHTS, value_down = 1.0, name = _('Anti collision lights switch'), category = _('Lights')},
{down = 3002, cockpit_device_id = devices.LIGHTS, value_down = 1.0, name = _('Navigation lights switch'), category = _('Lights')},
{down = 3003, cockpit_device_id = devices.LIGHTS, value_down = 1.0, name = _('Formation lights switch'), category = _('Lights')},
{down = 3004, cockpit_device_id = devices.LIGHTS, value_down = 1.0, name = _('Taxi/landing lights switch'), category = _('Lights')},

 

The lines in the joystick lua are 288-294 (same content).

[RagnarDa]

Rolluptito, thanks for summarizing some current bugs! It actually helps both prioritizing issues and also to know that the issues are still there and wasn't a one-off thing that resolved itself (they rarely do, but you always have hope ;)

 

About the rudder-trim issue: I am unfortunately unable to replicate this. Are you 110% sure you haven't touched the emergency trim controls before? They will block the normal trims use for the remainder of the flight. What I did notice is that I was confused at some point and added a emergency rudder trim, which doesn't seem to exist in the cockpit, it's just the normal rudder trim and the course trim (or whatever it is called) for the autopilot. I've fixed that issue, and will await some way to reproduce the non-usable rudder trim issue.

[-IRRE-Rolluptito]

Thank you for you answer and implication RagnarDa. Yes I'm 200% sure I haven't. I have hundred of flights these days with the beast. :) I have this problem with both 1.5 and 2.6. I checked everything in my configuration, nothing seems wrong and it is working well with every other planes. Weird. :/

[whaaw]

when im flying in 2.1 i got no radar lines (the small black lines indicating the middle and the range) the radar screen is literally blank, except the radar image itself and the horizon indication tested with a cold startup at nellis 2.1

Edited July 10, 2017 by whaaw