Daniel
Daniel
Probably access to the high accuracy timer inside container is not allowed.
Yeah. Still broken.
Apprently can be fixed with app.renderer.plugins.interaction.moveWhenInside = true; Yep, that works.
I take it back, if I cross the border of the pixi canvas slow enough, then mouseEdges still moves. This might be a bug in pixi5 though
You can also prevent the angles from going to exactly zero/max to prevent gimble lock. No one will notice if an angel never goes to less than 0.0001 degrees.
I think an Async Api is more critical for this reason, interfacing with storage.
You could have a version of check that returned the scope guard so then you could decide when to drop it?
Been biting me too now. Always happens in chrome.
Found in dmesg: ``` Dec 09 11:57:33 pop-os kernel: NVRM: GPU at PCI:0000:01:00: GPU-61087b93-bcbe-0a03-89cc-aa22818b9325 Dec 09 11:57:33 pop-os kernel: NVRM: Xid (PCI:0000:01:00): 109, pid=4098, name=chrome, Ch 0000000e, errorString CTX SWITCH...