this was banging my head for a couple of days..
when you use image-tiles which was intended specifically for UDIM usage, the workflow is very simple
select any of the tiled image following naming convention for udims e.g. Earth_Disp_1001.tif for your 1st udim image in 8x4 tile array.
That means that your 9th image is not Earth_Disp_1009, but Earth_Disp_1011 cause the matrix is 8x4 and it advances in V coord space to 1.0
Attached image shows that eventhough the directory is listing correct file structure, the text output box that lists all the files it thinks are images to be load, clearly shows that it needs Earth_Disp_0009, Earth_Disp_0010,Earth_Disp_0019,Earth_Disp_0020... where in fact they are NOT part of a 8x4 array.
BTW. this setup works out of the box in Redshift straight from the rs-image texture node, where the only thing i had to is write Earth_Disp_<UDIM>.tif.
attachment=0]UDIM_bug.png[/attachment]
thank you.
C4d 2025.4 , oct plugin 2025.4, WIN 10, rtx 3090, ram 192GB
UDIM tiles obvious bug
Moderators: ChrisHekman, aoktar
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.
All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
H. A detailed description of the issue and steps to reproduce it (Include Screenshots or video capture), as well as an example scene if applicable.
I. Copies of the Octane Log window and Console window outputs (full text attached as a file to your post is recommended).
Please note that reports of issues inside existing threads will be ignored/removed, and reports may be closed if the reporter does not respond to subsequent queries in the thread.
Hi,
What happens if you set the array to 10x4?
You should see 0009, and 0010 as empty tiles.
ciao,
Beppe
What happens if you set the array to 10x4?
You should see 0009, and 0010 as empty tiles.
ciao,
Beppe
We will look into this.poison wrote: Tue Nov 11, 2025 8:37 am this was banging my head for a couple of days..
when you use image-tiles which was intended specifically for UDIM usage, the workflow is very simple
select any of the tiled image following naming convention for udims e.g. Earth_Disp_1001.tif for your 1st udim image in 8x4 tile array.
That means that your 9th image is not Earth_Disp_1009, but Earth_Disp_1011 cause the matrix is 8x4 and it advances in V coord space to 1.0
Attached image shows that eventhough the directory is listing correct file structure, the text output box that lists all the files it thinks are images to be load, clearly shows that it needs Earth_Disp_0009, Earth_Disp_0010,Earth_Disp_0019,Earth_Disp_0020... where in fact they are NOT part of a 8x4 array.
BTW. this setup works out of the box in Redshift straight from the rs-image texture node, where the only thing i had to is write Earth_Disp_<UDIM>.tif.
attachment=0]UDIM_bug.png[/attachment]
thank you.
C4d 2025.4 , oct plugin 2025.4, WIN 10, rtx 3090, ram 192GB
in the meantime you could switch to using 2026.1, try to use the MaterialX Image node instead, and just put the same kind of path you use with RedShift:
Earth_Disp_<UDIM>.tif
MaterialX image nodes support UDIMs with this pattern out-of-the-box
What beppe says, UDIM has a fixed width of 10 tiles. You don't have to fill up that entire width but it is always 10.
Technically UDIM has a linear tile index starting at 1001. In any UDIM grids I’ve seen, the first row is 1001–1010, the second is 1011–1020, etc. Originally UDIM allowed other grid widths in which case it would wrap exactly in the way you observed. But in practice everyone uses 10 and Foundry now seems to have updated their spec to reflect that.
Technically UDIM has a linear tile index starting at 1001. In any UDIM grids I’ve seen, the first row is 1001–1010, the second is 1011–1020, etc. Originally UDIM allowed other grid widths in which case it would wrap exactly in the way you observed. But in practice everyone uses 10 and Foundry now seems to have updated their spec to reflect that.
-
arnon.marcus
- Posts: 13
- Joined: Wed Sep 06, 2023 11:17 pm
To add to what Roeland said, I've managed to demonstrate this working in Cinema4D, with a plane with camera-position projection used as UVs with a modulo of 8x4 to get the desired grid repeated: