When baking to two images, CUDA crashes on the second image. #94217
Labels
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
No Milestone
No project
No Assignees
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#94217
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-10
Graphics card: NVIDIA GeForce GTX 960
Blender Version
Broken: version: 3.0.0
Worked: 2.93.5
Short description of error
If an object has multiple materials, only the first will bake normal maps, and the second material will have a hole in the bake image.
Exact steps for others to reproduce the error
Setup a high res object and a low res object, give the low res object two materials, assign some vertices to material 1 and some to material 2, bake a normal map to the low res object, only material 1 will bake a normal map image, material 2 will have a hole.
Attached .blend file showing the bug, open it in 3.0.0 and press bake, second image "bake2" will have a hole. Open it in 2.93.5, press bake, "bake2" will bake as expected.
baking bug.blend
Added subscriber: @Memm
Added subscriber: @Baardaap
As I've been working on this code for 3.1 I'll have a look if it's something I understand.
If anybody knows what's going on, feel free to claim this one.
Very strange. If I use the official release I see this bug. If I compile 3.0.0 myself it works as it should!
Changed status from 'Needs Triage' to: 'Needs User Info'
I think the actual bug here is Cycles crashing for the second image. Maybe something with deinitializing and reinitializing CUDA?
For me it works correctly if I set Cycles to CPU only.
@Memm could you confirm if it works correctly if you set cycles to cpu rendering?
@Baardaap I can confirm it works with CPU rendering, you're probably right about CUDA failing to reinitialize. I'm just guessing here but maybe it's a memory leak, that seems to happen quite often with CUDA.
Multiple materials cause holes in normal map bakingto When baking to two images, CUDA crashes on the second image.Added subscriber: @brecht
@brecht CUDA reliably crashes on the second image on multiple machines over here. As have no experience whatsoever with CUDA I 'unclaim' this task.
So I just tried baking a roughness map and Blender froze up, then opened the same file in 2.93.5 and it baked just fine, not only that but baking in 2.93.5 uses much less memory and goes about 100x faster. Could it be that baking as a whole is broken with CUDA under 3.0.0? Basically all my baking has to be done in 2.93.5 right now, which seems like a major bug for 3.0.0.
are you sure 3.0.0 wasn't set to CPU only?
Also, maybe it's useful to open a new bugreport for that? Since it's probably not the same problem, though maybe related.
Maybe mention the new bugreport over here.
This comment was removed by @Memm
@Baardaap It might need a new bug report, but I get the feeling this is all related. If I set rendering to CPU like you suggested then the roughness map bakes and Blender doesn't crash. It also bakes just fine in 2.93.5 with CUDA. Too many coincidences in my opinion.
Added subscriber: @Sergey
Maybe it's related, sure. But being very slow (but CUDA not crashing) or CUDA crashing is still a different bug I think.
Anyway, I think the main person who can shed some light on this is @brecht , or maybe @sergey. Brecht is on holiday I think. Considering 3.0 is just out and Christmass is nearly here, I wouldn't be surprised is @Sergey is on holiday as well.
Turning off the noise threshold fixing it was incorrect?
@Baardaap Turning off noise threshold gets it to bake the second image in the example .blend file, but I don't want to say it fixes it because we still don't know the cause. It's probably best to just wait for someone that knows the baking code to look at it.
Changed status from 'Needs User Info' to: 'Confirmed'
So far can confirm the issue.
Not sure yet what causes it, maybe somehow non-initialized state of the auxiliary buffer used by adaptive sampling, or maybe some missing synchronization of a queue somewhere.
I have put in another ticket, I think this is related.
https://developer.blender.org/T94854
Added subscriber: @MaleneThyssen
I suspect this is related. Baking textures (Combined) from a multi material object only the first material in the list bakes right. The next materials bakes a mix of the previous materials + their own. This happens in Blender 3.0 with GPU and Denoise/Noise Threshold on. If I turn off Denoise and Noise Threshold the textures will bake right, albeit a lot slower and more noisy of course (If i switch to Diffuse though - the issue is back with these settings too). Whether I use OptiX or OpenImageDenoise seems to make no difference. Switching the materials in the list it will still be the top material that works and the ones lover in the list will be messed up. If I bake in CPU I have no issue.
System info:
Blender version: 3.0.0, branch: master, commit date: 2021-12-02 18:35, hash:
f1cca30557, type: releasebuild date: 2021-12-03, 00:44:02
platform: 'Windows-10-10.0.19043-SP0'
NVIDIA GeForce GTX 1070/PCIe/SSE2'
4.5.0 NVIDIA 472.84'
A few screenshots of the setup:
Added subscriber: @EMSI
Can confirm it, i was about to make a bug report for the similar Issue. I've been baking Alpha Info with Emission to an Image Textures; in mid-process of texture baking, Blender suddenly close itself without any warning what so ever. I'm using a simple props:
Configuration:
Render & Viewport sample : 1
Bake: Combined, without Light info (Direct/Indirect Lighting) with 1px margin.
System Info:
Microsoft Windows 10
Version 20H3 (OS Build 19042.985)
About Blender:
Latest Official Release Blender Version 3.0.0
Date: 2021-12-02 18:35
Hash:
f1cca30557Branch: Master
Note that the Crashes happens randomly and on standard frequent, and sometimes happen on Diffuse baking but more likely to happen with Combined Bake.
Changed status from 'Confirmed' to: 'Resolved'
Also fixed by
04c3b08.