Page MenuHome
Create Task
Maniphest T78972

Texture paint mode bug, brushes do not create a line until you release the stroke.
Closed, DuplicatePublic
Actions

Description

System Information
Operating system: windows 10
Graphics card: gtx1080

Blender Version
Broken version: Last release of 2.90 blender-2.90.0-75a09ba2ed26-windows64

Last Version where things were working well to my knowledge:

version: 2.90.0 Alpha, branch: master, commit date: 2020-06-01 20:37, hash: 1d4bae856690, type: Release
build date: 2020-06-01, 21:08:47
platform: Windows

The error is also not present in 2.83.2

Short description of error
Texture paint brush does not create line until the stroke is released from the screen.

Exact steps for others to reproduce the error
This bug as far I could tell only happens with painting bump maps, I dont know if it could be triggered by other things tho,
I cant post the blend file because it contains nodes groups from a payed addon so I'm not sure if I should be sharing the nodes,
however as far as I can see it does seem to be a bug because on 2.83.2 and on older builds from 2.90
this problem does not exist, i.e. I can paint strokes like ones I'm trying to do on this video with not problems,
I just load the file and all works perfectly on those builds, the occasional lag does happen but this is an
entirely new problem.

So on the video you can see I try to paint strokes that create new height/bump maps by means of a bw mask and a bump node connection, however when I click on
the mesh to draw a shape only until I release the stroke does the lines get drawn, I can move the wacom stylus all over the mesh in texture paint mode
after I do the initial stroke, but Blender only draws the line until I release the stroke from the screen.

Something must have changed after the 2 of june on how some part of the texture paint systems work as the last build I have of 2.90 where I can
paint without this problem I think is from that date.

This is a link to a google drive folder that has one video showing the problem, and one showing how things should work, and a
zip file with the last Blender build of 2.90 were the problem was not present, maybe comparing this one to the current 2.90 build
where this is happening a solution could be found?

https://drive.google.com/drive/folders/1hUUQAjQ6aDGD9NUJzZlRVMld4-gpmtiM?usp=sharing

I hope this helps, Im really looking forward to having this working as I can't do the texture painting I need to do for work unless this is solved,
having to jump from the 2.90 build where this is not happening to the new one that has the Intel denoiser to do renders is very time consuming.
That being said even with the occasional bug Blender allows me to work for a living doing 3d, so Thank you for making Blender so Awesome
that I can do so many things with it :) Cheers!

Event Timeline

Luis Felipe Peredo Noguez (renderluz) created this task.Jul 16 2020, 8:38 AM
Luis Felipe Peredo Noguez (renderluz) added a comment.EditedJul 16 2020, 9:03 AM

I think I was able to track the problem in terms of when the change happened that created it a bit more,
must have happened between the 2 of July and the 15 of July, I just downloaded this build, loaded my file and this strange brush problem is present in the build.

https://blender.community/c/graphicall/snbbbc/

On the post is written the build is Win64-2.90_Release_07-15-20

Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Needs Information from User.Jul 16 2020, 3:52 PM
Germano Cavalcante (mano-wii) added a subscriber: Germano Cavalcante (mano-wii).

Sometimes it is much easier to understand the problem through a simplified .blend file.

You will not be distributing proprietary content if you remove objects and disabling settings.

This would also make the problem reveals itself more clearly and save the developers time.

In the report you are just describing the bug, but for the development team to be able to help, there needs to be reproducible steps (start blender, press this, then that ...)

If there are many steps to reproduce the problem, just attach a .blend file saved right before the bug occurs, so only a few steps are needed to trigger the bug.

Luis Felipe Peredo Noguez (renderluz) added a comment.EditedJul 16 2020, 4:03 PM

Thank you for the reply :)

I will try to find a way to get a simplified version of the problem that can be reproduced as you mention,
I was hoping maybe someone might see the issue and recognize a change made to the texture paint systems between
the dates I shared.

I'm not as experienced in node magic as I could be so identifying the string of node
connections to make a simplified version of the problem might prove to be difficult for me, that
being said I will try to do it as this problem is really strange and its hampering my work so
I want to know why its there.

Some changes to the texture paint mode had to be made as of the last past two weeks tho,
so if anyone can think of a reason this could be happening in relation to something committed on
the beginning of of the month that would be great, maybe a new build on the next week will fix this as
well... either way I will try to create a simplified file of the issue.

Luis Felipe Peredo Noguez (renderluz) added a comment.Jul 16 2020, 4:32 PM

I think I got a simplified file that shows the problem,
and it does not have to do with bump maps because I disconnected all but a principled
shader an image texture and an output node and the problem is there, I'm organizing my files
and recording the steps now.

Germano Cavalcante (mano-wii) added a comment.Jul 16 2020, 4:50 PM

Since the problem does not involve bump maps, it might be better to do another report then.

Luis Felipe Peredo Noguez (renderluz) added a comment.Jul 16 2020, 5:05 PM

Ok I got the simplified file working, here's the google drive link:

https://drive.google.com/drive/folders/1MwjAgdw-3WuV2yw9m4dq7bfaoX4ZBQ6i?usp=sharing

In it there's a video showing the steps, and a blender file to reproduce the problem I'm testing this on the last
2.90 build that I just downloaded a few minutes ago, blender-2.90.0-75a09ba2ed26-windows64

I think its something to do with the render view, because the problem only happens if I'm in: Viewport shading: rendered, in Eevee

Quick steps, is:

1.-Load the file, go into Viewport shading: rendered.

2.-Go into texture paint mode, and click the mouse into the metal.png texture hold for a few secs, then draw some lines into the mesh.

3.-Release the hold and the stroke gets drawn, the video show the steps very clearly, the key strokes I used are screen casted in it so
reproducing it should not be a problem.

Let me know if this makes the problem identifiable, Cheers!

Germano Cavalcante (mano-wii) changed the task status from Needs Information from User to Needs Triage.Jul 16 2020, 7:28 PM
Germano Cavalcante (mano-wii) closed this task as a duplicate of T78991: EEvee late responce for shader and texture paint changes.Jul 16 2020, 8:33 PM