Author Topic: Timeline freeze first time used  (Read 2624 times)

2021-09-16, 17:30:21

RM87

  • Users
  • *
  • Posts: 2
    • View Profile
Hi,

I have a problem that has persisted since the 3dsmax 2016, i have now 2021 version.
When I use the timeline for the first time after opening the program, it freezes for a few minutes. I managed to live with it because it was just a few minutes. And I recently discovered that the direct cause has to do with the open of slate material editor window. So, I proceeded to close the slate material editor before using the timeline.

I recently added some material libraries and the problem has increased. Now when I accidentally hit the "end" shortcut or forget to close the slate materials window, the program stops completely indefinitely. Surely have something to do with the amount of material I have in the library.

Anyone has came across with this problem? I cannot find the solution to this, if there is any.

(I've already removed the shortcut that goes to the end of the timeline)


Thanks in advance

2021-09-16, 17:56:54
Reply #1

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 12711
  • Marcin
    • View Profile
Have you tried using some scene "cleaning" tools like Prune Scene or Sini Forensic?

Is this happening only with Corona, or generally in 3ds Max?

If it's Corona only (or you observed it only with Corona), could you send us a scene where this can be reproduced?
The uploader is in my signature.
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2021-09-16, 19:26:56
Reply #2

romullus

  • Global Moderator
  • Active Users
  • ****
  • Posts: 8779
  • Let's move this topic, shall we?
    • View Profile
    • My Models
I have this problem for quite some time (3ds max 2016). I'm not sure if it's Corona related, because most often i work with scanline being set as default renderer. The issue is not consistent, sometimes it manifest itself everyday and sometimes i don't see it for weeks, or months. I never had unrecoverable freeze due to this, just a single 20-30 seconds freeze at the first scrub of timeline. I also didn't notice relation to slate editor being open or closed, i can get freeze in either case.
I'm not Corona Team member. Everything i say, is my personal opinion only.
My Models | My Videos | My Pictures

2021-09-16, 20:35:11
Reply #3

Frood

  • Active Users
  • **
  • Posts: 1903
    • View Profile
    • Rakete GmbH
I recently added some material libraries and the problem has increased.

Do those libs make use of CoronaBitmaps? If yes, try to remove them from SME and restart max. It might be a similar issue described here and below:

https://forum.corona-renderer.com/index.php?topic=21189.msg130891#msg130891

I just tested with Corona 8 DB and it's still the same. And it also happens when having scanline renderer activated after starting max.


Good Luck



Never underestimate the power of a well placed level one spell.

2021-09-17, 12:43:19
Reply #4

RM87

  • Users
  • *
  • Posts: 2
    • View Profile
Thank you for the replies.

The problem happens with a emply scene, not sure if it's corona related.

I'm using coronabitmaps in some of those libs. Like Frood said in the other thread it seams 3dsmax it's loading something in the backbround.

The more materials I add to the library, the longer the process takes, and just happens for the first time i use the timeline. (with an empty scene)

What's bothering me is trying to understand what the relationship has with the timeline.

The obvious solution it's to remove the libraries and load when i want to use it, or close the SME before i use the timeline. Not the solution i'm happy with.

Thank you.



2023-03-23, 14:03:05
Reply #5

RolandB

  • Active Users
  • **
  • Posts: 335
  • Corona fan
    • View Profile
    • Béhance portfolio
Hi all
I am digging up this topic because I have the same frozen timeline problem, and this on the different versions of 3dsMax that I have installed over time. On the 2023 it is also the case, but I do not think it comes from Corona.
As a reminder, when you move the cursor of the timeline, whether or not you are in autokey, 3dsMax freezes completely for at least a minute.

For all intents and purposes, if anyone has found a solution to this problem, I'd be happy to share it with us.
Roland
Portfolio on Béhance
http://www.behance.net/GCStudio

2023-06-29, 11:43:55
Reply #6

philipbonum

  • Active Users
  • **
  • Posts: 73
    • View Profile
So has it been confirmed this is indeed "coronabitmaps" in material libraries that does this?
I've been plagued by this issue for some time, and I have resorted to remove the timeline from my UI so I don't accidentally press it.

Can any corona devs shed som light or try this on their end? Should be quite simple to check without any scenes from us users.

I just might convert my entire library to exclusively use native bitmaps if this is the case.

2023-06-29, 11:53:50
Reply #7

romullus

  • Global Moderator
  • Active Users
  • ****
  • Posts: 8779
  • Let's move this topic, shall we?
    • View Profile
    • My Models
Since i upgraded to Max 2023 (now Max 2024) a year ago, i hadn't this issue once.
I'm not Corona Team member. Everything i say, is my personal opinion only.
My Models | My Videos | My Pictures

2023-06-29, 11:58:20
Reply #8

philipbonum

  • Active Users
  • **
  • Posts: 73
    • View Profile
Unfortunately not the same here experience here. I'm using a fresh install of Max 2024 and Corona 10.
(I still have several versions of Max installed though, but I'm not about to uninstall that)


2023-06-29, 14:34:46
Reply #9

Frood

  • Active Users
  • **
  • Posts: 1903
    • View Profile
    • Rakete GmbH
Here is what I get currently (Corona v9/v10):

Max 2023: no change, all assets are pulled from the network (-> freeze), memory usage increases to 20GB+ (empty scene)

Max 2024: all assets are pulled from the network (-> freeze), but memory usage does not increase any more

Btw: OutOfCoreCache entries (if not disabled) are generated for all assets of the material library additionally.


Good Luck



Never underestimate the power of a well placed level one spell.