MULTI-CANVAS-STRESS-TESTS:
TEST: Multi-Canvas Simultaneous 4 scenes
RESULT: ~60FPS
TEST: Multi-Canvas Simultaneous 8 scenes
RESULT: ~50-60FPS
TEST: Multi-Canvas Simultaneous 16 scenes
RESULT: ~40-60FPS
TEST: Multi-Canvas Simultaneous 32 scenes
RESULT: ~30-60FPS
NOW FOR SEQUENTIAL TEST… using 32 scenes HIDDEN and showing one at a time (10 sec).
Is it still ~30-60FPS or 60FPS???
Any guesses?
This is why we run TESTS. The results contained TWO GOOD SURPRISES.
Because (as usual) aFalcon makes a mistake - and it turned out to be a performance optimization. I dont know why.
FIRST - the SEQUENTIAL TEST - 32 scenes (formerly 30FPS) (without the mistake)
RESULT: solid 60FPS (you might’ve guessed)
SECOND - the SEQUENTIAL TEST (with the mistake of NON-REPLACEMENT)
- not hiding the other scenes that were just shown (oops)
RESULT: SURPRISE! SOLID 60FPS… what???
Anyone know why? aFalcon will just store this away somewhere.
Ok now FOR THE BIG TEST!!!
100 scenes (with replacement) - is there a performance hit???
WARNING: this is DANGEROUS. 
TEST: 100 SEQUENTIAL SCENES - with REPLACEMENT:
RESULT: ~60FPS
TEST it yourself:
CONCLUSION: aFalcon thinks this is GREAT for making Motion~Picture~Shows in BABYLON.
Thanks @Pryme8.
: )
UPDATE: just in case YOU were wondering… and I know you were!
TEST: 1000 scenes
RESULT: 60FPS
I dont know why. And we are going to keep working with this in the future.