Blender 3.2. - Crash while loading production scene #98662

New Issue

Christoph Werner · 2022-06-08T10:55:37+02:00

Christoph Werner commented

2022-06-08 10:55:37 +02:00

System Information
version: 3.2.0, branch: master, commit date: 2022-06-07 18:03, hash: 2161a89251, type: release
build date: 2022-06-08, 00:04:42
platform: 'Windows-10-10.0.22000-SP0' (Windows 11)

renderer: 'NVIDIA GeForce RTX 3090/PCIe/SSE2'
version: '4.5.0 NVIDIA 512.95'

Short description of error
Trying to load a scene file for a TV series, we're currently working on.
Blender crashes some seconds after the loading started. Scene will not be loaded.

Exact steps for others to reproduce the error
The scene is under NDA. I can't publish it here in the forums. If you provide a way to send it to the developers, please drop me a line.

Further infos
The scene is loading in Blender 3.0.1, it's the version we currently use for the production.
I've tried to load the scene in Blender 3.1, it works there also.

Here's the crash file I get from Blender 3.2:
blender.crash.txt

**System Information** version: 3.2.0, branch: master, commit date: 2022-06-07 18:03, hash: 2161a892519e, type: release build date: 2022-06-08, 00:04:42 platform: 'Windows-10-10.0.22000-SP0' (Windows 11) renderer: 'NVIDIA GeForce RTX 3090/PCIe/SSE2' version: '4.5.0 NVIDIA 512.95' **Short description of error** Trying to load a scene file for a TV series, we're currently working on. Blender crashes some seconds after the loading started. Scene will not be loaded. **Exact steps for others to reproduce the error** The scene is under NDA. I can't publish it here in the forums. If you provide a way to send it to the developers, please drop me a line. **Further infos** The scene is loading in Blender 3.0.1, it's the version we currently use for the production. I've tried to load the scene in Blender 3.1, it works there also. Here's the crash file I get from Blender 3.2: [blender.crash.txt](https://archive.blender.org/developer/F13138005/blender.crash.txt)

Christoph Werner commented

2022-06-08 10:55:37 +02:00

Added subscriber: @ChristophWerner

Philipp Oeser commented

2022-06-08 11:28:59 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2022-06-08 11:28:59 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Philipp Oeser commented

2022-06-08 11:28:59 +02:00

Stack trace:
blender.exe         :0x00007FF62F8D2590  blo_do_versions_300
blender.exe         :0x00007FF62F8A3A10  do_versions
blender.exe         :0x00007FF62F8A6C50  read_libraries
blender.exe         :0x00007FF62F8A22B0  blo_read_file_internal
blender.exe         :0x00007FF62F8DC1E0  BLO_read_from_file
blender.exe         :0x00007FF6349583B0  BKE_blendfile_read
blender.exe         :0x00007FF62F85E7F0  WM_file_read
blender.exe         :0x00007FF62F85DE00  wm_open_mainfile__open
blender.exe         :0x00007FF62F874EE0  wm_handler_fileselect_do
blender.exe         :0x00007FF62F876830  wm_handlers_do_intern
blender.exe         :0x00007FF62F875C90  wm_handlers_do
blender.exe         :0x00007FF62F872820  wm_event_do_handlers
blender.exe         :0x00007FF62F85C900  WM_main
blender.exe         :0x00007FF62E9411D0  main
blender.exe         :0x00007FF634953770  __scrt_common_main_seh
KERNEL32.DLL        :0x00007FFBF93054D0  BaseThreadInitThunk
ntdll.dll           :0x00007FFBFADE4830  RtlUserThreadStart

Thx reporting! Unfortunate to hear on release day ;)

But we are not in the position to handle NDA related content/scenes.
You can either make the scene public, simplify to the point of non recognition (so replace as much as possible with standin cubes or similar).
There is also the possibility to hire professional support elsewhere (e.g., the canonical support).

If this can be confirmed/reproduced though and turns out critical, a fix can be included in a corrective release.

