CUDA error on RTX 4090 if using Volumetrics in scene #114035

New Issue

Closed

opened 2023-10-22 17:24:39 +02:00 by ShizzyZzZzZz · 13 comments

ShizzyZzZzZz commented 2023-10-22 17:24:39 +02:00

Copy Link

System Information
Operating system: Windows 11
Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.42

Blender Version
Broken: version: 3.6.4, branch: blender-v3.6-release, commit date: 2023-09-25 13:24, hash: 21bfc5e7fe3f This happens on all versions of blender, on all previous ones after 3.5 version
Worked: (newest version of Blender that worked as expected)

Short description of error
When adding object like sphere or box in to the scene with transparent shader node and volume scatter node most of the times after you doing pre-redner of vieport it gives me an error[first screenshot]

Illegal address in CUDA queue copy_from_device (integrator_shade_surface integrator_sorted_paths_array integrator_compact_shadow_states prefix_sum)

after that rendered section freezes and only pressing "Z" or switching in solid mode gives you ability to navigate, and working in general without any problems, but you can not use render option, because when you trying to start another pre-redner it gives you another error message [second screenshot]

Failed to create CUDA context (Illegal address)

to fix that you need to restart blender completely, reloading project not helping, only complete restart.

This happens only when using volumetrics, and the bigger object the bigger chance to get that error. But when you just start finish render it goes well, i got this error on finish render only 2 times, like from 100~ so it's more like accident, but in viewport it's 95% chance to get this error at start of the processing pre-render of the viewport, sometimes it happens after 40-100 samples, sometimes after 300+ sometimes it is not happens at all, but most of the time it happens around 40-100 samples, unfortunately i can not share any of my scenes, but i can say it's mostly people with complex pbr skin shaders, multyscattering levels and etc, memory usage in acceptable limits so this is not the case, because this also happens when i just rendering single human model on hdri background, where gpu memory usage around 5-8gb, it's happens only on 4090, i tested it on my laptop with 1060 and everything works fine.

Exact steps for others to reproduce the error

• Using global volume scatter on world or adding object with transparent and volume scatter nodes

UPT 31.10.2023:

I found 1 pattern in which the error occurs more often. When you selecting limited region for render and scrolling in to it with pre-render on in viewport, you can get this error more often when zooming too close to that region[screenshot 3] Also using DOF with Empty sphere as target for focus, just in case.

**System Information** Operating system: Windows 11 Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.42 **Blender Version** Broken: version: 3.6.4, branch: blender-v3.6-release, commit date: 2023-09-25 13:24, hash: `21bfc5e7fe3f` This happens on all versions of blender, on all previous ones after 3.5 version Worked: (newest version of Blender that worked as expected) **Short description of error** When adding object like sphere or box in to the scene with transparent shader node and volume scatter node most of the times after you doing pre-redner of vieport it gives me an error[**first screenshot**] ``` Illegal address in CUDA queue copy_from_device (integrator_shade_surface integrator_sorted_paths_array integrator_compact_shadow_states prefix_sum) ``` after that rendered section freezes and only pressing "Z" or switching in solid mode gives you ability to navigate, and working in general without any problems, but you can not use render option, because when you trying to start another pre-redner it gives you another error message [**second screenshot**] ``` Failed to create CUDA context (Illegal address) ``` to fix that you need to restart blender completely, reloading project not helping, only complete restart. This happens only when using volumetrics, and the bigger object the bigger chance to get that error. But when you just start finish render it goes well, i got this error on finish render only 2 times, like from 100~ so it's more like accident, but in viewport it's 95% chance to get this error at start of the processing pre-render of the viewport, sometimes it happens after 40-100 samples, sometimes after 300+ sometimes it is not happens at all, but most of the time it happens around 40-100 samples, unfortunately i can not share any of my scenes, but i can say it's mostly people with complex pbr skin shaders, multyscattering levels and etc, memory usage in acceptable limits so this is not the case, because this also happens when i just rendering single human model on hdri background, where gpu memory usage around 5-8gb, it's happens only on 4090, i tested it on my laptop with 1060 and everything works fine. **Exact steps for others to reproduce the error** - Using global volume scatter on world or adding object with transparent and volume scatter nodes UPT 31.10.2023: I found 1 pattern in which the error occurs more often. When you selecting limited region for render and scrolling in to it with pre-render on in viewport, you can get this error more often when zooming too close to that region[screenshot 3] Also using DOF with Empty sphere as target for focus, just in case.

