Well I managed to get some decent results with 11 nodes.

However, there are 7 key numeric parameters that must be adjusted for the scale of the props you're dealing with and the position of the camera. I despair of ever being able to explain the effect of these 7 values to normal people. Even though the math is pretty straightforward add, subtract, multiply, and divide, there is a lot of it.

I would have to make a parameterized version that has many more nodes, which could reduce the number of control parameters a user would have to deal with to 4 instead of 7.

I'm not sure anybody would find it useful.

I suppose a script could be written that would measure all the props and camera location and set the shader up automatically.

I tested with the Dystopia city props. These are miniatures - not full size. The camera here is only 10 inches above the ground, so it's clear that the numbers I'm using would have to be completely different for a full sized scenario.

Note: I know - there should not be distinct shadows. I didn't bother setting up a legit lighting regime for this scenario.

---

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)