``` Stack trace: blender.exe :0x00007FF62F8D2590 blo_do_versions_300 blender.exe :0x00007FF62F8A3A10 do_versions blender.exe :0x00007FF62F8A6C50 read_libraries blender.exe :0x00007FF62F8A22B0 blo_read_file_internal blender.exe :0x00007FF62F8DC1E0 BLO_read_from_file blender.exe :0x00007FF6349583B0 BKE_blendfile_read blender.exe :0x00007FF62F85E7F0 WM_file_read blender.exe :0x00007FF62F85DE00 wm_open_mainfile__open blender.exe :0x00007FF62F874EE0 wm_handler_fileselect_do blender.exe :0x00007FF62F876830 wm_handlers_do_intern blender.exe :0x00007FF62F875C90 wm_handlers_do blender.exe :0x00007FF62F872820 wm_event_do_handlers blender.exe :0x00007FF62F85C900 WM_main blender.exe :0x00007FF62E9411D0 main blender.exe :0x00007FF634953770 __scrt_common_main_seh KERNEL32.DLL :0x00007FFBF93054D0 BaseThreadInitThunk ntdll.dll :0x00007FFBFADE4830 RtlUserThreadStart ``` Thx reporting! Unfortunate to hear on release day ;) But we are not in the position to handle NDA related content/scenes. You can either make the scene public, simplify to the point of non recognition (so replace as much as possible with standin cubes or similar). There is also the possibility to hire professional support elsewhere (e.g., the canonical support). If this can be confirmed/reproduced though and turns out critical, a fix can be included in a corrective release.

Christoph Werner commented

2022-06-08 11:36:04 +02:00

Removed subscriber: @ChristophWerner

Christoph Werner commented

2022-06-08 11:36:05 +02:00

Added subscriber: @ChristophWerner

Christoph Werner commented

2022-06-08 11:39:46 +02:00

Thank you.

We are getting in contact with Canonical within the next days. But I hoped to get some first ideas posting it here.

I'll try to reduce the scene to a public version and post it here, if possible. Please don't close this issue meantime.

Thank you. We are getting in contact with Canonical within the next days. But I hoped to get some first ideas posting it here. I'll try to reduce the scene to a public version and post it here, if possible. Please don't close this issue meantime.

Philipp Oeser commented

2022-06-08 11:55:19 +02:00

Crash is somewhere in this function (this might give you a hint if you check what is happening there)
https://developer.blender.org/diffusion/B/browse/master/source/blender/blenloader/intern/versioning_300.c$1619

Can stuff still be appended into a fresh file? (check scenes/collections/objects piece by piece)
You could also check when this broke with builds from the archive https://builder.blender.org/download/daily/archive/

Are you building blender yourself and could launch a debugger?

Crash is somewhere in this function (this might give you a hint if you check what is happening there) https://developer.blender.org/diffusion/B/browse/master/source/blender/blenloader/intern/versioning_300.c$1619 Can stuff still be appended into a fresh file? (check scenes/collections/objects piece by piece) You could also check when this broke with builds from the archive https://builder.blender.org/download/daily/archive/ Are you building blender yourself and could launch a debugger?

Christoph Werner commented

2022-06-08 12:14:39 +02:00

In #98662#1370372, @lichtwerk wrote:
Crash is somewhere in this function (this might give you a hint if you check what is happening there)
https://developer.blender.org/diffusion/B/browse/master/source/blender/blenloader/intern/versioning_300.c$1619

Can stuff still be appended into a fresh file? (check scenes/collections/objects piece by piece)
You could also check when this broke with builds from the archive https://builder.blender.org/download/daily/archive/

Are you building blender yourself and could launch a debugger?

Scene is crashing when completely appended. I'll try to do it by using seperate objects.
We also use the whole scene objects for Grease Pencil (All objects are 3D, not painted!)
We are also using a lot of linked data and overrides. This could be a problem source, too.
I'm not building my own versions and use the daylies for Blender 3.2 tests

I drop you a line, when knowing more.

Thank you

> In #98662#1370372, @lichtwerk wrote: > Crash is somewhere in this function (this might give you a hint if you check what is happening there) > https://developer.blender.org/diffusion/B/browse/master/source/blender/blenloader/intern/versioning_300.c$1619 > > Can stuff still be appended into a fresh file? (check scenes/collections/objects piece by piece) > You could also check when this broke with builds from the archive https://builder.blender.org/download/daily/archive/ > > Are you building blender yourself and could launch a debugger? - Scene is crashing when completely appended. I'll try to do it by using seperate objects. - We also use the whole scene objects for Grease Pencil (All objects are 3D, not painted!) - We are also using a lot of linked data and overrides. This could be a problem source, too. - I'm not building my own versions and use the daylies for Blender 3.2 tests I drop you a line, when knowing more. Thank you

