fixed Gunsight Target Distance does not work at all (both variants)

[virgo47]

After 2.9 update, the Gunsight Target Distance does not work - which is quite a serious usability problem as it affects a lot of weapon delivery procedures. I'm sure it is one of the 2.9 updates, as I tried the module and its training missions quite recently and it was working fine.

It's not possible to move it with an axis, nor with buttons. Both the axis and buttons are responsive in the Controls setting.

Can anyone else confirm it? (Just in case it's some upgrade+random mod problem, although I don't believe I have any mods that could affect this.)

Edited October 30, 2023 by virgo47

[Vlad_Mig]

Confirm

[Art-J]

Ditto, unfortunately.

[hsth]

Confirm, stable version still works fine.

[Flappie]

On 10/30/2023 at 11:16 PM, virgo47 said:

It's not possible to move it with an axis, nor with buttons. Both the axis and buttons are responsive in the Controls setting.

I can move it with an axis, not with buttons. Can you please recheck the axis? What are your joystick and throttle model?

 

Buttons are now reported.

Edited November 1, 2023 by Flappie

[Vlad_Mig]

The gunsight is moving, but the distance bar under it doesn't move

[virgo47]

38 minutes ago, Vlad_Mig said:

The gunsight is moving, but the distance bar under it doesn't move

That's the reason why I thought it didn't work at all... not only the distance bar, but the twisty element on the throttle doesn't move either - that's where I was checking, not the HUD.

2 hours ago, Flappie said:

I can move it with an axis, not with buttons. Can you please recheck the axis? What are your joystick and throttle model?

Buttons are now reported.

Thanks, Flappie, always nice to hear from you. So to summarize:

• buttons don't work at all
• the axis seems to work on the HUD, so hopefully, it works properly in the action while in gyro mode, etc.
• graphics element in the cockpit don't work - that is the twist on the throttle and the distance wheel indicator on the gunsight.

[Flappie]

17 minutes ago, virgo47 said:

graphics element in the cockpit don't work - that is the twist on the throttle and the distance wheel indicator on the gunsight.

I guess that is the distance bar, right?

And what is the twist on the throttle you're talking about? Can you post a screenshot, please?

[virgo47]

50 minutes ago, Flappie said:

And what is the twist on the throttle you're talking about? Can you post a screenshot, please?

From the L-39 manual - element 1:

The whole handle was turning previously, because that is the actual control - the distance bar on the sight is only an indicator. Both turned previously.

Edited November 1, 2023 by virgo47

[Art-J]

^ Yes, the grip should rotate like on P-51D, P-47D, F-86, MiG-15, MiG-21... They all share the same manual ranging method.

[Flappie]

I've just reported the missing cockpit animations (throttle and wheel). Thank you all.

[hsth]

Temp solution, at least it worked for me:

copy ..\Eagle Dynamics\DCS World\Mods\aircraft\L-39C\Cockpit

to ..\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\L-39C\Cockpit

I did not bother finding out what specific file(s) cause this problem. Just copied the directory.

[MartinKrq]

In Mods\aircraft\L-39C\Cockpit\clickabledata.lua add the following row in the "if not ASP_disabled then" block that starts at row 543 (Atleast in latest openbeta). The last four numbers are not correct (just copied from the mirror depression) but seems to work anyway.

elements["pnt_107"] 					= default_axis			 (_("ASP-3NMU Gunsight Target Distance")						   ,devices.ASP_3NM, device_commands.Button_2 , 107, 0.0, 0.1  , true, false, false, {135,45}, {135,10})

Edit: So it looks like this on my machine after the edit with version 2.9.2.49940

Edited January 5, 2024 by MartinKrq
Clarifications

[Vlad_Mig]

Thanks, just added the string and everything works again!

elements["pnt_107"] 					= default_axis			 (_("ASP-3NMU Gunsight Target Distance")						   ,devices.ASP_3NM, device_commands.Button_2 , 107, 0.0, 0.1  , true, false, false, {135,45}, {135,10})

[bwRavencl]

The bug is still present in 2.9.3.51704 - ED please fix.

[paco2002]

On 4/5/2024 at 11:49 PM, bwRavencl said:

The bug is still present in 2.9.3.51704 - ED please fix.

There are major 3D bugs reported from December 2020 and still not addressed, so I wouldn't bother on asking for a fix. It isn't going to come

 

[virgo47]

36 minutes ago, paco2002 said:

There are major 3D bugs reported from December 2020 and still not addressed, so I wouldn't bother on asking for a fix. It isn't going to come

I'd rather have this fixed than those other 3D errors, because this gives me feedback for the setting. If it can be fixed by some LUA adjustment as suggested above (I haven't tried it myself) then I don't understand the reason for waiting unless there is 0 people working for ED who understand this module.

In any case, any kind of bugs accumulating in any module over time are really sad.

Edited April 8, 2024 by virgo47

[yaping8816]

I just found this bug

[cuervo111]

I came here to report this bug, it's still there....

And that the fix above still works. Thanks @MartinKrq

Edited August 29, 2024 by cuervo111

[Flappie]

I've just bumped the internal report.

[Draken401]

It's really sad that such a simple issue is not fixed in 10 months.

[Morpheus]

On 9/8/2024 at 9:14 AM, Draken401 said:

It's really sad that such a simple issue is not fixed in 10 months.

And what say about this one  ........ 

 

[virgo47]

42 minutes ago, Morpheus said:

And what say about this one  ........ 

 

These are all sad graphical bugs, the "long hand" definitely affects the gameplay as well if you go for that immersion. I'd like to see them fixed as it really looks ugly when you look around. But this "new" one is a sad regression that takes away some feedback from us. Perhaps not the twisty grip, but the distance scale does.

If we "integrated" the bugs over time, even if their weight (severity) was low, it would be an immense value of bugginess for sure. And, L-39 is not even the worst module.

But I really don't understand why it's fixable by a simple LUA change, yet we can't get it to the release. What is ED afraid of, that doing something will make the module worse than doing nothing? Because that would be a terrible message about the fragility/code quality.

Edited September 17, 2024 by virgo47

[Fawaz_Q8]

bump

[johnysed]

Hey, bumping this.