while there are finally quite some modders who make custom models for battlefront, thanks to repsharpshooters meshtool, most do not go the extrasteps that can make a good model look even better and a great model look awesome ingame because they do not know about them.
after being asked by some people about some things for some time now i decided to start a thread that explains the most important things that can be done with the pandemictool or hexediting or in xsi which will make your models look more polished. Realize the full potential of your models now!!!

ill update this thread withing the coming days or weeks, so check back.

XSI

Lowres model
a lowres model is what battlefront displays when you see an object from a distance. if the object has no lowres model, it will become invisible. thus you should create lowrez models for your objects especially if they are used on large maps and/or maps with many objects at once on the screen.

Creation
hence its name, the lowresmodel is supposed to have less polygons than the normal model. therefore you should create a copy of the normal model and reduce its polygons. you must not use the "polygon reduction" tool for this, it doesnt work on gamemodels because it cant know which edge is important and which is not, it will just evenly remove them. deleting unneeded edges will take some minutes but it is worth that, especially because you can use the lowresmodel also as base for the shadowvolume and collision.
the two things that are important on a lowresmodel are:
the shape, you see lowresmodels only from far away so you will not be able to see any details and if some surfaces are round.
the UV, every UV has cuts somewhere, make sure not to delete the edges where the uv pieces are split.
thats basically what you need to pay attention to, all edged that dont contribute to the shape or the UV should be deleted.
there is no hard number for the polycount of the lowresmodel, depending on the shapes complexity and details on the normal model it could have from a quarter to three quartes less polygons.

Integration
All you have to do is naming the lowrezmodel "whatever_lowrez", if it has multiple parts, you don't need to number them, the "_lowrez" extension is enough.
Units are a special case, they use a seperate msh for the lowresmodel and have to be enveloped to the lowres skeleton. You can find one converted by AceMastermind in Andes XSIZETools or download it from here.

Example
Here you see the normal and lowresmodel of a railing:

this lowres model is too detailed for normal usage, but here its needed because models switch to lowres even when the camera is really close.
While making this i realized that i wasted too many polys on the railings....
anyway, this is also a very good example on how very little effect rounding edges have ingame.

Shadowvolume
In battlefront all objects recieve shadows but they don't cast shadows by default. in order to make an object cast a shadow you have to include a shadowvolume in the msh. There is also a msh.option line "highresshadow" that makes btatlefront use the normal model as shadowvolume but because shadows eat a large amaount of performance in battlefront you should only use it on very primitive models.

Creation:
The shadowvolume should be created just like the lowres model or be based on it. A shadow volume is even less detailed than a lowres model because it doesn't need support edges for the UV and the shape can be more rough because it is ony projected on the ground which distorts it and the player pays less attention t it that something in front of him.

Integration:
To make battlefront use amodel as shadowvolume, name it "sv_whatever". if you have multiple shadowvolumes, just give them all the "sv_" prefix. that may not work all the time, if it doesn't then merge the parts together.

Example:
Here is the shadowvolume of the acp repeater:

As you can see the shadowvolume also casts a shadow on the normal model, you can see the notchs shadow on the gunbody.

Pandemic Tool

Specular map
A specularmap allows to have dynamic specular highlights on the model where it is hit by light.
The highlights are generated depending on the orientation of the objetc to the camera and the lightsource.
The specularmap itself is a greyscale texture that contains information about how bright the surface gets when it is hit by light. The brighter the specularmap is, the brighter the surface will get ingame.

You can have no specularmap at all, then the model will have bright round specularspots and look like plastic.
You can have a specularmap with solid colors so that you differ the specular insensity of the different materials on a texture.
You can also have a detailed specularmap which contains as much details as the diffuse texture. You can have scratches that become brighter than the surounding surface or dirt that does not react to light all that much.

Creation:
You can create a specularmap from the diffuse texture. make it a greyscaleimage and increase the overal contrast through "values" or "curves" in e.g. gimp.
The brightness from the specularmap will be added to the diffusemap when the light hits the model so pay attention to brighter/darker areas and make the specularmap darker/brighter there (if that suits the material of course)
Ideally the diffusetexture should not contain any specular at all because it is added by the specularmap dynamically. therefore, if you create a new diffusetexture, don't include much specular highlights e.g. bright streaks on cylinders.

