Incorrect Control Bounds data

[markusalbrecht-procam]

Hi there,
we are playing with this since several days now as we encountered problems getting the 3D control Viewport fully sized via the Bounds. In order to find the source of the issue we removed almost any view data and only kept the control full sized to the window. The result is always wrong --> delivering 30% less then the actual max window width and height:

Should be at least 1900*980 when looking at the real window size:

So it seems that the Bounds calculation of Avalonia is doing something but not getting the real size of the control or window for some reason ?

What is the problem here ?

[markusalbrecht-procam]

By adding a factor of 1.25 it works but I do not think that this can be the solution as it might differ from GPU to GPU and Res to Res ?!?!

[stevemonaco]

Even when setting the system scaling here to 1.25x (Windows 11), I'm still getting the correct Bounds in Avalonia 11.0.6 for the top-level <Window> when inspecting via DevTools (F12). Some more information as to which OS you're using (looks like Win), Avalonia version, and which control you're querying for Bounds might help troubleshoot.

[markusalbrecht-procam]

This solved the issue

[maxkatz6]

Render scaling. You can get your render scaling from TopLevel/Window.RenderScaling property.

[markusalbrecht-procam]

@maxkatz6 Thanks this solved the issue right away ;)

[anose001]

@maxkatz6, I tried the above approach via TopLevel on Android in the MainView.axaml.cs file but received a null reference. Is there a proper way of retrieveing RenderScaling or dpi values on mobile?