Emissive Highlight Issue with ASOBO_INSTRUMENT_Clock_Template

Version: 1.3.4

Frequency: Consistently

Severity: High

Context:
Occurs in-flight when using a panel with ASOBO_INSTRUMENT_Clock_Template.

Description:
Hovering over any highlight node in the cockpit causes the clock screen’s backlight to briefly activate and then deactivate, resulting in an unintended flicker. The backlight is intended to remain continuously on for nighttime visibility but is affected by the global highlight system due to insufficient scoping of node IDs.

This behavior does not occur in FS2020 with the same setup.

Code Sample:

In FS2020, this works correctly — even without the <EMISSIVE_CODE_FACTOR>.

Question:
Is there a way to scope or isolate the highlight behavior so it applies only to specific nodes (e.g. the clock)? Or is this a known limitation or bug with the template?

Video:

Hello,

Are you using a background texture ?

I think it’s the same issue as this one : SU3 Beta now causes white flash on html gauges with textures

Regards,
Boris

@Boris hello,

The screen uses the default clock textures, Clock_Screen_albd/comp/emis which are in the sim’s base texture folder. As we use the same clock model in 2020, we mapped our model on top of your textures.

It does seem to be the same issue @Flysimware faces.

Thanks,
Alex

Thank you for the infos,

I’ll tag this topic as a duplicate, but I’ve also added a link to it in the issue that I had already been reported in our backlog.

Regards,
Boris

1 Like

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

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.