Author Topic: BIG archviz scene takes forever to load  (Read 2144 times)

2023-06-16, 22:15:24

Daniel Mikolajčák

  • Active Users
  • **
  • Posts: 174
  • ArchViz specialist
    • View Profile
    • Behance portfolio
Hi I noticed a big exterior scene loads and renders fine in v.9 but gets stuck due to low RAM in v10

2023-06-19, 10:55:31
Reply #1

burnin

  • Active Users
  • **
  • Posts: 1535
    • View Profile
Ouhmmm... comparison with specs and stats would definitely provide better 'picture'.

2023-06-19, 11:54:51
Reply #2

Daniel Mikolajčák

  • Active Users
  • **
  • Posts: 174
  • ArchViz specialist
    • View Profile
    • Behance portfolio
Hi, I am attaching some screenshots:

r26 RAM usage:
37 GB physical
43.5 GB virtual

2023 RAM usage:
52.8 GB
90.8 GB

I think it is the Laubwerk surfacespread objects, if I turn them off, the scene in 2023 renders fine

2023-06-19, 15:41:07
Reply #3

Beanzvision

  • Corona Team
  • Active Users
  • ****
  • Posts: 3873
  • Bengamin
    • View Profile
    • Cormats
Would Chaos Scatter help here? Just curious ;)
Bengamin Jerrems l
Portfolio l Click me!

2023-06-19, 16:29:15
Reply #4

Daniel Mikolajčák

  • Active Users
  • **
  • Posts: 174
  • ArchViz specialist
    • View Profile
    • Behance portfolio
I thought about it and it probably will, however, I still consider it to be a bug you may want to look at, I still work in v.9 where it works fine, I just wanted to check out v.10 and discovered this. I guess C4D cloner may have the same issue, but haven't tried it.

2023-06-20, 12:07:38
Reply #5

burnin

  • Active Users
  • **
  • Posts: 1535
    • View Profile
This sounds to me very likely to be 'old' Maxon's design flaw. (and I believe they are aware of it, just keeping quiet about it) It has also come up many times before during past decade (since 'core update', on different forums but was never properly addressed and corrected.

2023-06-21, 00:23:03
Reply #6

Stefan-L

  • Active Users
  • **
  • Posts: 514
    • View Profile
i had similar impressions, but somehow it solved it for me to set the same texture search paths as i had in r25. so it seems the search for some missing items took lot of ram and stalled my system quite.
also i had seen some hair material settings didn't transport right from r25 to r2023.

as it vanished then suddenly after solving the above, all that is only my guess, but maybe worth a try.
at least for me after some problems v10 runs fine now on 2023.2.1 also on huge scenes (3-4gb)
« Last Edit: 2023-06-21, 00:28:50 by Stefan-L »

2023-06-21, 12:15:19
Reply #7

burnin

  • Active Users
  • **
  • Posts: 1535
    • View Profile
Indeed, great logistic is 'must' ^^And I consider it common practice - always have whole WIP data accessible for processing AFAP (w/o need for reaching remote, slow or sleepy disks). That's why C4D even asks to copy maps by default... and also, why it doesn't come to mind as possible issue.

2023-06-23, 07:17:56
Reply #8

Daniel Mikolajčák

  • Active Users
  • **
  • Posts: 174
  • ArchViz specialist
    • View Profile
    • Behance portfolio
i had similar impressions, but somehow it solved it for me to set the same texture search paths as i had in r25. so it seems the search for some missing items took lot of ram and stalled my system quite.
also i had seen some hair material settings didn't transport right from r25 to r2023.

as it vanished then suddenly after solving the above, all that is only my guess, but maybe worth a try.
at least for me after some problems v10 runs fine now on 2023.2.1 also on huge scenes (3-4gb)
thank you Stefan, this worked for me, I had one path missing compared to r26, now it runs fine

2023-07-19, 21:23:14
Reply #9

Stefan-L

  • Active Users
  • **
  • Posts: 514
    • View Profile
glad i could help :)