12.png

942 KiB

123.png

1.1 MiB

111.png

707 KiB

ShizzyZzZzZz added the

Status

Needs Triage

Priority

Normal

Type

Report

labels 2023-10-22 17:24:40 +02:00

Jesse Yurkovich commented 2023-10-23 04:00:13 +02:00

Member

Copy Link

I'm not able to reproduce using a 4090 here. Can you provide a small .blend file that can be used or a better set of steps to follow?

I'm not able to reproduce using a 4090 here. Can you provide a small .blend file that can be used or a better set of steps to follow? 

image.png

1.7 MiB

Jesse Yurkovich added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-10-23 04:00:23 +02:00

ShizzyZzZzZz commented 2023-10-23 11:10:11 +02:00

Author

Copy Link

As i said in post i can not provide any scenes with my models, and as i said this problem happens when scene have complex models and shaders on them with multy-layered scattering for pbr skin shading, also alot of glassy refraction and etc, the more complex scene the higher chance of this errors, in simple scenes everything wortks fine. In that scene(nsfw) from screenshots i used limited box with volumetric and noise texture for volume vibrance as sauna's steam, also there is water shader with refrection, and fluid shader which uses and refraction and volume scatter shading on it. There is 3 human models with pbr skin shaders with additional stuff like polygonal hairs with alot textures with alpha-channels, so scene is complicated. and my light paths setup is kinda expensive for resources, like alot for transparency and also for volume, in older versions i used 1 for volume and 12 for transparency, but in that case volume is very poor on details and etc, so this can be also the case... i don't know)

As i said in post i can not provide any scenes with my models, and as i said this problem happens when scene have complex models and shaders on them with multy-layered scattering for pbr skin shading, also alot of glassy refraction and etc, the more complex scene the higher chance of this errors, in simple scenes everything wortks fine. In that scene(nsfw) from screenshots i used limited box with volumetric and noise texture for volume vibrance as sauna's steam, also there is water shader with refrection, and fluid shader which uses and refraction and volume scatter shading on it. There is 3 human models with pbr skin shaders with additional stuff like polygonal hairs with alot textures with alpha-channels, so scene is complicated. and my light paths setup is kinda expensive for resources, like alot for transparency and also for volume, in older versions i used 1 for volume and 12 for transparency, but in that case volume is very poor on details and etc, so this can be also the case... i don't know)

123123.png

20 KiB

Jesse Yurkovich added

Status

Needs Triage

and removed

Status

Needs Information from User

labels 2023-10-23 11:21:50 +02:00

Germano Cavalcante commented 2023-10-23 21:13:36 +02:00

Member

Copy Link

Thanks for the report, @ShizzyZzZzZz. Usually, before forwarding it to the developers, the report is first confirmed by a triage team (necessary due to the large flow of daily bug reports).

While we understand that you are unable to share your production files, it would be helpful if you could try to reproduce the issue in a simplified setup and provide an example .blend file that triggers the issue. This will allow us to investigate the issue more effectively.

To better understand the problem, could you please clarify the following:

• Does the error occur consistently when using any specific settings or configurations with the transparent shader and volume scatter nodes? Are there any specific values or parameters that trigger the error more frequently?

• Have you tried adjusting the CUDA settings in Blender? For example, changing the tile size or enabling/disabling GPU features like OptiX denoising. If so, did it have any effect on the issue?

Based on the information provided, here are a few possible causes and solutions for the error you're encountering:

1. GPU memory limitations: The error could be related to the GPU running out of memory when rendering scenes with volumetrics. Try reducing the complexity of the scene, such as lowering the number of scattering levels or simplifying the PBR skin shaders, to see if it helps alleviate the issue.

2. CUDA compatibility: There might be a compatibility issue between Blender and the CUDA version used by the RTX 4090. Make sure you're using the latest version of Blender and CUDA, and check if there are any known issues or updates related to CUDA support for your graphics card.