Christoph Werner commented

2022-06-09 10:01:56 +02:00

Small feedback about this problem:
I've spent a lot of time to reduce the scene for the problem to be reproducable. Until now I can say, some Library Overrides that were made in versions bevore Blender 3.2 are not compatible with the current release. I will try to seek for the objects inside the scene, that are responsible for this. But I don't have anough time this week to dive deeper into it, because of other projects. I'll keep you updated, when I'm back from my holiday in two weeks.

Please don't close this issue meantime.

Best wishes
Chris

Small feedback about this problem: I've spent a lot of time to reduce the scene for the problem to be reproducable. Until now I can say, some Library Overrides that were made in versions **bevore Blender 3.2** are not compatible with the current release. I will try to seek for the objects inside the scene, that are responsible for this. But I don't have anough time this week to dive deeper into it, because of other projects. I'll keep you updated, when I'm back from my holiday in two weeks. Please don't close this issue meantime. Best wishes Chris

Philipp Oeser commented

2022-06-26 16:01:49 +02:00

@ChristophWerner: since #98847 is fixed, can you recheck with a fresh buildbot build?

Christoph Werner commented

2022-06-27 13:27:00 +02:00

Hi. I'm back from my holidays.

Small feedback: Looks like Blender 3.2.1 RC loads the mentioned scene without issues. I'll make some more tests with other scenes, but it looks fine so far.

Hi. I'm back from my holidays. Small feedback: Looks like ***Blender 3.2.1 RC*** loads the mentioned scene without issues. I'll make some more tests with other scenes, but it looks fine so far.

Christoph Werner commented

2022-06-29 18:20:06 +02:00

In #98662#1380971, @ChristophWerner wrote:
Hi. I'm back from my holidays.

Small feedback: Looks like Blender 3.2.1 RC loads the mentioned scene without issues. I'll make some more tests with other scenes, but it looks fine so far.

I was a bit fast with my optimistic comment. After some more in depth tests, we still have problems loading 3.0.1 files into 3.2.1 version.
The good thing is, we CAN finally load our scenes from 3.0.1. into the current daily 3.2.1 versions. That's great and works much faster than before. But it seem there're still problems updating library overrided assets, in our case some characters. I've made additional tests and loaded the issued source rigs and characters into 3.2.1 seperately - all worked well. The sources seem to be fine. Maybe there's something wrong with the old 3.0.1 file format when using library overrides?

I still can't create a reproducable version of the problem, because the main issue seem to be a library updating problem. Realistic test environments are hard to create and not possible to just upload them, like a scene with local (not linked and overriden) assets.

Our production manager also contacted Canonical two weeks ago to get professional support, but no one answered us. Strange, because we are an professional animation studio and introduced us. We'll try it again.

I hope the upcoming daily updates will change something. It's not easy to do bug testing and work on new assets simultanously...

Best wishes
Chris

> In #98662#1380971, @ChristophWerner wrote: > Hi. I'm back from my holidays. > > Small feedback: Looks like ***Blender 3.2.1 RC*** loads the mentioned scene without issues. I'll make some more tests with other scenes, but it looks fine so far. I was a bit fast with my optimistic comment. After some more in depth tests, we still have problems loading 3.0.1 files into 3.2.1 version. The good thing is, we CAN finally load our scenes from 3.0.1. into the current daily 3.2.1 versions. That's great and works much faster than before. But it seem there're still problems updating library overrided assets, in our case some characters. I've made additional tests and loaded the issued source rigs and characters into 3.2.1 seperately - all worked well. The sources seem to be fine. Maybe there's something wrong with the old 3.0.1 file format when using library overrides? I still can't create a reproducable version of the problem, because the main issue seem to be a library updating problem. Realistic test environments are hard to create and not possible to just upload them, like a scene with local (not linked and overriden) assets. Our production manager also contacted Canonical two weeks ago to get professional support, but no one answered us. Strange, because we are an professional animation studio and introduced us. We'll try it again. I hope the upcoming daily updates will change something. It's not easy to do bug testing and work on new assets simultanously... Best wishes Chris

Philipp Oeser commented

2022-07-04 12:34:19 +02:00

