madrendermanI'll write in this topic when it will be available)
Is Fusion available on orbolt ?
By the way it took around three weeks for my tool, hope it will be faster this time…
Anyway I'll be free to ask, how much money I have to put aside
Thank you kindly for answer.
What actually happening, it is *value* of shop_materialpath attribute in imported .obj file, set to something like /shop/my_material , and that obviously is not recognized by mat network. By changing that value to something like /mat/my_material, let's say using the VOP network ( even without using Material SOP ) - material is recognized by mat network, everything is fine.
In other words, if shop become obsolete in favor of mat network, perhaps it's good idea to “update” the obj importer too, to write something like /mat/my_material, as value of shop_materialpath.
just noticed that shop_materialpath attribute, created on imported obj files from Maya, is not recognized by new mat network in h 16. Which is, well, expectable, also i was able to create groups based on shop_materialpath and assign new materials, suitable for mat network, so no problems there.
Anyway I'm still curious, is there a some other automatism like this one, now working with mat network too. Or… shop_materialpath, or something else in this style is considered as obsolete, together with SHOPs. Docs are saying, “SHOPs are obsolete as of Houdini 16”.