BennyKok
commented
3 years ago yoyoyo @shuanghenyanshang , thanks for leaving feedbacks, I never thought there would be other people actually looking at using this haha.
You are right about from 1 to 3, here is some extra notes 1) Since the sp + texture export path will be handled by Taper, saving the blender project gives access to the relative file path for saving the sp project 2) By default, a texture export path will be sent to sp, so by doing a quick export (ctrl + shift + e and press export), the textures should go to the right path 3) Each model should do a quick UV unwarp and assign a material since the texture lookup with "Pull Textures" depends on the material slots data, most of the time, just close SP, and press "Send To Painter" again should update your model in SP, btw the SP project path will be also sent to SP, so by just pressing ctrl save in SP will save to the managed path, and next time you send to painter, the same file will be opened. 4) In theory, the textures should be mapped correctly if you are using the default output template in SP. under the hood, Taper referenced the texture slot mapping code heavily from Node Wrangler, so the result should be similar.
Other than this, the second major use case of this addon is to export stuff quickly into Unity, and I have got a unity c# editor scripts to map the SP textures to Unity with one click, in case anyone else seeing this, let me know if you are interested at that scrip, and I can post it somewhere.
Thank you for trying out!
shuanghenyanshang
Test results: plug-in version 0.0.5, software version 2.92, mainly test the bridging function with Substance painter (hereinafter referred to as SP), it seems that there are several details that need attention:
1: The project transferred to the SP needs to be saved as a blender project, and cannot be transferred if it is not saved
2: In SP, you need to export textures so that the items in blender can also have image textures
3: Blender objects need to be assigned to the material node before being transferred to the SP, otherwise they cannot be directly transferred back using the plug-in. It is also not feasible to add material nodes in Blender after the work of SP is completed. In this situation, I tried two methods: manual texture mapping / another is to re-import the SP into the plug-in, which seems to solve the problem.
4: The only thing that seems to be problematic is that when using the plug-in to import the texture materials that SP has prepared, it seems that only the metallic texture and base color texture can be imported, and the other textures have not successfully entered the blender.
Finally, thank you very much for being able to develop this plug-in, thank you~