21–30 of 93 posts
Lead Bevy developer here: feel free to ask me anything!
Lead Bevy developer here: feel free to ask me anything!
Super happy to see 0.6 released, great work! I've been sponsoring for close to a year, but haven't kept up with the Discord in many months. Currently I'm just been checking for updates every couple of weeks, and sometimes checking the state of GitHub issues and milestones. However, is there any better way for me to keep up with progress? If not, has there been any thought about having regular status updates? They don…
Earlier quoted context omitted.
Any public roadmap?
All the way to the bottom of the blogpost, there is a list of areas being focused on.
If you use this project and you can afford to donate, you definitely should!
Having paid close attention to the Bevy Discord this past year, the sheer amount of work that's happened on this release is mind-boggling.
With 3 month release cadence one question becomes more pressing: will it be 1.0 or 0.10?
With 3 month release cadence one question becomes more pressing: will it be 1.0 or 0.10?
To me good anti-aliasing strategies is the single most important factor when it comes to graphics. I don't really care about things looking realistic or whatever, but I do care about my screen not being full of moving, weird, and distracting grainy patterns.
This involves more than just softening the edges around polygons. There's also textures that contain shapes and the borders in textures with transparency to think about (usually foliage).
My go-to solution in games with lackluster anti-alias is to just render them at a super-high resolution (4k/8k) and downscale, but that's not great for performance usually. You can compensate a bit because you won't need as much anisotropic filtering and such if you downscale, but even on expensive hardware that's not a solution in all games.
To get to the point: In some older games I've seen blurring (possibly due to hardware limitations) of further-away detailed textures reducing aliasing. I'd love to see that technique revived in more modern games, possible with the help of AI to detect patterns/edges on textures that may be susceptible to aliasing, and selectively running those through a filter - basically shifting the work from the artists having to design textures that don't create artifacts to something automatic.
In general good AA tends to be a second-class citizen in many modern game engines, partly because of how their renderer is configured by default (looking at you, Unreal). I really wish it wasn't so.
Lead Bevy developer here: feel free to ask me anything!
Evil question: I wonder why do you have version zero.something - this looks good enough for a version 1. What do you like to accomplish? And... What kind of help you'll need to get there??
The What's Next For Bevy? heading in the release announcement covers this:
Lead Bevy developer here: feel free to ask me anything!
Looks really nice! If one was to implement a simple "3d arcball rotator" viewer for 3d formats to get familiar with the engine (i.e. load obj, view) can you suggest which examples would be most relevant (presuming bevy architecture is the only unfamiliar topic here)?
https://github.com/bevyengine/bevy/tree/main/examples/input https://github.com/bevyengine/bevy/blob/main/examples/3d/loa...