Vincent wrote:This is still the same problem, i.e., the wait() command is not working.
So all the commands that follow the wait() command won't be taken into
consideration by the script...
fsgregs wrote:OK, I give up!
Frank, probably one last try.
As I understand from Vincent, there is someting with the wait() and in a previous post he also told the same about the tick() method, that's why your CELurl was previously also not working. But the wait() function is necessary to to start rendering all things you changed during the previous celx methods. In fact, without a wait() nothing will be changed on your screen
What I recognize in your test with Cham's script is that your first goto is about doing what is must do, but the observer orientation does not do the things specified, because they are called
after the wait(), which is not working properly and that's why the following celx methods are not taken into consideration.
In the celx I posted to replace your CELurl, the same occurs, because the script contains a wait(0.0) somewhere in the middle,
which is not absolutely necessary there to start rendering the changes made. So it may be deleted there, leaving just
1 final wait(0.0) as a last statement in the script.
You also can try the same with Cham's script to MOVE the wait(0.0) to the final line of code.
Probably it's wishful thinking, but I was triggered for this, because I saw your example that the distance is merely correct, but the rotation is failing. With the explanation of Vincent, this problem can probably circumvented by only
having 1 wait(0.0) as the last line of code in the script.
So although wait() is probably not working correct, you need it to render and probably as a final line of code in the script it probably may still render the changes made.
Marco