Appearing and ereased strokes

[luc�a_5315]

Hi! I've been having this problem for 2 months, I've tried to work even with getting things deleted but there's no way :'

This only happens to me when texturing in hand-painted, after a while of texturing, when I want to go back a step with ctrl+z it doesn't go back a single step, but several steps, about 7 or 8 strokes are erased. For this I can try to not work with the ctrl+z, although it is very difficult, but the biggest problem comes when I save the file to close it, then I open it at some other time and part of the wall of the house that I texture is erased, it is erased uniformly in different layers. And with the new update some strokes that I have not painted appears. I share screenshots:

I have to add that I have had this problem in 2 different files, and it also happens to me from other computers, I have no idea what it could be :'(.

Thank you very much for reading me :))

[Cyril Dellenbach]

Hi @luc�a_5315,

Which version of Substance Painter are you using? This really looks like a bug we had with with the 11.0.0. Have you already update to 11.0.1 ?

Let me know.

[luc�a_5315]

Hi @Cyril Dellenbach !

Yep, this has been happening to me since the 11.0.0 update, but I already have 11.0.1 installed and it's still happening to me. I suspected it might be a bug in the update but didn't know 100%.

The files were created in 11.0.0, and it seems that even if I upgrade to 11.0.1 the bug is not fixed because the file drags it? Or should it be fixed even if the file was created in that other version when upgrading?

If the solution is to create a new file from this last version and re-texture everything... Is fine, I just don't want things to be deleted hahahah.

[Cyril Dellenbach]

The update should fix the problem, regardless of when the project was created. Are you by any chance on Mac?

[luc�a_5315]

No, I use Windows 10, this could be the problem?

[Cyril Dellenbach]

I don't think so... If you were using a MAC, we maybe had a lead... Could you send me your log at cdellenbach@adobe.com with a link to this thread?

Make sure that the bug occured in you latest session before sending the log (Help > Export log).

Keep me posted.