OTOY Forums

Spectralis wrote:I've experienced the same problem. It didn't happen in Build 3.0.20.20 but that's now expired. Any chance of renewing this beta while we wait for the next build?

When will this problem be solved? I can no longer use the previous versions and I need to finish an animation.

When will this problem be solved? I can no longer use the previous versions and I need to finish an animation.

It is fixed in the next release - which is waiting on the next version of Octane to be released. You should be able to export the animation to Standalone and render there, or revert to 2.25.

Paul

face_off wrote:

When will this problem be solved? I can no longer use the previous versions and I need to finish an animation.

It is fixed in the next release - which is waiting on the next version of Octane to be released. You should be able to export the animation to Standalone and render there, or revert to 2.25.

Paul

Approximately, On what date? I need to do an animation for a contest and must be finished before July 14.

I'm unsure - you'll will need to ask Otoy. If you have a deadline, you should be on the STABLE version of the plugin, not the TEST version. Or, as I said above, export the scene to ABC/OCS and render the animation in Octane Standalone.

Paul

If I revert to v2.25 is it just a case of reinstalling it over the latest v3 version or do I need to uninstall v3 before reinstalling v2? After reverting to v2 I assume it's necessary then to save the project as a v2 version? It's a shame we can't revert to Build 3.0.20.20 because that rendered animation 30% faster than v2 on my system.

Yes, you can install the 2.25 version of the plugin over the top of the 3.00 version. I am unsure how .duf files saved in 3.00 will go loading into 2.25 - suggest you keep a backup of the 3.00 version just in case...

Paul

Has v2.25 been updated to include d-former animation? If not, how do I render in the standalone? I exported the scene as an abc file, loaded it into the v3 standalone but the render viewport and the controls are grayed-out. I can't figure out how to activate the scene in the standalone render viewport so I can render it.

Select the rendertarget once you have loaded the OCS file into Octane Standalone. https://docs.otoy.com/#60System%20Tab.

Paul

I followed the instructions in the link you posted but when I import the scene into the standalone using Geometry-scene node only part of the scene is visible in the render viewport. I'm not really sure what I'm doing wrong and probably need to spend time with the standalone manual.

From the manual....

From release 3.0.4.11, when you save to an Alembic file, the plugin will also save to an OCS file which contains that ABC file, with all the material connections in place. The OCS file saved to be the ABC filename with a .OCS file extension.

Load this OCS file into Standalone and select the rendertarget.

Paul