3. Software bug: It's possible that the error is caused by a bug in Blender. Since you mentioned that the issue started occurring after a specific version (3.5), it would be helpful to know if you encountered the problem in any earlier versions. If you have access to older versions of Blender, please try rendering the same scene to see if the error persists.

Also, based on the error messages, this issue may be related, or even a duplicate of one of these others:
#110175: CUDA misaligned address error when rendering the image
#110657: Blender Cycles "Launch failed in CUDA queue copy from device (integrator_intersect_shadow)"
#112843: Error when editing displacement values: Illegal address in CUDA queue copy_from_device
#113212: Illegal adrees in CUDA queue copy_from_device
#113709: Blender Crashing Mid-Render
#112880: Blender lockup/stops responding on Pop!_OS 22.04
#113521: Cycles renderer only loads 1 texture when set to GPU compute
#105623: Mesh to Volume crash on small geometry
#111639: "Illegal address in CUDA queue" error occurs when I use both Principled BSDF and Adaptive Subdivision

Thanks for the report, @ShizzyZzZzZz. Usually, before forwarding it to the developers, the report is first confirmed by a triage team (necessary due to the large flow of daily bug reports). While we understand that you are unable to share your production files, it would be helpful if you could try to reproduce the issue in a simplified setup and provide an example .blend file that triggers the issue. This will allow us to investigate the issue more effectively. To better understand the problem, could you please clarify the following: - Does the error occur consistently when using any specific settings or configurations with the transparent shader and volume scatter nodes? Are there any specific values or parameters that trigger the error more frequently? - Have you tried adjusting the CUDA settings in Blender? For example, changing the tile size or enabling/disabling GPU features like OptiX denoising. If so, did it have any effect on the issue? Based on the information provided, here are a few possible causes and solutions for the error you're encountering: 1. GPU memory limitations: The error could be related to the GPU running out of memory when rendering scenes with volumetrics. Try reducing the complexity of the scene, such as lowering the number of scattering levels or simplifying the PBR skin shaders, to see if it helps alleviate the issue. 2. CUDA compatibility: There might be a compatibility issue between Blender and the CUDA version used by the RTX 4090. Make sure you're using the latest version of Blender and CUDA, and check if there are any known issues or updates related to CUDA support for your graphics card. 3. Software bug: It's possible that the error is caused by a bug in Blender. Since you mentioned that the issue started occurring after a specific version (3.5), it would be helpful to know if you encountered the problem in any earlier versions. If you have access to older versions of Blender, please try rendering the same scene to see if the error persists. Also, based on the error messages, this issue may be related, or even a duplicate of one of these others: #110175: CUDA misaligned address error when rendering the image #110657: Blender Cycles "Launch failed in CUDA queue copy from device (integrator_intersect_shadow)" #112843: Error when editing displacement values: Illegal address in CUDA queue copy_from_device #113212: Illegal adrees in CUDA queue copy_from_device #113709: Blender Crashing Mid-Render #112880: Blender lockup/stops responding on Pop!_OS 22.04 #113521: Cycles renderer only loads 1 texture when set to GPU compute #105623: Mesh to Volume crash on small geometry #111639: "Illegal address in CUDA queue" error occurs when I use both Principled BSDF and Adaptive Subdivision

Germano Cavalcante added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-10-23 21:13:48 +02:00

ShizzyZzZzZz commented 2023-10-24 14:52:08 +02:00

Author

Copy Link

As ia said it happens ONLY when using volumetrics in scene, it doesn't matter if it's global volumetrics or applied to object for limited volumetrics. Usual setup of my working scene is:

1. Hdri map, in viewport, i using from 4K to 8K resolution for good performance in viewport and 10k-16k for final render.
2. Enviroment objects such as rooms or just furniture, nothing special, using PBR materials from Poligon or PBR assets created by me in Substance Painter, not the case.
3. Main models - People, as described before with comlex material of which i can not share too, because it's paid thing which i don't want to share with anyone. I only can show some math nodes for SSS radius and for Specular IOR.
   In general multySSS shader based on 3 principled shaders[Multiscatter GGX, Random Walk(Fixed Radius)]
