Nothing relevant I presume, but I had to let it out :)
1. According to slab6.txt, pressing INSERT alone is enough to paste an image, while in practice that can only be achieved with SHIFT+INSERT. Not that it takes you more a few seconds to figure that out, but it wouldn't hurt to correct that line.
2. The brush radius for the slice editor is limited to either a single voxel or flood fill + it's dangerous variant. It would be handy to be able to increase the radius of the brush in order to paint larger (but specific) areas more efficiently.
3. An optional flood fill mode that fills all the air areas on the slice at once rather than just the one under the cursor. Since dangerous flood fill will destroy everything, it's not an option here.
4. Allow the 3d selection tool to be positioned (kind of like shift+kp) without actually removing voxels from the model.
5. Show the boundaries of the grid ala KubeGL.
6. When working with massive voxels, rendering may become a lil sluggish, so I was wondering if being able to manually disable the 3d view while working on the slice editor would be an acceptable/feasible/practical idea.
7. The slice editor reports the maximum dimension of the axis right after the "/", let's make it 64 for the example, yet the slices will be numbered from 0 to 63 rather than from 1 to 64, resulting in "63/64" when positioning the selector on the latest slice. I'm not saying there's anything wrong with this, but I'd be interested in reading the explanation for what seems to be an unnecessary inconsistency to me.
8. Resize the grid to accommodate pasted images larger than the actual grid.
9. Using Shift+SPACE to paint a model when rotating it results in slow rotation, which can cost you a considerable amount of time depending on the size of the surface. Can this behavior be improved?
10. Building/carving slopes with any degree of precision is actually more complicated than it sounds. How about allowing the 3D selection tool to lower one of it's side so to create a sloped selection which should retain the capabilities of the regular "cubic" selection?
11. Deep painting. Imagine start painting on a slice and have either all the other slices or selectively those from one side or the other, painted as well. This would definitely be a big time saver. You could, for example, build a whole cylinder by just painting a circle on a single slice.
12. Axis rotations through numerical input. Say I wanted to rotate a model exactly 45 (or -45) degrees on the X axis; I'd type in the number and presto! This would be extremely handy for creating sprites.
13. Saving paletted screenshots with dimensions cropped down to those of the actual voxel model :)
14. Model stretching ala SLABSPRI.
15. A tool for identifying unused colours.
16. A voxel counter. This is to make it easier to establish a link between the mount of voxels and the framerate.
17. Allow slab to keep more than just one image in the memory.
18. Shortcuts for doubling and halving dimensions.
19. 64 values for RGB? bring back the 255! Now seriously, why is this?
20. Even though one of the voxel dimensions is limited to a maximum of 255, you're still able to select the 256th slice of the grid with the 3d selector, but any attempt to insert an extra voxel with this tool (not that you should be doing this) will cause slab to crash. Deleting big chunks from a 256x255x256 cube using the 3d selector will also cause slab to crash, but I guess it's just part of the instability inherent to working with voxel models bigger than the editor was intended to handle comfortably, specially on my ancient computer.
21. Create a voxel model from a strip of properly numbered images resized and paletted to fit in slab as slices. You may choose which axis to align them to. Now that would be great :)
22. A variant of the "C" tool for changing colours that works just like the flood tool, and by this I mean, change ONLY the colours of the same-coloured voxel cluster under the cursor, which would be akin to filling only the "air" area under the cursor using "F" in the slice editor.
Thanks a lot for taking the time to read, Cheers.
Awesoken at
Re: 22 suggestions and observations for SLAB6
Hi Maren,
Some of your suggestions are quite good - thanks for writing them down and sharing it. Please keep in mind that I wasn't planning on doing much more support for SLAB6 - that's why I released the source code. Before I can address any of your ideas, I would need to fix some issues with the mouse cursor, which is not working right under Windows 7.
Scott_AW at
Glad I'm still using XP, I didn't know about that.