Environment

• Noesis.GUI 4.0.1 from NuGet, Linux x64
• Native SDK 4.0.1 (r18228) headers
• Ubuntu 26.04.1 LTS
• .NET SDK 10.0.401, targeting net10.0

Description

A custom managed RenderDevice constructs successfully in 4.0.1, but its capability flags do not reach native Noesis correctly.

Native DeviceCaps contains four one-byte booleans. The managed struct still includes a four-byte CenterPixelOffset float before those booleans. Consequently, native code reads the float’s bytes as the capability flags.

Our wgpu UI is black despite the managed device reporting DepthRangeZeroToOne = true.

Reproduction

Extract the attached project and run:

dotnet run --project NoesisCapsRepro.csproj

The standalone console app needs no license, GPU, window, XAML, or game assets. Its device reports:

new DeviceCaps
{
DepthRangeZeroToOne = true,
ClipSpaceYInverted = true
}

It calls Noesis_RenderDevice_GetCaps with the device’s native handle and an eight-byte output buffer prefilled with 0xA5.

Actual result

Managed DeviceCaps size: 8
CenterPixelOffset offset: 0
LinearRendering offset: 4
SubpixelRendering offset: 5
DepthRangeZeroToOne offset: 6
ClipSpaceYInverted offset: 7
Managed depth range: True
Managed Y inverted: True
Native caps (8-byte canary): 00000000A5A5A5A5

Expected result

00000101A5A5A5A5

The first four bytes should represent the four native flags; the remaining canary bytes should remain unchanged.

Rendering cross-check

With the normal binding, the UI is black even in evaluation mode without a key. Temporarily placing the expected native capability bytes in the first four bytes of the managed struct makes the loading screen and main menu render correctly. That diagnostic was removed.

Requested fix

Please update managed DeviceCaps and callback marshalling to match the four-byte native layout, removing CenterPixelOffset and preserving one-byte boolean fields.

Please also check the callback write size: the managed assignment appears to write eight bytes where the native structure contains only four.

This is separate from constructor issue 0005188. Windows has not been tested.