@ChristophWerner: sorry to hear (both that the issue is not fully fixed as well as Canonical not responding).
So do we have a chance of some sort to a repro case?

@ChristophWerner: sorry to hear (both that the issue is not fully fixed as well as Canonical not responding). So do we have a chance of some sort to a repro case?

Christoph Werner commented

2022-07-04 14:46:46 +02:00

Still no. Problem is: There's a point where I delete the elements, and all works in 3.2.1, but the most parts are deleted. Sounds good, but isn't reproducable because it happens not always at the same point.

But I've found another interesting issue:
All seem to work, when I load the scenes into Blender 3.1.2 first (All are created in 3.0.2) and then save them out of Blender 3.1.2.
As soon as I load them into 3.2.1 RC, all is working as exected.

I'll currently doing a test with the complete sequence. We have 9 shot files here.

I'll drop an info if all works by using Blender 3.1.2 first and "covert" the files then into 3.2.1. RC.

Best wishes
Chris

Still no. Problem is: There's a point where I delete the elements, and all works in 3.2.1, but the most parts are deleted. Sounds good, but isn't reproducable because it happens not always at the same point. **But I've found another interesting issue:** All seem to work, when I load the scenes into Blender 3.1.2 first (All are created in 3.0.2) and then save them out of Blender 3.1.2. As soon as I load them into 3.2.1 RC, all is working as exected. I'll currently doing a test with the complete sequence. We have 9 shot files here. I'll drop an info if all works by using Blender 3.1.2 first and "covert" the files then into 3.2.1. RC. Best wishes Chris

David commented

2022-07-11 05:02:45 +02:00

Added subscriber: @Potato_potato

David commented

2022-07-11 05:02:45 +02:00

Hi, total newbie here.
I just noticed this and thought I should share a similar experience.

GeForce GTX 1660 Ti
Cycles, Featured set - Supported, Device - GPU compute.
When I switch over to rendered view, the scene would just hang there with a message near the top left of the viewport saying:-
loading render kernels (may take a few minutes for the first time)
Then, blender just stops responding.

Doesn't happen all the time, though.
But when it does, I just switch over from OptiX to CUDA under the Cycles Render Devices in the System Preferences.
And somehow that fixed it.

Sorry if this didn't help.

Hi, total newbie here. I just noticed this and thought I should share a similar experience. GeForce GTX 1660 Ti Cycles, Featured set - Supported, Device - GPU compute. When I switch over to rendered view, the scene would just hang there with a message near the top left of the viewport saying:- loading render kernels (may take a few minutes for the first time) Then, blender just stops responding. Doesn't happen all the time, though. But when it does, I just switch over from OptiX to CUDA under the Cycles Render Devices in the System Preferences. And somehow that fixed it. Sorry if this didn't help.

Ton Roosendaal commented

2022-07-11 09:46:33 +02:00

Added subscriber: @Ton

Ton Roosendaal commented

2022-07-11 09:46:33 +02:00

If you experience issues with Canonical's service, mail foundation@blender.org with tangible info (mails, contact info etc). We'll check on it.

Christoph Werner commented

2022-07-11 09:58:04 +02:00

In #98662#1388542, @Ton wrote:
If you experience issues with Canonical's service, mail foundation@blender.org with tangible info (mails, contact info etc). We'll check on it.

Hi Ton. Thank you for the fast feedback. I'll forward your information to our production management. It's holidays here in Germany, but we get in contact in the upcoming weeks.

> In #98662#1388542, @Ton wrote: > If you experience issues with Canonical's service, mail foundation@blender.org with tangible info (mails, contact info etc). We'll check on it. Hi Ton. Thank you for the fast feedback. I'll forward your information to our production management. It's holidays here in Germany, but we get in contact in the upcoming weeks.

Christoph Werner commented

2022-07-18 16:40:12 +02:00

Hello. I've a small update, while trying to create a REPRO file for you. It's not that easy as you think...

We've investigated more time into the problem and have the following results:

Our animated production files that were saved in Blender 2.93 doesn't work in 3.2.1. All Blender 3.2 versions crash, even the current release 3.2.1.
But if you do the following steps, then all seem to work in 3.2.1. We've made several tests and hope there'll be no more issues. Here are the steps to make our production files work:
a) We open a 2.93 file in Blender 3.0.1
b) We save the file and CLOSE Blender 3.0.1.
c) We open the saved file in Blender 3.0.1 AGAIN and save it AGAIN. (No joke) The very same file is smaller after the 2nd save.
d) Now we can open the last saved animation file without any problems in Blender 3.2.1

