[Bug] Semi-transparent white NUI elements render darker in Enhanced than Legacy

[rlxone]

Summary

NUI elements that use a white color or white texture with CSS opacity/alpha are composited differently in FiveM for GTAV Enhanced. With the same resource and styling, the elements appear noticeably darker and have a different effective opacity in Enhanced than in Legacy. The issue is consistently reproducible and affects both solid white backgrounds and textured elements.

Issue type

Client

Repro rate

Always

Server build version

b96 linux (client-side NUI rendering issue)

OS

No response

CPU

No response

GPU

No response

RAM

No response

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

None

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

None

Hosting provider

None

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Create or use an NUI page with a transparent body and a semi-transparent white element. For example:

<div class="overlay"></div>
<style>
  html, body { margin: 0; background: transparent; }
  .overlay {
    width: 520px;
    height: 520px;
    background: rgba(255, 255, 255, 0.25);
  }
</style>

The same mismatch can also be reproduced with a white background texture/image and CSS opacity.
2. Start the resource and join the same server/scene using FiveM Legacy.
3. Observe or capture the overlay.
4. Without changing the resource or styling, repeat using FiveM for GTAV Enhanced.
5. Compare the element's brightness, tint, and effective opacity between the two clients.

Expected Behavior

The NUI element should be composited identically in Legacy and Enhanced: the same white point/texture appearance and the same effective opacity over the game scene.

Actual Behavior

In Enhanced, the same semi-transparent white element is significantly darker and has a visibly different effective opacity than in Legacy. The mismatch is visible in both attached comparison pairs, including the large top-left overlay and the smaller lower-left overlay. No resource or styling change is made between the Legacy and Enhanced runs.

Evidence

Four screenshots from the same UI setup are attached below:

• div1-legacy.jpg and div1-enhanced.jpg: large semi-transparent white element.
• div2-legacy.jpg and div2-enhanced.jpg: second view highlighting the opacity/compositing difference.

The resource and styling are unchanged between the Legacy and Enhanced captures.

Additional Context

The issue is not limited to a CSS solid color. It is also visible when opacity is applied to an element that uses a white texture/image, which suggests an alpha/color-space compositing difference rather than a single CSS property. It is easiest to see over dark game content. The Legacy screenshot identifies client build b3751 Beta.

[unknown-urge]

I can confirm this.

[IchigoWalker]

Same issue, annoying and breaking UI

[chromium-cfx]

Thanks for the report, this issue was able to be reproduced and will be fixed in a future patch.

[Gogsi]

A fix for this bug has been implemented and is available in Hotfix 7 (b104). Please try again and let us know if the issue persists. Thanks for your help!

[rlxone]

I confirm it is fixed now. Thanks!