Page 11 of 25
Re: Version 3.06
Posted: Tue May 09, 2017 6:22 pm
by lancemoody
Hello--thanks for all the work on the plugin!
I am reporting this bug but fear that my report is not properly technical. Apologies in advance.
What I am seeing that that sometimes (not always) sending an animation to the picture viewer causes a hang and Octane never advances to actually rendering frames (it sticks on Updating).
This locks up C4D and requires killing the whole task.
In every case (as I remember) this hang only happens if I have been working with the live viewer adjusting the animation and then attempting a render to the picture viewer.
Restarting and reloading the same project and immediately sending it to the picture viewer starts rendering as expected.
Thanks!
Windows 10 Build 15063
Intel 6950X
2 Titan Xps/2 1080's
256GB Ram
C4D R18
Re: Version 3.06
Posted: Tue May 09, 2017 7:29 pm
by aoktar
lancemoody wrote:Hello--thanks for all the work on the plugin!
I am reporting this bug but fear that my report is not properly technical. Apologies in advance.
What I am seeing that that sometimes (not always) sending an animation to the picture viewer causes a hang and Octane never advances to actually rendering frames (it sticks on Updating).
This locks up C4D and requires killing the whole task.
In every case (as I remember) this hang only happens if I have been working with the live viewer adjusting the animation and then attempting a render to the picture viewer.
Restarting and reloading the same project and immediately sending it to the picture viewer starts rendering as expected.
Thanks!
Windows 10 Build 15063
Intel 6950X
2 Titan Xps/2 1080's
256GB Ram
C4D R18
Can't help without know that do you have but check your scenes for these notes:
https://docs.otoy.com/#cinema-4d-v3-per ... renderings
Re: Version 3.06
Posted: Fri May 12, 2017 9:22 am
by Cheiser
Sorry for my ignorance but what do u use the ref shader for? i didnt see any documentation on this
+1 for this message, i have no idea what is ref shader node. Hope for the answer
Re: Version 3.06
Posted: Sun May 14, 2017 9:17 am
by Kretschi
Hi,
Any idea when it will be possible to render spherical video together with Adaptive Sampling and Motion Blur?
Now I must do it in 3.05 which works fine but is in some situations much slower...
Thanks for all the work.
Re: Version 3.06
Posted: Sun May 14, 2017 9:19 am
by aoktar
Cheiser wrote:Sorry for my ignorance but what do u use the ref shader for? i didnt see any documentation on this
+1 for this message, i have no idea what is ref shader node. Hope for the answer
It's a shader to allow the using of same shader in multiply inputs. Like shader instancing. I did it when node editor is not available.
Re: Version 3.06
Posted: Sun May 14, 2017 9:27 am
by aoktar
Kretschi wrote:Hi,
Any idea when it will be possible to render spherical video together with Adaptive Sampling and Motion Blur?
Now I must do it in 3.05 which works fine but is in some situations much slower...
Thanks for all the work.
It's fixed on test SDK but not available yet for public.
Re: Version 3.06
Posted: Sun May 14, 2017 9:44 am
by Kretschi
ah... great.
Thanks.
Re: Version 3.06
Posted: Sun May 14, 2017 3:21 pm
by alexchopjian
lancemoody wrote:Hello--thanks for all the work on the plugin!
I am reporting this bug but fear that my report is not properly technical. Apologies in advance.
What I am seeing that that sometimes (not always) sending an animation to the picture viewer causes a hang and Octane never advances to actually rendering frames (it sticks on Updating).
This locks up C4D and requires killing the whole task.
In every case (as I remember) this hang only happens if I have been working with the live viewer adjusting the animation and then attempting a render to the picture viewer.
Restarting and reloading the same project and immediately sending it to the picture viewer starts rendering as expected.
The exact same thing happened to me last night as I sent a render before I went to bed. I came back to check my render and it said it was still updating, and had been updating for 10 hours.
I have an extremely simple scene with a character walking in an HDRI environment, so I'm very confident nothing in my scene is set up incorrectly, especially since restarting C4D and rendering right away lets me render the scene. I have been using Octane for about a year now, and have done much more complex work with pretty insane geometries and have never ran into this until 3.06.
I hope this is an issue we can somehow diagnose, considering I use render queue a lot over the weekends at work, and I now don't know for sure whether my scene will actually send or not.
Thanks
-alex
Re: Version 3.06
Posted: Sun May 14, 2017 4:07 pm
by aoktar
alexchopjian wrote:lancemoody wrote:Hello--thanks for all the work on the plugin!
I am reporting this bug but fear that my report is not properly technical. Apologies in advance.
What I am seeing that that sometimes (not always) sending an animation to the picture viewer causes a hang and Octane never advances to actually rendering frames (it sticks on Updating).
This locks up C4D and requires killing the whole task.
In every case (as I remember) this hang only happens if I have been working with the live viewer adjusting the animation and then attempting a render to the picture viewer.
Restarting and reloading the same project and immediately sending it to the picture viewer starts rendering as expected.
The exact same thing happened to me last night as I sent a render before I went to bed. I came back to check my render and it said it was still updating, and had been updating for 10 hours.
I have an extremely simple scene with a character walking in an HDRI environment, so I'm very confident nothing in my scene is set up incorrectly, especially since restarting C4D and rendering right away lets me render the scene. I have been using Octane for about a year now, and have done much more complex work with pretty insane geometries and have never ran into this until 3.06.
I hope this is an issue we can somehow diagnose, considering I use render queue a lot over the weekends at work, and I now don't know for sure whether my scene will actually send or not.
Thanks
-alex
Well! Please send me a scene with full specs and description to reproduce here. So i can take a look for problem. Also open Octane Log window before that and check outputs.
Re: Version 3.06
Posted: Sun May 14, 2017 9:58 pm
by fatfreemedia
alexchopjian wrote:lancemoody wrote:Hello--thanks for all the work on the plugin!
I am reporting this bug but fear that my report is not properly technical. Apologies in advance.
What I am seeing that that sometimes (not always) sending an animation to the picture viewer causes a hang and Octane never advances to actually rendering frames (it sticks on Updating).
This locks up C4D and requires killing the whole task.
In every case (as I remember) this hang only happens if I have been working with the live viewer adjusting the animation and then attempting a render to the picture viewer.
Restarting and reloading the same project and immediately sending it to the picture viewer starts rendering as expected.
The exact same thing happened to me last night as I sent a render before I went to bed. I came back to check my render and it said it was still updating, and had been updating for 10 hours.
I have an extremely simple scene with a character walking in an HDRI environment, so I'm very confident nothing in my scene is set up incorrectly, especially since restarting C4D and rendering right away lets me render the scene. I have been using Octane for about a year now, and have done much more complex work with pretty insane geometries and have never ran into this until 3.06.
I hope this is an issue we can somehow diagnose, considering I use render queue a lot over the weekends at work, and I now don't know for sure whether my scene will actually send or not.
Thanks
-alex
For me this happens when a slave crashes.
It seems to prevent the master from collating all the data (? I have no real technical knowledge about how this works) and it will wait and wait until the slaves are toggled off and on via the network preferences dialogue. It often happens with fairly quick renders (under say 45 seconds a frame) when the slave can't get info from the master before the master finishes the frame.
On every shot of the project I'm working on I have had to restart the slaves. They're mixed 9 and 10 series as you can see from my signature, but it doesn't seem to matter with regards to their stability.