render speed difference unreal - blender - c4d
Posted: Fri Sep 18, 2020 1:07 pm
so i have been carping and asking about this for a while now and the answers i´ve gotten made me think i was going insane.
the official word was: the performance is the same across the board between plugins. and that makes sense, its the same core.
however the experience i have had with unreal (and cinema4d) far surpassed that of blender in terms of speed (and workflow too but i will shut up about it)
i kept hearing here how octane is very fast but before i switched to unreal i felt octane is much slower than cycles in direct comparison. e-cycles vs octane was a joke.
in any case, i am fed up now and decided to do a quick test to get some proof that something is severely broken:
i have exported the scene from blender to unreal and c4d end aligned the values.
the comparison is viewport only and just aproximative because i wasted enough time on testing out blender plugin as it is.
the actual rendered region is infact larger in UE and c4d so if the comparision is biased, its towards blender.
i added c4d although i havent really updated octane plugin in a long time, still beats blender by a country mile aswell.
just look at the screenshots.
other problems with blender:
- the blender plugin is extremely slow. something i will get difference around 500% (UE was 10 seconds and blender in some instances up to 48 seconds)
- the render speed fluctates wildly. i wrote about this in a separte post. here again i have 100samples rendering at 24 seconds and 200 samples at 22secm then 200 at 35 sec.
- denoiser with camera will straight up not work all the sudden. either it stays 0 or cant move after a certain value. (screenshot 22seconds_nodenoise.jpg)
before i go on a tirade again, i really want to hear how any of this makes sense.
since ue and c4d perform well, its obviously not some driver issue.
the problem is blender plugin as i was saying for some time now.
it is, in this state, unusable. this is not a hyperbolic in the least.
the official word was: the performance is the same across the board between plugins. and that makes sense, its the same core.
however the experience i have had with unreal (and cinema4d) far surpassed that of blender in terms of speed (and workflow too but i will shut up about it)
i kept hearing here how octane is very fast but before i switched to unreal i felt octane is much slower than cycles in direct comparison. e-cycles vs octane was a joke.
in any case, i am fed up now and decided to do a quick test to get some proof that something is severely broken:
i have exported the scene from blender to unreal and c4d end aligned the values.
the comparison is viewport only and just aproximative because i wasted enough time on testing out blender plugin as it is.
the actual rendered region is infact larger in UE and c4d so if the comparision is biased, its towards blender.
i added c4d although i havent really updated octane plugin in a long time, still beats blender by a country mile aswell.
just look at the screenshots.
other problems with blender:
- the blender plugin is extremely slow. something i will get difference around 500% (UE was 10 seconds and blender in some instances up to 48 seconds)
- the render speed fluctates wildly. i wrote about this in a separte post. here again i have 100samples rendering at 24 seconds and 200 samples at 22secm then 200 at 35 sec.
- denoiser with camera will straight up not work all the sudden. either it stays 0 or cant move after a certain value. (screenshot 22seconds_nodenoise.jpg)
before i go on a tirade again, i really want to hear how any of this makes sense.
since ue and c4d perform well, its obviously not some driver issue.
the problem is blender plugin as i was saying for some time now.
it is, in this state, unusable. this is not a hyperbolic in the least.