Light index=0 omitted is not longer treated as index=0 for ported fs-2020 aircraft

[MariopilotPD808]

Version: 1.6.34.0

Frequency: Consistently

Severity: High
Marketplace package name: mnd-aircraft-fn333

Context: in flight

Similar MSFS 2020 issue: none

Bug description:

In FS-2020 systems.cfg [LIGHTS], when a lightdef.N does not include index=0, the default behaviour is that of index=0

When a FS-2020 package is loaded into FS-2024, the absence of index=0 links the lightdef.N to the last available index=N for that light type.

Repro steps:

Can be observed on mnd-aicraft-fn333:

The tail navigation light is connected to index=2. This circuit is “blinked” via model behaviours.

The wing navigation lights do not have “index=0”. They now blink as if “Index=2” was applied

adding Index=1 (their correct circuit) restores correct behaviour. also will work if index=0 is added instead.

Other light .fx will not display unless index=0 is added (example: beacon).

(Note: some .fx do not work anyway. This is not due to this bug.

[Boris]

Hello @MariopilotPD808,

@MariopilotPD808

The tail navigation light is connected to index=2. This circuit is “blinked” via model behaviours.

The wing navigation lights do not have “index=0”. They now blink as if “Index=2” was applied

Could you post a short video showing the exact wing navigation light you’re referring to?

In 1.6.34.0 (SU4) I don’t see the nav light blinking. I have the same behavior in both MSFS2020 and MSFS2024 :

Regards,
Boris

[MariopilotPD808]

Please try again under SU5 Beta (1.7.7). I can still see the problem there.

It can be difficult to spot, as the bloom effect is about the same size as the .FX sprite. Check the wing navigation lights, especially red (easier to see), at night.

Additionally, the backlighting for the engine “gauge cluster” shall be on in both the “WHITE” and “RED” panel light setting, but now it only works under “WHITE” (same would apply to all the other instrument backlight FX, but they are defective and do not work under FS24 now. Update lined up to fix all this after SU16.1 Beta)

.

[Boris]

Thank you for the details,

I was able to reproduce the issue and logged it in our backlog.

Regards,
Boris

[Boris]

Hello,

This is fixed with the SU5 flighting 1.7.11.0.
Can you confirm ?

Regards,
Boris

[MariopilotPD808]

Now working as intended. Thanks!

[d41k4n]

Why is this fix not mentioned anywhere in the release notes for 1.7.11.0?

[Boris]

Hello @d41k4n ,

The release notes related to this type of fix are included in the documentation release notes section.

However, as we identified some critical issues, we were unable to release a new SDK alongside the latest SU5 1.7.11.0 flighting as originally planned.

The next SDK release, likely in version 1.6.6, should be available a few hours after the next flighting update.

Regards,
Boris

[system]

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.