Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] Bug Reporting => [Max] Resolved Bugs => Topic started by: Jpjapers on 2015-03-10, 16:50:08
-
Ive had max crash twice today on two seperate files when reaching the 'Parsing the scene' rendering stage when using corona. Small scenes. It just does nothing and im forced to crash out max.
I cannot send the files as they are work files and are confidential but surely its a renderer issue and not a file issue if it has occurred on two completely different files?
Jack
P.S. I Also note that this version is noticeably slower than the A7 release
-
Is there some error message/window or 3ds Max freezes and you have to close it?
Are you using displacement?
-
No error message and no displacement either :/
-
So does 3ds max freeze or just suddenly disappears?
-
Just a freeze, no errors or close i've left it for over an hour before and its definitely stuck and not just being slow.
-
Aren't you running out of memory? What's the resolution? Can you tell more about the scene?
-
Rendering at 1920x1200, i have 32gb of memory in my machine so i doubt its running out.
The scene is very basic. its a counter layout for a shop and it has less than 100k polys. It sometimes renders fine, ive had many renders from the scene, other times it completely crashes. It says parsing the scene but the progress bar stays at 0.
-
When 3ds Max is frozen, could you try saving a dump like in this article? (2. Reporting Error Messages)
https://coronarenderer.freshdesk.com/support/solutions/articles/5000524006
Maybe Ondra would take a look at it.
-
It doesnt bring up a max crash dialog unfortunately. it just stops responding completely. the only way to exit it is to end the process.
-
Yeah checking the cpu load and ram useage it has just frozen the ram and the cpu load is <1% so its a complete freeze. are there known issues with multiple lights in a scene? i have about 26 lights in the scene at the moment.
-
It doesnt bring up a max crash dialog unfortunately. it just stops responding completely. the only way to exit it is to end the process.
Please check the article again. I meant this part:
2. Reporting Error Messages
If you are experiencing a recurrent error that you are able to reproduce (for example a window shows up in 3ds Max saying "DEBUG ALERT"), please use this tool:
Process Explorer
When the error message appears, run the Process Explorer, find "3dsmax.exe" process (it is usually visible after clicking the + icon next to "explorer.exe"), select 3dsmax.exe and go to Process > Create Dump > Create Minidump... then save the file in a desired location and upload it to us using the Corona Uploader.
Create the dump when 3ds max is frozen.
-
Oh ok ill give that a go next time it crashes :)
thanks
-
Ive narrowed this down to a single set of actions.
I Render my scene, its too bright so i go and adjust my lights. When i re-render it sticks on parsing the scene. I just tried to dump out the process but it caused an unexpected reboot. This seems like a pretty big problem...
-
Does it only happen in this specific scene or also in other scenes? Can you describe in steps (1,2,3...) what you are doing?
-
It has happend in multiple scenes of diferent sizes. Step 1 i render the image after some material changes or something else. step 2 i stop the render. step 3 i adjust the lighting step 4 i render the image again. step 5 the render stops at parsing scene.
-
I seem to be getting this quite a lot recently too. Every test render has to parse the scene a few mins first. Odd thing is they were all rendering fine last week..no slow parsing..
-
Took a while to work out but what seems to have fixed it for me at least is to not have any 'network paths' for textures etc.
Copied everything locally and seems to be working fine now.
Iain
-
I have same problem in all my project files. And I use only network paths because of network rendering. It freezes very often on main computer. Now I used to press save button before rendering.
But I'm wondering why application is not freezing on network machines if the problem in network paths...
-
The issue is probably elsewhere than textures (I had this bug in latest alpha daily where it occasionally go from 5 seconds to 5 minutes after 2-3 test renders).
I use only network paths (directly mapped though, not UNC due to simplicity) and since 1.002 have few seconds parsing even for 50 consecutive test renders (although I am still chilling if it won't freeze...due to past behaviour).
-
I am using network textures yeah. I cant really change that though because if my scene is picked up by a colleague at any point they would have to manually remap them which would be a right pain. Im glad others are seeing this error too though and its not just my machine.
J
-
Hi There
Sorry to report this, but I also have had numerous Max "freezes" while "parsing the scene". Small scene, playing with fake volumetric light effect. Start, stop , adjust, re-render > freeze.
Our workstations should be up to the task, I'd say. (Viz department of a major architectural firm)
When it happened once, few days ago, it was merely "interesting". Now, after several crashes it takes a bit of the polish off your, otherwise, great product.
I am still evaluating Corona's suitability for our office.
Any thoughts?
Thanks,
Marek
-
We have recently identified many sources of possible freezes/crashed in parsing stage. Do you have access to daily builds so you could verify it it's still happening?
-
Inactive topic, moving to resolved. If you still experience the issue, feel free to create new bug report.
-
I encounter the exact same problem recently with too long times parsing. First of all, my scene was converted from vray, then the main vray scene had network paths for maps. After I converted it and start render , I got that error, and after I took all materials and check them by hand the problem still was. Then I made a search on web and found this topic. After I saw that some users said that a network maps path could cause the problem, I checked my path in asset tracking and saw that all my maps have "found" at the status instead of network (as original) or ok. Then I retrack all maps to my folder maps path and after that they got "ok" status but the problem still was there. Then I figure it out to make a new scene and copy all the objects in the new one, but the problem still was there; then I decided to create another new scene but now instead of copy all objects at one time with copy/paste script, I tooked gradualy with just one object at a time. And this way I found out that an object with some symetry modifier on top cause the problem, after I colapsed the object the problem was gone.
So I reply to this post because there wasn't a real problem answer to it and I thaught someone else like me will search for an answer and maybe they will have the same error because of some modifiers. In my case this was and colapse them it was solved. If others will have a different situation, will see.
Cheers
-
i covert everything to poly and it works for me thanks
-
i covert everything to poly and it works for me thanks
A simple fix that worked for me!!
After spending best part of a day trying all sorts of complicated things to try fix it!
could kiss ye!