In the beginning I was using features to abstract specific behavior.
The features were sadly not used later on, meaning that they are basically useless right now.
This would confuse people as they try to activate or remove features without any effect.
Therefore this a chance to rework the features to be more useful
Features I'd like:
editor, see #36
serialize, with a coming system to serialize/deserialize grass chunks completely with all the needed informations to recreate them. This should also have a way to compress the data (such as the grass positions) in files. (Should be its own feature request)
performance, as more stuff get's added to the pipeline, a performance mode should be available.
This could be split into multiple tiny features removing things like wind or shadows (not there yet)
debug, this should more be a dev feature for easier debugging the crate.
static, we lose some performance by keeping resources in the main world and on the cpu in general. This is useful for changing the data from time to time (maybe adding some grass blades over time). Removing the data however would greatly benefit games that are not changing the grass anyway
Describe the bug
In the beginning I was using features to abstract specific behavior. The features were sadly not used later on, meaning that they are basically useless right now. This would confuse people as they try to activate or remove features without any effect.
Therefore this a chance to rework the features to be more useful
Features I'd like:
editor, see #36serialize, with a coming system to serialize/deserialize grass chunks completely with all the needed informations to recreate them. This should also have a way to compress the data (such as the grass positions) in files. (Should be its own feature request)performance, as more stuff get's added to the pipeline, a performance mode should be available. This could be split into multiple tiny features removing things like wind or shadows (not there yet)debug, this should more be a dev feature for easier debugging the crate.static, we lose some performance by keeping resources in the main world and on the cpu in general. This is useful for changing the data from time to time (maybe adding some grass blades over time). Removing the data however would greatly benefit games that are not changing the grass anyway