Debug UI is rendering too small to read.
using the debug mode of ambient run --debug The debug UI renders but it is too small to read
Per discussion on discord at: https://discord.com/channels/894505972289134632/1078283561540530216/1080411889449832478
hierachy.yml https://gist.github.com/kevzettler/e0b7f261653dcc1cd6c4b1961a422114
renderer.txt
shadow
shader "standard_shader_pbr_material_shader_true-true"
material "material000": 18 entities
forward
shader "standard_shader_pbr_material_shader_true-true"
material "material000": 18 entities
shader "standard_shader_flat_material_shader_true-false"
material "62m7s8mU8EuEvizkBXk9w1": 1 entities
transparent
0 entities
outlines
server_hiearchy.yml https://gist.github.com/kevzettler/40419d3340a0a99aecbbc3c073305ff1
Have updated the hiearchy.yml dump with suggested changes from:
https://discord.com/channels/894505972289134632/1078283561540530216/1080542583224279200
That UI dump is super useful, thanks! Not sure when we'll have a chance to investigate, but is there any further information you can provide about your system? e.g. OS, display and scaling settings, GPU. I'm guessing a recent-ish macOS with an external display that runs at a different DPI to your main display?
This issue occurs without using an external display. Happens on built in laptop display.
% uname -a
Darwin kevs-mbp-3.lan 21.5.0 Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:29 PDT 2022; root:xnu-8020.121.3~4/RELEASE_ARM64_T8101 arm64
That's... really weird (we develop on similar hardware). Thanks for the info, we'll look into it!
I have the same resolution (2560x1600) on my LG gram, and the same issue occurs.
Intel(R) Iris(R) Plus Graphics Windows 10
Okay yep, reproduced it - it's definitely an issue with scaling. Thanks for reporting, we'll look into it!
I ran git bisect and the bug was introduced in either https://github.com/AmbientRun/Ambient/commit/27f3f079b441483a928d8650a5f9d9cad9184824 or https://github.com/AmbientRun/Ambient/commit/b210d7b6d8f49cd95a96ad33a8c1c6f6c9ee947e @ten3roberts
I managed to reproduce the issue and fix it on my side.
Let me know if it is now also fixed on your end