Robert Swain
Robert Swain
nvtt can run CPU-only on windows and Linux. As there are Linux aarch64 binaries, it could be run in docker on macOS but that would be too awkward for most....
Could we use existing skybox and environment map textures in the repository to avoid having to add new ones? Having large binary files in the repository should have good motivation...
Reduce frame rate to what?
I tested with 0.11.3 and 0.14.0-rc.2 and observe the same. Using scale_factor of 1.0 makes no difference. It hovers around 40-50% CPU in Activity Monitor, top, htop. I looked at...
[bevy-mrp-macos-performance.gputrace.zip](https://github.com/user-attachments/files/15746501/bevy-mrp-macos-performance.gputrace.zip) Here's the GPU trace with scale factor 1.0.
And just to note that I think tracy traces showing waiting on prepare set systems makes sense as they are blocked by waiting on vsync for a new swapchain texture.
As a note, bevy aims to be able to manage assets on web as well as native. That doesn’t mean that C++ dependencies can’t be used, but bear in mind...
https://github.com/matrix-org/matrix-js-sdk/commit/139f40721e7091e8a981ba01eb96d8b7b9e91b55
So if I understand correctly, you’re suggesting that an additional argument be added to the run closure here: https://github.com/rust-windowing/winit/blob/master/src/event_loop.rs#L152 and that the call sites pass the time stamp. Right?