FYI, I'm getting a similar preview error if the asset browser is visible.

In D13958#387738, @Aras Pranckevicius (aras_p) wrote:

In D13958#387720, @Bay Raitt (spiraloid) wrote:

I just saw this thread. In case it's of any use to you for testing Aras, here's a dense polymesh from zbrush with the extra per vertex "polypaint" data. This is a pretty common obj variant. it should look like this when properly imported.

@Bay Raitt (spiraloid) if this is a feature request for something that the old OBJ importer was not supporting, then the new one definitely won't support it either. It's supposed to be "just faster", with more or less zero functionality changes. If you want the OBJ importer (or exporter) to support extra stuff, best would be to open new bug reports or feature requests somewhere else.

I just saw this thread. In case it's of any use to you for testing Aras, here's a dense polymesh from zbrush with the extra per vertex "polypaint" data. This is a pretty common obj variant. it should look like this when properly imported.

here's a hacky catchall I used to force an update when all the other solutions failed me.

Just adding enthusiasm here. This feature is going to open a lot of creative opportunities.

Thanks so much @Michael (michael64), Much appreciated.

Different issue then T93950.

done.

@Jeducious (jameshcrowther) man I had to chase this for ages to get a repro. I wrote an addon to do it. this addon loads a template file with a camera in it and tries to save it to a new file. it has something to do with just the presence of a camera in the loaded template scene.

Hitting this too. so glad to find this thread.

Thanks for the response. I like that it's not changing anything. I am wondering how to put characters in it so that they can be added to scenes without additional setup.

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".

I'm basically trying to create lightweight memory blend files for my http://3dcomic.shop 3d comics. if I do it on disk I know I'll ignore the resource constraints present in the web browser so I want the whole chapter loaded into memory and not on disk (same as it will be in the browser)

even if I turn specular and clearcoat to 0 on the default Principled BSDF shader, it's still a little brighter than the bake.

yeah I noticed that. I switched over to cycles and I'm still seeing dull specular. I wonder what it is...

cheers, thanks for the tip.

Confirmed it's fixed. Thankyou!!

I see this was marked as invalid. is there some other way to stop the tab key from toggling to pose mode on an armature?

interesting. what makes the click select+activate worth special casing then? is there some essential use case that requires a mismatch between selected bones and a deselected active bone?

hmm.. we might want to revisit this. if the user has clicked on a bone to make it active, then box selected a new set of bones (removing the highlight for the originally active bone) the UI is now displaying a stake state that is longer correct right?
both the viewport, and the outliner are saying that the highlighted bones are selected. but if the user performs an operation that requires an active bone, the box selected bones are ignored and only the last clicked bone is acted upon.

After looking at it it a bit more, it looks like these issues are all because multires was not implemented as a conventional hierarchical subdiv and is instead storing the vertices relative to the edgewise linear interpolation of the parent level subdivision. it's also not adjusting the parent's cage vertice positions during level switching and instead only does a reshape when choosing "apply base" instead of on each level switch.

looks to still be a problem in

on further reflection, I think I made be misunderstanding the intended behaviour of multi-res. I was expecting it to behave like open subdiv (i.e. pixar, zbrush, maya etc)
http://graphics.pixar.com/opensubdiv/docs/release_34.html

hitting apply base on subdivided cube after modifying lowest and highest levels of subdivision is producing odd artifacts too.

Just hit this trying to use "group remove" w a texture mask on a VertexWeightEdit Modifier as well.