Problem rendering multiple scripted objects (Groovy related) about artofillusion HOT 3 OPEN

Did a little research...

It would seem that Raytracer.addObject() is not thread safe, when it has to recursively call itself. That happens, when theObject is and ObjectCollection, it this case a ScriptedObject.

Adding some debugging code shows that addObject() always finds both of the first level objects (scripts), but sometimes misses one of the cubes the scripts produce. Setting addObject synchronized naturally takes care of the problem but then we'd lose (some of the) benefit of parallel processing.

As I recall, in the earlier case the scripted object was supposed to create arrow heads out of primitives by boolean operations and in that case the outcome was in most cases only partially made as if the object from the collection had been read before the script had completed the build. That would also explain what happens here.

If that theory is correct, the question would be, how can it be made sure that running the script has been competed before addObject() requests the content?

Edited a bit.

from artofillusion.

So, the problem is that Groovy is not thread safe! -- This is actually nothing new, it tends to fail with recursion levels and things of that sort too...

I changed the objects so that one of them is a Cylinder and one a Cube. When I render the 1 second movie, sometimes one of the objects is missing entirely and sometimes their position coordinates are confused...

Scripted primitives.zip

I did not quite understand what the mechanism that triggers updating the ScriptedObjects is, but it turns out that SriptedObject.getObjectScript() is visited twice for each rendered frame. Once before Raytracer.addObject() and once after. Apparently the firts one happens in the model scene and addObject() triggers the latter one is for the raytracing scene. With Groovy the latter visit is sometimes missing for one of the objects (typically looks like the 1st one on the list). Other times both objects end up in the same coordinates.

In the coordinates swapping case I find it a bit strange that the coordinates that are changing places are not in the script, they are the Scene position coordinates. Internally the scripts only use new CoordinateSystem().

When I change the language to BeanShell the scripts work as expected.

from artofillusion.