| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005230 | NoesisGUI | Unity | public | 2026-09-30 10:53 | 2026-09-30 19:46 |
| Reporter | ARPP3 | Assigned To | jsantos | ||
| Priority | normal | Severity | major | ||
| Status | assigned | Resolution | open | ||
| Product Version | 4.0 | ||||
| Target Version | 4.0.1 | ||||
| Summary | 0005230: Mangled Text Glyphs | ||||
| Description | A bug report from my initial forum post: https://www.noesisengine.com/forums/viewtopic.php?f=3&t=4021&p=20187#p20187 It's been seen on macOS and Windows. Both inside and outside of the Unity editor. Likely happens on Linux but we don't have much coverage there. I spent time yesterday trying to reproduce this, it is not a 5% repro rate as I initially guessed. I set up a test harness to re-launch the game repeatedly and compare screenshots against a known-good screen. After ~150 launches it couldn't be reproduced. This was tested on the same commit my colleague (macOS) found the issue on (the images attached are from his run). And I've personally seen it before in builds, and in editor. It leads me to believe this is under some extenuating circumstances. Could be that the system is low on resources or the application loses focus or it could be caused by discord/steam overlays or something strange like this... Atlas size is 2048x2048 at the time of discovery. I tested 256x256 and the symptoms were different (missing characters + clearly reported warnings). We did not catch errors in the console (They have have appeared and been lost, I've set debug logs to the highest verbosity now to catch all messages and informed my team to share logs from sessions if they see this error again). I wish I had better repro steps - I do not unfortunately. I wonder if it could be a sort of race condition between multiple graphics jobs in Unity since, we have native graphics jobs enabled. I don't have other ideas for debugging aside from just walking the load path for glyphs into textures. My motivation for selecting severity as major is that, this is an unrecoverable event and not detectable. Only a full-restart fixes it. If you need more details let me know I will do my best. If any repro steps or logs turn up I will be updating this ticket instantly, | ||||
| Platform | Windows | ||||
 |
Please indicate the Unity version you're using. I think I know what's happening. There is a bug on Unity's side in the D3D12 renderer, and we applied a workaround that doesn't seem to be enough. Just to make sure I'm on the right track, I wonder how easy it would be for you to check the following:
This issue shouldn't occur on macOS, though, and that's the part that leaves me a bit uncertain. Could you please confirm whether you're seeing the same issue on macOS as well? I assume you're using the Metal renderer there. |
 |
Hi! I am really sorry, I followed up with my colleague and there was some miscommunication. Although he does most of his development on macOS, he was testing a live build on Windows this time! So please ignore what I'd written in the bug post, those screenshots I was sent are from a DX12 build, Unfortunately, I can't test Dx11, we have a lot of native plugins we maintain which are only written for metal, Dx12, and vulkan. In the meantime we can test vulkan on windows for the next week or so and let you know if it's stopped. But I think your instinct is probably right, Again, apologies for the misleading bug report, |
