Cool.

For the sake of completeness, I did a 20-bounce render. Very few pixels were actually affected by this, but it cost a lot in render time. This is because Poser is missing an important feature in a raytracer. It does not understand or recognize that some bounces are just unimportant. This is easily worked out when a reflection is only 1% and the next interaction is also 1% - the resulting ray will only be returning 1% of 1% of whatever it finds. Unless that is a super bright object, it will be a waste of time as the pixel will be the same with or without this bounce (and any that follow!).

So - this is your job as production manager. You decide how many bounces to allow it to use, and it will either work well or it won't, and you have to judge your outcome.

I always allow 2, and frequently allow 4. I rarely go above 4 but when it is needed, it is needed. There's no other way to say it without writing a book of all the scenarios.

Render times of my scene:

1 bounce = 43 seconds

2 bounce = 70 seconds

3 bounce = 92 seconds

4 bounce = 113 seconds

20 bounce = 31 minutes

---

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)