Task

Investigate input system designs in the context of an ECS.

Requirements

• Control mappings using configuration files.
• Abstract concrete system inputs using abstract actions.

Please documents your findings in this issue thread.

Feature Request

Implement the main loop used to run the application.

Details

Windowing should be implemented using the winit crate.

Task

Investigate various designs for a asset loading/storage system for crius.

Details

• The system will have to be used as a resource inserted into the main ECS world structure so that the user can retrieve it and use it from within scenes.
• Investigate possiblities for asynchronus loading using tokio or async-std.
• Investigate possibilities for asset streaming.
• Have a look at https://github.com/amethyst/atelier-assets , https://torkleyy.github.io/blog/amethyst-assets/ for getting some ideas

Document possible design ideas in this issue as comments or start a discussion on gitter or discord

Task

The engine's settings should be able to be configured using a configuration file.

Details

• The engine should be configurable using a settings struct.
• This struct should contain values that control various modules of the engine like windowing, rendering, input etc.
• The application struct should accept an instance of this struct on construction and use it's values to configure and initialize its sub-systems accordingly.

Note: The initial version of this struct should not contain the entire configuration of the engine. Instead is should be a starting point towards that goal. This file will be gradually completed as new configuration needs arise.

I strongly recommend using YAML for any kind of configuration since it is human readable and allows for adding comments making it more intuitive to manipulate by the user.

Deserializing a YAML file is really easy in Rust using the serde and serde_yaml crates.

Task

Create an abstraction over the Vulkan graphics API to be used by the engine internally and potentialy by the user in their own scenes for submitting render commands to the engine.

Details

Since this is a learning experience for Vulkan, it is recommended to use the ash crate that provides low lever Vulkan bindings.

Also it is highly recommended to use the vk-mem crate that provides bindings to AMD's Vulkan memory allocator. A C/C++ library that has be proven and used in various released projects.