Undo doesn't work on UVmap deletion & only 5-6 UVmaps on same object possible #84690

Closed
opened 2021-01-13 22:34:44 +01:00 by Ahmad Bilal · 13 comments

System Information
Operating system: Windows 10
Graphics card: AMD Vega64 (20.11.1 driver)

Blender Version
Broken: 2.92.0 Beta (Jan 14 build)
Worked: Testing older versions.

Short description of error
There are two seperate issues, both related to UVmaps (under Object Data Properties)


1. First of all the undo doesn't revert the deletion of UVmap (I tested with 2 recent versions of blender). even reverting the file doesn't work! (while blender is open).

Exact steps for others to reproduce the error

  • Have multiple UVmaps
  • Delete one using the '-' button on the right side
  • Ctrl+Z to undo the deletion of UVmap (broken)

Temporary Workarounds

  • Close blender without saving, launch it again
  • Or restore from a autosave
Undo was temporarily broken, but was already fixed by rB73169628a1853fcc5e93c6d0c70c6668452b8a61

  1. I'm working on something that requires me to have multiple uvmaps (I created a total of 7). But it seems after creating a 5th or 6th one, blender seems to have issue in displaying them properly. (I'm only using each UVmap (Uvmap node) connected to a Image Texture connected to Emission Shade (see attached image)).

5-6 out of 7 uvmaps are showing up correctly as intended, but only the lowest one in the list is displaying wrong (see attached image)

At first I thought I was doing something wrong, so I redid the steps a few times. But now I'm sure its a bug as:

  • Deleting 1 of the other UV maps, corrupts the the lowest one automatically (I deleted the top most one, here in this case its name 'UVmap_Tree_Original')
  • But after that the 2nd UV map in the list (here marked 'UV_Top') .. doesn't display correctly anymore.

UV_issue.png

