Long Waiting before rendertime.

[dmiko]

Hello,
I have noticed that my scene takes about minute processing prior to rendering. It says: "exporting keyframe for frame time 0.00" and loads it very quickly but many times. I have not set up any animation. Does anyone have an idea what may be causing this delay?

[vladimir.nedev]

What do you mean by "quickly but many times" ?
The progress bar goes back and forth ?

How many triangles do you have in the scene ( after subdivision ) ?
Do you have any meshes where the veiwport and render levels for the subdivision do not match ?

If you imported CAD geometry, make sure to delete any extra part tags.

Greetings,
Vladimir Nedev

[dmiko]

hello Vladimir,
check out this youtube video https://youtu.be/QOPjQep_3dQ

GL: 2 000 000

I dont usually set different level of subdivision, I could be there is one mesh like this, but I doubt it.

I use bunch of vray proxies

[vladimir.nedev]

The most likely reason for this behavior is many meshes, where the viewport and render subdivision levels do not match.
The initial progress bar estimation is made based on the viewport number of triangles, since that's the only available number.
But then the actual progress is reported based on the render number of triangles.

Also I have noticed a performance bug in previous version of Modo, where mismatching viewport/render levels will lead to much much longer times to get the mesh from Modo.

If you indeed don't have any meshes like this, I will need a scene to check why this is happening.

Greetings,
Vladimir Nedev

[dmiko]

vladimir, this waiting time happens also when i render isolated mesh

[vladimir.nedev]

Can't say what's going on without a scene.
You can send it to my e-mail as well.

Greetings,
Vladimir Nedev

[dmiko]

do you need textures and proxies too? can I pack the scene? Or lxo file is enough?

[dmiko]

Hello, it must be something with proxies, as if I turn them off, the queuing disappears.

[dmiko]

Hello,
it has been after all many cushions which had render level of subdivision set to 5, was not aware of that. now it is fixed and set back to 2.
thanks for the quick diagnose vladimir,
Daniel