Alright, alright, I'll post it...

Easily creating a new model from scratch
1. Import an AoM model which will act as your base model.
2. Align and scale your new model so that it fits with the AoM model.
   
3. Delete all the materials on the new model.
   
4. Delete all polygons with isolated vertices of the AoM model.
   
5. Attach the new model to the now 'empty' model.
   
6. Open the material navigator and drag a material from the base model onto selected polygons of your new model. This assigns the texture to the polygons. You can either drag one texture on all polygons or use multiple textures; i.e. drag certain textures on certain polygons. When you use ReplaceTexture it'll then only replace the texture on the polygons you assigned the respective texture to; i.e. you'll have a multi-material model. Make sure though that all polygons have been covered. (Hint: If you forget polygons, AoMED will show a black log window with green letters when you convert the 3dx to brg, otherwise it won't.) Polygons that haven't been covered will remain white.
   
7. Make a (or multiple) UVW maps.
   
8. Animate your new model (feel free to use bones and the Skin Modifier).
   

Merging two AoM models with materials will follow...

Okay, thanks AoMPlayer000. Anyone else? What about the player colour area modification? Possible?

Oh, yes of course. That player color thing requres that you do a rather simple reassignment of texture flags in Gmax. Load the model like you usually would, then select it and add an "edit mesh" modifier (pretty sure that is necessary). Go to select faces, and go all the way down the edit mesh menu. At the bottom there is a box for "Texture ID." Check the properties fo the multitexture that is assigned to the model; there are two or three copies of the the same map. If I remember correctly, one is for pure color that is on the texture, another for player color, and another for transparency. They are numbered. Select the faces on the mesh that you want to be for player color, and change the texture ID to the number in the multi-texture that is associated with player color. Then, save, export etc. like you would any other model.

Same thing for transparency.

My 2 cents: Transparency on the Phoenix model is done with a DDT with no alpha channel; instead, the amount of black in the texture is rendered for variable transparency.

And lets not forget editing PRTs with a hex editor.

[This message has been edited by Lord Zorinthrox (edited 05-17-2005 @ 04:09 PM).]

Thanks for the input, Lord Zorinthrox, but I can't find any "Texture ID" box at the bottom of the faces menu. There's a "Surface Properties" menu with numbered "Smoothing Groups", but I'm not sure if that's what you're referring to or not. No multi-textures or the like. Could it be another modifier?

Merging two AoM models together
1. Import the model you want to attach to another model.
   
2. Import the model you want to have another model attached to (order is important; you can do it vice versa but then have to adjust the number of frames manually).
   
3. Attach the model (before that you should delete the two Mirror Modifiers of the two models), in "Attach Options" select the default options (which are IIRC the first one and the small box at the bottom un-ticked). The object that gets attached will lose its animations.
   
4. Make a new texture that combines the two models' textures, for example:

   

   Edit: I forgot something important:

5. Drag the newly created texture on the attached model's polygons. Again, if you leave out polygons they'll remain white and AoMED will show a black log window with green letters during the 3dx to brg conversion, which it won't when everything is fine.

6. Adjust the UVW maps accordingly, use "Move Horizontal" and "Scale Horizontal" for that purpose. Take care of the different IDs!

   UVW, ID2
   UVW, ID7

7. Now you should be ready to go (animate the model, maybe add the mirror again etc.). I used that method for example for the llama rider's death animation in which the llama and the rider actually joint.

   

I'm aware that these are rather sloppy instructions and that they're not fully self-explanatory... Just try around and ask me if something is not clear. (BTW, I didn't really recreate the situation for this small guide, so there might be faults in it... As I said, ask if it's necessary.)

[This message has been edited by AoMPlayer000 (edited 05-17-2005 @ 06:32 PM).]

The box is labeled "ID," now that I think about it. It should be right above the smoothing groups part (I think; can't check, haven't reinstalled Gmax after a computer rearrangement).

Okay, I see what you mean now, Lord Zorinthrox. And, by George, I think I've got it. Thanks.

But even now, yet another question presents itself. Fiddle-dee-dee! Seriously though, is there a way to make it such that low-graphic models are not loaded for modified units with low-graphic mode engaged? For example, if I made a new unit using a Hoplite's models, is there a way to prevent that unit from reverting to the low-graphic models and textures in low-graphic mode? Editing the BRG, perhaps?

[This message has been edited by King Jared (edited 05-18-2005 @ 00:34 AM).]

I'd say move the brg into the models/low folder and write "lp " in front of the name, for example "lp infantry g hoplite ...". At least the BAR Explorer shows the files that way to me; I'd suggest to try that out.

aomplayer,you've done a hillaric job with the"lama-warrior"
could you send him in as a mod?
I think it would look great between my serious cyclopses

I haven't had a chance to try the low-poly renaming idea yet, but another question comes to mind: has anyone found out how to make new attachpoints? Or simulate attachpoints, perhaps? I recall reading something about bones or something a while ago....

King Jared, LOTS of modders have tried to make new attachpoints, but no one has been succesful.

By the way, if you want to make a model to work as it is in low graphics, you just have to copy/paste it and rename it. Then use that model's name in the anim.

May the Force be with you...

I don't think we're understanding each other. I've made new units using Hoplite models that look different from Hoplites. In low graphics, though, because I used Hoplite models, the units appear as the low-graphic Hoplite units; nothing like my new units. What I want to do is make it so that my new units appear the same in both high and low graphics, but without replacing the original low-graphic models. Meaning if someone were to use my units on low graphics, they would see my units, but at the same time, if they were to use Hoplites on low graphics, they would see Hoplites, not my units. Follow?

Anyway, I figured as much for the attachpoints. Just thought I'd ask.

[This message has been edited by King Jared (edited 05-18-2005 @ 03:55 PM).]

King Jared, have you tried out what I suggested?

Quote:

It isn't possible at all, because AoMED simply doesn't know what in the models' code defines attachpoints and what not, and thus it can't create or overwrite them either.

Just because AOMEd can't do it, that doesn't mean it's impossible . (Admittedly it does suggest that it's non-obvious and possibly quite tricky, but where's the fun in doing easy things? )

Quote:

Well, combined with the fact that we have no other tools it is .

Quote:

Said like a true code-cutter.

As an observation, there seems to be about 16-4 byte segments in .brg formats (just before the texture definitions), that get lost with an AOMED conversion.

Wishful thinking is that they are the extra attachpoint definitions - the only one that seems to survive an import export with no changes is the default pivot point.

Quote:

While your engaged ... I think I can fudge new civilisations but I need to tweak your AOMXMOD modification - I just need to change the name of the language.dll file - so that it doesn't destroy the original for every unsuspecting downloader.

Is that OK?

I say there are some terrific tricks here.
(had to say something)

[This message has been edited by wakain (edited 05-19-2005 @ 01:43 PM).]

Next time use eMail, won't you... This is a nice topic, let's not spam it .

Answer is: Maybe combined with some other, really cool units I made. Problem is, some of them aren't complete yet... Things like skeletons are missing and the textures need tuning. Also I'm not committed at all to AoM modding right now, so don't expect a release that soon, sorry .

alright,it's just so much easier to just say it here,but I will edit my comment.
is there any chance of posting it before christmas?

How do you think editing your (already posted) comment and asking another question will help ?!

I can't guarantee anything because, as I said, I'm currently not working at it. Come on, there're enough cool mods in the DL section, like the Hive Spiders by FlipBizcut .

Now please don't comment on that unless it's related to the topic .

Quote:

Hmm, interesting... Do you have any examples of BRGs with which this happens? When I try it with some models from the AoM demo (just reading/writing internally, rather than going through the painful 3ds max import/export system, though the effect should be the same), it comes out identically to how it went in, and no data is lost; so I can't reproduce the effect here. <insert unhappy but non-angry non-animated smiley>

Quote:

Yep, please feel free to do whatever you want with it - I originally stole the .exe from someone else anyway (to get around the Safedisc encryption)

I was playing around with construction models at the time and the problem could well be with the import/export scripts (I didn't have your single material ones at the time). The section I mentioned stands out on the construction .brg's and has the following format (taken from building construction dockA.brg)

0100 0000 0E26 EA03 0000
0000 0000 0000 0000 0000 0000 0000 0100
0000 0F26 EA03 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0100
0000 1026 EA03 0100 0000 1126 EA03 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0100
0000 1126 EA03 0000 0000 0000 0000 0100
0000 1326 EA03

the format 0100 XX26 EA03 looked like some sort of flag setting, and there just happens to be enough space for the 24 attachpoints defined in the .exe. I wondered if it was used to switch attachpoints on and off?

Anyway, after converting to .3ds, importing, remodelling, exporting and converting back to .brg this section ended up all null and attach statements no longer worked.

I'll try it,sorry didn't thought of that.
I just found you lama warrior funny.

What the hell is this?

Please, don't post if you don't have a clue.

BTW, I forgot to say that you made a nice thread, KJ .