No, the global one shouldn't have anything to with it, local yaw has been defined in that scope already so that is used, and the report says it was local anyway.runs wrote:I've check the lua manual and it has sense: http://www.lua.org/manual/5.2/manual.html#3.5
If yaw is global and has a nil value, doing "yaw = yaw + pi" produces nil + pi. So it should be better make "local yaw = ...get_yaw() + pi" than "local yaw = ...get_yaw(); yaw = yaw + pi"
One reason i can think of is you're probably calling remove() somewhere before within the same engine step.
Engine behavior might have changed in that regard, i think it used to be so they get removed only after exiting lua.
Try cleaning the queues before you call remove()