Just thought I'd share my latest DX11 pixel shader, made for displaying 3D voxel models in CF2.5, which also includes some basic directional lighting (look out for an updated voxel terrain shader, coming soon).
Download: https://1drv.ms/u/s!Atq7cUIJ7uextF5X...5-2Xu?e=1ROUbq
As always, feel free to share, modify or use it in any way you like.
PS. Thanks to NaitorStudios for his recent help, which made this possible.
Amazing!
Curious if these will work right on other runtimes, I'll port as soon as I can
Yeah, I don't know the limitations of the other runtimes. Using DX11 definitely made me very lazy though, since it has so few limitations - there's definitely plenty of potential for more streamlining if needed.
I'm wondering if I need to modify the shader to support multiple rows of images in a texture. My B24 Liberator model, which is not huge, still ends up with a texture almost 4000px wide (but far less tall), and in WebGL I believe the maximum texture size that's guaranteed to be supported by all hardware, is 4096 x 4096 pixels, so perhaps some other runtimes might have similar restrictions?
EDIT: In fact, I just tried it again, and since the last changes I made to the shader, the B24 has started causing the app to just silently close on startup (it worked before)
EDIT2: It turns out that isn't the problem - it just crashes any time I choose the texture using the file selector instead an expression with apppath$ + "filename.png". That's really weird...
Version 2 is out now:
(100x100x100 cube!)
The big change is that it now uses a two-dimensional grid of frames, rather than a single row, and you can specify which frames to use (allowing for easy animation).
Other enhancements include a new fog/darkness system, the ability to set the centre of rotation (like the "hotspot" in Cf2.5) and the order of rotations.
I've also included a very basic user guide.
Download: https://1drv.ms/u/s!Atq7cUIJ7uextGB0...Yzk7w?e=x8rgd6
How to install?Originally Posted by MuddyMole
I put the files into fusion but it doesn't show the plane.
No issues starting at all, just no plane showing up.
Thanks
It only works on DX11, because DX9 shaders couldn't handle it...
It could be backported but would need to be really simplified.
TY for the info!
I'm experimenting with making the voxels more like proper cubes. The results look quite nice, but performance has taken a big hit, so unless I can manage some serious optimisation, this may be a dead end...
That's incredible
I love the subtle chamfer/bevel, kind of reminds me of Minecraft artwork
Even if this performs badly, please let me have it xD
There's not much to it really - in the getPixel function, right after where it says "int3 pos = round(position);" you simply divide "pos" by a scaling factor. I used 8 in those examples, so each cube is technically 8x8x8 voxels. And then you need to increase the number of loop iterations in the main function, because the maximum view distance is also reduced by a factor of 8 - and of course, that's what causes the performance to suffer.
That example with the trees is actually quite a challenging scenario, since more than half of the view is sky, meaning that the loops are running to completion (500 iterations), rather than stopping early when the ray hits a solid object (if you tilt the camera down towards the ground a bit, it runs much faster). If used for a game with more confined spaces, I think performance could be very much better. I remember Sinclair Strange recreated the first level of Alien Trilogy using P3D, and that would be the perfect scenario - very confined spaces (including low ceilings), and a lot of darkness to limit the player's range of vision: https://youtu.be/FKrUEqdtR94?t=232
In fact, I believe the original Playstation generally used a 320x240 display mode, and at that low resolution, I can already manage 60fps, so there's hope yet!
I've also found heaps of ways to simplify and optimise the engine, which should help.
The next part of the plan is to make that "3D tilemap" version I talked about, where each pixel on a map texture becomes a 16x16x16 (same as minecraft) volume of voxels. These cubes were actually the first step towards that. And then I'm going to try that "fake depth buffer" idea, so that voxel models or billboarded sprites can be used inside the voxel world! (though it won't be user-friendly)
Posting Permissions
Reply With Quote
