Game Development Community

Milkshape version of Kork?

by Bruno Campolo · in Torque Game Engine · 09/08/2006 (6:28 am) · 4 replies

Hi all, I am new to Torque and would like to mess around with modifying the models a bit and changing mount points and stuff like that, but to my surprise the player model is only in max. Some models in Torque are shipped with ms3d format and some with max... I'm not sure why. Does anyone know how I can get the kork model with skins and animations to Milkshape format? or does anyone have a place to get a different model with all the correct bones/animations in Milkshape format?

Thanks,
Bruno
Bruno Campolo's profile picture
Torque Owner Bruno Campolo

About the author

Creator of Bantam City Games, a one-man independent game development studio. To learn more, check out 'A Game Developer's Saga', a game development blog at: http://www.bantamcity.com/blog

Recent Threads

  • TGB onMouseEnter onMouseLeave problem
  • TGB onMouseEnter onMouseLeave problem
  • Alt+Tab and Alt+Enter don't work when GuiTextCtrl present
  • commandToClient networking questions
  • The 24 Hour Game Experiment
    • NextNext Thread
    PrevPrevious Thread
    More from Torque Game Engine


    Torque Owner Fucifer
    #1
    09/08/2006 (6:32 am)
    The Brave Girl come in MilkShape format. Look in the content pack section here. I just did some export on the pack from MilkShape everything export find.

    Torque Owner Bruno Campolo
    #2
    09/08/2006 (7:08 am)
    Thanks Michael, that will work perfectly. I didn't even realize that the kork model had dsq files... I think I'd rather have them in one dts anyway (which the brave tree girl would provide).

    Thanks Again,
    Bruno

    Torque Owner Fucifer
    #3
    09/08/2006 (7:24 am)
    You very welcome.

    Torque Owner Rex
    BrokeAss Games
    #4
    09/08/2006 (8:19 am)
    Embedding sequences inside a dts shape that may require blends and/or playing two sequences containing the same Nodes is probably not a good thing to do, you'll sacrafice fileSize and Node conflicts if used with a shape needing many sequences. Mechanical type objects this is perhaps fine for; becareful with organic/human types...;).

    ...you'll wonder why your blends don't work very well....


    I try to keep sequence information down to the Nodes needing the transforms for exporting only, or by logical movementThread category...actionThreads, armThreads, headThreads, visibilityThreads....etc...upperbody, lowerbody, hand gestures...:).