Tom D

Tukifri

About Me

Connect

LOCATION
Luxembourg, Not Specified
WEBSITE

Houdini Skills

Availability

Not Specified

Recent Forum Posts

Karma XPU Artifacts with 4090? May 2, 2024, 9:24 a.m.

Hi


I have the same issues with my 2080, I thought that a new Gpu (4090) will fix the problem but as I read your post it will not..

I tested to add this envvars.
KARMA_XPU_OPTIX_SPARSE_TEXTURES = 0
It fixed the issues but Optix doesn't start (initializing) so very poor performance

I tried also with this 3 envvars. Same result
KARMA_XPU_OPTIX_SPARSE_TEXTURES=0 (default is 1)
KARMA_XPU_OPTIX_HQ_LINEAR_FILTERING=1 (default is 0)
KARMA_XPU_DISABLE_MIPMAPS=1 (default is 0)


Is there any other solutions to fix it?

Thanks

Artifacts appears in Houdini XPU - UDIM Issues April 25, 2024, 8:55 a.m.

Pretty weird bug to reproduce.. So I did a simple scene with a mesh from kitbash. I only connected a normal-map texture.
When I used <UDIM> the artifacts appear in XPU. NB: The textures for the tests are not related to the mesh but I got the same bug with my working mesh that have correct UVs and UDIMS.

I did the test with a folder of 80 maps(normal)and the bug appear but when I connect half of the textures, there's no bug anymore.. The bug also disappear when I reduce the mesh polygon by deleting half of the mesh for example.

I did some tests with .abc and .fbx and it's the same issues

Artifacts appears in Houdini XPU - UDIM Issues April 23, 2024, 11:45 a.m.

Hi,

I got an issue when I render with XPU that seems to be related to udims.

On huge assets(building) it seems that the UDIM workflow doesn't work properly and break the render with some artifacts.

The asset has a mtlxStandardSurface and everything is working fine in houdini GL or CPU but as soon I used XPU render, the mesh disappears and create some artifacts in all the scene.

After some tests it seems to be a UDIM problem as it only happen when I used <UDIM> token in my texture path otherwise if I used the texture path "1001" the XPU work correctly.

I'm not seeing any errors in the logs.

Is there any solution or update that would fix that issue?