Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Details here, if you like reading bug reports. It took the cooperation of developers at all four levels to fix this. I wrote a test project to reproduce the problem, the jpeg2k developer was able to reproduce the problem under valgrind (a tool for finding bad pointer references in C, seldom needed by Rust users), an OpenJPEG developer fixed the C code, and everybody in the chain updated versions. Thanks to everyone who had a part in this.
That's been fixed. It was one of those things where a complicated workaround for Rust's ownership rules, one that required maintaining internal consistency between multiple tables, was inconsistent.
That's a known problem, and it's now getting attention after my previous post.
A simple TextEdit window with content being added from the bottom becomes blurry. What actually happens is that, at 60 FPS, alternate frames are displaced upwards slightly. A 30 FPS video capture looks fine, but a 60 FPS capture shows the problem. This worked in previous versions of egii, but is broken in 0.21.0. This may be related to a generic problem with "bottom up" mode in the layout engine. Egui has one-pass layout, done on each frame, but tries to do some things which are hard to do in one pass.
Profiling on the CPU side is well handled by tracy, which is a game-oriented profiler. My programs render-bench and ui-mock are prepped for Tracy, as is Rend3, so you can try it out on them.
Profiling on the CPU side is well handled by tracy, which is a game-oriented profiler. My programs render-bench and ui-mock are prepped for Tracy, as is Rend3, so you can try it out on them.
There's a wgpu profiler for finding out where the GPU is spending its time. Haven't tried that.