Hi Chris and Ahmet,
i prepared the scene once again for sharing with other people here .it now includes the complete city (without texures/HDRI) created with the fantastic DEM-Earth_Plugin from Paul Everett)) more or less in realworldscale) and a baked driving-bus-animation (simulated with the amazing Drive-Plugin from Heyne) , combined with different cameras (stageobject-animation) with this animation/camsetup i get some "funky" unusable MB-results with cam2 and cam4 which are directly constrained with the driving bus.thanks in advance to have a look on this MB-issue and once again thank you so much for this fantastic support ahmet! whenever I have to switch the renderer ,I will immediately depressed....
Hi useruser,
can you play and see the strange movement of test text? It's correctly allocated when you stop but else of playing. I think here is a problem with constraints.
thank you!
yes! something goes wrong. the if you look with a different camera to the "fog_Sphere there is always 1 frame it lags behind the cam-move so this cant be working correctly. i try to set the priority to "generators and/ore bake the cam an the fog_Sphere and look what happens.
Workstation: Win 10 PRO 64 bit, 3,4 GHZ ,6-cores, 64 GB RAM , 4x RTX 2080 Ti
1. RenderSlave: Win 10 Pro 64 bit , 3x GTX 980Ti
2. RenderSlave: Win 10 Pro 64 bit 2x GTX 980 Ti
thanx for the updated testscene. I had a look and the text from aoktar`s scene is also not located correctly here.
This scene reminded me on a bug I realised during my last project, but hadn`t time to post yet... its related to motion blur and the stage object.
I will open a new thread to keep it organised.
ChrisVis
C4D R15 - C4DOctane 4.0 | Win7 64 | NVIDIA 417.22 | EVGA GTX 980 Ti SC | EVGA GTX 780 Ti SC |EVGA GTX 780 Ti SC
i7 4930K 6x4.3GHz OC | 64GB | ASUS P9X79-E WS
+ Netstor Turbobox 250A | 2x EVGA GTX 780 Ti SC + 2 x Palit GTX780 Ti 3GB | all watercooled
thanx for the updated testscene. I had a look and the text from aoktar`s scene is also not located correctly here.
This scene reminded me on a bug I realised during my last project, but hadn`t time to post yet... its related to motion blur and the stage object.
I will open a new thread to keep it organised.
ChrisVis
I think this is a C4D problem rather than a plugin bug. Seems that we couldn't get correct transform to produce correct motion blur. Solution should be to use a different system.
ok, maybe you are right. I also thought of it might be a general C4D problem and how c4doctane calculates motion blur. I call it bug, because it should not behave like this.
Have a look at my bug report scene in the bug subforum.
Cya,
ChrisVis
C4D R15 - C4DOctane 4.0 | Win7 64 | NVIDIA 417.22 | EVGA GTX 980 Ti SC | EVGA GTX 780 Ti SC |EVGA GTX 780 Ti SC
i7 4930K 6x4.3GHz OC | 64GB | ASUS P9X79-E WS
+ Netstor Turbobox 250A | 2x EVGA GTX 780 Ti SC + 2 x Palit GTX780 Ti 3GB | all watercooled
ok, maybe you are right. I also thought of it might be a general C4D problem and how c4doctane calculates motion blur. I call it bug, because it should not behave like this.
Have a look at my bug report scene in the bug subforum.
Cya,
ChrisVis
I can't be agree on this. It's not my job to fix the problems of C4D. They should fix this kind of strange issues and support all kind of renderers. Not only cpu renderers. Also don't forget to understand this; Our plugin is not straight renderer like others. It's a state machine and optimised for high performance and fast feedback.
useruser wrote:Hi Chris and Ahmet,
i prepared the scene once again for sharing with other people here .it now includes the complete city (without texures/HDRI) created with the fantastic DEM-Earth_Plugin from Paul Everett)) more or less in realworldscale) and a baked driving-bus-animation (simulated with the amazing Drive-Plugin from Heyne)
Hi useruser,
thank you for pointing to the Drive Plugin, that looks really neat and worth a deeper look.
I heard of the DEM-Earth Plugin. One question: The texturing is generated automatically by the plugin, right?
Any problems with octane and the plugin, or any need to tweak the texturing? Or does it work just right out of the box with C4Doctane?
Cya,
ChrisVis
C4D R15 - C4DOctane 4.0 | Win7 64 | NVIDIA 417.22 | EVGA GTX 980 Ti SC | EVGA GTX 780 Ti SC |EVGA GTX 780 Ti SC
i7 4930K 6x4.3GHz OC | 64GB | ASUS P9X79-E WS
+ Netstor Turbobox 250A | 2x EVGA GTX 780 Ti SC + 2 x Palit GTX780 Ti 3GB | all watercooled
ok, maybe you are right. I also thought of it might be a general C4D problem and how c4doctane calculates motion blur. I call it bug, because it should not behave like this.
Have a look at my bug report scene in the bug subforum.
Cya,
ChrisVis
I can't be agree on this. It's not my job to fix the problems of C4D. They should fix this kind of strange issues and support all kind of renderers. Not only cpu renderers. Also don't forget to understand this; Our plugin is not straight renderer like others. It's a state machine and optimised for high performance and fast feedback.
Hi aoktar,
don`t get me wrong here, please!
I don`t know what is going on inside the software, and what excactly is C4D and what octane related on this topic. I just use it and want to let you know, when something seems not right. Also my "stageobject motion blur bug" report I pointed to is a bit different from the topic discussed here.
Somebody should report the issue from this thread to C4D, I guess. Not sure, if they are aware of it.
Thanx,
ChrisVis
C4D R15 - C4DOctane 4.0 | Win7 64 | NVIDIA 417.22 | EVGA GTX 980 Ti SC | EVGA GTX 780 Ti SC |EVGA GTX 780 Ti SC
i7 4930K 6x4.3GHz OC | 64GB | ASUS P9X79-E WS
+ Netstor Turbobox 250A | 2x EVGA GTX 780 Ti SC + 2 x Palit GTX780 Ti 3GB | all watercooled
useruser wrote:Hi Chris and Ahmet,
i prepared the scene once again for sharing with other people here .it now includes the complete city (without texures/HDRI) created with the fantastic DEM-Earth_Plugin from Paul Everett)) more or less in realworldscale) and a baked driving-bus-animation (simulated with the amazing Drive-Plugin from Heyne)
Hi useruser,
thank you for pointing to the Drive Plugin, that looks really neat and worth a deeper look.
I heard of the DEM-Earth Plugin. One question: The texturing is generated automatically by the plugin, right?
Any problems with octane and the plugin, or any need to tweak the texturing? Or does it work just right out of the box with C4Doctane?
Cya,
ChrisVis
hi chrisVis,
sorry for the long delay!
DEM-Earth works right out of the box. you evenb dont have to convert standard-mats (created by Dem-Earth) the only thing that does not work is the brandnew Dem-gradientmat. you have to manually setup your own octane-gradient because the transition does not work if you tray to convert the native-gradientmat to an octane-mat.
btw. i fixed all problems with fog and motionblur with baking the constrainted cams. the stage-object does not work properly but this is not a problem for me personally. just render every came separatly, bake constrained cams and start render. so i will use the stage-objekt for tweaking/adjusting the whole camera-animation only.
Workstation: Win 10 PRO 64 bit, 3,4 GHZ ,6-cores, 64 GB RAM , 4x RTX 2080 Ti
1. RenderSlave: Win 10 Pro 64 bit , 3x GTX 980Ti
2. RenderSlave: Win 10 Pro 64 bit 2x GTX 980 Ti