Page MenuHome

Mapping node glitches in Blender 2.82a
Closed, ArchivedPublic

Description

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: rB375c7dc4caf4
Worked: (optional)

Short description of error
I was previously in Blender 2.80 and working on a scene which involved textures being manipulated with the mapping node in the shader editor. I updated to Blender 2.82a to try a feature and in doing so, the file hasn't been the same since. The mapping node in the material included in the file is now "undefined" and doesn't do anything. The problem is that if I restart Blender, it might work once then not again until I restart my computer. For example: I restart blender and it's correct and accurately manipulates the texture. I then close it, navigate to another program, do whatever, and if I open it again, the nodes will be undefined and glitched. It seems to happen pretty frequently but occasionally, it will work fine and then glitch out. It's hard to describe...it's like it works or it doesn't. I'm sure adding a new mapping node to replace these could work but the problem is that I've had a scene I'm working on for a few months and I can't remember the settings. Is there a way to get the data from the old mapping node?

Exact steps for others to reproduce the error
Open the attached blend file


If it's functional, the shader editor will be on the left...I included a little carrot to indicate which nodes are having the problem.
If they're standard mapping nodes, try closing the program and opening it again (without restarting the whole system).
They should now be red, undefined nodes that just pass the UV data through without doing anything.

Event Timeline

Does this problem occur when opening the file saved by Blender 2.82a in Blender 2.82a or were you opening it in another version?

Brecht Van Lommel (brecht) claimed this task.

Once you save a file in a newer version, you can't generally open it again in an older version.

This file simple will not work anymore in 2.80, sorry, there's nothing we can do about that.

@Brecht Van Lommel (brecht) I'm not opening it in a previous version! It's only been opened in Blender 2.82a since I've updated.

@Robert Guetzkow (rjg) The problem occurs when opening the file saved and opened in 2.82a AND old versions. I've only tried opening it in 2.8 as after several occurrences in 2.82a.

Spuds (SpudsTheMann) changed the subtype of this task from "Report" to "Bug".Mar 19 2020, 7:10 PM
Brecht Van Lommel (brecht) reopened this task as Needs Triage.Mar 19 2020, 7:13 PM
Brecht Van Lommel (brecht) changed the subtype of this task from "Bug" to "Report".

The file header seems to shows this .blend file was saved with Blender 2.80, but it contains a screenshots of the glitch from 2.82.

So my understanding is that you opened this file in 2.82, saved it, then opened it in 2.80 and saved it again. Is that not the case?

@Brecht Van Lommel (brecht) I'm not sure why it opened and saved in 2.8. I must have miss clicked (I have both installed so that's my bad).

I've attached the correctly saved 2.82a file and also a screenshot of what it is supposed to look like, since it did "un-glitch" for 1 instance.

Spuds (SpudsTheMann) added a comment.EditedMar 19 2020, 7:25 PM

@Brecht Van Lommel (brecht) now that you mention it. I do have it set so when I double-click on the file itself, it opens with the previous 2.8 version of blender so I think it's been opening in that version all along. If I manually launch 2.82a and manually select it to open in that version it does work fine. My apologies for this...I should have remembered I set it to open in 2.8. I was under the impression I was opening a different version of blender than I actually was half the time. Thank you!

Robert Guetzkow (rjg) closed this task as Archived.Mar 19 2020, 7:36 PM
Robert Guetzkow (rjg) claimed this task.

I'm closing the ticket, since the issue was caused by opening the file in an older version of Blender.

@Robert Guetzkow (rjg) @Brecht Van Lommel (brecht) excellent. Well, at the very least, you helped me realize my own fault. Thanks again!