Julian Groß

> can you give this another try with the latest commit from #1111? It indeed works on #1111. > the characters are also seemingly offset by 1 (c renders as...

The original font should be fine, since it works fine with a limited chatset and works fine outside of Overte. Everything else: no idea. It is worth noting though that...

Having a button to send logs and everything somewhere, or maybe just creating a zip file with relevant data, would be great. But personally, having in-application bug reporting would be...

To repeat the information from https://github.com/vircadia/vircadia-native-core/issues/452 : Apparently it's better explained than I remember it: https://github.com/overte-org/overte/commit/3fa3cd8cfdb9be2ec3f4d1c160e000a35c9cceb8 There is a somewhat large High Fidelity PR which I believe never got merged:...

I do get a bunch of warnings in the log, which may or may not be related: ```log [10/15 13:50:01] [WARNING] [hifi.animation] Rig::getJointPositionInWorldFrame produced NaN. is owner thread = true...

I reported the issue to KDE: https://bugs.kde.org/show_bug.cgi?id=513472 I would think that if they build with XCB support, they should also include the libraries for it, especially since not just Gittyup...

I checked it with https://sandbox.babylonjs.com/ and it has the same behaviour. If you provide a lightmap without specifying which UV set to use, it also just uses the first UV...

> [@JulianGro](https://github.com/JulianGro) Are you sure it's the correct screenshot? On the screenshot you posted lightmaps are broken. Do they work correctly when UV set is specified? Yes. I only fixed...

I guess so. We changed this a long time ago and no one has complained, so I don't think this even needs much of a notice.

libnode22 also builds on macOS, which version 18 doesn't without patches due to it looking for the wrong Python executable.