Page 1 of 1
Octane Render Cache
Posted: Thu Sep 22, 2016 8:53 am
by pascherheinz
Hallo
System:
Windows 10
Cinema 4D R17
GPU Nvidia 980ti x2
Problem:
1. When I try to render the scene in the Live viewer, it hangs on the "2 Copying Document" command that I can see in yellow (upper left corner) in the live viewer window.
2. When I render to the picture viewer then everything is fine and it sends to cache in seconds and renders in less then a minute.
3. When I open other scenes then I do not have this problem, only with this one particular scene.
Why? and how do I reset or erase the cache to "reset" this scene?
What is exactly Octane doing?
Why is that this one cinema scene file is infected and the rest not?
Thank you for your help
Ron
Re: Octane Render Cache
Posted: Thu Sep 22, 2016 9:29 am
by bepeg4d
Hi pascherheinz,
probably something weird in the specific scene

Difficult to say without seeing it

Are you using c4d native shaders?
Can you reduce the scene complexity, while still having the issue, and share it with us?
At least, could you share some screenshots?
ciao beppe
Re: Octane Render Cache
Posted: Thu Sep 22, 2016 9:41 am
by pascherheinz
Thank you for your reply,
Sadly I cannot upload the file due to copyright issues.
I also cannot screenshot the problem, because as soon as I send this particular file to the live viewer window to render then Cinema freezes and there is no reaction at all.
Attached are screenshots, Picture Renders without problem. Live Viewewr never gets the chance. Hangs at the command "copying active document"
Using real Flow Plugin for Cinema 4D with Octane shaders from the LiveDB.
Any Ideas?
Thanks
Re: Octane Render Cache
Posted: Thu Sep 22, 2016 10:35 am
by pascherheinz
- other scenes render to the liveviewer with the Real Flow Plugin without problems.
Why is this one scene problematic? maybe we will never know.
Is there a way to force Octane to start over, like a fresh scene...even if that makes sense?
Thanks for all your help and ideas
Re: Octane Render Cache
Posted: Thu Sep 22, 2016 11:07 am
by bepeg4d
Hi pascherheinz,
ok, now that I know that Real flow is involved, the issue is less unexpected.
It's not an usual condition, but a very particular one.
What do you see in console or in the octane Log window?
ciao beppe
Re: Octane Render Cache
Posted: Thu Sep 22, 2016 11:19 am
by aoktar
pascherheinz wrote:- other scenes render to the liveviewer with the Real Flow Plugin without problems.
Why is this one scene problematic? maybe we will never know.
Is there a way to force Octane to start over, like a fresh scene...even if that makes sense?
Thanks for all your help and ideas
See this topic. I did some fixes to avoid possible crashes on RF. Also Nextlimit did some work to avoid these.
As i see you're not on latest version. When you have problems always take a look newer releases and changes list.
3.03.4-R2 is your friend i suppose.
viewtopic.php?f=30&t=54924
Re: Octane Render Cache
Posted: Thu Sep 22, 2016 12:02 pm
by pascherheinz
Thanks again for all your responses.
Attached is the render log, rendering in the picture viewer. I cannot produce a live viewer render log as I freeze (must go to task manager and force stop cinema freeze) the moment I hit update.
Strangely, only in this particular scene. As said before, all other scenes with real flow work in the live viewer, so something got in (bug) and it will not get out, that is why I was asking for a clear cache, or reset function way of doing things.
Personally, it is always a huge headache, updating versions across so many different platforms we Motion Designers use, Adobe, Plugins, Cinema, etc etc and now Octane... I only update when it a functionality issue, and this is not because I can get the desired results in other cinema files, just this one in particular hangs at the "copying active document" spot in the live viewer.
Anyways if there are no ideas about resetting the cache in Octane, like it is getting the scene for a first time, then I will be forced to update and try that.
Would be strange if that resolved the problem for this one scene only, although it works in all other real flow scenes.
Thanks again for all your help and super quick replies.
PH
Re: Octane Render Cache
Posted: Thu Sep 22, 2016 1:09 pm
by bepeg4d
Hi pascherheinz,
RealFlow c4d plugin is new and the first release is dated 23 June 2016, with two patches from now:
http://www.realflow.com/news
I guess that is quite obvious that you have to keep updated, and that is not a common task especially for c4dOctane.
Please, update both plugins and let us know if the issue is gone.
ciao beppe
Re: Octane Render Cache
Posted: Wed Oct 12, 2016 11:14 am
by pascherheinz
So, after alot of testing, updating and research I can confirm that Octane and Real Flow4C4D DO NOT WORK TOGETHER.
Yes, I have updated my RealFlow plug in to its latest stand. Yes, I have updated my Octane plugin to the last release.
THE ISSUE IS NOT GONE, infact it has gotten worse. The stability is horrible to nonexistent-
So then I thought I would use the Alembic files that the RealFlow saves for its own cache. WRONG! This does not render in the Picture Viewer through Octane either.
SUMMING IT UP:
600 dollars for Octane
800 dollars for RealFlow
Renderable image = 0
So sad...truley discouraging and frustrating that I am now required to learn teh vast array of different code to operate my own product.
Re: Octane Render Cache
Posted: Wed Oct 12, 2016 11:38 am
by aoktar
I don't know why being so harsh!!! And writing this: " I can confirm that Octane and Real Flow4C4D DO NOT WORK TOGETHER."
Why it works on us and others???
You may try to give some better info and do this not after 20 DAYS.
So we can help you!