-
I like exploring new features in Blender and enjoy rendering
To make Blender an almost perfect software
- Joined on
2023-11-16
Thanks for reminding me, it seems that the question I submitted is duplicated.
In the 4.3.0 alpha release on June 25th, the problem doesn't seem to be present anymore.
But I noticed that the work order is still open, does that mean it's not fully fixed?
@aafra I just tested it and finally realized why you don't get this error with your own files! I turned on Persistent Data
in Performance (since I'm not short of memory and want to render…
I did some more research and found a problem with my previous description, I'm recreating a bug report to organize it
**System Information**
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 555.85
**Blender Version**
Bro…
Might be misunderstanding, what exactly are you doing when "move the compositor, move the view rendering" ?
At that time, I was adjusting the node settings in the synthesizer, such as…
Hi, thanks for the report. Looking at the logs, openimagedenoise denoiser on GPU is used. Can you attach test.blend in which the error is reproducible? CUTLASS error appears to be related…
Yes, I found that after rendering the first image, save the image, then move the compositor, move the view rendering, and then move the camera before rendering, the probability of triggering is…