Hello,
I am observing some strange behaviors when linking nodes in node editor, if you follow up (attached scenario) with linking the noise to the diffuse channel, live viewer looses displacement until you refresh it.
Next one is, if you follow the example above and disconnect the noise from the diffusion and hit "Get Active mat", noise node gets deleted, although it is connected to the displacement node.
This random deleting of nodes is happening many times when you leave the output empty on the node that follows noise (like gradient, color correction, mix node..), sometimes it even crashes c4d when you refresh live viewer or click "Get Active mat", but I couldn't find a chain of commands the produce the crash every time, but from my tests the crash is inevitable if you refresh regularly.
BTW the crash is not a normal crash, it hangs cinema, so you need to close it from Task Manager.
I am on win 7, R15.
Last stabile version 2.06.1 - (09.09.14)
Moderators: ChrisHekman, aoktar
thanks for feedback. It's valuable for me. This editor is not finished. I cannot call it reliable at the moment. When you call "Get Active Mat", it's normal to remove unlinked nodes. Because it does not saves to any material. But crashes(hangs) shows some problems which are still here. ATM, we are busy on some other nice improvements. I'll continue to work on this editor later.ratata wrote:Hello,
I am observing some strange behaviors when linking nodes in node editor, if you follow up (attached scenario) with linking the noise to the diffuse channel, live viewer looses displacement until you refresh it.
Next one is, if you follow the example above and disconnect the noise from the diffusion and hit "Get Active mat", noise node gets deleted, although it is connected to the displacement node.
This random deleting of nodes is happening many times when you leave the output empty on the node that follows noise (like gradient, color correction, mix node..), sometimes it even crashes c4d when you refresh live viewer or click "Get Active mat", but I couldn't find a chain of commands the produce the crash every time, but from my tests the crash is inevitable if you refresh regularly.
BTW the crash is not a normal crash, it hangs cinema, so you need to close it from Task Manager.
I am on win 7, R15.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Sure thing, I am just reporting for future reference, since nodes are vital for real production I will be testing it as much as possible, so you can get it up and running in as few iterations as possible.aoktar wrote:thanks for feedback. It's valuable for me. This editor is not finished. I cannot call it reliable at the moment. When you call "Get Active Mat", it's normal to remove unlinked nodes. Because it does not saves to any material. But crashes(hangs) shows some problems which are still here. ATM, we are busy on some other nice improvements. I'll continue to work on this editor later.
Also thank you for your hard work.
Hi Ahmed,
since I updated to V2.06.1 I have an issue with picture viewer. Regardless of objects in scene or not rendering in PV gets the attached error message.
LV is doing fine.
I also attached a log file, which is written when rendering in LV. I don't think that log data is written when PV is used because the error seems to stop everything immediately.
Standalone version is 2.06
Regards - Ron
since I updated to V2.06.1 I have an issue with picture viewer. Regardless of objects in scene or not rendering in PV gets the attached error message.
LV is doing fine.
I also attached a log file, which is written when rendering in LV. I don't think that log data is written when PV is used because the error seems to stop everything immediately.
Standalone version is 2.06
Regards - Ron
Master: WIN 10 64bit, i7 4930 4,5 Ghz, 64 GB RAM, 1600 W PSU, 1 TB SSD, 14 TB RAID, 2 x RTX 3090
Hi Ron,Ron wrote:Hi Ahmed,
since I updated to V2.06.1 I have an issue with picture viewer. Regardless of objects in scene or not rendering in PV gets the attached error message.
LV is doing fine.
I also attached a log file, which is written when rendering in LV. I don't think that log data is written when PV is used because the error seems to stop everything immediately.
Standalone version is 2.06
Regards - Ron
what Octane Log window says? In Help->Octane Log
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Hi Ahmet,
I hope thats the thread to ask: do you have any timetable on releasing an update with the 2.10 features? Especially the multipass part...
I'm working on a compositing project right now and in about 2 weeks all the rendering starts. Can i plan on using native multipass or will i have to use the workarounds i came up with so far?
Thanks:)
I hope thats the thread to ask: do you have any timetable on releasing an update with the 2.10 features? Especially the multipass part...
I'm working on a compositing project right now and in about 2 weeks all the rendering starts. Can i plan on using native multipass or will i have to use the workarounds i came up with so far?
Thanks:)
6850k // 32 GB // 1080, 1080 Ti, 2080 Ti // Win 10 // C4D 19.068
Which passes are required for your project? I'm working on to complete. Still some issues are here on adoptation some passes and workflow. But I'm thinking to release a test version tonight but not safe yet for multipasses.KeeWe wrote:Hi Ahmet,
I hope thats the thread to ask: do you have any timetable on releasing an update with the 2.10 features? Especially the multipass part...
I'm working on a compositing project right now and in about 2 weeks all the rendering starts. Can i plan on using native multipass or will i have to use the workarounds i came up with so far?
Thanks:)
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Most wantedt would be shadow but as i said, we can tweak it. Specular is left out til now but if it would be supported we would certainly use it.
Will multipass support Object buffer with motion blur and DoF? Right now we do get the Object pass from cinema but the edges are not equal to the beauty pass due the lack of MB.
A test version would be much appreciated and as i said, final rendering start is about two weeks from now.
Will multipass support Object buffer with motion blur and DoF? Right now we do get the Object pass from cinema but the edges are not equal to the beauty pass due the lack of MB.
A test version would be much appreciated and as i said, final rendering start is about two weeks from now.
6850k // 32 GB // 1080, 1080 Ti, 2080 Ti // Win 10 // C4D 19.068
I think we have not shadow pass. And Octane has not this concept. I have talked about this with Thomas to add. But i'm not sure what's the shadow on Octane. Do you have a idea? Currently we have passes are in pictures. But object pass still not as you wish. All info passes are ignoring dof and mblur. I think this should be fixed. Isn't?KeeWe wrote:Most wantedt would be shadow but as i said, we can tweak it. Specular is left out til now but if it would be supported we would certainly use it.
Will multipass support Object buffer with motion blur and DoF? Right now we do get the Object pass from cinema but the edges are not equal to the beauty pass due the lack of MB.
A test version would be much appreciated and as i saif, final rendering start is about two weeks from now.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Thanks for your quick reply.
Sadly, thats a little disapointing. Sounds like a working MP System (including the two parts i mentioned above) is still down the road.
Anyway, I'm looking forward to what Otoy and you will come up with, seems workarounds will still be a buddy for some time
Sadly, thats a little disapointing. Sounds like a working MP System (including the two parts i mentioned above) is still down the road.
Anyway, I'm looking forward to what Otoy and you will come up with, seems workarounds will still be a buddy for some time

6850k // 32 GB // 1080, 1080 Ti, 2080 Ti // Win 10 // C4D 19.068