ria8651 / bevy-voxel-engine Goto Github PK

What are the goals? Any roadmap? Contributions welcome?

So I have a potential optimization, if you want to mix rasterization and raytracing,
So when you hit a voxel using raytracing you should draw all of the visible faces of that voxel using rasterization
do your usual depth comparisons, skip pixels that already have a voxel face drawn on them for raycasting, except for the edges, because of anti aliasing. (use a sobel edge filter)

The reason I think this might work is that any other visible voxels aren't going to be entirely smack dab on the voxel you've drawn, they're going to be slightly offsetted, larger, or entirely not visible, and using the depth comparison you can draw them in the correct order anyway, letting you skip raytracing to each and every pixel, only ones that haven't been drawn to yet.

This method should work as long as you rasterize every part of the voxel that should be visible.

I'm going to make a diagram in blender for this, of course transparent voxels still need the full raycasting treatment, until the ray hits a solid, anyway.

Look at this line of cubes, try and find a scenario where one cube entirely covers up another when it's not supposed to. Make new screenshots even, show a scenario where one cube that's supposed to be drawn would be covered up due to it's pixels already being taken entirely.

Hey Brian,

Started forking your project and bumping to the newest bevy version 0.12 => https://github.com/SebMenozzi/bevy-voxel-engine, still WIP tho.
Also tried to find your email to reach out to you but didn't find any haha, got some ideas I would like to discuss.
If you have some time (email on my profile) :)

Cheers

Hey there!

As that's the default combination in Rust ecosystem, I would suggest using it.
It's quite liberal true, but as this is already open source on Github I assume this would be fitting.

Thanks for your awesome work!