I hope this gives the developers some ideas, while I try to create a version that can be used for tests and published here.

I hope someone of the devs read this, please.

I'll drop a line if I have a file that can be used for tests.

Hello. I've a small update, while trying to create a REPRO file for you. It's not that easy as you think... We've investigated more time into the problem and have the following results: 1. Our animated production files that were saved in Blender 2.93 doesn't work in 3.2.1. All Blender 3.2 versions crash, even the current release 3.2.1. 2. But if you do the following steps, then all seem to work in 3.2.1. We've made several tests and hope there'll be no more issues. Here are the steps to make our production files work: a) We open a 2.93 file in Blender 3.0.1 b) We save the file and CLOSE Blender 3.0.1. c) We open the saved file in Blender 3.0.1 AGAIN and save it AGAIN. (No joke) The very same file is smaller after the 2nd save. d) Now we can open the last saved animation file without any problems in Blender 3.2.1 I hope this gives the developers some ideas, while I try to create a version that can be used for tests and published here. I hope someone of the devs read this, please. I'll drop a line if I have a file that can be used for tests.

Christoph Werner commented

2022-07-18 16:40:53 +02:00

Added subscriber: @eschwarze

Christoph Werner commented

2022-07-18 18:34:55 +02:00

IMPORTANT: Please read the post below this post. The following data can't be used as expected.

OK. Here we are. I was able to prepare a reduced file, that we use.

Before you open the file:
This version is prepared in this way:
I've used a production file that was saved in Blender 2.93 originally. I opened the file in Blender 3.0.1 and reduced it to the attached version.
Then I saved it from Blender 3.0.1 directly, without reopen it inbetween.

Unfortunately I was not able to reduce the scene directly inside a 2.93 version, because loading it there resulted in corrupted rigs. The original file from Blender 2.93 crashes Blender 3.2.x and can't be loaded there, without saving it in Blender 3.0.1 or higher first.

Nevertheless I hope this version helps the development to reproduce the problem or get an idea what's wrong.

Description how to work with this file:

Open the file in Blender 3.2.1 first. You'll see a destructed charakter. See the screenshot below for detailed infos, made in Bender 3.2.1.
To fix the problem, please open the file in Blender 3.0.1 or 3.1.2 and save it there. Saving it inside 3.2.1 doesn't fix the problem!
Now switch to Blender 3.2.1 and load the saved file. All should work and look fine now.

Important infos/questions:

The attached file is based on a file, that was originally saved in Blender 2.93. It was loaded in Blender 3.0.1 and saved there.
As soon as you reload the saved file in Blender 3.0.1 and save it there the 2nd time, without any changes, then it can be used for Blender 3.2.1.
I observed something: The files are smaller, when saved the 2nd time out of Blender 3.0.1 or 3.1.2.

Do you have an idea why the rigs are broken, when loaded in 3.2.1, without saving it in 3.0.1 first?

Thank you
Chris

Screenshots for documentation:

"Override Auto Resync" must be enabled to reproduce the problem in 3.2.1.

File for reproduction
saved_1st_time_in_301.zip