Integration:
you can set the specularcolor and decay(size of the spots) in the objects material and it will be carried over to the game.
to specularmap a surface, apply the rendertype "4", you dont have to set any values or additional textures.
the specularmap must be stored in the difuse textures alphachannel. you do that by adding a mask to the diffusetexture and then copy the specularmap in the mask.

you need to have your lighting setting atleast on medium to see the specular ingame.
in order to make the specularmap show up, your map requires a directional light that has "cast specular" enabled.

Example:
this is an example of the specularmap for the stock chainguntexture and its effect ingame


Bump map
a bumpmap allows to fake plastic detail on a surface. it is a greyscaleimage that contains a heigthvalue for each pixel, if its brighter than the sorrounding pixels, its moved "up" and if its darker its moved "down". ingame the shadows on the surface are created dynamically depeding on the objects orientation to the light.
bumpmaps work especially well on rough surfaces like rock or can make panels or bricks look plastic.
because their effect ingame doesnt change depending on the cameraorientation, they arent really noticeable on smaller objects unless they are moving and/or have specular/gloss applied.
the first downside of bumpmaps is that the heighinformation is only created by comparing directly neighbouring pixels. that means you cant fake round or sloped details with gradients! due to this its also not really possible to have various heights, for example you wont see a heighdifference ingame between two moved up panels that have a different brightness on the bumpmap.
the second downside is that the effect gets the weaker the sharper the angle is from which you look at the surface and it only looks really plastic if you are nearly looking straightly at it.

Creation:
you cannot, never ever create a bumpmap just from the greyscale of the diffusetexture! please dont use pandemics bumpmaps as reference for that. they did totally weird work, especially on the weaponbumpmaps.
anyway, its best to start with a solid grey texture "888888" so that you can move things up aswell as down.
now look at the diffusetexture to see which surfaces should be moved up, color them brighter/white. all surfaces/grooves that should be moved down need to be colored darker/black.
after you are done with these details you can add some "low frequency" detail like scratches or damage or structures on rocks etc. you can make these by using the greyscaled diffusetexture but remember that the result of that will always be totally incorrect(that doesnt mean that it will too look bad ingame) because the diffusetexture already contains shading most of the time.
if you have a small groove/ridge on the diffusetexture it often has a bright edge on one side and a dark edge on the other. if this is used for the bumpmap it will result in a groove one one edge and a ridge on the other edge rather than a groove/ridge in the middle.
if you create a new diffusetexture, dont include shading for the details e.g. bright edges on the borders of ridges because they will be added dynamically ingame.

Integration:
option 1:
to bumpmap surface, apply the rendertype "27", and enter the name of the bumpmap in the "texture1" slot.

option 2:
this does not requre a flag, create a .msh.option file for your model with
-bump
and after that list the names of the textures that should be bumpmapped, seperated through a " "(space).
this is usefull if you just quickly want to bumpmap something but be carefull, if you have any flag (rendertype/transparency) applied to a texture listed than either the bumpmap or the flag wont work and there may be lightingissues ingame.

create a .tga.option for the bumpmap with this in it:
-bumpmap -format bump
the first parameters makes battlefront convert the bumpmap to something usable as heighthmap and the second specifys that the bumpinfo is in the textures rgb-channels.
you can also modify the strength of the bumpmap with this command:
-bumpscale value
6.0 is about the default value.

you need to have your lighting setting on high to see the bumpmap.
in order to make the bumpmap show up, your map requires a directional light, i suppose.

Example:
this is the example of a bumpmap for the cloneassassinblade and its effect ingame, in combination with gloss. without that it would be not half as visible.


Normal map
a normalmap is basically a better bumpmap. while a bumpmap only has one channel (pixelheigth), the normalmap has 3: red (x-vector), blue (z-vector) and green (y-vector) and therefore contains much more information about the surface. it takes much more time to make than a bumpmap though because you cant just pain on the details, you have to bake them from a model that really has them modeled in.

Creation:
a normalmap is usually created with a 3d application, you need the model that is going to be in the game and contains all the basic shape and the silhuette and a highres model that has all the details modeled in you want to have in the normalmap. the highresmodel can either be created by a skulpting application like skulptris or zbrush or modeled with subdivision/hard surface modeling.
after you have finished the highresmodel you can apply a bumpmap if you want to have scratches or really small details or structures in the bumpmap.


