検索 - User list
Full Version: Subdivision or some other issue?
Root » Solaris and Karma » Subdivision or some other issue?
Mirko Jankovic
I as testing karma and xpu when 20.0 aws out, then had bni a bit busy to keep testing but now trying to make it work again for couple of my project and still running into old issue.
I have character animated in maya, exported as USD and imported in Solaris, added materials and hoping to render it. But I see these artefacts on the mesh. They are not there if I create object nit he H and smooth it, or even if I import this mesh as obj in the scene then move load into Solaris stage. But loading USD like thsi gievs me thsi issue.
I'm thinking that I'm probably doing something wrong either exportin from maya or importing into Solaris.
Any ideas, tip san tricks?
Attached image of the problem nd currently what I'm using to import into stage.
Enivob
I'd try adding a normal node to the end of the network chain.
Mirko Jankovic
No effect. I tried even with SOP Create, then in there USD import, unpack and polygon, and then normal as well. No change
jsmack
Is this only visible with Karma XPU renders? I remember there being a sample bias bug with environment lights and XPU.

It also looks a little bit like two overlapping meshes.
antc
If it's only XPU and not CPU then most likely a bug. If those artifacts are in both renderers it could be a normals issue maybe. Are those meshes configured to render as subdivision surfaces or (pre-subdivided) polygon meshes? Does the mesh have a "normals" primvar? Like jsmack said it does kind of look like overlapping meshes as well.
Mirko Jankovic
I tried exporting from maya again, export with all subdivison options in USD export, none, loop, bilinear, catclark... Now none of them renders smoothed as all. And on top of that rendering CPU still not smoothed but those artifacts are not visible. Rendering with XPU artefacts are there.

Now figured, they are here with dome light,
rendering with karma skylight and artefacts are not there.
Ok found it again. so it is still same bug as it seems s when H20 lunched.
When using HDRI I have to set Maximum HDRI size at something huge like 100000, now artefacts are gone.
Tim Crowson
Sometimes Maya includes normals in the export that actually cause problems later. I have sometimes fixed this in Solaris by blocking the normals attribute:

1. select any mesh
2. find the 'normals' attribute for this mesh in the scenegraph details panel (I'm assuming it's there)
3. right-click > Edit Properties
4. in the Edit Properties LOP that gets created, switch the control parm to 'block'. (In the scenegraph details panel, the normals attr should now appear grey, with no value)
5. Edit the prim pattern on this Edit Properties LOP so it affects the meshes you want

Basically this should cause the renderer to figure out the normals itself rather than pull them from an attribute.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Powered by DjangoBB