Light presets angledirectional and doubledirectional: work only with 0º or 180º headings

Version: 1.6.7

Frequency: Consistently

Severity: High

Marketplace package name:

Context: VASI/PAPI lights project developed in C++

Bug description:
When using light presets, light types Angle directional and Double-Angled directional work only at 0º and 180º headings with a tolerance of ±25º. Outside of these headings, lights are not displayed.

These type of lights are relevant and are used when creating PAI/VASI lights or lights with a particular beam angle. This bug restricts their use on runways oriented at 0º or 180º, making them impractical for any development project.

I understand these type of lights are a work in progress, according the documentation, but would like to hear the opinion of the developers on this.

Repro steps:

  1. Create a Light row along a runway surface with a heading of aprox. 180º
  2. Create a light preset usign the following parameters:
    Relative position: 0,1,0
    Direction (Y/Z/X): 0, 0, 1
    Direction2 (Z/X/Y): 0, 1, -0.1
    Llight is directed along the X-axis at a 9º angle over the horizontal. The cutoff plane normal is determined by the vector XY on Direction2 (1, -0.1).
  3. Assign the new light preset to the light row type.
  4. Light beam works correctly from 9º and above.
  5. Rotate light row to a heading of 90 or 270º. Light beam is active even with angles below 9º.

Attachments:

Private attachments:

Hello,

I logged the issue in our backlog.
I will keep you updated when I have some news to share.

Regards,
Boris

Hello @veroroutes ,

This is fixed in SU6 flighting version 1.8.5.0.
Can you confirm ?

1 Like

SU 1.8.5.0 resolve the light presets angledirectional and doubledirectional issue in MSFS2024. Thank you!

Small issue I have detected. When saving the changes on scenery editor, the angledirectional vector ‘Direction’ overwrites any value entered on Z axis (second element), with a value of 0.2 regardless of the value initially entered.

This topic has been automatically closed after 60 days of inactivity since it was marked as fixed.

If there is important new information about this same report, you can use the “Request reopen” button below to ask the moderation team to review it again.
For other issues or broader discussion, please open a new topic in the appropriate category.