[ANSWERED] Tracking down the reason for glitch . . .
Hello Troikatronix Team,
First, thank you for your amazing program. I've been using other software (VUO and QLab amongst others) for many years to support live dance through projected elements and only wish I had switched to Isadora long ago.
I'm having a bit of a concern as I continue the build for an upcoming show. I'm using the 3D Player Actor quite extensively, creating objects in Cheetah 3D to then manipulate in Izzy. The glitch happens when I'm x-fading from a scene with a moving element (ie. scrolling text or images) into a scene with a 3d object. If the 3d object has no texture, no problem. But if the object has a texture (saved as a jpg in the same folder), the moving element in the 1st scene stops for a few frames when I press 'go' (glitches noticeably).
I am so impressed with all the possibilities found in Isadora, lately exploring 3D objects, that I'm hoping you can help me get rid of this annoying glitch . . . and continue to create seamless scene x-fades.
I have included a simple file with 4 x-fade examples: the first 3 x-fade from the scrolling text seamlessly, but the 4th (moving into a 3D object with image texture), causes a glitch in the movement of the scene I'm fading out of.
Any help would be much appreciated.
Place an instance of the 3d Player with the corresponding stage, model and texture map assignment in the scene you are cross fading from. This will effectively preload the texture and avoid the glitch. The 3D Player content is hidden in the initial scene but still loaded. It works in the modified patch attached because the 3D Player is assigned to a virtual stage that is not active until the scene cross fade is initiated.
You can alternatively, program the cross fade in the same scene - this will also avoid the glitch.