Author Topic: 1.0 DR "Transforming vertices" waaaay too long  (Read 5905 times)

2015-02-26, 06:14:31

fobus

  • Active Users
  • **
  • Posts: 388
    • View Profile
I've discovered that "Transforming vertices" when using Displacement is much longer in 1.0 than it was in A7.2. In two of my scenes I've tested so far it was ~4 minutes in 1.0 (in A7.2 it was only 5-15 sec). Does it bug with my scenes or may be it is normal behavior in 1.0 (want to think not)?
« Last Edit: 2015-02-26, 06:28:24 by fobus »

2015-02-26, 10:44:38
Reply #1

Ondra

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

2015-02-26, 10:52:49
Reply #2

fobus

  • Active Users
  • **
  • Posts: 388
    • View Profile
I think it will be very difficult as scenes are very large. But I'll test it a bit more and will upload if it will beb more clear where and what is stucking it (if I'll find). Thank You.

2015-03-01, 19:15:07
Reply #3

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
ok, waiting for any scene - 4 minutes are waaaaay too much ;). If you zip only the scene without textures + displcement textures, it should not be that big
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)

2015-03-02, 04:36:03
Reply #4

fobus

  • Active Users
  • **
  • Posts: 388
    • View Profile
The scene is heavy itself, but as I remember in 7.2 it was much quicker to transform vertices to prepare scene before render. Unfortunately 7.2 isn't working now so I can't check this.


Scene is huge but I'll try to investigate what part of it causing this huge time to prepare.
« Last Edit: 2015-03-02, 04:54:36 by fobus »

2015-03-10, 07:28:19
Reply #5

fobus

  • Active Users
  • **
  • Posts: 388
    • View Profile
More of our scenes  (most of them) are having this behavior when rendered by network.

The same scene:

Rendered localy


Rendered by backburner:


Scene and password in PM. (0461-Atlantic-Ext_Day_Fob_14_ISO_2.rar)
« Last Edit: 2015-03-10, 11:33:50 by fobus »

2015-03-10, 12:59:12
Reply #6

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
I see you use max 2014... do you have the latest service pack installed on all computers?
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)

2015-03-10, 13:05:22
Reply #7

fobus

  • Active Users
  • **
  • Posts: 388
    • View Profile
Hm... nope. I see sp3 only installed. Will try to update it to sp5 and try again then.

2015-03-10, 13:32:22
Reply #8

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
ok, the problem could be caused by this - there is a known issue with max 2014 texmaps taking extremely long to intialize
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)

2015-03-11, 05:47:36
Reply #9

fobus

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

2015-10-21, 16:29:07
Reply #10

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
hi,
can you check this thread, if the solution applies to you? https://forum.corona-renderer.com/index.php?topic=9934
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)