Author Topic: Long scene parsing 1.3  (Read 26359 times)

2015-11-05, 07:12:35

fobus

  • Active Users
  • **
  • Posts: 388
    • View Profile
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.

2015-11-05, 07:37:18
Reply #1

fobus

  • Active Users
  • **
  • Posts: 388
    • View Profile
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.

2015-11-05, 09:48:08
Reply #2

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
can I have the scene?
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)

2015-11-05, 09:54:26
Reply #3

Nekrobul

  • Primary Certified Instructor
  • Active Users
  • ***
  • Posts: 1026
    • View Profile
I think it is the same problem with memory limit.

Try disabaling low thread priority.
---------------------------------------------------------------
https://www.blackbellstudio.com/
https://www.behance.net/blackbell3d
CEO at "Blackbell Studio"

2015-11-05, 10:10:55
Reply #4

fobus

  • Active Users
  • **
  • Posts: 388
    • View Profile
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.

2015-11-05, 10:24:17
Reply #5

fobus

  • Active Users
  • **
  • Posts: 388
    • View Profile
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.

2015-11-05, 13:20:33
Reply #6

fobus

  • Active Users
  • **
  • Posts: 388
    • View Profile
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.

2015-11-05, 14:19:58
Reply #7

fobus

  • Active Users
  • **
  • Posts: 388
    • View Profile
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.
« Last Edit: 2015-11-05, 15:09:32 by fobus »

2015-11-06, 17:13:07
Reply #8

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 12711
  • Marcin
    • View Profile
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2015-11-06, 17:15:26
Reply #9

fobus

  • Active Users
  • **
  • Posts: 388
    • View Profile

2015-11-08, 23:49:40
Reply #10

Ludvik Koutny

  • VIP
  • Active Users
  • ***
  • Posts: 2557
  • Just another user
    • View Profile
    • My Portfolio
Is there any chance some of the instances in your scene are animated?

2015-11-09, 04:46:57
Reply #11

fobus

  • Active Users
  • **
  • Posts: 388
    • View Profile
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.

2015-11-09, 15:40:13
Reply #12

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 12711
  • Marcin
    • View Profile
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?
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2015-11-10, 07:02:02
Reply #13

fobus

  • Active Users
  • **
  • Posts: 388
    • View Profile
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.

2015-11-10, 12:15:17
Reply #14

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 12711
  • Marcin
    • View Profile
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.
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us