4. This is not VRAM problem, as i showed on screenshot earlier im not reaching limits of VRAM, it just hepeens more often when scene is more complex and have a lot of stuff, but sometimes it happens even with simple scene, like simple pinup with one person, where average VRAM usage = 7-11gb in general.
5. In vieport i do not using any denoising features, my "System" setup is right now "OptiX" i will try to switch to just "CUDA" and test it today with my scenes. Will make an update if something will change in better or in worst way.

The problem is happens always accidentaly, so i can not track exact reason why it happend or what triggered it, sometimes it happens just at start of prerender in vieport, sometimes it happens when im trying to scale up by mouse wheel the frame from camera view, sometimes it happens when im trying to move something in scene like lights while prerender is active to find better lighting, but as i said i can not see dependency between my actions, so it's super annoying because i don't know what to do to avoid that problem.

I have an assumption that this may be a problem associated with a large number of calculations of shadows and volumetrics in polygonal hairstyles with a large number of textures with alpha channels, since the limit of calculations is 64 for transparency, then perhaps at some depth an error occurs related to volumetrics, which the blender also tries calculate along with the transparency of the textures and the shadow cast by them. I also use "translucent" to have it on outline of the hair, screenshot of hair material is attached.

As ia said it happens ONLY when using volumetrics in scene, it doesn't matter if it's global volumetrics or applied to object for limited volumetrics. Usual setup of my working scene is: 1. Hdri map, in viewport, i using from 4K to 8K resolution for good performance in viewport and 10k-16k for final render. 2. Enviroment objects such as rooms or just furniture, nothing special, using PBR materials from Poligon or PBR assets created by me in Substance Painter, not the case. 3. Main models - People, as described before with comlex material of which i can not share too, because it's paid thing which i don't want to share with anyone. I only can show some math nodes for SSS radius and for Specular IOR. In general multySSS shader based on 3 principled shaders[Multiscatter GGX, Random Walk(Fixed Radius)] 4. This is not VRAM problem, as i showed on screenshot earlier im not reaching limits of VRAM, it just hepeens more often when scene is more complex and have a lot of stuff, but sometimes it happens even with simple scene, like simple pinup with one person, where average VRAM usage = 7-11gb in general. 5. In vieport i do not using any denoising features, my "System" setup is right now "OptiX" i will try to switch to just "CUDA" and test it today with my scenes. Will make an update if something will change in better or in worst way. The problem is happens always accidentaly, so i can not track exact reason why it happend or what triggered it, sometimes it happens just at start of prerender in vieport, sometimes it happens when im trying to scale up by mouse wheel the frame from camera view, sometimes it happens when im trying to move something in scene like lights while prerender is active to find better lighting, but as i said i can not see dependency between my actions, so it's super annoying because i don't know what to do to avoid that problem. I have an assumption that this may be a problem associated with a large number of calculations of shadows and volumetrics in polygonal hairstyles with a large number of textures with alpha channels, since the limit of calculations is 64 for transparency, then perhaps at some depth an error occurs related to volumetrics, which the blender also tries calculate along with the transparency of the textures and the shadow cast by them. I also use "translucent" to have it on outline of the hair, screenshot of hair material is attached.

2ior.png

95 KiB

1sss.png

91 KiB

hairMat.png

222 KiB

Germano Cavalcante commented 2023-10-24 15:06:07 +02:00

Member

Copy Link

Hmm, the steps are still too complex and too time consuming for us to track down :\

And, even though not directly related to volume, I believe this is probably a duplicate of #112843: Error when editing displacement values: Illegal address in CUDA queue copy_from_device

I will leave the report open to try to confirm at another time...

Hmm, the steps are still too complex and too time consuming for us to track down :\ And, even though not directly related to volume, I believe this is probably a duplicate of #112843: Error when editing displacement values: Illegal address in CUDA queue copy_from_device I will leave the report open to try to confirm at another time...

Germano Cavalcante added

Status

Needs Triage

Interest

Cycles

Interest

Render & Cycles

and removed

Status

Needs Information from User

labels 2023-10-24 15:06:40 +02:00

ShizzyZzZzZz commented 2023-10-24 16:58:23 +02:00

