Just tested with blender-4.3.0-beta+v43.5c880a52916e-windows.amd64-release - works correctly! Thanks!
@PratikPB2123 Hello! Nope, Sorry, I have no time for experimentations with my working rig. But I thought that my previous answer - blender/blender#123145 (comment)…
Hello! I'm very busy these days so can't hassle with all this experiments for now. Neithertheless I will try as soon as some free time will appear. The only thing that wasn't time-consumpting…
I found a reasonable solution for such cases:
- Select problematic vertices in edit mode.
- "Vertex" menu (ctrl+v) / "Vertex Groups" (ctrl+g) / Remove from All.
- Assign to desired vertex group.
I have mesh from modeling artist, some parts of it composed of unconnected quads. That is - whole part of mesh (tooth for example) are composed of independent quads. I figured it out in late stage…
I have encountered this error again, and there is video, explaining all things. After all I disabled XMP in BIOS, and there weren't any crashes under any…
@Alaska It's really strange: I tried to record video of rendering crash with OBS, with XMP and without it. And it doesn't crash today! )) I will try to report you later, when the same crash will…
Oops, I occasionaly closed this ticked, sorry!
@Alaska Hello! No, I haven't overclocked/undervolted any of my gear parts. And never had any cpu-ram problems on it. But I'm using XMP profile (never thought it could be treated as overclocking…
If it could help there is some additional info I forgot to tell: my renders set up to use OptiX, not CUDA. RAM reservation for CUDA is set by default in driver settings. I'm not sure what does it…
Good time of day! My guess is that OIDN data unpredictably replaces some crucial data of render itself (part of persistent data), because of lack of vram. But interesting part is that it happens…