Integration:
to normalmap a surface, apply the rendertype "27".
in the "Texture 1" slot insert the name of your normalmap with .tga extenstion.
create a .tga.option file for your normalmap and put this in it:
-format bump
this it actually not necessary for it to work, it results in some kind of compression of the texture which is probably better for performance.

you need to have your lighting setting on high to see the normalmap.
in order to make the normalmap show up, your map requires a directional light.

Example:
this is a part of the clonecommando visor for which i made a normalmap:

remember, however that battlefronts lighting system is a little old so the normalmaps will ingame not be as clear and strong as in xsi.

Bump/Normal and Specularmap
not much explanation needed, its a combination of both bump/normal and specularmap

Creation:
the specularmap needs to be put in the bumpmaps alphachannel. to do this, open the bumpmap in your favourite image editing application, apply a mask to the bumpmap and copy the specularmap in the mask.

Integration:
to normal/bump and specularmap a surface, apply the rendertype "28".
in the "texture 1" slot insert the name of the bump/normalmap with .tga extension.

you need to have your lighting setting on high to see the bumpmap.
if you have your lighting setting on medium this flag will be interpreted as specularmap flag. this means that you have to also put the specularmap in the diffusetextures alphachannel if you dont want people who play on lower settings to see your model looking all plasticy.
in order to make the specularmap show up, your map requires a directional light that has "cast specular" enabled.

Example:
heres is the clonecommando without and with specular and normalmap, i didnt have the white commando in the map so i had to take this one which makes especially the normalmap not that recognizeable.


Environment map
an environment map allows the model to reflect the environment dynamically, depending on the orientation of the model and camera. envmaps look especially cool on round surfaces.
you can have no environmentmap, then the model will reflect the real environment
you can have an environmentmap (cubemap), then battlefront will generate a textured cube from it, that surrounds the model and project the cubes texture onto it.


Creation:
the cubemap is basically an unfolded cube and each side represents one side of the "room" in which the object is located.
because of its special purpose a cubemap cant have a resolution that is power of two. the resolution is "apoweroftwo*threequartersofthepoweroftwo", for example 256px*192px
here are two examples of cubemaps:

when you fold the sides to a cube, they fit together and form a seamless "environment".(atleast the naboo cubemap )
the alphachannel of the environmentmap determinates its opacity.
make sure that sides arent switched, its supposed to reflect whats behind you when you look at it.

Integration:
to environmentmap a surface, apply the rendertype "6".
in the "texture 3" slot insert the name of the environmentmap with .tga extension.
create a .tga.option for the environmentmap with this in it:
-cubemap
it tells battlefront to use the texture as a cubemap

you need to have your lighting setting atleast on medium to see the environmentmap ingame.

if you take a look at the examples ingame, you will see that the envmaps have a different effect. this is the result of different speculardecay. if you dont modify the speculardecay in xsi the object will be very bright and glowy and you will hardly recognize the envmap. the fountainball on naboo has no glow at all. these are the two extremes. the laatballs have a speculardecay inbetween those two, to be exact they use the tantive4troopers inserted through hexediting.

Example:
here are the above envmaps in action:


Hexediting
all the rendertypes explained above can be done through hexediting in combination with repsharpshooters great meshtool
AceMastermind made a list of the hexvalues for every rendertype in this topic, if you scroll down, you can also see a list of all hexvalues for the 5thplace flags.

in order to create the flags that need an input for texture1, apply a bumpmap with the meshtool.
then open the msh with a hexeditor like HxD.
search for "ATRB", this marks the beginning of the section that contains the flags of a material.
after this you will see "TX0D" and a texturename, this is the diffusetexture. your msh will most likely have several materials so make sure to select the one with the right texture.
after the diffusetexturename this material should also have "TX1D" and the name of another texture (with "_bump" at the end), this is the "texture1" slot from the pandemictool. you can name the texture however you want, just make sure that you dont override any data if you increase the length.
now set your cursor behind the "B" of "ATRB", the value "04" right after "42" should be selected in the hexvalues.
this is the first place after ATRB.
things like transparency,glow,gloss are stored in the fifth place
the rendertypes are stored in the sixth place


