Yet Another Parsing topic

[1equals2]

Hi all,

I have recently updated all itoo plugins, alongside with latest service pack available for 3ds max 2018.
Interactive becomes slower with every single project, no matter the scale. I can narrow the culprits down to Railclone and Forest pack.
Parsing takes 10+ min and literally makes unusable. That of course applies when scene is prepared (modelling done).

I have recently discovered that using many RailClone objects with clipping splines slows down considerably the 3ds max scene - saving, opening and parsing.
The only workaround is to convert to poly  objects once they have  been generated with RC. It is not applicable to many of the projects due to never ending comments, hence I am looking desperately to solution or workflow that limits these excessive parsing times.

By the time writing this post, I have the 3ds max file open with a project. Parsing- 15 min. Swtiching from corona camera to perspective takes 20 min to re-parse/re-load despite the use of PT.

Has anyone else experienced problems with RC alongside 3ds max and  what workarounds can suggest.

PS. Railclone used with clipping splines with "intance mode ON" produces many artefacts as well.

[dj_buckley]

Not much help but I stopped using Railclone for a while because of this issue.  I'm back using it, but as you say I have to convert to edit poly before even attempting any form of rendering.  However, I do select all Railclone objects before converting and save selected them to make sure i still have the parametric versions if necessary

[rowmanns]

Hi,

Which version of Corona are you using?

Rowan

[1equals2]

Latest officially realeased from Corona team - v5, the
Updated windows 10 to latest available builds.
Hardware is already old one, but super stable overall - xeon v4, with sufficient RAM installed.
Latest FP and RC.
I have few cars moving within scene, and rendering motion blur. Also active displacement and using the 2.5D one at 2 px. Autobump disabled.
Cars are using path constraint.

Transforming vertices with or without FP - takes 10 min.

Despite the latest updates with RC, I think  that have to change habits and stop using it for a while, until find proper solution.
Will try to collapse geometry, especially the one using splines for clipping and will post results.

[rowmanns]

Hi,

Thanks for the information. We updated to the newest iToo APIs in the v6 daily builds, so it might be worth trying this version out and seeing if there are any improvements.

If you are able to send over your scene we can look and see if anything can be done on our side to improve the parsing times..

Thanks,

Rowan

[1equals2]

Hi,

Thanks rowmanns  for the suggestions. Will see if latest v6 builds will help. Barely find any free time to delve into testing new software currently.

I have managed to reduce parsing at half. Switching all RC objects visiblity to point clouds and limitting FP scatter area  in half, resulted in much better handling of the scene.
Same scene, same file - from 10 min to 5 min.
Initially I though the issue could be due to motion blur present in scene.
Will keep posting observations.