Blender doesn't recognize UDIMs if they don't start at 1001 #82119

New Issue

Robert Rioux · 2020-10-27T01:01:28+01:00

Robert Rioux commented

2020-10-27 01:01:28 +01:00

System Information
Operating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro Vega 64 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18

Blender Version
Broken: version: 2.83.7, branch: master, commit date: 2020-09-30 06:12, hash: 192e591af9
Worked: (newest version of Blender that worked as expected)

Short description of error
I have 6 objects in my scene. The first 3 share the same shader, UDIMs 1001, 1002 and 1003. All good. The last three objects share another shader, UDIMs 1004, 1005, 1006 (they have a different name, like fooA.1001, fooA.1002, fooA.1003, fooB.1004, fooB.1005 and foo.1006). Blender doesn't recognize the second texture set. That's a show stopper when you get your textures from Substance Painter os Mari. It needs to be fixed asap please.

Exact steps for others to reproduce the error
Create a scene like the description above.

**System Information** Operating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits Graphics card: AMD Radeon Pro Vega 64 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18 **Blender Version** Broken: version: 2.83.7, branch: master, commit date: 2020-09-30 06:12, hash: `192e591af9` Worked: (newest version of Blender that worked as expected) **Short description of error** I have 6 objects in my scene. The first 3 share the same shader, UDIMs 1001, 1002 and 1003. All good. The last three objects share another shader, UDIMs 1004, 1005, 1006 (they have a different name, like fooA.1001, fooA.1002, fooA.1003, fooB.1004, fooB.1005 and foo.1006). Blender doesn't recognize the second texture set. That's a show stopper when you get your textures from Substance Painter os Mari. It needs to be fixed asap please. **Exact steps for others to reproduce the error** Create a scene like the description above.

Robert Rioux commented

2020-10-27 01:01:28 +01:00

Added subscriber: @Funnybob

Evan Wilson commented

2020-10-27 06:36:09 +01:00

Closed as duplicate of #77989

Evan Wilson closed this issue

2020-10-27 06:36:09 +01:00

Robert Rioux commented

2020-10-27 11:28:52 +01:00

You have to understand that UDIMs are NOT an image sequence that needs to start at 1001. UDIMs only represents tiles. They can be non-sequential and they don't have to start at 1001. This is how it works in every software in the industry. This is a perfectly valid UV setup that would work in every software but Blender.

You have to understand that UDIMs are NOT an image sequence that needs to start at 1001. UDIMs only represents tiles. They can be non-sequential and they don't have to start at 1001. This is how it works in every software in the industry. This is a perfectly valid UV setup that would work in every software but Blender.![Screen Shot 2020-10-27 at 6.27.37 AM.png](https://archive.blender.org/developer/F9109752/Screen_Shot_2020-10-27_at_6.27.37_AM.png)

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Blender doesn't recognize UDIMs if they don't start at 1001 #82119