Increased "Preparation Time" between 3.03.03 R1and 3.03.4 R3

[GIOLETS]

I've made some test using the same Cinema release (R17 or R18 same results) and the same animation scene (created with 3.03.3):

I've noticed (except in case of my mystake) an increment (about +30%) of the "preparation time" needed to each frame, upgrading from 3.03 to 3.03.4

Octan Log says:
Scene created in plugin version 3030301
Scene plugin version is older than version:3.03.4-R3
Plugin will convert the parameters of displacement texture.
Animated attributes should be changed by manually

What would you mean here Ahmet? For scene created before 3.03.4 is better to assign the Object tag at the animated object?
I've tried to change also the Geometry Control from "Auto detect" to "All objects movable" but the preparation time increase even more.

Thanks for all your help.

Luca

[aoktar]

Huh! We're on 3.06. Why do you stuck on unsupported ancient version?
This message is a warning when some changes are done to provide back-ward compatibility changes on older scenes. It cannot fix animated parameters because it's complicated to do automatically.

[GIOLETS]

Sure we moved from 3.03 to 3.06 last week and have noticed the problem in animation scene.

So, for find the reason I have to switch back from version to version arriving finally to the one where the problem started.
And I've noticed this difference between 3.03.03 and 3.03.4

[aoktar]

Sure we moved from 3.03 to 3.06 last week and have noticed the problem in animation scene.

Which problem you notified?

So, for find the reason I have to switch back from version to version arriving finally to the one where the problem started.
And I've noticed this difference between 3.03.03 and 3.03.4

As i cannot go back old versions. Sometimes this can happen on versions and always i'm trying improve times.

[GIOLETS]

Sure we moved from 3.03 to 3.06 last week and have noticed the problem in animation scene.

Which problem you notified?

The problem is in the "preparation time" when i have an animation with N frames. The preparation time after the first frame (from the second one to the last) is too long, switching from 3.03.3 to 3.03.4.
An example: same scene, with 3.03.3 it took 3min to render the first frame, for the second, it took 2 seconds for preparation time, and then the normal render time (in this case, 30 seconds). If i use the 3.03.4 or newest, the first frame is the same, but from the second, the preparation time takes, in my case, 20 second, and then the normal render time (30 seconds, like the previous version.)
This for every frame in the animation.

the results are:
30 sec per frame with the older version
50 sec per frame with the newer.

[aoktar]

If you say newer is slower than 3.03.3 in this area that looks strange. You may have a partial case which can cause some hard times on Renderer's accelerator. What do you have in this scene?

[GIOLETS]

For avoid every problems related to the elements of the scene I've created a new scene with:
- a cube animated (90 frame)
- a map with a heavy texture applied on the cube
- an hdr image for lighting

my results are:

(scene created with 3.03.3)

with 3.03.3
frame 1 : 22 sec
frame 2 : 5 sec
frame 3 : 5 sec
frame 4 : 5 sec

with 3.06
frame 1 : 22-29 sec
frame 2 : 12 sec
frame 3 : 12 sec
frame 4 : 12 sec

Here I've enclosed the scene test without texture map, if you want to test I suggest to load an heavy texture for the cube in order to have some relevant Prepariong time to compare.

test_luca.rar

(50.04 KiB) Downloaded 104 times

[aoktar]

15K hdri on sky and 8k png on box. See render times. Next frames are just 1sec as should be.
We don't resend any images in scene between frames. So will not spend any extra time to reload these. Also moving an object will not cause reloading images in materials. I'm still supposing you have a different problem.

[aoktar]

Have you had somethings about Network paths in textures and Texture paths in C4D Preferences?

[GIOLETS]

Many thanks ahmet for your time and support.
We double checked about texture path but but we haven't had any problem at all.
But today we made another test: we've create a new scene, very simple, with an high texture in it (a png 15000x12000), created with octane 3.06 with very few elements. We've saved the scene and try to render it with Octane 3.06 and Octane 3.03.3.
We had the follow result:

This with Octane 3.03
Render time per frame after the first one, 2 seconds

This with Octane 3.06
Render time per frame after the first one, 6 seconds
The rendered images are different due to Sun configuration. Then we made the exactly same render image (different sun settings between 3.06 and 3.03) but we had same render time results.

3.06 have more than double render time per frame due to "preparation Time".
In top left of the screen you can see our kernel settings if you need it.
Any suggestion?