Eeh I have added wrong label.
Can you describe step by step what I need to do to cause crash? Just adding new action seems to work well here.
Assert mesh_eval != nullptr was triggered in
libc.so.6!__pthread_kill_implementation(int no_tid, int signo, pthread_t threadid) (pthread_kill.c:44)
libc.so.6!__pthread_kill_internal(int…Sounds like different issue than #124731. More in line with #129520. User there reports that dragging extension multiple time eventually succeeds. Can you check that to establish whether it is the…
Perhaps same issue as #130309
Not sure who to poke about this. @pablovazquez you seems to be active on website front, perhaps this file should be removed until fixed.
I assume the node is from 3195c1a669b1378c1556c09f415ab779293554f2. This added file node_geo_sample_volume.cc which is not around anymore. No mention about this specific node in git log.
I am getting solid white output. Looking at compositor, render layers node is not connected to denoise node. I assume, this is not intentional and the issue you are facing?
Hi, thanks for the report. Updating GPU driver may resolve the situation. Can you check : https://docs.blender.org/manual/en/dev/troubleshooting/gpu/windows/amd.html
GPENCIL_OT_stroke_sample is marked as ported in #112858 so not sure what is its state really.
@filedescriptor Can you share more info?
I wasn't able to reproduce crash. I assume that crash happens when you push down action on armature? If not can you share steps to reproduce?
I would say, that is a feature - long string is shortened I guess due to limited space available, but then I have seen longer path strings displayed. It happens in bunch of places.
But even…
Also click on Help > Save System Info and upload saved file.
I am not quite sure how you are using vulkan in 4.3 stable, when it is experimental feature. But it seems to be the same issue as #127619 indeed, so will close as duplicate.
Check if blender is using integrated GPU. Try to force it to use one or the other and see if either works correctly.
Possibly duplicate of #127835
Adding high severity, because filling the smallest area does cause endless loop
Yes, that indeed would explain that. Not sure how I feel about bad addon bringing down Blender UI...
@Michael-Colina If you have trouble removing addon or restoring preferences to factory…
In 4.4 the performance is good again. @Sean-Kim Is this something, that is expected in 4.3? Not sure how viable it would be to fix in corrective release, but will keep high severity label just in…