Author

Copy Link

This is not about displace at all, do you read it carefully? IT IS ONLY HAPPENS WHEN VOLUME SCATTER IN THE SCENE, ONLY IN THAT CASE it crashed, it's not about displace, not about anything else. Without volumetric everything works fine, i repeated it million times already.

This is not about displace at all, do you read it carefully? IT IS ONLY HAPPENS WHEN VOLUME SCATTER IN THE SCENE, ONLY IN THAT CASE it crashed, it's not about displace, not about anything else. Without volumetric everything works fine, i repeated it million times already.

Germano Cavalcante commented 2023-10-24 17:00:04 +02:00

Member

Copy Link

"even though not directly related to volume" I was referring to #112843

#112843 is also not directly related to displacement, but in that file the displacement seems to trigger a bug with the same error message.

"even though not directly related to volume" I was referring to #112843 #112843 is also not directly related to displacement, but in that file the displacement seems to trigger a bug with the same error message.

Pawel commented 2023-10-25 17:50:22 +02:00

Copy Link

I have the same problem in blender 3.6.

Illegal address in CUDA queue copy_from_device (integrator_shade_surface integrator_sorted_paths_array integrator_compact_shadow_states prefix_sum)

Interestingly, blender 4.0 beta doesn't seem to have this issue. Problematic scene renders there without error.

I have the same problem in blender 3.6. _Illegal address in CUDA queue copy_from_device (integrator_shade_surface integrator_sorted_paths_array integrator_compact_shadow_states prefix_sum)_ Interestingly, blender 4.0 beta doesn't seem to have this issue. Problematic scene renders there without error.

👍 1

Pratik Borhade referenced this issue 2023-11-10 08:27:13 +01:00

Blender 3.5.6 + Flip Fluids 1.7.1 not rendering #114666

Pratik Borhade commented 2023-11-13 11:05:43 +01:00

Member

Copy Link

#110657 occurring with volumetrics. Though I'm not able to confirm it locally.
@ShizzyZzZzZz , would be helpful if you can check #110657
And a blend file would help us for further investigation.

#110657 occurring with volumetrics. Though I'm not able to confirm it locally. @ShizzyZzZzZz , would be helpful if you can check #110657 And a blend file would help us for further investigation.

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-11-13 11:05:55 +01:00

ShizzyZzZzZz commented 2023-11-13 14:41:12 +01:00

Author

Copy Link

I described everyting above(aslo little addition to original post with UPT tag in the end), if any of developers need visual representation/demonstration i can show them my few scenes in discord voice channel if they don't mind NSFW stuff to see(becasue i am NSFW artist yup), I got one where is even no chance to render the scene because error happens everytime and in viewport(randomly) and when im trying to start render.(99% constantly) So maybe they will be able to see patterns in it, and as i said a lot of times already i can not share any of my projects becasue of privacy(no chance of it).

Btw here screenshot of console when error happens, idk if this could help to localize it

I described everyting above(aslo little addition to original post with UPT tag in the end), if any of developers need visual representation/demonstration i can show them my few scenes in discord voice channel if they don't mind NSFW stuff to see(becasue i am NSFW artist yup), I got one where is even no chance to render the scene because error happens everytime and in viewport(randomly) and when im trying to start render.(99% constantly) So maybe they will be able to see patterns in it, and as i said a lot of times already i can not share any of my projects becasue of privacy(no chance of it). Btw here screenshot of console when error happens, idk if this could help to localize it

console.png

148 KiB

Pratik Borhade commented 2023-11-14 10:18:05 +01:00

Member

Copy Link

Sharing the affected file publicly will allow multiple devs to have a look at it for investigation.
Maybe create another sample scene which you can share publicly and where problem is more visible.
Not much we can do without being able to replicate the bug locally (hard to identify the buggy code).

Similar error has been triggered before due to various factors.

Sharing the affected file publicly will allow multiple devs to have a look at it for investigation. Maybe create another sample scene which you can share publicly and where problem is more visible. Not much we can do without being able to replicate the bug locally (hard to identify the buggy code). Similar error has been triggered before due to various factors.