your material should have "80" in the fifth place which results in gloss, put in "00" if you dont need it or some other value.
your material should have "1b" in the sixth place, which is rendertype 27 (bumpmap), now replace this value with the hexvalue of the rendertype you want to apply.
save the file and you are done!

if you want to apply an envmap, just use the meshtool. you can modify the name of the envmaptexture, it can be found after "TX3D" (texture 3 slot of the pandemictool) in the material.

Glow
glow allows you to have lightbloom on surfaces, it will also make them brighter. the color of the diffusetexture determinates the glowcolor and the alphachannel determinates the glowstrength.
the strength of the glow depends on the size of the glowing surfaces ingame. really small surfaces will hardly have lightbloom but this glow gives already much better results than the glow through rendertype.

Creation:
white is extreme glow and black is no glow. if you still want to be able to see the surfaces color ingame, something like white with atleast 60% black is a good place to start with. you might have to adjust the strength several times though.
when you are done with the glowmap, add a mask to the diffusetexture and copy the glowmap into it.

Integration:
in order to apply glow to a surface you have to hexedit the 5th place flag of the material to either "02" - glow or "03" - increased glow (glow and emissive colors to be exact).
when you make the model, surround the parts that will glow with edges to seperate it from the rest of the surface and give the glowing polygons a seperate material so that you can enable glow only on these. you have to do this because a polygon with glow applied, even if the glowmap is black, will be brighter than other polygons and not recieve any lighting.

you need to have lightbloom enabled to see the glow ingame (suprise, suprise!), with it disabled the glowing polygons will still be brighter than usual though.

Example:
glow on consolescreens. the glow changes dynamically if the surface is obstructed somehow, so if you have something dark scrolling over the screen, the glow will be weaker on these spots.


Gloss
gloss is pretty similiar to specular. its also calculated depending on the surfaces orientation to the lightsource and camera. the difference is that while specular generates white spots, gloss makes the model really glow when it is directly hit by light. therefore it should be only used on small models because you will get huge glowing areas otherwise. the disavantage of gloss is that you cannot edit the intensity.

Creation:
gloss doesnt care about the textures alphachannel so nothing to do there.

Integration:
in order to apply gloss to a surface you have to hexedit the 5th place flag of the material to either "80 or "A0", i dont know if there is any difference betwene these two.

you need to have your lighting setting atleast on medium to see the gloss ingame.
you need to have lightbloom enabled to see the glow ingame where the surface is directly hit by light,
in order to make the specularmap show up, your map requires a directional light that has "cast specular" enabled.


Example:
here are two examples of gloss. it looks pretty good on the blade in this moment but if it has a certain orientation the whole surface glows and you will hardly see the texture. on surfaces as big as on the wall it just doesnt look right.


Hardedged Transparency
the special feature of hardedged transparency is that it outputs only two transparency values ingame. either a pixel is visible or its invisible. this is especially usefull for objects like fences or railings or a thin surface with holes.
the advantage of hardedged transparency is that you dont get the usual display "bug" when you see multiple transparent surfaces behind eachother which displays the rear surface as if it is in fron of the other surface.

Creation:
no extrawork on the texture needed, its handy the have the alphachannel with strong values though.
that prevents you from being suprised when pixels show up ingame that are not supposed to be displayed or vice versa and thus having to edit the alphachannel again.

Integration:
to add additive transparency, you have to add "1" to the first number of the fifth place. since you will most likely have transparency enabled the fifth place will be "14" or "18", the second number being onesided and "8" being doublesided transparency.

Example:
hardedged transparency on the laats missiletubes, allowing to have holes without and additonal polygons


Additive Transparency
the special feature of additive transparency is that it has a soft glow that increases when you see multiple polygons behind eachother. the glow also gets more intensive the more opaque the texture is.
additive transparency can be used really well for holograms of (force) ghosts.

Creation:
no extrawork on the texture needed, you could modify the brightness though if the glow is too strong or weak.

Integration:
to add additive transparency, you have to add "4" or "6"(with emissive colors) to the first numberof the fifth place. since you will most likely have transparency enabled the fifth place will be "44", "48" or "64", "68", "4" in the second number being onesided and "8" being doublesided transparency.

Example:
additive transparency on a hologram, you can see pretty well how it gets brighter in front of the glowing screen and where the pieces intersect.


more updates are coming soon

