VController readFile warning
by Joseph W. · in Verve · 06/02/2010 (1:32 pm) · 2 replies
I am receiving the following warning when using the readFile script method on a controller. It also comes up when using the Open file under the editor window.
ConsoleSetType( TypeName ) should not be called. A ProtectedSetMethod does this work!
It appears to be happening when reading the XML file and attempting to setField for the name of the controller. It is causing issues with playback of sequences, I am unsure if this is something you know how to fix but hoping you can give some direction.
ConsoleSetType( TypeName ) should not be called. A ProtectedSetMethod does this work!
It appears to be happening when reading the XML file and attempting to setField for the name of the controller. It is causing issues with playback of sequences, I am unsure if this is something you know how to fix but hoping you can give some direction.
#2
But in my experience it doesn't hurt to squash all warnings and errors that one can find that may be causing effects that you cannot always link directly to the warnings.
Also, any ideas on how to get the VPath to better draw the path in the editor so that it is easier to see when it is near other objects? I realize this is an issue with the GFX primitives but wasn't sure if you maybe even thinking of creating something more useful as this is also an issue with the standard Torque path, snap node/path to terrain would be a nice feature to consider as well.
06/02/2010 (8:37 pm)
Well I won't 100% say it is what is causing our sequence file to not play back as Verve is defiantly a slight learning curve and other factors could be contributing.But in my experience it doesn't hurt to squash all warnings and errors that one can find that may be causing effects that you cannot always link directly to the warnings.
Also, any ideas on how to get the VPath to better draw the path in the editor so that it is easier to see when it is near other objects? I realize this is an issue with the GFX primitives but wasn't sure if you maybe even thinking of creating something more useful as this is also an issue with the standard Torque path, snap node/path to terrain would be a nice feature to consider as well.
Associate Phillip O'Shea
Violent Tulip