View Full Version : Frankensteining two store meshes.
traelia
21st Jun 2012, 05:41 AM
So I've decided to take on this beast that is frankensteining.
I've chosen two store meshes:
http://www.modyourpanties.com/hosting/36097_120621003115Bohemian Blouse with Bow.jpg
And
http://www.modyourpanties.com/hosting/36098_120621003145Tiered Skirt.jpg
Now upon exporting these meshes, I found that TSRW couldn't recognize the morphs, so for whatever reason they don't work. Now I opened the files in S3PE and they do have morphs, and I don't know why TSRW isn't getting it, but still. I just need to figure out if there's a way to grab their old morphs and use them for the new meshes. All I did to the old meshes was delete some verts and re-assign a bone or two.
I've attatched a picture of the new combined meshes. I put them as LOD1_1 and LOD1_2, with no immediate problems in game testing, but they do explode obviously because of the lack of morphs.
I guess what I'm asking is if I can take the original morphs and some how apply them to the new mesh?
omegastarr82
21st Jun 2012, 07:06 AM
Stalk Cmar's latest posts to grab his/her latest link to the meshtoolkit. If you only deleted things you can use the match morphs tool/tab on both meshes. After using the tool double check everything in milkshape, mostly the seams. Then use the Frankenstein meshes tab/tool to make it all one mesh. Then IF you want to use TSRW, use the convert to TSRW WSO file. I've just had to do these same steps and it worked just fine.
http://modthesims.info/showthread.php?p=3876514#post3876514 This one maybe.
traelia
21st Jun 2012, 10:05 PM
Okay thanks Omega. I think Cmar's tool is just what I was looking for!
traelia
21st Jun 2012, 10:43 PM
Uuuh so yes, the tools would work.. if I had the morphs in a form other than .bodyblend.. Unless they can handle .bodyblend.. Or if there is a way to get .bodyblend to be .simgeom.. or something.
EDIT: Nevermind found the simgeom's in the package file of the original. I'm a dummy. I'll come back if I still can't get it to work.
CmarNYC
21st Jun 2012, 11:57 PM
Just wondering - did TSRW successfully export the morphs in the original wso files you imported into Milkshape and Frankensteined? If so, my Toolkit also has a function to take a wso with the base mesh changed with vertices removed or added, and update all the morphs to match so TSRW should be able to import it. I'd love for people to test this. There's no function to Frankenstein wso meshes because I figured you can just regroup in Milkshape, but do you think that would be useful?
Link to the current latest version of Toolkit, with BGEO to morphs conversion fixed to actually DO something: http://modthesims.info/showthread.php?t=478895
BTW I'm a she. :)
omegastarr82
22nd Jun 2012, 02:19 AM
I knew that! I just didn't want to get it wrong, your gender that is. While I haven't tried in a long time, I'm fairly certain you cannot just regroup meshes for TSRW frankenmmeshing. Unless they've changed something.
traelia
22nd Jun 2012, 02:33 AM
No you can't regroup for TSRW, but no they did not export with their morphs at all. They just exported as base and that was it. So using the toolkit will not work for .wso.
I tried exporting the morphs out of the package and using a converted .wso to .simgeom with the tool kit and the exported morhps, and that didn't work either. :/
CmarNYC
22nd Jun 2012, 03:13 AM
The store packages I've seen have used morph meshes instead of BGEOs so possibly that's why TSRW didn't export morphs - maybe it only uses BGEOs/bodyblends?
I think the morph meshes with the TSRW exported base didn't work because TSRW renumbers on import and the morph matcher depends on the vertex ID numbers. I really can't think of any way to fix this without starting over - export the original base and morph meshes from the store package. Then either convert to WSO and continue using Milkshape to Frankenstein the base, Toolkit WSO tool to match the morphs, and import into TSRW -or- work with simgeoms directly by Frankensteining the base mesh, Toolkit GEOM tool to match morphs, and either use CTU or convert to WSO at that point.
BloomsBase
22nd Jun 2012, 08:25 AM
do not clone a store file to frenkenstein, it will never work.
CmarNYC
22nd Jun 2012, 02:03 PM
Bloom is right that cloning in TSRW won't work, but you can definitely extract the meshes and convert to WSO.
http://www.modthesims.info/showthread.php?t=474871
If you're stuck on identifying which mesh is which, you can upload the package or pm me a link and I'll do it. Once I finalize my tool I'll write a tutorial since this will come up again.
omegastarr82
22nd Jun 2012, 04:49 PM
@Cmar - very small thing to point out regarding the convert BGEO to mesh part of your tool. It does work very well for me so far. The only small little annoyance I've had so far is that your tool looks for a BGEO file while the packaged files are actually blendgeom files. They still work just as intended you just have to click the "show all files" button when you're importing them into that part of the tool.
And Did anyone else know that when you import a morph GEOM over an altered base GEOM in milkshape it updated the morph for you?
CmarNYC
22nd Jun 2012, 05:02 PM
Thanks for that info about Toolkit - I can include .blendgeom in the file selection although I think you'll still have to manually change the filter. I'll have to look at whether it can filter more than one filetype at the same time.
Yes, very often if all you did was move vertices the original morphs will work just fine. It's not that Milkshape updates the morph - morph meshes contain only information on how to move each vertex to make the morph so unless the base has been changed drastically the morph usually still works. For example - if the fat morph mesh says to move a hip vertex to the right by 3.14, if you change the base mesh position of that vertex when you import the morph it'll still move to the right by 3.14 from the new position.
traelia
23rd Jun 2012, 05:34 PM
Ooooh Thank you for the replies everyone. I will try the method on Elexis' thread.
vBulletin v3.0.14, Copyright ©2000-2013, Jelsoft Enterprises Ltd.