ShizzyZzZzZz commented 2023-11-14 10:37:49 +01:00

Author

Copy Link

And it will also give other people to get freely my models and use them to gain profits so no, as i said thousands times, i can not. and i will not not, even for big money.
I tried to make different scene with complex elements but it was okay, without errors, because my models was build for years and have too many small things to repeat to get that level of "complexity" to get that error, so i have no time for it to waste a week creating assets just to reproduce error, becuase i can not say even if i will get error or not, so i can not afford to waste so much time without understanding the final result, and when this result will be received, it may happen the next day or it may not happen within a month, it's too random. But as i said i can show it in discord, so if no one wants to spend 30 minutes - 1 hour on this to check it in discord stream and see and try changing different scene settings, then I won’t spend a day on it. I have my work to do.

And it will also give other people to get freely my models and use them to gain profits so no, as i said thousands times, i can not. and i will not not, even for big money. I tried to make different scene with complex elements but it was okay, without errors, because my models was build for years and have too many small things to repeat to get that level of "complexity" to get that error, so i have no time for it to waste a week creating assets just to reproduce error, becuase i can not say even if i will get error or not, so i can not afford to waste so much time without understanding the final result, and when this result will be received, it may happen the next day or it may not happen within a month, it's too random. But as i said i can show it in discord, so if no one wants to spend 30 minutes - 1 hour on this to check it in discord stream and see and try changing different scene settings, then I won’t spend a day on it. I have my work to do.

Pratik Borhade commented 2023-11-14 11:12:11 +01:00

Member

Copy Link

I understand that you can not share the file publicly and recreating same situation in new file is quite time consuming.
In such situation I would close the report due to insufficient resources for replicating and fixing the bug.
Thanks for offering the discord streaming but it won't help much in identifying the responsible code. For debugging the code, we require a .blend file to reproduce the problem locally or exact steps to create the situation from scratch (which may not be possible in this case since the issue is happening in complex scene).

tagging @lichtwerk in case I've missed something.

I understand that you can not share the file publicly and recreating same situation in new file is quite time consuming. In such situation I would close the report due to insufficient resources for replicating and fixing the bug. Thanks for offering the discord streaming but it won't help much in identifying the responsible code. For debugging the code, we require a .blend file to reproduce the problem locally or exact steps to create the situation from scratch (which may not be possible in this case since the issue is happening in complex scene). tagging @lichtwerk in case I've missed something.

Pratik Borhade closed this issue 2023-11-14 11:12:15 +01:00

Blender Bot added

Status

Archived

and removed

Status

Needs Information from User

labels 2023-11-14 11:12:17 +01:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

partial-write-refactor

brush-assets-project

universal-scene-description

fix-121021

blender-v4.1-release

blender-v3.3-release

blender-v3.6-release

blender-v3.6-temp_wmoss_animrig_public

temp-sculpt-dyntopo

gpencil-next

anim/animation-id-113594

blender-v4.0-release

blender-projects-basics

bridge-curves

sculpt-blender

asset-browser-frontend-split

asset-shelf

tmp-usd-python-mtl

tmp-usd-3.6

blender-v3.5-release

blender-v2.93-release

realtime-clock

sculpt-dev

bevelv2

xr-dev

v4.1.1

v3.6.11

v3.3.18

v4.1.0

v3.3.17

v3.6.10

v3.6.9

v3.3.16

v3.6.8

v3.6.7

v3.3.14

v4.0.2

v4.0.1

v4.0.0

v3.6.5

v3.3.12

v3.6.4

v3.6.3

v3.3.11

v3.6.2

v3.3.10

v3.6.1

v3.3.9

v3.6.0

v3.3.8

v3.3.7

v2.93.18

v3.5.1

v3.3.6

v2.93.17

v3.5.0

v2.93.16

v3.3.5

v3.3.4

v2.93.15

v2.93.14

v3.3.3

v2.93.13

v2.93.12

v3.4.1

v3.3.2

v3.4.0

v3.3.1

v2.93.11

v3.3.0

v3.2.2

v2.93.10

v3.2.1

v3.2.0

v2.83.20

v2.93.9

v3.1.2

v3.1.1

v3.1.0

v2.83.19

