# Getting empty string when trying to get resolvedPath of UDIM path

**URL:** <https://forum.aousd.org/t/getting-empty-string-when-trying-to-get-resolvedpath-of-udim-path/406>\
**Category:** USD\
**Tags:** rendering, python\
**Created:** [August 21, 2023, 8:47pm UTC](https://forum.aousd.org/t/getting-empty-string-when-trying-to-get-resolvedpath-of-udim-path/406 "2023-08-21T20:47:49Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![dhruvgovil](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.aousd.org/dhruvgovil/32/3_2.png) [@dhruvgovil](https://forum.aousd.org/u/dhruvgovil)\
**Post date:** [August 21, 2023, 9:08pm UTC](https://forum.aousd.org/t/getting-empty-string-when-trying-to-get-resolvedpath-of-udim-path/406/2 "2023-08-21T21:08:12Z")

</div>

Hi @Quaxo , welcome to the forum.  
Unfortunately, the UDIM resolution is left up to the renderer.

USD itself doesn’t have a UDIM resolver so the empty string is due to failed resolution.

If you’re trying to resolve this without a renderer doing it for you, the easiest method is probably querying the raw string and substituting the UDIM token yourself, then asking usd to resolve that.

---

_[View the full topic](https://forum.aousd.org/t/getting-empty-string-when-trying-to-get-resolvedpath-of-udim-path/406)._