I am personally unable to reproduce the issue on my computer. Although I used Windows default SMB version which probably isn't 1.0, and I'm on Windows 11 Home, not pro. Although I'm doubtful these…
The crash log is very generic, so we will need a file to test with to identify the exact cause.
Since you don't have a file, and the steps to reproduce are basically "Use Cycles and sometimes…
@datonepumpkin There are two issues here.
- The bug you described in your original post.
- A bug resulting in the
Report a bug
button not working properly.
Please re-post issue 1 over…
I don't know why a three channel image is loaded as if it has 4 channels of data. I assume Cycles is creating a "empty" or "constant" alpha channel, but I don't know why.
i try this "C:\Program Files\Blender Foundation\Blender 4.0\blender.exe -- --cycles-print-stats" but not work
That should work.
one other things 4096 x 4096 x 4 x 8 = not is 67,108,864…
To get the memory statistics, you need to run Blender with /path/to/blender -- --cycles-print-stats
and render a scene on the CPU.
I should note not all memory statistics are tracked here.…
Using the attached keyboard layout, I can confirm the crash.
I ran a debug build of Blender to see if I could identify the cause, but my knowledge in this area is limited.
[NSApp…
And not understand why, if i change the texture format and lost 400mb of weight texture, increase the vram usage instead of decreasing
This is a separate issue, please create a new bug report…
@William-Asperti as @ChengduLittleA pointed out, Cycles uses uncompressed textures. What does that mean? It means the size of the raw image is how much space the texture will take up in memory.…
Considering the scene consumers a large amount of RAM, and you're now getting out of memory errors instead of crashing. Then I assume this is just a out of memory issue, which isn't considered a…
@Calibrator , feature requests should be made on right click select.
As for your concern about DOF going through the portal, there are a few…
If I understand the crash log correctly, the crash is occuring when processing keyboard inputs (which is expected based on the information provided). This eliminates other things like add-ons…
The scene did not crash when I tested it. However the scene does consume a lot of memory when rendering (60GB). So if you don't have enough RAM and page file space, then Blender could crash.…
As pointed out, the trace function is not supported with OptiX OSL. So this is expected. It would be nicer if there was a more description error message. CC @pmoursnv is a more descriptive error…