Hello Blender friends :),
It’s not often that I ask a question on the web, but here I’m really stumped.
I think I noticed a serious bug in blender’s texturing.
After several experiments under multiple versions of blender, several OS (windows/linux), GPUs (Radeon/Nvidia) and PCs, the painting generates artifacts.
It generates dots (pixels) on the drawn areas.
The more you increase the resolution (4K,8K,16K), the more visible and very disturbing it is.
I really think I have tried everything to fix this problem without success.
To try, start by subdividing a cube with 3 or 4 iterations and create a 16K texture.
Start painting on it… You will see dots and lines.
Interesting.
Can’t offer anything useful, but I too have encountered similar behavior. Usually just a few pixels (on 2k textures). After changing zoom and/or view angle I could paint over it.
What I haven’t noticed before is that it seems to occur only on diagonal “edges” inside quads
edit. huh, wrong observation: it occurs at edges that have 45 degree angle in UV map…
A solution I have for the lines showing up is to scale down the UVMapping so there is blank boarder around the UVMap Islands. Then paint the model using a bleed of at least 8px.
Hmmm…that is strange as I have never seen this on any version…and I have an older AMD processor 6-core with Nvidia 2070 RTX…and using a 32" HDMI TV to view., (I’m old)
it is over 6 years old…started out as
Cybertron PC Hellion (Blue) TGM1213J Gaming PC (3.5 GHz AMD FX-6300 6-Core, 2GB GeForce GT740, 16GB DDR3 1600MHz, 1TB HDD, WiFi, Windows 10 Home 64-Bit
Updated Ram and GPU
If you think it’s a bug, please report it.
The devs normally don’t hang out here, and if you make a proper report of it with all steps involved you will get more traction.
Also, be sure you can reproduce it every time.
Hi,
Indeed, this is exactly what I was thinking of doing tomorrow on the Blender github.
Did you also have another link to propose ?
I just experimented the bug on a friend’s laptop.
Old intel CPU and same bug.
I don’t think the CPU is the cause.
I think this bug concerns everyone. Really