IMPORTANT: Please read the post below this post. The following data can't be used as expected. OK. Here we are. I was able to prepare a reduced file, that we use. **Before you open the file:** This version is prepared in this way: I've used a production file that was saved in Blender 2.93 originally. I opened the file in Blender 3.0.1 and reduced it to the attached version. Then I saved it from Blender 3.0.1 directly, without reopen it inbetween. Unfortunately I was not able to reduce the scene directly inside a 2.93 version, because loading it there resulted in corrupted rigs. The original file from Blender 2.93 crashes Blender 3.2.x and can't be loaded there, without saving it in Blender 3.0.1 or higher first. Nevertheless I hope this version helps the development to reproduce the problem or get an idea what's wrong. **Description how to work with this file:** 1. Open the file in Blender 3.2.1 first. You'll see a destructed charakter. See the screenshot below for detailed infos, made in Bender 3.2.1. 2. To fix the problem, please open the file in Blender 3.0.1 or 3.1.2 and save it there. Saving it inside 3.2.1 doesn't fix the problem! 3. Now switch to Blender 3.2.1 and load the saved file. All should work and look fine now. **Important infos/questions:** 1. The attached file is based on a file, that was originally saved in Blender 2.93. It was loaded in Blender 3.0.1 and saved there. 2. As soon as you reload the saved file in Blender 3.0.1 and save it there the 2nd time, without any changes, then it can be used for Blender 3.2.1. 3. I observed something: The files are smaller, when saved the 2nd time out of Blender 3.0.1 or 3.1.2. Do you have an idea why the rigs are broken, when loaded in 3.2.1, without saving it in 3.0.1 first? Thank you Chris **Screenshots for documentation:** ![119_bug_001.jpg](https://archive.blender.org/developer/F13298971/119_bug_001.jpg) "Override Auto Resync" must be enabled to reproduce the problem in 3.2.1. ![119_bug_002.jpg](https://archive.blender.org/developer/F13299164/119_bug_002.jpg) **File for reproduction** [saved_1st_time_in_301.zip](https://archive.blender.org/developer/F13298976/saved_1st_time_in_301.zip)

Christoph Werner commented

2022-07-28 09:10:17 +02:00

Bad infos: Look like there's no way for you to reproduce the problem above without having the linked data and be in our project hierarchy.

We would be very happy if someone of the developers would have time to get into this problem. Please come in contact with us. We can implement you into our workflow environment and you can investigate the issue under real conditions.

You can contact me at info(at)christoph-werner.de

Bad infos: Look like there's no way for you to reproduce the problem above without having the linked data and be in our project hierarchy. We would be very happy if someone of the developers would have time to get into this problem. Please come in contact with us. We can implement you into our workflow environment and you can investigate the issue under real conditions. You can contact me at info(at)christoph-werner.de

Philipp Oeser commented

2022-08-17 12:10:01 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Philipp Oeser commented

2022-08-17 12:10:01 +02:00

Was on parental leave and status was still stuck at "Needs Information From User", appologies.
Will change status now to get other eyes on it, still think though that commercial support is probably better suited for this kind of scenario (requirement to being implemented into a studio workflow environment to investigate in real conditions).

Was on parental leave and status was still stuck at "Needs Information From User", appologies. Will change status now to get other eyes on it, still think though that commercial support is probably better suited for this kind of scenario (requirement to being implemented into a studio workflow environment to investigate in real conditions).

Philipp Oeser commented

2022-10-11 13:36:00 +02:00

Still would like to follow up on this, but dont know how exactly:

we dont have a way to reproduce
we dont do remote triaging (as in: drop into studio environments) on this tracker

Was there really no way to replicate on a stripped down version of the scenario?

Still would like to follow up on this, but dont know how exactly: - we dont have a way to reproduce - we dont do remote triaging (as in: drop into studio environments) on this tracker Was there really no way to replicate on a stripped down version of the scenario?

Philipp Oeser commented

2022-10-11 13:36:11 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Christoph Werner commented

2022-10-11 13:59:15 +02:00

Please set this issue to archived. We're not able to reproduce nor create a simplified version for the described problem above.
We will start to work in Blender 3.3.x LTS soon.

Our latest tests shows we can work with the 3.3.x LTS version. If any new errors appear in the future, I'll create a new issue. If there's a way to create a reproducable file I will try to do this also.

Thank you for your time

Please set this issue to archived. We're not able to reproduce nor create a simplified version for the described problem above. We will start to work in Blender 3.3.x LTS soon. Our latest tests shows we can work with the 3.3.x LTS version. If any new errors appear in the future, I'll create a new issue. If there's a way to create a reproducable file I will try to do this also. Thank you for your time

Philipp Oeser commented

2022-10-11 15:03:40 +02:00

Changed status from 'Needs User Info' to: 'Archived'

Philipp Oeser closed this issue

2022-10-11 15:03:40 +02:00

Philipp Oeser commented

2022-10-11 15:03:40 +02:00

In #98662#1430725, @ChristophWerner wrote:
Our latest tests shows we can work with the 3.3.x LTS version.

Relief to hear this!

Please set this issue to archived.

OKi, will do.

> In #98662#1430725, @ChristophWerner wrote: > Our latest tests shows we can work with the 3.3.x LTS version. Relief to hear this! > Please set this issue to archived. OKi, will do.

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 3.2. - Crash while loading production scene #98662