Blender crush with render on all pc of the studio #120754

New Issue

William-Asperti · 2024-04-17T23:55:46+02:00

William-Asperti commented

2024-04-17 23:55:46 +02:00

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.40

Blender Version
Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: 9be62e85b727
Worked: (newest version of Blender that worked as expected)

Short description of error
I'm encountering a terrible error during the rendering phase... Also because if I render in viewport everything works perfectly, but if I then press f12 it loads a little, but as soon as it reaches the "initialising" item it freezes and then closes suddenly without giving any type of error

It is a 90 frame animation scene made up of 1 environment and 1 character.
1 furry character (made with the fur system with geo nodes) linked with overrides. I need the overrides to be able to attack the MDD Mesh cache exported from the animated scene. I also tried importing the character and connecting the cache, but it crashes anyway.

In addition to the character there is an internal environment. The structure of this environment is 1 mother scene with the links to all the elements that compose it. This mother scene is in turn linked to the lighting scene that I use for the render. For this specific shot, however, I had to do some overrides on the room, to be able to move some elements that remain in front of the shot.

There are many cases in which the scene crashes, I have made several attempts, but I can't figure it out:

_If I take the scene where the environment has all the necessary overrides, link the character, connect the MDD cache and launch the render, it crashes immediately. Only by deactivating the MDD modifier on the geometries that have the fur connected it doesn't crush.. But obviously I need the figure to move and carry the fur with it

_I also tried to do a new scene. If I just insert the character and launch the render with the cache connected it works too, but as soon as I add the environment with the necessary overrides nothing works anymore.
After the crush, if I reopen the scene and try to delete the environment, nothing works anymore... I'm forced to delete the character and reconnect the cache from scratch... I've tried all day today there's no way

I had the same problem with another scene, but it was resolved by clearing the cache modifier on the character and rebinding it again.

Maybe it's the combination of all the overrides that throws Blender into overdrive? between those on the character and those on the environment, I had to do 4/5, but I don't see any other solutions, I can't create a specific environment for each shot...

I try with my pc 3090 64gb ram (with a limitation on textures use, that take only 12gb of Vram), and also other 3 pc with 4080 and 64gb ram... the resul is the same

Exact steps for others to reproduce the error
I attach the crushlog file

**System Information** Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.40 **Blender Version** Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: `9be62e85b727` Worked: (newest version of Blender that worked as expected) **Short description of error** I'm encountering a terrible error during the rendering phase... Also because if I render in viewport everything works perfectly, but if I then press f12 it loads a little, but as soon as it reaches the "initialising" item it freezes and then closes suddenly without giving any type of error It is a 90 frame animation scene made up of 1 environment and 1 character. 1 furry character (made with the fur system with geo nodes) linked with overrides. I need the overrides to be able to attack the MDD Mesh cache exported from the animated scene. I also tried importing the character and connecting the cache, but it crashes anyway. In addition to the character there is an internal environment. The structure of this environment is 1 mother scene with the links to all the elements that compose it. This mother scene is in turn linked to the lighting scene that I use for the render. For this specific shot, however, I had to do some overrides on the room, to be able to move some elements that remain in front of the shot. There are many cases in which the scene crashes, I have made several attempts, but I can't figure it out: _If I take the scene where the environment has all the necessary overrides, link the character, connect the MDD cache and launch the render, it crashes immediately. Only by deactivating the MDD modifier on the geometries that have the fur connected it doesn't crush.. But obviously I need the figure to move and carry the fur with it _I also tried to do a new scene. If I just insert the character and launch the render with the cache connected it works too, but as soon as I add the environment with the necessary overrides nothing works anymore. After the crush, if I reopen the scene and try to delete the environment, nothing works anymore... I'm forced to delete the character and reconnect the cache from scratch... I've tried all day today there's no way I had the same problem with another scene, but it was resolved by clearing the cache modifier on the character and rebinding it again. Maybe it's the combination of all the overrides that throws Blender into overdrive? between those on the character and those on the environment, I had to do 4/5, but I don't see any other solutions, I can't create a specific environment for each shot... I try with my pc 3090 64gb ram (with a limitation on textures use, that take only 12gb of Vram), and also other 3 pc with 4080 and 64gb ram... the resul is the same **Exact steps for others to reproduce the error** I attach the crushlog file

