In my tests Bevy is incredibly slow at starting up and choppy. I must be doing something wrong, as I see others even do 3D stuff?
This is me starting my little test. A 2D camera, JPG background and 41 sprites. Should it take this long? Most of the time the window is blank my logging says that everything is loaded and Bevy is doing something own. Once it starts, it's really choppy for some seconds. After that it animates quite nicely.
I run a dev build. A release is better.
The video is now slowed down. Hm, there's a libbevy_dylib.dylib in the target/debug folder and it's 420MB. But shouldn't that one be loaded before the window is even shown? I used the "dynamic_linking" feature as it was supposed to be better for performance. Maybe I need to get rid of all modules and whatnot that I don't need.
This slowness makes quick iterations annoying and I am slightly disappointed. Making anything bigger than tiny tests will not be feasible as it is now.
Jan Ekholm