Bravo! Good on you for making this topic, D.D! Hopefully we'll all start using maps a bit more. I've been using normal maps occasionally, but never tried a specular.....Are they useful in any model, or are they mainly used for units/weapons/vehicles? What i mean is, would you apply this to a brick/stone wall?

I had another question. Does bf2 support height maps? Or are they just a more basic form of normal/bump maps?

EDIT: Are these maps a lot more resource-intensive then only applying stock textures?

first: specularmaps look good on pretty much anything (except on materials with very weak specular), especially in things that move (e.g.units!). depending on the lightorientation its not always visisible on smaller things like weapons.
on "rough" surfaces like rocks or a brickwall with a lot of possible additional heightinformation going one a bumpmap is going to have a better effect, if you have to choose. but you dont have to, you can have both specular- and bumpmap (its rendertype 28 and the specularmap is in the bumpmaps alphachannel) but im going to write that in detail tomorow or so.
heighthmaps(in the currect- previsouly next-gen games) are used additionally to normalmaps to add details to the silhuette which normalmaps cant do. they look just like ordinary bumpmaps. battlefront doesnt support them.
in older games "heighthmap" can refer to bump- and normalmaps as far as i know.

This is great, thanks D.U.C.K. I can't wait for more updates.

It looks best on units, vehicles, and weapons. I find it looks poorly on building models, specifically stone or wood textures. Specular looks best on metal and plastic textures.




Well that depends on your certain point of view. In order to see bump or normal maps, you have to use High light settings, which are more resource intensive.

Nice work.
If youre using the Pandemic Exporter you can change your materials specular color(definitely works with straight specular, dunno about spec-maps). Depending on the material of your model this can make it look even better.

i wrote some more.... and thanks for the info ande! i added it now.

not really, they mostly cost memory (both in the mapsize and ram) because they have to be loaded additionally to the normal textures. specmaps dont need a seperate texture so they dont take up much space and have great effect in relation to their "size".
most people have a pretty good internet though and dont care about a few mb more, especially if it adds to the visuals of the map.
i wouldnt refrain from adding more flags or shadows for that matter because everybody cna just turn the settings down if its to much for his computer.

wow, thx my friend for such a good tutorial/guide. i think it will help many people here

Really nice explanations. I am really interested with maps these days (looked lot of topics on Polycount ). Thanks.



It is your opininon, but normal maps are really usefull for baking details on the lowrez mesh from a sculpted/high poly mesh, especially on stone and wood.

I was talking about Specular, not Normal maps.

Ah ok, it is alright then .

i added an explanation for bumpmaps and hexediting rendertypes now.
and glow
and additive transparency
and hardedged transparency

Thanks a lot for doing this Darth. It's really helpful to me, and i'm sure a lot of others too. I was wondering about your hex-editing section - is their any benefits to hex-editing instead of using the meshtool? They both achieve the same thing don't they??

You can do more stuff with hexediting, but you have to do it manually.

And dont ever edit the first 4 places after ATRB(or any chunk)unless you know what youre doing, this could break the whole msh file.

like andeweget said, you can only do three things with the meshtool (glow, bumpmap, envmap). the glow can be done better by hexediting (meshtool uses the rendertype glow which requires and extra texture and isn't that strong) and the 5th place flags like the different transparencies can't be done with either meshtool or pandemic tool.

i added gloss to the first post

Gonna have to read through this carefully since I wanna do a v2 of the N-1 but have the chrome parts actually look chrome if possible.

Maybe an environment map ?

I just noticed this. I actually used the values from from the HK-49 model, but the values from the Tantive 4 Trooper would also work.

thanks, i changed that.

ive added lowres and shadowvolume to the xsi section now. ill probably also add hard edges and vertex colors later.

Additional info for shadowvolume and lowres.

If you have a really big model (such as the Azzameen space sation I am working on), it is good to break the lowres to multiple parts. Having one really big one can cause the model to "flash" in and out of lowres depending upon where you are looking. Also you can use _lowres as the extension works the same as _lowrez.

For shadowvolumes, especially on buildings, you may actually have to add extra geometry to block the light coming though some walls. Example if you have a building with a window on one wall and it is suppose to be solid wall opposite if the shadwvolume for the wall isn't solid you will see light from the window on the ground outside the solid wall. Basically all shadowvolume geometry should be solid, no deleted faces.