1. Updated Resource Submission Rules: All model & skin resource submissions must now include an in-game screenshot. This is to help speed up the moderation process and to show how the model and/or texture looks like from the in-game camera.
    Dismiss Notice
  2. DID YOU KNOW - That you can unlock new rank icons by posting on the forums or winning contests? Click here to customize your rank or read our User Rank Policy to see a list of ranks that you can unlock. Have you won a contest and still haven't received your rank award? Then please contact the administration.
    Dismiss Notice
  3. From the gates of hell, the 5th Special Effect Contest Results have emerged.
    Dismiss Notice
  4. Rubbed the right way, the genie is out of its lamp! The 12th Concept Art Contest Results have been announced.
    Dismiss Notice
  5. Race against the odds and Reforge, Don't Refund. The 14th Techtree Contest has begun!
    Dismiss Notice
  6. Check out the Staff job openings thread.
    Dismiss Notice
Dismiss Notice
Do you have good ideas for new contests? If so, please open new threads in the Contest Submission sub-forum to discuss them.
Dismiss Notice
60,000 passwords have been reset on July 8, 2019. If you cannot login, read this.

Map Size strategy

Discussion in 'Map Development' started by Verdun, Apr 11, 2012.

  1. Verdun

    Verdun

    Joined:
    Jun 9, 2008
    Messages:
    138
    Resources:
    4
    Models:
    4
    Resources:
    4
    Greetings one and all,

    If you have a minute, I'd love to hear other opinions on a "strategic" issue.

    See, I am working on a fairly massive project, that might use over a hundred custom objects (that cannot be made with the standard warcraft models), and that's a very conservative estimate. So I am thinking about how I can prevent the maps from getting too big (unit/ability-data and imports).

    Here is one idea: Certain unit concepts are fairly similar, if not identical in their animations. Do you think it makes sense to import just one custom animated model file as a basis for them all, and then just import the parts that distinguish them (helmets, armor, weapons) as separate attachments?

    -less work: having to make fewer animated models
    -having fewer animated models and several dozens of unanimated attachments is surely less costly than to have a lot of animated models?
    -or do you think the advantages are neutralized by the need for attachment abilities and the overall greater number in (mostly unanimated) models
    (example: instead of two model files for two soldier units, you have- one main model, two helmet models, two shield models, two weapon models plus the necessary attachment abilities)?

    I'm already using this approach, but I wonder somewhat if I should push it to the extreme. Any suggestions?
     
  2. Space_Ship

    Space_Ship

    Joined:
    Oct 4, 2011
    Messages:
    223
    Resources:
    0
    Resources:
    0
    I dont know how overused you want a model to be and how much it matters for your particular map.
    For Ex, If you use a soldier model multiple times.
    (1)Add a frostsword import & attach, Change animation colors to (255 - x, 255 - y, 255) to add a blue tint. "Unit name is Frozen commander"
    (2)Add a firey blade import & attach, maybe tweak colors a bit or dont. maybe some redish or theme appropriate armor imports. "Unit name is Scorched vangaurd"

    Okay so these are not real suggestions just an obvious comparison. So really that could be perceived as easily the same unit used differently or if you tried hard enough and the theme fit it would make more sense and look pretty diverse while still using 1 animated + portrait unit model.

    Better understanding how your uses of the models come to life would help me suggest changes of course. And is it a pimp my peon type of deal? that map used peons and all attatchments lol only played it a few times though.
     
  3. maddeem

    maddeem

    Joined:
    Jan 1, 2011
    Messages:
    1,287
    Resources:
    5
    Maps:
    2
    Spells:
    3
    Resources:
    5
    You don't have to use abilities for attaching models to each other. So go for the attachment approach, it saves size drastically.
     
  4. Verdun

    Verdun

    Joined:
    Jun 9, 2008
    Messages:
    138
    Resources:
    4
    Models:
    4
    Resources:
    4

    Sorry, total noob here, aparently, since I have no idea what that "attachment approach" is. Did a quick search but didn't find it. Can you show me where this is explained? Would be awesome.
     
  5. GhostThruster

    GhostThruster

    Joined:
    Jul 24, 2009
    Messages:
    4,845
    Resources:
    34
    Models:
    7
    Icons:
    21
    Packs:
    1
    Skins:
    1
    Maps:
    3
    Spells:
    1
    Resources:
    34
    special effects noob
     
  6. maddeem

    maddeem

    Joined:
    Jan 1, 2011
    Messages:
    1,287
    Resources:
    5
    Maps:
    2
    Spells:
    3
    Resources:
    5
    • Special Effect - Create a special effect attached to the overhead of (Triggering unit) using Abilities\Spells\Other\TalkToMe\TalkToMe.mdl

    Attachments work exactly like abilities do, except they are placed ingame and placed manually.
    For attachment help you might want to check out Attachment And Special Effects Tutorial
    The thing about attachments through triggers is that you must remove it before a unit leaves the map (dies and decays) or it will create a leak. If you are not familiar with leaks then check this out Memory Leaks and Custom Scripts Tutorial
     
  7. map designer

    map designer

    Joined:
    May 2, 2011
    Messages:
    999
    Resources:
    1
    Maps:
    1
    Resources:
    1
    interesting. I will see this again
     
  8. Fingolfin

    Fingolfin

    Joined:
    Jan 11, 2009
    Messages:
    3,220
    Resources:
    154
    Models:
    144
    Icons:
    1
    Packs:
    4
    Skins:
    2
    Maps:
    1
    Spells:
    1
    Tutorials:
    1
    Resources:
    154
    Keep in mind though that adding attachments through triggers can cause wierd bugs if you don't destroy the effect when the unit dies.

    As for saving space, i would say that 100 objects is not an unrealistic number. I believe i have much more in WiF, and you will be fine as long as you properly compress any custom textures with a rate of between 50 and 60 (you can compress textures as you convert them with wc3viewer). You should be able to get a 256x256 texture down below 60kb if you do this.

    Anyhow, judging by how you speak about the models, do you intend to model them yourself or do you have a few you want to choose from?