so, there is still a problem in the sculpt, the first dot of a stroke has maximum pressure, both in wintab and windows ink, besides it, windows ink pressure doesn't work at all

In T85582#1113181, @Harley Acheson (harley) wrote:

@Germano Cavalcante (mano-wii) - that video was almost unusable for me too. But in the last few seconds of it I think they are showing us that items in the middle of Timeline header shift horizontally to a new center only when moused over. Although it looks like item hovering I am guessing that is just entering the area, so probably doing a refresh then.

But I have not been able to recreate this on my multimonitor Windows setup so only guessing.

yep. windows ink works flawlessly in this build, even changing the monitor setup it still works fine

alright. the position seems right, but now wintab sometimes is glitching like windows ink, and sometimes its glitching in another way
P1948

and detaching the principled volume while in render view freezes blender.

I reported this issue some time ago in T78027
also related:
T77858

Possible duplicate T82856.
May you try update your blender to 2.91.2?

it also happens with factory settings, was the first thing I tried.

this is already a known issue with dyntopo and it happens because of the way dyntopo works and the structure it uses, there is a thread about dyntopo plans created by Pablo Dobarro T73934, but for now I don't think they will do much about it.

it seems a high priority bug since it really breaks user experience

I checked in other software to see how they name it and how they work. Most of the times the brush "radius" is refered as just size(diameter). So the problem here is just naming I guess, it should be size(or diameter) and mm instead of px Unless its set to screenspace.

so, I think unit is not actually pixels, its milimiters in the scene.

well, weirdly the bug came back after I deactivated the second monitor(not unplugging it)

What tablet do you have and does it have an in-built screen?

the huion kamvas 13 has a 1080x1920 screen built in.

and the paste link: P1912

There is already a bit of a discussion regarding the symmetry options in:

well, it has been in blender for a while, I also think this needs a bit more attention

for some reason it had been disabled in default settings then because I never changed it

krita is working perfectly right out of the box. I even checked if it wasn't using windows ink and no, it was with wintab.

I'm assuming you tried Windows Ink and it worked for you?

1- yes, and also, changing the scaling has no effect.

here it goes P1862

created at T84179

I just experienced a similar issue on gimp (https://youtu.be/OoPiBoD23dw) and I discovered the source of the problem. it seems like it'ss some incompatibility with multiple monitors, It still is only present in this last build tho.

so, I tested the new build , it kinda looks like the navigation is fixed but it also looks like cursor clicks are offset from the real one by a lot.

yep. it seems like blender stops grabbing the pen presure whenever you create a new window, mind taking a look @Nicholas Rishel (nicholas_rishel) ? :)

I have one of those and I'm not having any problem with it in blender 2.91, tho the alpha version 2.92 broke pen displays in general and it is being worked on by @Nicholas Rishel (nicholas_rishel).

possible duplicate T82856

Thank you Vilem =D

I'm also having trouble with blenederkit, I think since beta 2.91, the items of the store weren't loading, I thought it was a problem of their website.

as I mentioned before, it is working for me since 2.90.1, but there is a caveat

In T75319#1065498, @Tashvit Verma (silverstar48) wrote:

However it shows an error with cycles enabled in blender version 2.91

sorry, I didn't see the notification.

@Jälgar (voyager3) try 20.11.2 not 20.11.1

Normal F12 render takes a really long time to load

Yep, I can confirm it has been fixed, as josh said, it takes a while loading and even gave me a kernel error, but if you go to solid mode and go back to render it works fine.

@Nicholas Rishel (nicholas_rishel) may you have a look

you can also just revert the drivers to 20.4.2, render with only the cpu or use eevee/luxcore

I've experienced the same issue using a huion kamvas 13, the buttons do work tho, but only if the pen is touching the display, and this problem is gone if you have a floating blender window.

well, this was one of the first things I tried when I got this bug, It didnt work back then neither it did now, I get the following error

why did you close this thread? it hasn't been resolved for those who still use amd

yes, it no longer crashes, as in T81775 the bug changed from a crash to a weird behavior, but I think the crash while trying to render is a different bug, @Jesper Kondrup (coindrop) and @Camille (Ekiwnox) could try testing it now.

yea, blender is working fine with driver version 20.4.2., at least on my RX5700XT

yes, as evan said

every bake I did was using cpu, because for some reason blender is crashing sometimes with gpu baking for me.

I think you can get it with at least 5-6 bakes, with some of those from different objects to different objects, e.g baking the color of the lower part of the skirt, and then baking the upper one right after, I don't think there is an specific type of bake that triggers it, but I'm almost sure I got it baking emit and normals, switching between then sometimes.

the file is fairly heavy, I tried deleting what I could purging all and leaving just the skirt, I just don't know if this is enough to reproduce the bug, but what I can say is that I already experieced a similar problem a bunch of times, but instead of the image not updating in the image editor, it would not update in eevee unless I reloaded the file.

Yes, changing those values seems to fix the problem, I couldn't find the reason why it was being caused as I only looked on this page of the manual: https://docs.blender.org/manual/en/latest/render/eevee/render_settings/shadows.html

I don't know if I can comment it here but wouldn't it be better if instead of 8 fixed colors the user could select the color in a color wheel? and I don't know if this is because of my theme but the color 7 is the same as "no color" by default

@Chloe Hase (ChloeHase) are you rendering with CPU+GPU?if so, this is a known issue https://developer.blender.org/T50193. I said "fine" with quotes because its a bit unstable thing and it tends to crash, like the example I made above

@Chloe Hase (ChloeHase) try to downgrade the driver to 20.4.2, its working "fine" on my 5700xt

I'm getting this almost every time

well I just tried it again with default settings to see if it was my settings but no, even with default settings(I activated pie menus only) it crashed, It was a bit harder to reproduce but I still got it

here it goes

@Aviel Warschawski (avielw) Weirdly enough I already got that 99% once, you don't need to reboot your system, puting it in sleep mode and going back is enough and faster, tho for some reason I'm not getting stuck in the kernel compile part anymore, its rendering fine, tho I still have that problem of disconnecting the volume node while rendering.

My RX5700XT is not overclocked, blender is only working with drivers that are v20.4.2 and below, unless its a scene that contains volume, tho I think in this case this may not be a driver problem, its probably a blender problem since 2.83(?) as you can see in this task https://developer.blender.org/T78027