MM_lgt_Sh08_v006__Env.crash.txt

80 KiB

William-Asperti added the

labels 2024-04-17 23:55:47 +02:00

Iliya Katushenock commented

2024-04-17 23:59:40 +02:00

Thanks for report, please, provide some way to reproduce this issue. For example, simple example file.

William-Asperti commented

2024-04-18 00:12:52 +02:00

Yes, i create this empty scene with an object and a cache MDD to attach it

Test_renderCrush.zip

1.8 MiB

Jesse Yurkovich commented

2024-04-18 00:36:37 +02:00

I can reproduce the crash with 4.0 but not with the recently released Blender 4.1. Please try 4.1 to see if this has been fixed in your full scenario: https://www.blender.org/download/

Jesse Yurkovich added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2024-04-18 00:36:48 +02:00

William-Asperti commented

2024-04-18 08:52:22 +02:00

Ok yes with 4.1.1 it works... It's not like the problem has really been solved in this way haha.
My studio should be working on an animated series, if halfway through the work you notice a similar bug, changing the blender version on all 200 PCs is no joke. especially because maybe this problem will be solved, but could switching to a different version lead to new problems that weren't there on the first one?
Which version of blender would you recommend me to use if I had to start with a production of approximately 2 years?

However, I think I have identified the error... The AOV Vector pass conflicts with the cache connected to the furry character... If you turn off the Vector pass, the rendering starts... But unfortunately I need that pass, so I will use the other version of blender this time :)

Ok yes with 4.1.1 it works... It's not like the problem has really been solved in this way haha. My studio should be working on an animated series, if halfway through the work you notice a similar bug, changing the blender version on all 200 PCs is no joke. especially because maybe this problem will be solved, but could switching to a different version lead to new problems that weren't there on the first one? Which version of blender would you recommend me to use if I had to start with a production of approximately 2 years? However, I think I have identified the error... The AOV Vector pass conflicts with the cache connected to the furry character... If you turn off the Vector pass, the rendering starts... But unfortunately I need that pass, so I will use the other version of blender this time :)

Jesse Yurkovich commented

2024-04-18 09:07:13 +02:00

The only versions of Blender that are support for the long term, 2 years, are our LTS versions: https://www.blender.org/download/lts/. Blender 3.3 and 3.6 are the current LTS versions right now, and 4.2 will be the next one to be released sometime in July. Non LTS versions have very little support between releases. Ideally, if your (large) studio is comfortable with taking on the risk of using non LTS versions, or even when using LTS, a strong technical director & team comfortable with making changes to Blender and producing your own builds is definitely the way to go to tailor your experience really.

Of course new versions can have new problems etc. though we obviously try not to have that happen. Notably 4.1 does have changes in how smooth-shading works for meshes that affect both internal working and user-facing workflow. Though using 4.1 on a render-farm to do your rendering while the artists and larger portion of the studio remains on 4.0 could also be something for you to explore.

Getting back to this bug, no further releases are planned for 4.0 so yes, you'll need another version.

The only versions of Blender that are support for the long term, 2 years, are our LTS versions: https://www.blender.org/download/lts/. Blender 3.3 and 3.6 are the current LTS versions right now, and 4.2 will be the next one to be released sometime in July. Non LTS versions have very little support between releases. Ideally, if your (large) studio is comfortable with taking on the risk of using non LTS versions, or even when using LTS, a strong technical director & team comfortable with making changes to Blender and producing your own builds is definitely the way to go to tailor your experience really. Of course new versions can have new problems etc. though we obviously try not to have that happen. Notably 4.1 does have changes in how smooth-shading works for meshes that affect both internal working and user-facing workflow. Though using 4.1 on a render-farm to do your rendering while the artists and larger portion of the studio remains on 4.0 could also be something for you to explore. Getting back to this bug, no further releases are planned for 4.0 so yes, you'll need another version.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Blender crush with render on all pc of the studio #120754