5 ms·

Lead developer here. Feel free to ask me anything!

by _cart 6y ago

brobinson 6y ago
No question, but thanks for fixing the CPU usage issues. Only seeing 0.4% CPU usage on the breakout example in release mode now. (credit to the rayon developers as well)
- _cart 6y ago
  I'm glad it worked for you! All credit goes to @lachlansneff and @aclysma. They really did a great job here :)
macawfish 6y ago
Will this allow for async systems?
- wwright 6y ago
  Don’t systems normally want fairly tight bounds on when they execute and how long? (Genuine question)
  - _cart 6y ago
    We are considering async systems, but in general I do think that allowing them to suspend execution across frames would be undesirable (at least as a default).
    - wwright 6y ago
      What kind of use case would want to suspend within a frame?
      - macawfish 6y ago
        Well, I know I just want to be able to poll futures from a system. There's a rust FRP library called futures-signals that would be really useful for taking input from a controller and transforming it into high level, meaningful streams. I'd like to react to those streams. I don't think they'd take multiple frames to poll, but even if they did I wouldn't mind too much. (I'm new to both rust and ECS so if you have a suggestion for how to approach this problem differently, I'd love to hear it)
mechaxl 6y ago
Maybe I'm missing something looking at the examples on github, but is there an "end-to-end" example? I'm interested in seeing an example that has main/pause/settings menus, for example.
- _cart 6y ago
  We don't really have a good end-to-end demo at this point. We're still building out some of the "core" pieces of state management (namely the Scene system, which works in the current form but isn't fully featured yet). In general transitions between menus/levels will happen via Scene transitions (similar to how godot handles it). You can also adopt a `enum State { Menu, InGame }` Resource pattern, then have your systems key off of that state where necessary.
mikelpr 6y ago
comparison to amethyst?
- rudedogg 6y ago
  Check out his post here (https://community.amethyst.rs/t/bevy-engine-addressing-the-elephant-in-the-room/1645/9 https://community.amethyst.rs/t/bevy-engine-addressing-the-e...) He goes into a lot of the differences.
mkesper 6y ago
Is a roadmap available in some flat list? The roadmap feature at Github gives no good overview "at one look".
- _cart 6y ago
  Github issues/roadmaps are the source of truth for the project. I totally get that its not as easily digestible as a well formatted document, but anything that isn't directly tied to the backlog is immediately out of date the second we add/remove/update something. Adding a separate document and committing to keeping it up to date is more work than I'm willing to do right now. I've made myself a project management bottleneck in the short term, which means I need to optimize as much as I can.

Lead developer here. Feel free to ask me anything!

by _cart 6y ago

Lead developer here. Feel free to ask me anything!

No question, but thanks for fixing the CPU usage issues. Only seeing 0.4% CPU usage on the breakout example in release mode now. (credit to the rayon developers as well)

_cart 6y ago
I'm glad it worked for you! All credit goes to @lachlansneff and @aclysma. They really did a great job here :)

macawfish 6y ago

Will this allow for async systems?

wwright 6y ago
Don’t systems normally want fairly tight bounds on when they execute and how long? (Genuine question)
- _cart 6y ago
  We are considering async systems, but in general I do think that allowing them to suspend execution across frames would be undesirable (at least as a default).
  - wwright 6y ago
    What kind of use case would want to suspend within a frame?
    - macawfish 6y ago
      Well, I know I just want to be able to poll futures from a system. There's a rust FRP library called futures-signals that would be really useful for taking input from a controller and transforming it into high level, meaningful streams. I'd like to react to those streams. I don't think they'd take multiple frames to poll, but even if they did I wouldn't mind too much. (I'm new to both rust and ECS so if you have a suggestion for how to approach this problem differently, I'd love to hear it)

mechaxl 6y ago

Maybe I'm missing something looking at the examples on github, but is there an "end-to-end" example? I'm interested in seeing an example that has main/pause/settings menus, for example.

_cart 6y ago
We don't really have a good end-to-end demo at this point. We're still building out some of the "core" pieces of state management (namely the Scene system, which works in the current form but isn't fully featured yet). In general transitions between menus/levels will happen via Scene transitions (similar to how godot handles it). You can also adopt a `enum State { Menu, InGame }` Resource pattern, then have your systems key off of that state where necessary.

mikelpr 6y ago

comparison to amethyst?

rudedogg 6y ago
Check out his post here (https://community.amethyst.rs/t/bevy-engine-addressing-the-elephant-in-the-room/1645/9 https://community.amethyst.rs/t/bevy-engine-addressing-the-e...) He goes into a lot of the differences.

mkesper 6y ago

Is a roadmap available in some flat list? The roadmap feature at Github gives no good overview "at one look".

_cart 6y ago
Github issues/roadmaps are the source of truth for the project. I totally get that its not as easily digestible as a well formatted document, but anything that isn't directly tied to the backlog is immediately out of date the second we add/remove/update something. Adding a separate document and committing to keeping it up to date is more work than I'm willing to do right now. I've made myself a project management bottleneck in the short term, which means I need to optimize as much as I can.