Sorry for the title, I didn’t find a more self explanatory one.
I would like to be able to us wrap3 to bake textures from many megascan assets having their own individual uvs and textures, onto a poly reduced and re-uved “AssetC”.
The goal being to take advantage of all megascan datas to build a new assets with a good start of albedo, rougness normal maps from the original source but with non
overlapping uvs.
Is it something possible in Wrap3? Or would any of you have a better idea on how to achieve that with any existing software?
(sorry for image quality but the size limitation is quite low)
The forum wasn’t active for a while, please sorry for such a late response.
Unfortunately, in Wrap you can’t merge objects in 3D. But you can get Projected Textures from Asset_A and Asset_B to Asset_C without this feature.
If Asset_C has only one UDIM, you need to make ProjectTextures from Asset_A to Asset_C and from Asset_B to Asset_C. The results can then be merged using the MergeImage node.
If Asset_C has many UDIMs, you need to indicate which UDIM you want to use for projection. This can be done using the TransferTexture node. After that, you should save different UDIMs to separate files.
Many thanks for your feedback.
It could indeed be a work around, but it require some more prep work with some bank asset before to project them as you need to duplicate the asset, edit the uv and rename all the texture with
a new udim value. And this can be different from one assembly to the other based on the number of bank asset you have used.
I completely understand if it is not a common usage and if it doesn’t go in the line of development of your software, but to me it sounded like a nice feature to implement.
Many thanks for your hard work on this amazing program!
Textures can already be projected. To do this, you can use a combination of TransferTexture + ExtrapolateImage nodes. Within a month we are going to release a new version of Wrap that will include support for floating images. As you probably know, they have higher accuracy and are more suitable for albedo transfers, normal maps, and so on. At the moment, their transfer can be performed with the same combination, however, most likely some accuracy will be lost.