Page MenuHome

Texture Map goes blank
Closed, ArchivedPublic

Description

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: Radeon RX Vega ATI Technologies Inc. 4.5.13559 Core Profile Context 26.20.12001.7006

Blender Version
Broken: version: 2.81 (sub 15), branch: master, commit date: 2019-10-18 14:41, hash: rB970d7ed860f1
Worked: (optional)

Short description of error
While painting .. my texture map just disappeared .. I don't even know what caused it.. it just happened while working. And this is definitely a bug.. see my screenshot.. the texture paint is there .. somewhere in the memory. Btw, I'm in cycles render engine

Exact steps for others to reproduce the error

  1. Was painting in texture paint
  2. Went to sculpt mode to add some more details to mesh
  3. texture map just goes blank!

Note: Loading a previous save .. when the texture map was alright.. doesn't work either. Nor opening the file in 2.8.. infact in 2.8 it deletes that thumbnail as well.. and it goes blank.

Lost me a few hours of work :(

Details

Type
Bug

Event Timeline

Ahmad Bilal (SomeAB) updated the task description. (Show Details)

if you had use dynotopo to add particular IMO this is not a bug

You forgot to upload a simplest possible .blend file to reproduce this problem

Ahmad Bilal (SomeAB) added a comment.EditedSat, Oct 19, 6:25 PM

no dyntopo was not used at all. Besides, see my screenshot carefully .. And here is the .blend file

in your file stone texture is a flat brown texture, can you try my .blend file with packed inside one mine texture and confim that you still have same problem

thank you

I think there is a misunderstanding here. I didn't claim .. that I can't make texture maps at all. Let me word it differently:

  1. I started by creating a brownish texture map .. 2k res, and kept painting in the details with different colors.
  2. In the middle of painting, I had to sculpt a bit .. but I didn't add any additional geometry.
  3. Around that time .. few clicks/keypresses back or forth .. I was suddenly staring at a blank brownish map .. and I'm 100% positive that paint bucket was not even touched.
  4. The proof of this being a bug is .. that in the thumbnail .. I can still see the texture map.. as it was suppose to be (and NOT blank) .. but in image viewer .. it shows up plain brown.

Looks like you didn't save your texture regularly while painting, so all your strokes were on ram, which was needed when you started doing something else. And then blender just read again the only data it had, that you gave it generating the image, brownish texture map at 2k resolution.

You could argue that the way the data is handled right now with texture painting isn't optimal, forcing you to save your blend file AND your images, but that's another topic.

I don't know how often the preview update itself, it's just the old one showing I think.

But still, while painting.. and while the blender session is maintained .. textures shouldn't just disappear like that. The preview is not the old one btw.. it is what I was in the process of painting.

@Ahmad Bilal (SomeAB)
This certainly should not be happening.
If you can, please try to find a way to reproduce this.

Ahmad Bilal (SomeAB) added a comment.EditedThu, Nov 7, 6:35 AM

I honestly don't have a clue, that what exact steps may have caused this, but it seems to be still happening in 'very' rare cases .. and seems to be happening around when you switch images from the dropdown menu in image-editor.

  • Today I baked a heightmap inside blender, and thankfully saved it.
  • Adjusted my terrain and baked a slightly adjusted height map. Saved it.
  • Switched between the two, from inside the image-texture NODE .. and no problems still.
  • but when I switched between the images using the image-editor window on lower-left of my shading tab. One of my textures went blank!

Thankfully this time, I had everything saved.. so there was no damage.

We need specific steps to reproduce the problem, there's not much we can do in a report like this.
Maybe some user will find the reason for the bug and report it in the future.
But for now this one will be closed.