Stuck on Starting renderer...

[voxelz]

Hi All,

I'm currently working on some projects with Corona where it get stuck on starting renderer... .
It happens random; so scene renders sometimes and ok and other times it gets stuck on starting renderer...
Same scene reach pass 2 after 03.48 min, the next test render is after 10.30 still on starting renderer... ?
Monitoring the CPU this is almost not in use, arround 7%.

No displacement is used in scene, there are render instances for the trees and other vegetation.
It try to delete setings and test fresh settings but it doesnt solve the issue.
Strange is that if i test all those scenes in Alpha 3.0 all renders fine and start on ... pass after a couple of minutes.

So i need to go back to alpha 3.0 for all my projects. :-/

Cheers

[maru]

Have you tried with the newest build? (a5 rc2)
I experienced more or less the same problem (sometimes it would freeze on render start, sometimes on render stop) and the newest build fixed it.

[riccky]

where can we download the latest build ?

[maru]

If you want to become beta tester please send me an email to miodek@corona-renderer.com.

[voxelz]

It sadly also happens with the a5 rc2 :-/
This time never ending initial pass and no CPU use...

To my impression this doesn't happen with a white standard material in the override slot!

cheers

[maru]

There are some similar problems which seem to be PC-specific (I am experiencing them too). The fix should be available soon...

[voxelz]

Any news on the stuck on starting render error?
The problem is also in the 5.1 :-/
After heavy working with corona last days on some projects this only happens when there is lot of work for the RAM.
So when using displacement or scattering lots of polys, in other cases never have this error.

Cheers

[Marvey]

did you changed the displacement screen size settings? with the new version if you change the value to 1 or 0.5 he seems to stuck on starting rendering... i hope this got fixed soon because the quality of displacement is importante with this settings.

[voxelz]

I do did change the displacement to 0.9.

cheers

[Marvey]

exactly, thats the problem

[Jaycop]

Hello voxelz and Marvey,
lowering the original value (2) to half results in quadratic (= 4 times) increasse of polygons. Of course, it requires more RAM and time for scene parsing.

[Marvey]

Hello voxelz and Marvey,
lowering the original value (2) to half results in quadratic (= 4 times) increasse of polygons. Of course, it requires more RAM and time for scene parsing.

Hi Jaycop

Yes of course i am ware of it, i have 96gb of ram and a nice cpu the prob here is it take hours if you lower to 0.5 to start rendering, and with the version rc3 it starting rendering in few seconds.

[voxelz]

I also have the feeling the r3 version could handle lots more of geometry like all versions after, scenes that get stuck are rendering without any problem if i reinstall the r3 on the same machine.

Cheers

[Marvey]

I also have the feeling the r3 version could handle lots more of geometry like all versions after, scenes that get stuck are rendering without any problem if i reinstall the r3 on the same machine.

Cheers

yeah exactly