MarkWheadon
commented
7 years ago Sure. There are a couple of constants in surfaceSpeed() -- xWidth and yWidth. They control the physical size of the image as it is projected through the model. So if xWidth and yWidth are, say, 20 then the image will be a 20mm square.
The image itself is mapped into greyscale by the script, so it can be colour or black and white or greyscale, and pretty much any image format, although it doesn't handle transparency right so if you have, say, a PNG file with transparency you need to map that transparency to (usually) white -- saving it as a JPEG is an effective way of doing that.
I find black and white, simple images tend to look best, but greys between black and white will be handled correctly (with a speed part way between the lowest and the highest speeds).
DPI -- the more the merrier, but I would think 100 DPI once projected onto the model would be anough (so 80 pixels across for my 20mm example, for example). Having a low DPI may look great in some circumstances, as you'll be able to see the pixels (think Pacman, low-poly Pokemon etc., which benefit from the lo-tech look).
ghost
I am currently testing the script on an ubuntu machine. it would be very helpful, if you could add specific information on the usage of images (size relative to the model, colors, dpi etc.).