61
[Max] Resolved Bugs / Re: Long scene parsing 1.3
« on: 2015-11-11, 17:15:08 »
Here is the video showing one of our render nodes rendering test file locally and through BB on the same node.
2024-04-28, 22:26:18
News:
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
62
[Max] Resolved Bugs / Re: Long scene parsing 1.3
« on: 2015-11-11, 13:29:12 »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.
63
[Max] Resolved Bugs / Re: 1.3 Proxy mapping error
« on: 2015-11-10, 10:25:10 »
Many thanks. Will wait for release.
64
[Max] Resolved Bugs / Re: 1.3 Proxy mapping error
« on: 2015-11-10, 09:47:42 »
I have found that 1.3 proxy format is completely new .cgeo files. Црн so many formats for proxies and what the differences between them? Do I have to convert .cbin to .cproxy only or I can convert it to new .cgeo?
65
[Max] Resolved Bugs / Re: Long scene parsing 1.3
« on: 2015-11-10, 07:02:02 »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.
66
[Max] Resolved Bugs / 1.3 Proxy mapping error
« on: 2015-11-10, 07:00:32 »
I faced strange proxy behavior in 1.3
Some proxies (.cbin) have no mapping coordinates in 1.3. I rolled back to 1.2 and the same proxies are good with mapping coordinates. I hope no one will "help" me with advice to convert all my proxies in all projects to newer format!
Scene in attachment.
Some proxies (.cbin) have no mapping coordinates in 1.3. I rolled back to 1.2 and the same proxies are good with mapping coordinates. I hope no one will "help" me with advice to convert all my proxies in all projects to newer format!
Scene in attachment.
67
[Max] Resolved Bugs / Re: Long scene parsing 1.3
« on: 2015-11-09, 04:46:57 »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.
68
[Max] Resolved Bugs / Re: Long scene parsing 1.3
« on: 2015-11-06, 17:15:26 »Do you have bitmap paging disabled?
https://coronarenderer.freshdesk.com/support/solutions/articles/5000675862
YES. Bitmap paging disabled always and forever.
69
[Max] Resolved Bugs / Re: Long scene parsing 1.3
« on: 2015-11-05, 14:19:58 »
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.
Update:
Main big scene had no benefit from Corona bitmap conversion. 8+ minutes for scene parsing is extremely high.
70
[Max] Resolved Bugs / Re: Long scene parsing 1.3
« on: 2015-11-05, 13:20:33 »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.
71
[Max] Resolved Bugs / Re: Long scene parsing 1.3
« on: 2015-11-05, 10:24:17 »
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.
72
[Max] Resolved Bugs / Re: Long scene parsing 1.3
« on: 2015-11-05, 10:10:55 »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.
73
[Max] Resolved Bugs / Long scene parsing 1.3
« on: 2015-11-05, 07:37:18 »
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.
74
[Max] Resolved Bugs / Long scene parsing 1.3
« 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.
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.