3 ms·
I'm using Rend3 for a Second Life/Open Simulator client. The current system with Rend3 has one thread doing nothing but refreshing the screen, while other low
by Animats 5y ago
I'm using Rend3 for a Second Life/Open Simulator client.
The current system with Rend3 has one thread doing nothing but refreshing the screen, while other lower-priority threads are independently changing the scene based on incoming messages from the network. Is that something the Bevy architecture can handle? Should I consider switching to Bevy?
- _cart 5y agoPipelining allows rendering and app logic to run in parallel. You can adapt to changes from the network when the app logic runs, so in that sense, it seems like a good fit. And you can use bevy_tasks to spawn background tasks (and spawn tasks across different thread pools, if that is required). I think it is worth considering Bevy, but I also think Rend3 is a great piece of software. We discuss rendering with that project's lead constantly :)