Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] Bug Reporting => [Max] Resolved Bugs => Topic started by: fobus on 2015-11-05, 07:12:35
-
In previous versions (pre 1.3) of Corona it was "normal" to expect long (~4 min) scene parsing with backburner network rendering. But in 1.3 it grows up to impossible 6-8 minutes. Plus 3dsmax.exe process seems to be freezed as it can't be closed even by task manager for some time (at least in DR mode).
On pictures you can see scene rendered with 1 minute time limit. Scene parsing takes up to 8 minutes at random frames and servers. No DR used.
-
Local scene parsing (not via backburner network rendering) took just 40 sec. All assets are located at network server so it was not local speed improvement.
-
can I have the scene?
-
I think it is the same problem with memory limit.
Try disabaling low thread priority.
-
can I have the scene?
I'm currently trying to debug it. From first tests its look like it has something related to materials. Шэшш try to investigate it and send You scene if it will be possible.
-
Here is the simplified version of scene. It looks like it renders with backburner the same way. Look at render times from backburner at picture. All render nodes are the same PCs and located in same network near file server.
-
I think it is the same problem with memory limit.
Try disabaling low thread priority.
Low thread priority had no effect in this case. Parsing scene on some PCs way too long even with unchecked low thread priority.
-
It seems to be a bug with standart bitmap loader or smth related. I just converted all bitmaps to corona bitmaps and render times equalized between all render nodes.
Update:
Main big scene had no benefit from Corona bitmap conversion. 8+ minutes for scene parsing is extremely high.
-
Do you have bitmap paging disabled?
https://coronarenderer.freshdesk.com/support/solutions/articles/5000675862
-
Do you have bitmap paging disabled?
https://coronarenderer.freshdesk.com/support/solutions/articles/5000675862
YES. Bitmap paging disabled always and forever.
-
Is there any chance some of the instances in your scene are animated?
-
Is there any chance some of the instances in your scene are animated?
In bigger scene yes. But in part of it (https://forum.corona-renderer.com/index.php/topic,10136.msg64690.html#msg64690) therу are no animated objects.
-
Are you using in this scene proxies which were saved using the older version of Corona? What file format are you using for the proxies?
-
Are you using in this scene proxies which were saved using the older version of Corona? What file format are you using for the proxies?
Yes. There are .cbin and .cproxy format used. But scene in attachment has no one proxy and parsing from time to time as long as 4+ minutes in network rendering.
There are no network activity during it, no disk using on server side no other visible bottlenecks to slow it down.
-
Sorry, but I am not sure if I already asked this somewhere, it's hard to keep track of everything, especially with people post on the forum and in support/other places with different nicknames. ;)
Are you getting any error messages?
If you are using DR, can you:
-go to the DrData folder on the faulty node PC (it is inside DrServer installation folder)
-delete its content
-run another rendering where the parsing time is excessive
-gather the newly created content of DrData and send it to us
If you are using BB only:
-send us the BB log - https://knowledge.autodesk.com/support/3ds-max/troubleshooting/caas/sfdcarticles/sfdcarticles/How-to-find-and-analyze-your-backburner-error-logs.html
Another idea:
https://coronarenderer.freshdesk.com/support/solutions/articles/5000678431
Please see that article and check if there are any suspicious entries in the FTH log in registry.
-
Hi guys, i'm really struggling with this problem of the long parsing time...i came in to it Yesterday after dinner, when, after converting all the models and the texture, the scene simply refuse to start render, and stay in the "scene parsing state" for a huge amount of time (i let it go for 3hours, becouse i didn't notice it, my bad). So when i noticed it, i came back to the last working scene e starting over doing what i'm doing: I was converting the whole scene, an archinteriors with the use of the corona material converter..I was able to render the scene in the evening, and in the last part of the evening i finish importing the last model in my scene..But when i press render i wasn't able to actualy render the image because of the long "parsing scene" state... I tried everything, uncheck the low priority flag in the system panel, convert all the bitmap to corona bitmap via the converter, even unistall forest pack lite, and disabling the FTH for 3ds max like maru suggest i the previous post, check the bitmap paging (disabled), but nothing work...and i don't know what to do to solve this problem...
I don't know if this can help but i noticed that when the scene parsing state is processing, actually no cores is used(1.1%)..and there is a strange network activity (like 5 Mbps) ..also the ram usage is very low, 7GB for the entire scene...and i'm not rendering in DR, i'm rendering on a single machine... (i'm on a Windows 10 machine, running 3ds max as administrator)
Any help would be great..thank you again guys..have a good night.
Daniele
P.S. I'm uploading the minidump through the private uploader right now...i thought that maybe it will be useful
P.P.S. The name of the file uploaded is 1447207375_3dsmax.7z
-
Thank you for the minidump. You could even make more of them - like 3, it could be useful.
Also, are you using some custom Windows skin/theme? Do you have some special features like Aero disabled or enabled? Which version of Windows?
Are you getting any error messages from Corona's Error Messages window?
-
Are you getting any error messages?
No errors.
If you are using BB only:
-send us the BB log - https://knowledge.autodesk.com/support/3ds-max/troubleshooting/caas/sfdcarticles/sfdcarticles/How-to-find-and-analyze-your-backburner-error-logs.html
BB log with scene from attachment (in a bit previous post) attached.
Another idea:
https://coronarenderer.freshdesk.com/support/solutions/articles/5000678431
Please see that article and check if there are any suspicious entries in the FTH log in registry.
Nothing 3ds max related logged in FTH.
-
Hi maru, thank you for your time..
Right now i'm trying to reimport all the models that i have imported Yesterday, and now it seams to work as usual..i'm not done importing all the models but the majority of them doesn't make trouble with the scene..
Answering to your questions:
-No, i'm not using any custom theme for Windows and i'm on Windows 10 pro and, actually, i don't know if there is Areo on Windows 10 pro...i know that the feature called areo snap is enable..Also the last update that does not involve Windows defender is the KB3106932, and i check and don't have the last one installed (KB3105213)
-The only messages of errors i get is the one from the missing texture (but it's ok, i know that that is not linked), and the one of the vray material not converted, but they are in the override switch and they render as a corona material with default settings..
For the minidumps ok, no problem i will make Others after lunch!
(i don't know if this will help, but during the process of conversion, i noticed a huge drop down in the viewport performance, like drop from 100 fps to almost freeze for 0.5 seconds and then go straigth up to 70/80 fps for another second..and then redrop again..This drop down affect also the performance navigating through the menu of the interface...)
P.S. i Have finished to import all the models and the one that create problem are the books, wich they have a lot of textures, but i have used that ones before and they doesn't have any kind of problemin the past..anyway if this will help, i will make a minidump, with the correct scene and another with the borken scene, so maybe the problem will show up.. i will update this post with the name of the minudumps :)
-
i noticed a huge drop down in the viewport performance, like drop from 100 fps to almost freeze for 0.5 seconds and then go straigth up to 70/80 fps for another second..and then redrop again..This drop down affect also the performance navigating through the menu of the interface...)
Are you using Corona Bitmaps for the textures, or standard Bitmaps? Can you try switching to the other type and see if it changes anything about the viewport slowdown? Do you have a lot of materials with textures nested inside a multi/sub material? For example for the books?
-
Are you using Corona Bitmaps for the textures, or standard Bitmaps? Can you try switching to the other type and see if it changes anything about the viewport slowdown? Do you have a lot of materials with textures nested inside a multi/sub material? For example for the books?
Maru, i cannot thank you enough... It works!! by using the converter script i switched back from have all corona bitmap, to have all standard bitmap, and the scene started rendering again...actually i think it is also faster, (i was facing very high value of rays/sample with corona bitmap: 2300/1700 on the first pass and then dropping down till 400, now with all the standard bitmaps i have 300 rays/sample starting from 600 on the first pass)
It also increase the reactivity of the viewport and cut out the lag of the interface.. Please tell me if you need something that can help improve the usage of the coronaBitmap with a lot of texture nested inside a multisub material, like you said..i can provide the minidump of the functional scene, or the other one from the broken scene if it is necessary.. Anyway...Thank you, i really appreciate your effort..thanks again!
P.S. Sorry i forgot to mention that now the scene parsing time is 8 seconds...
-
I am glad it works now. This is a known issue, but we were not able to reproduce this on our computers yet. Here is what you could do to help us:
-send the minidumps - the more the merrier ;)
-send us the scene with all the textures and assets, and if it's impossible - a sample scene where this happens, it could be something completely new, but the problem has to be there
We would reeeeaaaly appreciate that.
-
Ok i will provide you the Whole scene with the texture and the model, it's a big scene, so it will take me some time to upload it...the fiber network coverage end like 500m from here, Italy is a very beautiful place to live........................
Anyway i'm making also Others minidumps so i will update this post with the name of the minidump and the uploaded scene when it's done..hope this will help you solve the problem.
Thank you again maru!
-
Great. Thank you. No need to hurry. Take your time.
-
Here is the video showing one of our render nodes rendering test file locally and through BB on the same node.
-
Great. Thank you. No need to hurry. Take your time.
This is the name of the two minidumps from the working and the non working scenes:
1447259433_Minidumps_Working_Not_Working_scenes.7z
P.S i'm uploading the Whole scene with the private dropbox uploader..i think in 3 hours the file will be uploaded (there is one big textures folder, but inside that, there is also 2 other folder due to the fact that i have some textures with the same name..)
-
Here is the video showing one of our render nodes rendering test file locally and through BB on the same node.
Could you see what happens if you rename the file so that it does not contain cirillic characters? Only latin ones.
Also, a minidump taken during the freeze would be great.
https://coronarenderer.freshdesk.com/support/solutions/articles/5000524006
("2. Reporting Error Messages or freezes")
-
Great. Thank you. No need to hurry. Take your time.
This is the name of the two minidumps from the working and the non working scenes:
1447259433_Minidumps_Working_Not_Working_scenes.7z
P.S i'm uploading the Whole scene with the private dropbox uploader..i think in 3 hours the file will be uploaded (there is one big textures folder, but inside that, there is also 2 other folder due to the fact that i have some textures with the same name..)
Hi,
I looked at the minidump. It was captured inside checking if one of the 286 textures used exists. But I cannot see what triggered the check. Your 3dsmax.exe does not match mine. Do you have your 3ds Max updated to the latest version (SP3 ext2)? Do you use network image paths in the scene?
-
Hi,
I looked at the minidump. It was captured inside checking if one of the 286 textures used exists. But I cannot see what triggered the check. Your 3dsmax.exe does not match mine. Do you have your 3ds Max updated to the latest version (SP3 ext2)? Do you use network image paths in the scene?
Hi Ondra, thank you for your time..sorry for the late answer but i was away fro the computer. Actually i have checked, and i have 3ds max 2015 Sp 2 with only the extension 1 installed..sorry i should have said that before.. I also wasn't able to upload the file in the dropbox private uploader, it gives me an error, simply: "an error as occured, try again later"...Can i upload the file to my dropbox and then share the link with you? (i put the file in upload again right now, but i'm not sure if it will work..)
Again, thank you for your time.
P.S. Sorry i forgot to answer to your questions about the network image: Yes, i use a nas attached to a switch as my notwork storage unit, and i know for sure that there are two texture not linked because i don't have that texture in my archive..So yes, every texture is linked to a shared network location, through the assett tracking in max..
-
sure, sharing it via your dropbox is fine
-
Ok, right now I'm uploading it in the private Dropbox uploader and it is at 41%, if it will stuck again, I will upload it to my Dropbox and then send you the link! Thank you!
update: the upload it's over, so you guys can find the file in your dropbox..hope it helps solve the problem and makes this program more awesome than it alredy is, have a nice day!
-
I'd like to thank you for that topic 100 times! - it has made my day today.
I also have huge and (unfortunately) messy scene that started to parse forever - I tried to convert every bitmap to CoronaBitmap but it was more than worse, but I was too narrow in my thinking to check the other way - converting everything to (Standard)Bitmap.
And tadaaa - everything works perfectly! :)
Thank you again - 101 time.
-
We are still really interested in obtaining a scene where this would happen ON OUR PCs.
-
We are still really interested in obtaining a scene where this would happen ON OUR PCs.
Is this scene freezes only on our nodes?
https://forum.corona-renderer.com/index.php/topic,10136.msg64690.html#msg64690
-
Just a random idea: are you using forestpack? Could you temporarily uninstall it and see if the same happens?
-
Do you use UNC location for the bitmap files?
And is your server is in local network or remote?
I do not know shurely but might be long parsing be caused by that the distant machines are trying to locate nesesary files but can not sucsede? As i noticed distant machines are downloading textures when the parsing goes on so that is why it might take forever.
But it is just an idea.
And i found this on the freshdesk.
3ds Max freezing on first rendering: There was a bug in 3ds Max 2014 causing excessive texture loading times during the first rendering.
-
Hi! Same problem width "building acc structure" long time calculation 3-4 minute, i render animation some time freze on 15th frame some time on 52th randomly freze. after restarting 3ds max work well after 10 frame again. :( 32GB ram i7 4930k max 2014 64, Corona 1.3 Plugin, Craft director studio. sorry for bad english
-
i am having the same issue, didn't know it was an issue till i saw this now, i am also using 1.3, its actually says parsing and then its stuck, fully frozen, its really big scene, up to 400 mb and i am using laubwerks for all my trees and alot of high poly models so am not sure whats going on, when this happens i have to restart 3ds max so its just a matter of saving before i start to render incase i get stuck
-
wow, now it wont even render! it parses for 20 seconds and then all is frozen and to be specific i have over 18 million polys and its a 320 mb file. idk what's going on
-
ahh so turning off low thread priority seems to solve the issue, i saw it in another post here
-
Just a random idea: are you using forestpack? Could you temporarily uninstall it and see if the same happens?
Nope.
Do you use UNC location for the bitmap files?
Yep.
And is your server is in local network or remote?
I do not know shurely but might be long parsing be caused by that the distant machines are trying to locate nesesary files but can not sucsede? As i noticed distant machines are downloading textures when the parsing goes on so that is why it might take forever.
But it is just an idea.
All textures are on their places. It's just a matter of seconds to reach them and download. No way to search it for so long.
And i found this on the freshdesk.
3ds Max freezing on first rendering: There was a bug in 3ds Max 2014 causing excessive texture loading times during the first rendering.
We have latest SP5 installed on 2014.
P.S.
Low thread priority had no effect as I wrote earlier.
-
Is this scene freezes only on our nodes?
https://forum.corona-renderer.com/index.php/topic,10136.msg64690.html#msg64690
Just because no one seems to report tests with this scene: It renders fine here (after adjusting map paths of course). 30 seconds initial frame, 12 seconds subsequent ones. Used 15 nodes, nothing unusal to be found. (Max 2014 SP3 / BB 2014.0.0.1635 / Corona 1.3)
Good Luck
-
Is this scene freezes only on our nodes?
https://forum.corona-renderer.com/index.php/topic,10136.msg64690.html#msg64690
Just because no one seems to report tests with this scene: It renders fine here (after adjusting map paths of course). 30 seconds initial frame, 12 seconds subsequent ones. Used 15 nodes, nothing unusal to be found. (Max 2014 SP3 / BB 2014.0.0.1635 / Corona 1.3)
Good Luck
Confirm that, tested on our nodes. And also can not replicate 3dsMAX 2014 Corona 1.3 Backburner 2015.0.2.1699. Local network 1+6.
Think the problem actualy is in network setup or the network drives setup. Do you use PC name or PC ip for network drive location? If you use name than you should swith it to make it work properly and the path should look like this (drive letter)\\192.168.4.7\(folder name)
-
This problem should be fixed in 1.4. Create a new topic if you still encounter problems even with the latest build
-
The same trouble. I have a big scene. Rendertime on my slow comp (i7 920) is 3.5 minutes but parsing is 1,5 minutes. Rebus farm renders each frame for 5 minutes and most of it - parsing. No idea why ((( Corona 1.5 / Max 2014
-
Can you report this issue to us? https://coronarenderer.freshdesk.com/support/tickets/new
-
if you're using forest pack like me, and use corona proxies to spread in the scene and in forest pack pro, you wanna try two things:
*disable animation mode in every Corona Proxy
*disable edge mode in Forest Pack Pro
Let me know if this helps.