Hi @alejandro-melgoza I believe this is not actually a bug. In 3.5 there's a new option on the header to specify curve fall off, which allows you to change how much influence a brush can impose on…
void WM_cursor_modal_set(wmWindow *win, int val)
{
if (win->lastcursor == 0) {
win->lastcursor = win->cursor;
}
win->modalcursor = val;
WM_cursor_set(win, val);
}
I…
This might be related to how the cache is built. Could you provide us a file where the issue is replicable? Thanks!
We probably need more input from graphic guys here.
The only erroneous "lag" I've encountered related to a driver issue is to have a shader subroutine exit while locks in place, and sometimes a…
@Stay_Here Thanks for the additional info! Will look into it once I have time.
I see, that's indeed what's happening here... Will investigate. @Stay_Here
Can confirm the issue in 3.6. Additional information:
- The "weird region" seems to be made up with these portions, I drew the black stroke without lifting the pointer
- This only happens in…
@Stay_Here Okay, then I believe it's probably a versioning issue. Do you know which version this file is saved with? From what I can see rn the broken conversion seem to use the radius property…
Actually this issue can be open because for some reason the mask coloring isn't always shown when there's modifier involved.
@Ahmed-Mohammed-Abd-El-Sabour You also have masks in your base mesh, use alt-M to clear the mask in edit mode, it should enable you to work on the mesh normally.
@Ahmed-Mohammed-Abd-El-Sabour By deleting the shape keys, I'm able to work with sculpting tool without any problem, could you describe the issue a bit more if you still can't get it to work?
@Stay_Here I'm not able to reproduce the issue either with Successfully conversion.blend or a new file, it only happens in Convert curve to curves.blend.
There must be some other stuff you…
Looks like it's because that converted curves have too high a thickness ("Attribute->radius"). By default that value is 1, (We should make this value a property in the Convert to curves operator…
Hi @hissatsuneko I found the issue. It's actually because you have locked materials. Unlocking all materials resolved the issue. Further more, unlocking all layers enables you to interpolate…
@hissatsuneko I recommend that you edit out those explicit parts, and if you can still trigger the issue, then you could share it here.
Can confirm the problem. Tested when placing the asset from another file, the asset will appear inside the active collection as expected. The bug only appears when placing asset from current file,…