Hi,
Question has been asked a few times but greatly appreciate your analysis of my situation.
Octane renders image in 13seconds but the "preparing" time last over 2mins D: My fear is that my processor is too slow.
Attached my console reports. Please let me know if any other information is needed.
Model Name: Mac Pro
Model Identifier: MacPro5,1
Processor Name: 6-Core Intel Xeon
Processor Speed: 2,66 GHz
Number of Processors: 2
Total Number of Cores: 12
L2 Cache (per Core): 256 KB
L3 Cache (per Processor): 12 MB
Memory: 24 GB
Boot ROM Version: MP51.007F.B03
SMC Version (system): 1.39f5
SMC Version (processor tray): 1.39f5
Many thanks in advance.
Jai
Octane and Cinema 4D preparing time
Moderators: ChrisHekman, aoktar
You can see times for different phases of exporting the scene and also for render times.
He I cannot see here any times long as minutes.
He I cannot see here any times long as minutes.
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
If so it's not about plugin, maybe you have dynamics objects or hair, etc...jaivw93 wrote:Hey!
The preparation time is in picture viewer in cinema, I can post screen shots, but basically it gives me the message preparing for 2minutes before it starts rendering octane which then takes very little time.
Any advice?
Cheers,
Jai
They can take time to pre-build until the frame, it's a c4d thing
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
Two minutes is a bit slow, but not unreasonable, if you've got a lot of textures to convert, or special geometry to generate. But for reference, we've got a Mac very close to yours, except with 40 gigs of RAM. It's currently rendering a scene with 18 million polygons, 700 meshes, 75 reasonable res textures, using around 4 gigs of total VRAM, and it takes about 30 seconds to prepare the scene before rendering begins.
I'm guessing it's something about your scene construction that's slowing you down, not the hardware you're running it on. Are you generating a lot of procedural geometry or textures, for instance? If so, that all needs to be done ahead of time and passed off to the GPU before things can get started.
I'm guessing it's something about your scene construction that's slowing you down, not the hardware you're running it on. Are you generating a lot of procedural geometry or textures, for instance? If so, that all needs to be done ahead of time and passed off to the GPU before things can get started.
Animation Technical Director - Washington DC