**System Information** Operating system: Windows 10 Graphics card: AMD Vega64 (20.11.1 driver) **Blender Version** Broken: 2.92.0 Beta (Jan 14 build) Worked: Testing older versions. **Short description of error** There are two seperate issues, both related to UVmaps (under Object Data Properties) ---- ~~1. First of all the undo doesn't revert the deletion of UVmap (I tested with 2 recent versions of blender). **even reverting the file doesn't work! (while blender is open)**.~~ ~~**Exact steps for others to reproduce the error**~~ - ~~Have multiple UVmaps~~ - ~~Delete one using the '-' button on the right side~~ - ~~Ctrl+Z to undo the deletion of UVmap (broken)~~ ~~**Temporary Workarounds**~~ - ~~Close blender without saving, launch it again~~ - ~~Or restore from a autosave~~ ``` Undo was temporarily broken, but was already fixed by rB73169628a1853fcc5e93c6d0c70c6668452b8a61 ``` ---- 2. I'm working on something that requires me to have multiple uvmaps (I created a total of 7). But it seems after creating a 5th or 6th one, blender seems to have issue in displaying them properly. (I'm only using each UVmap (Uvmap node) connected to a Image Texture connected to Emission Shade (see attached image)). 5-6 out of 7 uvmaps are showing up correctly as intended, but only the lowest one in the list is displaying wrong (see attached image) At first I thought I was doing something wrong, so I redid the steps a few times. But now I'm sure its a bug as: - Deleting 1 of the other UV maps, corrupts the the lowest one automatically (I deleted the top most one, here in this case its name 'UVmap_Tree_Original') - But after that the 2nd UV map in the list (here marked 'UV_Top') .. doesn't display correctly anymore. ![UV_issue.png](https://archive.blender.org/developer/F9577856/UV_issue.png)
Author

Added subscriber: @SomeAB

Added subscriber: @SomeAB
Author

I just tested this in 2.91.0:

Additional observations:

  • Confirmed: Deleting the topmost UVmap in the list, corrupts the next one below it
  • Confirmed: Undo works fine in 2.91.0
  • After confirming that 2nd-topmost UVmap gets corrupted, I did undo multiple times.. and I was back at 7 UVmaps .. and 6 lower ones are working fine now, but the topmost is now not working.
I just tested this in 2.91.0: Additional observations: - Confirmed: Deleting the topmost UVmap in the list, corrupts the next one below it - Confirmed: Undo works fine in 2.91.0 - After confirming that 2nd-topmost UVmap gets corrupted, I did undo multiple times.. and I was back at 7 UVmaps .. and 6 lower ones are working fine now, but the topmost is now not working.

Added subscriber: @rjg

Added subscriber: @rjg

This might be a combination of multiple issues. Please wait for the next daily build that includes 01b9dfeab4 and test again.

This might be a combination of multiple issues. Please wait for the next daily build that includes 01b9dfeab4 and test again.
Author

In #84690#1093201, @rjg wrote:
This might be a combination of multiple issues. Please wait for the next daily build that includes 01b9dfeab4 and test again.

The undo part seems to be.

But the other issue is not (as it is broken in 2.91.0 as well).

> In #84690#1093201, @rjg wrote: > This might be a combination of multiple issues. Please wait for the next daily build that includes 01b9dfeab4 and test again. The undo part seems to be. But the other issue is not (as it is broken in 2.91.0 as well).

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

I could not reproduce the second problem. I've created a minimal example project and it seems to work without any issues. Does this file work for you?

T84690_3.blend

@SomeAB Could you please provide a minimal example project that causes these issues in your project?

I could not reproduce the second problem. I've created a minimal example project and it seems to work without any issues. Does this file work for you? [T84690_3.blend](https://archive.blender.org/developer/F9578346/T84690_3.blend) @SomeAB Could you please provide a minimal example project that causes these issues in your project?
Author

I will upload the file I was working on (its not a important project anyway). But will do tomorrow.

I will upload the file I was working on (its not a important project anyway). But will do tomorrow.
Author

Here is the example file: https://drive.google.com/file/d/1U_h6f4njwUv6TtRfYJLSU8EY6G21yA3s/view?usp=sharing

The object 'Tree_Final' has the multiple UV maps.

How to reproduce:

  1. Add another UVmap node + image texture node

  2. In UV map node, select the 'UVMap_Tree_Original' .. and for image texture ..select "EonTexture_Tree_01".

  3. Connect Each Texture node (now there shoudl be total 7 instead of 6) directly to the Material Output (Surface), one-by-one.

  4. (IMPORTANT: Please notice that UVmaps currently in this file are projected from 6 sides: Top, Bottom, X1 (X-axis positive).. and so on. So X1 would look correct while viewing from X positive side only (numpad 3 to view it). This is NOT the issue.

However when viewing each of them from their respective sides, they should all look correct, but you will notice 1 out of the 7 (it happens randomly) .. won't look correct.

  1. Now delete 1 of the UVmap from the 7 (try deleting the top-most in the list), and check again (specially the second most in the list). Most probably, the one that was not showing/displaying properly earlier would get corrected automatically.
Here is the example file: https://drive.google.com/file/d/1U_h6f4njwUv6TtRfYJLSU8EY6G21yA3s/view?usp=sharing The object 'Tree_Final' has the multiple UV maps. How to reproduce: 1. Add another UVmap node + image texture node 2. In UV map node, select the 'UVMap_Tree_Original' .. and for image texture ..select "EonTexture_Tree_01". 3. Connect Each Texture node (now there shoudl be total 7 instead of 6) directly to the Material Output (Surface), one-by-one. 4. (IMPORTANT: Please notice that UVmaps currently in this file are projected from 6 sides: Top, Bottom, X1 (X-axis positive).. and so on. So X1 would look correct while viewing from X positive side only (numpad 3 to view it). This is NOT the issue. However when viewing each of them from their respective sides, they should all look correct, but you will notice 1 out of the 7 (it happens randomly) .. won't look correct. 5. Now delete 1 of the UVmap from the 7 (try deleting the top-most in the list), and check again (specially the second most in the list). Most probably, the one that was not showing/displaying properly earlier would get corrected automatically.

I was not able to reproduce the described issue. All image textures get correctly displayed from the respective perspective they've been projected from. Does the issue still occur for you with the current daily builds?

I was not able to reproduce the described issue. All image textures get correctly displayed from the respective perspective they've been projected from. Does the issue still occur for you with the current daily builds?

@SomeAB Are you still having this issue in current daily builds of Blender 2.92?

@SomeAB Are you still having this issue in current daily builds of Blender 2.92?

Changed status from 'Needs User Info' to: 'Archived'

Changed status from 'Needs User Info' to: 'Archived'

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thank you for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thank you for the report. If the problem persists please open a new report with the required information.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#84690
No description provided.