Hi all,

The different behaviors of movies running in the director's authoring
environment and runtime mode is nothing new. I can remember issues related
to puppeting and accessing certain sprite properties since.. forever.
But today I faced the 'memory can not be read' thingy for the first
time.Don't know if it is mentioned in some list somewhere, but anyway...
I had some really heavy processing (extensive list functions, imaging lingo,
member generating, sprite puppeting) being initiated from the 'on
beginSprite' handler of several sprites. Everything was running smooth in
authoring, but -as you guessed- that was not the case in projector/plugin
mode. The weird (though not 'Director-ly' unexpected thing was that not all
saved versions -with very slight differences- caused the error.
The problem was solved by moving the processes from on beginSprite to on
enterFrame. Quite inconvenient, since this required to include a property to
check if it was the first 'on enterFrame' for every sprite. Well, it works,
but not exactly as I like it, so soon as I find some time I'll try to find
what exactly causes the error. Till then, just thought of posting this, case
anyone else has faced (or will face) a similar problem.