- User Since
- Jul 4 2019, 11:34 PM (86 w, 4 d)
Thu, Feb 18
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
Tue, Feb 16
Fri, Feb 12
Fri, Feb 5
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
Wed, Feb 3
and detaching the principled volume while in render view freezes blender.
Possible duplicate T82856.
May you try update your blender to 2.91.2?
Jan 30 2021
Jan 29 2021
it also happens with factory settings, was the first thing I tried.
Jan 28 2021
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.
Jan 26 2021
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
Jan 22 2021
Jan 21 2021
Jan 19 2021
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
Jan 10 2021
Jan 8 2021
for some reason it had been disabled in default settings then because I never changed it
Dec 31 2020
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?
Dec 30 2020
1- yes, and also, changing the scaling has no effect.
here it goes P1862
Dec 27 2020
created at T84179
Dec 22 2020
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.
Dec 21 2020
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.
Dec 16 2020
yep. it seems like blender stops grabbing the pen presure whenever you create a new window, mind taking a look @Nicholas Rishel (nicholas_rishel) ? :)
Dec 15 2020
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
Dec 6 2020
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.
Dec 3 2020
as I mentioned before, it is working for me since 2.90.1, but there is a caveat
Dec 1 2020
Nov 27 2020
Nov 25 2020
sorry, I didn't see the notification.
Nov 21 2020
@Jälgar (voyager3) try 20.11.2 not 20.11.1
Nov 18 2020
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.
Nov 17 2020
@Nicholas Rishel (nicholas_rishel) may you have a look
Nov 15 2020
Nov 14 2020
Nov 11 2020
you can also just revert the drivers to 20.4.2, render with only the cpu or use eevee/luxcore
Nov 10 2020
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.
Nov 9 2020
Nov 7 2020
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
Nov 6 2020
why did you close this thread? it hasn't been resolved for those who still use amd
Nov 4 2020
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.
Nov 3 2020
yea, blender is working fine with driver version 20.4.2., at least on my RX5700XT
Nov 2 2020
yes, as evan said
Oct 29 2020
every bake I did was using cpu, because for some reason blender is crashing sometimes with gpu baking for me.
Oct 28 2020
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.
Oct 26 2020
Oct 25 2020
Oct 22 2020
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
Oct 21 2020
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
Oct 18 2020
@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
Oct 14 2020
Oct 13 2020
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
Oct 11 2020
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.
Oct 10 2020
Oct 9 2020
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