Author Topic: Urgent Help Needed on a Scene Crashing at Every Few Frames  (Read 2914 times)

2021-07-02, 08:20:48

Byteman3D

  • Active Users
  • **
  • Posts: 91
    • View Profile
I've been trying to find a way to render a 1750 frame medical animation which is crashing during render, sometimes after rendering 5 frames and sometimes not even a single frame. I have tried literally everything, and consumed all options.

Is it possible to send over a link to my Max 2022 archive scene file in private? It is about 60 mbytes.


Edit: I'm still trying to find a workaround. May be speaking early, too, but as a last resort, I turned of motion blur and depth of field on the Corona Camera object. DOF F-Stop parameter was animated. No crash yet after 4 frames. If it is related to an animated F-Stop parameter, what can be done as a workaround? DOF adds realism to medical scenes.

Thank you

« Last Edit: 2021-07-02, 08:39:46 by Byteman3D »

2021-07-02, 09:04:58
Reply #1

Frood

  • Active Users
  • **
  • Posts: 1903
    • View Profile
    • Rakete GmbH
Quick thoughts:

- Minidump?
- Animated DOF: personally I never had issues/crashes and also never heard of any
- Motion blur: if you had cam and object motion blur activated, try at least without object mb, There have been repeatedly crashes due to object motion blur (a lot have already been fixed, so what's your Corona version?)

And you can always upload a scene for investigation here:
https://corona-renderer.com/upload


Good Luck



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

2021-07-02, 09:15:35
Reply #2

Byteman3D

  • Active Users
  • **
  • Posts: 91
    • View Profile
I'll be uploading in a minute. Thank you.

I don't have any animations on motion blur parameters. I only animated the F Stop as the camera moves among different depths. But I think I'Ll be turning that off, too.

I started the scene from the drug molecule (from a drug data bank site- meaning they are small) and built the entire surrounding over it. There may be scale issues. I couldn't achieve all depths equally focused at the highest possible F-Stop value.

Corona version: 6.2 EDU license
« Last Edit: 2021-07-02, 09:59:49 by Byteman3D »

2021-07-02, 09:32:12
Reply #3

Byteman3D

  • Active Users
  • **
  • Posts: 91
    • View Profile
I have uploaded the file to dropbox.

I notice that the material of object named IGE1 (and 4 other copies of the object) renders black. That is because I was trying to replace potentially problematic materials like Skin (SSS) with simpler materials. Converted many polygon objects to mesh.
There is a substance material which I thought might be a problem but changing it  with a simple material didn't work.

The original material I use for those objects is Material #3. (The one just above the object's current material in the Material Editor)

2021-07-02, 10:30:57
Reply #4

Byteman3D

  • Active Users
  • **
  • Posts: 91
    • View Profile
I need to add one more thing:
I have rendered this scene until around frame 400. Right now I started rendering from frame 558. Crashed at 560. Frames after 400 are causing crashes.
Rendering this scene on a Dell Prec.7810 ws. Dual Xeon E52640V3. I also tested on an I7 3930 K and a Ryzen Threadripper PC. (Don't know exact specs.) That's a friend's PC.

Right now started from 561, rendered 562, saved and crashed.


2021-07-02, 10:40:24
Reply #5

romullus

  • Global Moderator
  • Active Users
  • ****
  • Posts: 8779
  • Let's move this topic, shall we?
    • View Profile
    • My Models
I have uploaded the file to dropbox.

Please leave uploaded file name here for the support person who will be looking at your issue.
I'm not Corona Team member. Everything i say, is my personal opinion only.
My Models | My Videos | My Pictures

2021-07-02, 12:13:55
Reply #6

Byteman3D

  • Active Users
  • **
  • Posts: 91
    • View Profile
Scene1_final2022.zip

It is a max archive.

I've rendered the substance maps to bitmap files and simplified the material. Still crashing in a few frames.

2021-07-02, 13:17:24
Reply #7

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 5434
    • View Profile
The minidump would be useful, as it lets us see where the crash happened - if you could upload that too, that would be helpful, in case the crash is not reproducible here. (see the link in my signature if you don't know where to find the minidump)

PS - it's also useful to mention here which version of Max was used - looks like 2022 since it wouldn't load in my 2021 ?
« Last Edit: 2021-07-02, 13:22:17 by TomG »
Tom Grimes | chaos-corona.com
Product Manager | contact us

2021-07-03, 06:57:49
Reply #8

Byteman3D

  • Active Users
  • **
  • Posts: 91
    • View Profile
I've sent the minidmp files, presumably containing the crash data from this scene yesterday and also sent a 2021 zip file(Ihope). I don't have MAx 2021 myself but saved to Max 2021 to test on other PCs.


Today I am sending the minidmp file from a friends pc with the file rendering the scene in 2021. It may be the most accurate file. I couldn't find the other two error log files (xml) for this one.

This is the file name with the usual upload method:
1625288342_SCENE1-FINAL2021-file-withminidmp.rar

2021-07-03, 08:31:04
Reply #9

TomG

  • Administrator
  • Active Users
  • *****
  • Posts: 5434
    • View Profile

2021-07-06, 13:08:50
Reply #10

Avi

  • Corona Team
  • Active Users
  • ****
  • Posts: 476
    • View Profile
Hi,

Thank you for uploading your file. I was able to investigate your scene and I was also able to reproduce the crash on my end.

The workaround for your issue is however if you delete the "Wind Binding(WSM)" in your scene then your scene does not crash anymore.

Here is a screenshot : https://prnt.sc/18zxp1a

Try deleting this & your scene will not crash anymore. However, I do not know the exact cause why this is causing this issue so, I have logged your issue into our system for further investigation.

I hope this helps.

Regards,
Avi

(Report ID=CRMAX-779)
Arpit Pandey | chaos-corona.com
3D Support Specialist - Corona | contact us

2021-07-10, 23:56:07
Reply #11

Byteman3D

  • Active Users
  • **
  • Posts: 91
    • View Profile
Thank you very much indeed Avi, and all of the team.

That was invaluable. I might think of the particles but I would never think of the wind spacewarp causing this.

I have to find a way to push the particles now.

I am very grateful.

2021-07-15, 09:17:07
Reply #12

Byteman3D

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


Here is a screenshot : https://prnt.sc/18zxp1a

Try deleting this & your scene will not crash anymore.


(Report ID=CRMAX-779)
[/quote]

It worked in this case but I needed a force to pust the particles in the right direction. I tried Gravity and the same thing seems to happen.

Any progress in determining the reason under this. Any ideas on what  I can use to force these particles without crashes?

2021-07-15, 12:49:06
Reply #13

Avi

  • Corona Team
  • Active Users
  • ****
  • Posts: 476
    • View Profile
Hi,

Thanks for getting back to us.

This issue is currently being looked at and will be fixed in a later version. However, a second workaround for your issue is to disable the multithreading in the Development rollout.

The option can be found here: https://bit.ly/2Tb3LZ1

You will not see crashes after you have disabled this option.

I hope this helps.

Regards,
Avi
Arpit Pandey | chaos-corona.com
3D Support Specialist - Corona | contact us

2021-07-16, 15:19:34
Reply #14

Byteman3D

  • Active Users
  • **
  • Posts: 91
    • View Profile
* * * I really appreciate your efforts  * * *
*    T   H   A    N    K         Y    O   U    !   *
**********************************
:D :D :D

Rendering is moving on.