v2.93.8

v3.0.1

v2.93.7

v3.0.0

v2.93.6

v2.93.5

v2.83.18

v2.93.4

v2.93.3

v2.83.17

v2.93.2

v2.93.1

v2.83.16

v2.93.0

v2.83.15

v2.83.14

v2.83.13

v2.92.0

v2.83.12

v2.91.2

v2.83.10

v2.91.0

v2.83.9

v2.83.8

v2.83.7

v2.90.1

v2.83.6.1

v2.83.6

v2.90.0

v2.83.5

v2.83.4

v2.83.3

v2.83.2

v2.83.1

v2.83

v2.82a

v2.82

v2.81a

v2.81

v2.80

v2.80-rc3

v2.80-rc2

v2.80-rc1

v2.79b

v2.79a

v2.79

v2.79-rc2

v2.79-rc1

v2.78c

v2.78b

v2.78a

v2.78

v2.78-rc2

v2.78-rc1

v2.77a

v2.77

v2.77-rc2

v2.77-rc1

v2.76b

v2.76a

v2.76

v2.76-rc3

v2.76-rc2

v2.76-rc1

v2.75a

v2.75

v2.75-rc2

v2.75-rc1

v2.74

v2.74-rc4

v2.74-rc3

v2.74-rc2

v2.74-rc1

v2.73a

v2.73

v2.73-rc1

v2.72b

2.72b

v2.72a

v2.72

v2.72-rc1

v2.71

v2.71-rc2

v2.71-rc1

v2.70a

v2.70

v2.70-rc2

v2.70-rc

v2.69

v2.68a

v2.68

v2.67b

v2.67a

v2.67

v2.66a

v2.66

v2.65a

v2.65

v2.64a

v2.64

v2.63a

v2.63

v2.61

v2.60a

v2.60

v2.59

v2.58a

v2.58

v2.57b

v2.57a

v2.57

v2.56a

v2.56

v2.55

v2.54

v2.53

v2.52

v2.51

v2.50

v2.49b

v2.49a

v2.49

v2.48a

v2.48

v2.47

v2.46

v2.45

v2.44

v2.43

v2.42a

v2.42

v2.41

v2.40

v2.37a

v2.37

v2.36

v2.35a

v2.35

v2.34

v2.33a

v2.33

v2.32

v2.31a

v2.31

v2.30

v2.28c

v2.28a

v2.28

v2.27

v2.26

v2.25

Labels

Clear labels   

Interest

Alembic

  

Interest

Animation & Rigging

  

Interest

Asset Browser

  

Interest

Asset Browser Project Overview

  

Interest

Audio

  

Interest

Automated Testing

  

Interest

Blender Asset Bundle

  

Interest

BlendFile

  

Interest

Collada

  

Interest

Compatibility

This issue affects/is about backward or forward compatibility

  

Interest

Compositing

  

Interest

Core

  

Interest

Cycles

  

Interest

Dependency Graph

  

Interest

Development Management

  

Interest

EEVEE

  

Interest

EEVEE & Viewport

  

Interest

Freestyle

  

Interest

Geometry Nodes

  

Interest

Grease Pencil

  

Interest

ID Management

  

Interest

Images & Movies

  

Interest

Import Export

  

Interest

Line Art

  

Interest

Masking

  

Interest

Metal

  

Interest

Modeling

  

Interest

Modifiers

  

Interest

Motion Tracking

  

Interest

Nodes & Physics

  

Interest

OpenGL

  

Interest

Overlay

  

Interest

Overrides

  

Interest

Performance

  

Interest

Physics

  

Interest

Pipeline, Assets & IO

  

Interest

Platforms, Builds & Tests

  

Interest

Python API

  

Interest

Render & Cycles

  

Interest

Render Pipeline

  

Interest

Sculpt, Paint & Texture

  

Interest

Text Editor

  

Interest

Translations

  

Interest

Triaging

  

Interest

Undo

  

Interest

USD

  

Interest

User Interface

  

Interest

UV Editing

  

Interest

VFX & Video

  

Interest

Video Sequencer

  

Interest

Virtual Reality

  

Interest

Vulkan

  

Interest

Wayland

