Page 10 of 31
Re: Beta 0.72 (SDK 1.20)
Posted: Fri Jul 26, 2013 10:47 pm
by NVN
aoktar....i have the next problem.
I send u a pm
Re: Beta 0.72 (SDK 1.20)
Posted: Fri Jul 26, 2013 11:11 pm
by Silverwing
I like to share a video to show incoming new editor for node based editing for materials. This is a little preview for new Material Node Editor. This is under highly WIP. Please ignore some problems, this is not final quality product.
That looks fantastic. Very well done. I´m impressed!
Keep up the good work. Cant wait to play with this!
Cheers,
Raphael
Re: Beta 0.72 (SDK 1.20)
Posted: Sat Jul 27, 2013 7:00 pm
by sphericall
Re: Beta 0.72 (SDK 1.20)
Posted: Sat Jul 27, 2013 7:09 pm
by pokeit
Do you have Turbulence FD?
In that case uninstall TFD or (this workaround possibly unstable) copy Octane.dat and Octane.dll into the Cinema 4d root directory.
I believe a workaround is being worked on...
Cheers!
Poke
Re: Beta 0.72 (SDK 1.20)
Posted: Sat Jul 27, 2013 7:24 pm
by sphericall
pokeit wrote:Do you have Turbulence FD?
copy Octane.dat and Octane.dll into the Cinema 4d root directory.
Poke
Problem solved. Ihave different Cinema home dir so the installer installed plugin into default plugins location, while older Octane plugin version still existed in the homedir plugins directory. After deleting one of them, everything runs smoothly.
Re: Beta 0.72 (SDK 1.20)
Posted: Sat Jul 27, 2013 7:49 pm
by pokeit
Jolly good!
Re: Beta 0.72 (SDK 1.20)
Posted: Mon Jul 29, 2013 8:34 am
by areafilm
I've Octane for 3DSMax and for C4D.. I must to say that in 3DSmax the engine is very stable.. not the same for C4D versione..for now.. but you are doing a great work
Re: Beta 0.72 (SDK 1.20)
Posted: Mon Jul 29, 2013 12:24 pm
by aoktar
areafilm wrote:I've Octane for 3DSMax and for C4D.. I must to say that in 3DSmax the engine is very stable.. not the same for C4D versione..for now.. but you are doing a great work
which version? still do you have any crash?
Re: Beta 0.72 (SDK 1.20)
Posted: Mon Jul 29, 2013 12:58 pm
by DennisK4
The Material Node Editor looks fantastic aoktar. Keep up the great work.
main RAM overflow
Posted: Mon Jul 29, 2013 1:40 pm
by dinf
Hi again,
Cinema crashes while rendering an animation because of RAM overflow. Not the VRAM! This is about 1GB while rendering. RAM usage is exceeding limit while rendering frame by frame until Cinema crashes. In the picture you see the line between the renderings, going up.
The scene contains static objects and keyframe animated and a huge count of baked dynamically animated objects. I first tried "Update Materials Every Frame" and "Update Meshes Every Frame" and gave all animated objects the Object Tag with different numbers. So it is starting to render fast every frame, but the main RAM flls up after a bunch of frames and is shutting down Cinema. After a while, some render instance objects weren't rendered anymore.
So I tried the "Full update Scene" option. Starting to render each frame now takes a minute longer due to the complete scene export, though RAM is also exceeded like seen in the above picture. I'm wondering about that since exporting every frame should empty more RAM in between the exports (I think the down pikes), right? But it does only a bit and fills up RAM every frame a bit more until it crashes after some frames.
I can restart the rendering at this point for the next 20 to 40 frames. And so on. This means, RAM could be cleared up more between exporting and rendering, otherwise it would be exceeded immideately after restarting Cinema. Is there another way to control the RAM usage?
