It's been a while since I tried continuing my effort and after talking to some folks, there has been a great port/re-implementation of the XSIZETools to Blender. While I'm pretty proud of what progress I had made, I see no real reason to continue it. The tool that works really well is here:
https://github.com/PrismaticFlower/SWBF-msh-Blender-IO
ORIGINAL POST:
If this is not the correct place to post this then I apologies. But, I'm attempting to convert the XSIZETools to Blender and have already a loose prototype working for import. BUT, I'm looking for help or maybe to pay someone to complete this. OR, what would really be nice is someone telling me it's already been done and I can't Google foo for sh*t.
XSIZETools Request Ticket (I am not the creator of the initial request.)
https://github.com/Schlechtwetterfront/ ... /issues/12
Blender Code Prototype (Working in Blender 2.79)
https://code.itdominator.com/itdominato ... SH2-Plugin
Notes:
1 - Converted to use Python 3
2 - Please read the Issue ticket for the gist of what's been done plus images.
3 - THIS IS A VERY EARLY PROTOTYPE!! Best practices and actual project structure are TBD.
-- Images of Import Prototype Working --
Republic Barcspeeder mesh in Blender:
Here's the Republic combat speeder with Blender smooth shading enabled:
I also like the idea of keeping it hot swappable whereby the actual plugin code could be pulled out from the Blender wrapper and plopped into the old and crusty Softimage system with no fuss. (Technically, this requires making changes to what I did with the imports but whatever.) To do the desired outcome would require understanding WHAT the calls are returning and WHAT it actually means to the outcome of the mesh. Which means we need to know why what is being done is done and what the API calls are actually intended for. I am very new to 3D stuff when it comes to meshes, transforms, vectors, uv mapping, etc and its programmatic aspects. So, I'm kinda a lame duck right now until I get motivation or help.