We don't have the power of two requirement because Poser isn't a hardware renderer. Also, even if it was, a 200 image gets loaded into a 256 buffer and it still works. A 2000 goes into a 2048 and still works.

However, if you make an image 200, you consume the same resources as a 256, so why not make it 256 and get a better result.

The powers of two are still used for mipmapping the texture to different sizes on the fly. That is why internally they still get mapped into a power of 2, so they can be divided by 2 many times.

Of course you can divide 200 by 2 and get 100, then 50, then 25, then 12.5 whoops no such thing as half a pixel, trouble ensues, etc. The divide by 2 is simpler math if the software can start with a power of 2.

4096->2048->1024->512->256->128->64->32->16->8->4->2->1

---

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)