Blender 3.2 stops recognizing UDIM texture files with specific file name. #99077

New Issue

Yutaka Fukumoto · 2022-06-22T04:26:49+02:00

Yutaka Fukumoto commented

2022-06-22 04:26:49 +02:00

System Information
Operating system: Windows 10 64 bit
Graphics card:NVIDIA RTX 2070

Blender Version
Broken: 3.2
Worked:3.1,2.93

Is this glitch or just a new way of handling UDIM files?
There are 2 png files with name "1111_11.1001.png" and "1111_11.1002.png" in a folder and If I load those files in Image Texture node, those files are imported as UDIM files, but If I put 2 other files with name "2111_11.1001.png" and "2111_11.1002.png" in the same folder, files "1111_11.1001.png" and "1111_11.1002.png" can be recognized as UDIM files. And "2111_11.1001.png" and "2111_11.1002.png" can't be loaded as UDIM too.

I found this because I always name textures with timestamp as "YYYY_MMDD_HHMMSS" format, like "2022_0622_152305" and file name "2022_" triggers this glitch. File with "2xxxx_" name can be recognized as UDIM in blender 3.1 and 2.93 but 3.2 can't handle these files. Why?

**System Information** Operating system: Windows 10 64 bit Graphics card:NVIDIA RTX 2070 **Blender Version** Broken: 3.2 Worked:3.1,2.93 Is this glitch or just a new way of handling UDIM files? There are 2 png files with name "1111_11.1001.png" and "1111_11.1002.png" in a folder and If I load those files in Image Texture node, those files are imported as UDIM files, but If I put 2 other files with name "2111_11.1001.png" and "2111_11.1002.png" in the same folder, files "1111_11.1001.png" and "1111_11.1002.png" can be recognized as UDIM files. And "2111_11.1001.png" and "2111_11.1002.png" can't be loaded as UDIM too. I found this because I always name textures with timestamp as "YYYY_MMDD_HHMMSS" format, like "2022_0622_152305" and file name "2022_" triggers this glitch. File with "2xxxx_" name can be recognized as UDIM in blender 3.1 and 2.93 but 3.2 can't handle these files. Why?

Yutaka Fukumoto commented

2022-06-22 04:26:49 +02:00

Added subscriber: @Zcyber

Jesse Yurkovich commented

2022-06-22 04:54:51 +02:00

Added subscriber: @deadpin

Jesse Yurkovich commented

2022-06-22 04:54:51 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Jesse Yurkovich commented

2022-06-22 04:54:51 +02:00

The behavior did change a bit between the versions as it now favors searching the beginning part of the filename first rather than start from the end and ends up confused in your case. To fix this issue, modify the image in the Image Editor like the example below:

Change Source to UDIM
Change the filename to include the exact position where the tokens should be placed.

I'll look into improving this in the future.

The behavior did change a bit between the versions as it now favors searching the beginning part of the filename first rather than start from the end and ends up confused in your case. To fix this issue, modify the image in the Image Editor like the example below: - Change Source to UDIM - Change the filename to include the exact position where the <UDIM> tokens should be placed. ![ex0.png](https://archive.blender.org/developer/F13215030/ex0.png) I'll look into improving this in the future.

Yutaka Fukumoto commented

2022-06-23 09:23:29 +02:00

you said "it now favors searching the beginning part of the filename first", but your image's file name starts with 4 digits number. It will not be recognized as UDMI. My all files have timestamp "YYYY_MMDD_HHMMSS" , and blender 3.2 thinks it's UDIM tokens but they all have same UDIM tokens then blender can't load images, right?
Then what need to do is just remove timestamp. I need to rename all file names then.

you said "it now favors searching the beginning part of the filename first", but your image's file name starts with 4 digits number. It will not be recognized as UDMI. My all files have timestamp "YYYY_MMDD_HHMMSS" , and blender 3.2 thinks it's UDIM tokens but they all have same UDIM tokens then blender can't load images, right? Then what need to do is just remove timestamp. I need to rename all file names then.

Atair-1 commented

2022-07-19 03:02:15 +02:00

Added subscriber: @Atair-1

Atair-1 commented

2022-07-19 03:02:15 +02:00

this cant be right - any file with a ending like _1280 that usually indicates resolution, or as in the comment above - it might be a timestamp, get interpreted as udim?
And further fails to load in eevee / viewport - defaulting to the pink shader. Rendering in cycles, but only on the first run, if you change the type to single image and back to udim, it fails in cycles too

Basically we cant have any images like "myImage_1280.jpg" anymore - this does look like a critical bug..

this cant be right - any file with a ending like _1280 that usually indicates resolution, or as in the comment above - it might be a timestamp, get interpreted as udim? And further fails to load in eevee / viewport - defaulting to the pink shader. Rendering in cycles, but only on the first run, if you change the type to single image and back to udim, it fails in cycles too Basically we cant have any images like "myImage_1280.jpg" anymore - this does look like a critical bug..

Jesse Yurkovich commented

2022-07-19 03:15:08 +02:00

@Atair-1 that problem is the reverse of the issue here. When loading an image that may have such 4digit numbers in them between 1001 and 2000, unselect the "Detect UDIMs" option in the Image load dialog (Open the properties settings; Gear icon in upper right). It will load the image as Single and continue to work correctly in both Eevee and Cycles. The option in that dialog will remain as you set it for the duration of the blender session as well.

Bastien Montagne added

and removed

labels 2023-02-10 12:16:44 +01:00

Sign in to join this conversation.