OTOY Forums

Hey guys! Hoping for some help. I bought the Daz plugin to be able to animate, but after doing some reading on here, it looks like currently there is no way to render animation in 2.1. Is that correct? It renders the same frame over and over for me. Are there any workarounds that have been found? Does exporting to the standalone work?

I tried to go back to some of the older versions, but any time I install and of the 1.0 versions of the plugin, they are never recognized, and I can't render from there either. Currently I'm stuck without the ability to animate at all, and it's very frustrating. Any advice?

Hi Kezzex,

As of OCDS version 2.15 animation is still broken. I can confirm that animation works with camera movements, as well as objects' translation, rotation and scale, as long as it is done to their root node. However any animation that involves morphs or any of the child node in the rig (limbs, etc) is being ignored by OcDS. There is no workaround that I know of, I'm afraid.

Some folks here are sticking with OcDS 1.2 for animating in which it works, somewhat... I've been hearing good things about exporting to standalone, I haven't tried it yet but it's probably a viable alternative while waiting for OcDS to finally be able to render animation properly.

Thank you for your response. I would be totally fine with reverting to 1.2, but for some reason it will not recognize activation. I talk about that in this thread: http://render.otoy.com/forum/viewtopic.php?f=44&t=44880.

I have completely re-installed Daz, removed Octane 2.0, installed Octane 1.55, and used the correct activation codes for both. Despite all of this, version 1.2 of the plugin does not seem to recognize activation no matter what I do. I spent a ton of money last month on a brand new rig specifically for animation, and I can't do anything. The only way the plugin would work in the previous thread was to use the 2.1 version. Do you have any suggestions on how to make the plugin recognize my activation? Otherwise, do you know of a way I can get my money back for the plugin, or as a last resort transfer the plugin to work with another program?

Have you managed to delete every file associated with OR before reinstalling v1.2? I currently use 1.2 for animation. If I recall, it is installed to a different location to 2.1. There is a 1.2 thread that explains in detail how to install it or how to upgrade earlier versions to 1.2. I think it's a case of clearing out everything associated with OR and starting from scratch. That doesn't require reinstalling DAZ Studio or your OS because the Octane plugin is completely self contained and does not alter settings in any other application.

1.2 is passable for animation as long as it's not too complex, you have enough RAM and a reasonably powerful GPU/CPU. Problems occur with older systems where the clothing, hair and other wearable props aren't updated in each frame. Pushing the GPU's VRAM to its limits may also clog things up. Sometimes during rendering the 1.2 plugin will crash and the project will need to be reopened and rendering started again from the last rendered frame.

Please read or re-read the 1.2 installation thread to make sure you have cleaned out earlier or later files so that it really is a clean installation of 1.2. Once the activation file has been deleted there shouldn't be any problem with reactivating the plugin. After installation download all the textures and then activate. If you've followed this procedure and it still isn't activating then contact OTOY support. In the meantime we'll try to help.

One final thought, if you try to activate too frequently it can throw out the system and there might be a delay required between activation attempts. Also, did you deactivate any previous installations in your account? I assume you do have a serial for 1.2?

Thank you. Any idea where I can find that thread? I have searched several times and can't seem to find it. I have also attempted to uninstall and delete everything associated with Daz and Octane and re-install them several times, but something seems to remain. Whenever I re-install octane, it is already activated. The plugin, of course, continues to not activate. Please let me know if you know where I can find the thread.

Try these two links:

http://render.otoy.com/forum/viewtopic.php?f=44&t=38116

http://render.otoy.com/forum/viewtopic.php?f=44&t=29942

Thank you for replying so quickly. The one thing that I noticed I haven't been doing was deleting the octane folder under c:/users/octanerender. I deleted that folder, and it asked me for my username/password! I was beyond excited. I entered the info into the activator and started up Daz. Unfortunately, I still have a big red X staring at me saying it isn't activated. I click on the activator from the plugin, and there it says activated. Just to clarify, I do have activation codes for both 1.x and 2.x of both the standalone and daz plugins. Am I the only one that has run into this issue? Any ideas on how to get 1.2 to recognize its activation?

I had this problem once before and it was due to a corrupt auth file. PM t_3 for support asap. In the meantime please try deleting everything associated with Octane Render again. Make sure nothing is authorised in your account. If it is unauthorise it. Log out of OTOY and shut down your browser. Once this has been done shut down and then restart the computer. Install 1.2 again and then try authorising.

I found this thread with a lot of useful information! Some of it may help.

http://render.otoy.com/forum/viewtopic. ... 60#p131158

I have the same problem - Titan black rendered animation fine in 1.2. Upgraded to Titan X and suddenly Octane is not activated. Upgraded to 2.1, activation worked, but animation is broken. Installed 1.5, activation still worked, but animation still broken. Reinstalled 1.2, Octane is no longer activated.

So the issue is the Maxwell architecture? No animation in ORDS without fermi/kepler cards in 1.2?

Kezzex, you are using 980s, right?

You know, I never thought of that, but 1.2 is incompatible with Maxwell cards. It wasn't fixed in the Octane API until 1.54. Shouldn't really affect activation either way, per se, but I'd make sure 1.2 is compatible with your cards before driving yourself crazy over an activation that may still leave you unable to do what you want.