Issues relating to Wayland windowing support.

  

Interest

Workbench

  

Interest: X11

Issues relating to Xorg/X11 support.

  

Legacy

Blender 2.8 Project

  

Legacy

Milestone 1: Basic, Local Asset Browser

  

Legacy

OpenGL Error

  

Meta

Good First Issue

  

Meta

Papercut

  

Meta

Retrospective

  

Meta

Security

Issues relating to security: https://wiki.blender.org/wiki/Process/Vulnerability_Reports

  

Module

Animation & Rigging

  

Module

Core

  

Module

Development Management

  

Module

EEVEE & Viewport

  

Module

Grease Pencil

  

Module

Modeling

  

Module

Nodes & Physics

  

Module

Pipeline, Assets & IO

  

Module

Platforms, Builds & Tests

  

Module

Python API

  

Module

Render & Cycles

  

Module

Sculpt, Paint & Texture

  

Module

Triaging

  

Module

User Interface

  

Module

VFX & Video

  

Platform

FreeBSD

  

Platform

Linux

  

Platform

macOS

  

Platform

Windows

  

Priority

High

  

Priority

Low

  

Priority

Normal

  

Priority

Unbreak Now!

  

Status

Archived

  

Status

Confirmed

  

Status

Duplicate

  

Status

Needs Info from Developers

  

Status

Needs Information from User

  

Status

Needs Triage

  

Status

Resolved

  

Type

Bug

  

Type

Design

  

Type

Known Issue

  

Type

Patch

  

Type

Report

  

Type

To Do

No Label

Interest

Alembic

Interest

Animation & Rigging

Interest

Asset Browser

Interest

Asset Browser Project Overview

Interest

Audio

Interest

Automated Testing

Interest

Blender Asset Bundle

Interest

BlendFile

Interest

Collada

Interest

Compatibility

Interest

Compositing

Interest

Core

Interest

Cycles

Interest

Dependency Graph

Interest

Development Management

Interest

EEVEE

Interest

EEVEE & Viewport

Interest

Freestyle

Interest

Geometry Nodes

Interest

Grease Pencil

Interest

ID Management

Interest

Images & Movies

Interest

Import Export

Interest

Line Art

Interest

Masking

Interest

Metal

Interest

Modeling

Interest

Modifiers

Interest

Motion Tracking

Interest

Nodes & Physics

Interest

OpenGL

Interest

Overlay

Interest

Overrides

Interest

Performance

Interest

Physics

Interest

Pipeline, Assets & IO

Interest

Platforms, Builds & Tests

Interest

Python API

Interest

Render & Cycles

Interest

Render Pipeline

Interest

Sculpt, Paint & Texture

Interest

Text Editor

Interest

Translations

Interest

Triaging

Interest

Undo

Interest

USD

Interest

User Interface

Interest

UV Editing

Interest

VFX & Video

Interest

Video Sequencer

Interest

Virtual Reality

Interest

Vulkan

Interest

Wayland

Interest

Workbench

Interest: X11

Legacy

Blender 2.8 Project

Legacy

Milestone 1: Basic, Local Asset Browser

Legacy

OpenGL Error

Meta

Good First Issue

Meta

Papercut

Meta

Retrospective

Meta

Security

Module

Animation & Rigging

Module

Core

Module

Development Management

Module

EEVEE & Viewport

Module

Grease Pencil

Module

Modeling

Module

Nodes & Physics

Module

Pipeline, Assets & IO

Module

Platforms, Builds & Tests

Module

Python API

Module

Render & Cycles

Module

Sculpt, Paint & Texture

Module

Triaging

Module

User Interface

Module

VFX & Video

Platform

FreeBSD

Platform

Linux

Platform

macOS

Platform

Windows

Priority

High

Priority

Low

Priority

Normal

Priority

Unbreak Now!

Status

Archived

Status

Confirmed

Status

Duplicate

Status

Needs Info from Developers

Status

Needs Information from User

Status

Needs Triage

Status

Resolved

Type

Bug

Type

Design

Type

Known Issue

Type

Patch

Type

Report

Type

To Do

Milestone

Clear milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

No Assignees

5 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#114035

No description provided.