Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] Bug Reporting => Topic started by: Aldoren on 2017-04-27, 16:37:50
-
Preparing geometry sometimes take 3 minutes to complete, sometimes it take 3 seconds even though nothing in the scene has changed. Why is this? How can i lower the amount of time that the render is locked to this prerender thingy?
-
Do you by any chance have ForestPack in the scene and use 3ds Max 2016 without Service Pack 4?
-
Forest pack in some scenes, but not in another. I am actually on Max 2017
-
Is noone else having a problem with this? Its very frustrating not being able to make a "quick preview render" without having to wait for the "Preparing geometry" to grind for almost 3 minutes
-
Are you using displacement in your scenes?
-
I've had this happen seemingly randomly in the past and solved the issue by merging my scene into a new file. Maybe give that a try?
-
if i'm not wrong, I remember there was a thread here that completing windows update could solve this issue.
-
So, i've tried scenes at my office, i work on a i7 5960 there and it works just fine. Render starts in a few seconds.
At home, at my 2xXeon 2650, the phase takes about 2-3 minutes. Same scene... So i suppose it comes down to this station. I've done all the windows updates, updated drivers in general, nothing works.
Also, interactive mode starts up in a few seconds, so no problem there.
Any more suggestions?
-
you could capture a minidump during the parsing, I can then take a look at it (see my signature)
-
Thank you Ondra. I've upploaded a .dmp at dropbox. :)
-
note to self: filename is
Daniel Åström - 3dsmax.zip
-
Yeah, sorry, should have specified i suppose
-
no problem ;)
-
Hi, just checking in, when could i expect a verdict? :) Can't really start up projects with Corona when this persists, so if you have any idea to what action i need to take, do tell :)
-
hi,
one weird thing is that AcIPC_2_x64 tries to read some file in 4 threads. It looks like some bridge to autocad. You could try if removing it solves the issue.
Other than that it looks like VFB refresh issue, which is scheduled to be fixed in hotfix. Can you try increasing VFB refresh interval, or zooming out, to see if it helps?