OTOY Forums

I have been having some issues with Standalone and learning how to properly create an animated orbx package. I have managed to resolve most of those issues, and there are a couple of posts in the Cinema 4D section which chronicles my issues and resolutions to them.

This issue, however, is not resolved in the same manner, and points back to the original issue that I have been having regarding visible boolean operators when rendering in Standalone. As C4DtoOctane is the only way to create an animated orbx package, I am posting here as a bug. As the above pictures show, we see that one frame has a large cylindrical wedge on the left side of frame, while the other does not. When rendering in Cinema, this image renders correctly all of the time. On occasion I will see this object in Live View, but it disappears upon refresh. In Standalone, when rendering the Animated orbx package, the boolean operators are visible in the first frame, but disappear in subsequent frames. Note that I am showing you two different frames about 3 or 4 frames apart, so there are differences due to that.

However, on ORC, using the exact same animated orbx package, the operators are always visible, which differs notably from the results with Standalone. I am using 3.08 Octane and R19 Cinema. I prefer to keep these booleans live rather than bake them in for a variety of reasons (as they animate for effect). Hopefully we can figure out a quick fix.

And it appears that the subD operator is also not working properly in the ORC version, as noted in the red object to center top of frame. It is smooth (correct) on the local Standalone version, but not on the ORC version.

Do you mean it's correct in standalone but not in ORC? Did you tried to convert boolean objects to meshes?

Yes, it is correct in Standalone, but after the first frame. It is never correct in ORC, even though both were rendered from the same orbx file.

As I am animating these booleans for a reveal effect, it is difficult for me to convert them to meshes. I am also animating the source cylinder using the slice command, which adds to the complexity of converting them (and it renders correct in with C4DtoOctane anyway, so it should render correct in both Standalone and ORC.)

jayroth wrote:Yes, it is correct in Standalone, but after the first frame. It is never correct in ORC, even though both were rendered from the same orbx file.

As I am animating these booleans for a reveal effect, it is difficult for me to convert them to meshes. I am also animating the source cylinder using the slice command, which adds to the complexity of converting them (and it renders correct in with C4DtoOctane anyway, so it should render correct in both Standalone and ORC.)

ORC is not about plugin side. So this issue is more related to ORC section.

Perhaps, but ORC is being driven by the file that is written from the plug in, so it is relevant here.

As I wrote, in Standalone, the issue occurs on the first frame, but disappears in subsequent frames. That indicates that the issue is present in the orbx file; As I noted in one of my posts in the Cinema forum, when I choose the Edit in Standalone option, the issue does NOT present at all, however, choosing the Export Animated Package to Orbx, it DOES present -- it just goes away after the first frame. Perhaps there is some sort of latency thing happening. I am happy to PM you the orbx file to review if you like. Perhaps that can shed some light...

jayroth wrote:Perhaps, but ORC is being driven by the file that is written from the plug in, so it is relevant here.

Only thing is related with plugin is inconsistency of boolean objects. Rest is a compatibility issue on ORC version and standalone. Because you should expect same results between standalone vs. ORC. It's based standalone not plugin. Please send a scene to me.

Will do. Its a big one, so I will try and simplify it for you.

While ORC can run 3.08 test releases jobs (mostly for our testing), it's best to work with the latest stable version (3.07) for any production work, until 3.08 is finalized. I am not sure if that is the issue here, but it may be worth trying 3.07 just in case that reduces variables.