Fixed minor oversight in last update.

@Leon Zandman (lzandman) I will try to pull latest from master in the next few days.

I just tried (locally) to include some recent changes from master into the usd-importer-T81257-merge branch. But some merge issues popped up. This USD branch doesn't seem to be (regularly) rebased or merged with master. Is there a reason for this?

I am super excited about this new Asset Browser. I've started using it in the 3.0 Alpha and am really happy with what is already implemented. So way to go! 🎉 🎉 🎉

• USD import: Update Prim Path Mask option help.

Patch updates based on Sybren's latest review.

May I ask if there will be a folder management function like a file manager, which will be very useful for a large number of management.

@william eguienta (kaiz3r) : feel free to comment again if you could check/answer the above, wil archive for now though.

(otherwise will be closed in a week)

@Philipp Oeser (lichtwerk) can you close the report?

In D11584#298867, @Sybren A. Stüvel (sybren) wrote:

Please remember to update the release notes straight after committing.

Any chance on seeing some basic support for geometry nodes modifiers & node groups any time soon?

In T88605#1178714, @Sybren A. Stüvel (sybren) wrote:

@Philipp Oeser (lichtwerk) I overlooked that you had a patch already, hope you don't mind me committing my own version ;-)

Since rB7c681477094e: Fix T88605: Alembic import crashes when missing `arbGeomParams` was committed...

@Philipp Oeser (lichtwerk) I overlooked that you had a patch already, hope you don't mind me committing my own version ;-)

Please remember to update the release notes straight after committing.

In T81257#1177299, @Michael Kowalski (makowalski) wrote:

I think one could argue that the missing inputs should be handled differently in the importer, and this is open to discussion. But please let me know if I'm missing something.

@Leon Zandman (lzandman) Hi Leon. The emissive_map and normal_map UsdUVTexture shaders are definitely in the USD and these shaders are connected to the emmissiveColor and normal inputs of the UsdPreviewSurface shader, respectively. But the emissive_map and normal_map shaders are missing the file inputs, so they are not well formed, in that sense.

In T81257#1177262, @Michael Kowalski (makowalski) wrote:

I looked at that USD and it turns out that some of the UsdUVTexture shaders don't have file inputs specified.

@Leon Zandman (lzandman) Hi Leon. Thank you for reporting this! I looked at that USD and it turns out that some of the UsdUVTexture shaders don't have file inputs specified. The material reader prints warnings about this in the Blender console, e.g.,

LGTM, thanks!

I imported the Playdate game console USDZ (unzipped it first; used the experimental USD preview option). When switching to Cycles and to Render Preview I noticed the whole thing turned purple. This of course implied missing textures. A little experimenting showed all materials had a faulty node setup connected to the Emission node of the Principled BSDF. When I disconnected it the model had its original colors again.

To add my two cents:

• I agree the bottom input should accept full paths.
• Having the bottom input convert filenames into “safe” variants is unwanted functionality, especially for dialogs displayed for opening files (in contrast to save dialogs).
• I also think it’s wrong for the top input (folder path) to suggest creating a new directory when a path that doesn’t yet exist is entered. Having a dedicated button on the dialog for creating a new folder is the way to go.

FYI, project update here: Asset Browser Project Update.

Can reproduce on 3.0.0 (rB8c3f4f7edf9).

According to T79635 this action should be possible, and it is regression from 2.92, even though that didn't allow to move modifier of overridden object.

Some more review comments. I haven't read through everything yet, though, but I wanted to at least submit this.

Thanks for the response. I like that it's not changing anything. just trying to figure out how to put characters in it.
(The first thing I tried was to link a rig and create a library override for it and make an asset for it)

In T73366#1172878, @bay raitt (spiraloid) wrote:

Will the asset manager support skinned armatures?

There's no such thing in Blender.

Will the asset manager support skinned armatures? I've got an armature with a skinned mesh parented inside it. when I select the armature and mark as asset, I only get the skeleton without the skinned mesh.
when I select both the armature and the mesh and mark as assets, I get them separately without the skinning connection "because of renaming".

@william eguienta (kaiz3r) : could you check the above please? (otherwise will be closed in a week)