Last name binding - names don't load in specific scenario
Hi guys - I use the "last name" binding for my main ticker. I've always had issues with names not loading in a specific scenario. It seems that sometimes, a name will not load if the driver has joined the server, but not gone on track just yet. It usually only happens with one or two drivers, the rest will load fine. Somewhere there is a bug, just with the last name binding. All the other bindings, full name, first initial last name, etc, do not have this problem.
Side note - is it possible to add a control to stop a script? Currently, there's only "execute". Over time, scripts cause ATVO to grind to a halt.
Thanks guys!
Side note - is it possible to add a control to stop a script? Currently, there's only "execute". Over time, scripts cause ATVO to grind to a halt.
Thanks guys!
We've seen the name error but never managed to reproduce it... Your additional info may help, thanks.
For a script, it only executes once and then stops, unless you set it to execute every update. If you don't, then the script should only run once. You can make it loop yourself of course and use your own stop condition. For a script that executed every update you can also add your own stop condition by checking for some condition before doing anything heavy, and then returning out of the execution if your condition is met.
For a script, it only executes once and then stops, unless you set it to execute every update. If you don't, then the script should only run once. You can make it loop yourself of course and use your own stop condition. For a script that executed every update you can also add your own stop condition by checking for some condition before doing anything heavy, and then returning out of the execution if your condition is met.
Nick Thissen wrote:
We've seen the name error but never managed to reproduce it... Your additional info may help, thanks.
For a script, it only executes once and then stops, unless you set it to execute every update. If you don't, then the script should only run once. You can make it loop yourself of course and use your own stop condition. For a script that executed every update you can also add your own stop condition by checking for some condition before doing anything heavy, and then returning out of the execution if your condition is met.
Yeah, it seems like the name error only manifests if you load the theme before the drivers load onto the track, but it always gets most drivers, just one or a few don't load.
For the scripts - losing a ton of performance in the script I posted in the other forum that you helped me out with. I suppose it's due to being in a ticker. It almost acts like there's a memory leak, where it gets slower over time. Wish I knew how to fix my scripting so that wouldn't happen. Appreciate the response!
Nick Thissen wrote:
We've seen the name error but never managed to reproduce it... Your additional info may help, thanks.
For a script, it only executes once and then stops, unless you set it to execute every update. If you don't, then the script should only run once. You can make it loop yourself of course and use your own stop condition. For a script that executed every update you can also add your own stop condition by checking for some condition before doing anything heavy, and then returning out of the execution if your condition is met.
Hi Nick - this problem exists when using A.I. as well - last name binding shows nothing with AI drivers, while the other bindings work. May help track down the issue, potentially could be a similar issue. Not sure if the AI are handled differently, however.