marth sayed
-vertexlighting


For custom color all the time you make a new tga for your reticule.
hud_white.tga isn't a good name, because it's allready used by BF2.
you can call it hud_new.tga, hud_halo.tga

whatever you like. and than you put the tga in the same folder your msh goes. (you can reexport the hud with the new tga name, or edit it with an simple hex edit)

than go in the ingame.req file and add the new tga name to texture and the msh name to model

a step by step process would be nice. you say to put it with the msh, Marth says otherwise. and it's not working.

1. Give your tga file a new name.
2. Make sure your msh also knows the new tga name (hexedit or reexpprt from xsi with new texture.)
3. Make a new file with the same name of your msh file with .msh.option at the end.
4. Add marth code to the file.
5. All files go to data_XXX/common/msh
6. Edit your ingame.req file. Add the new msh and tga.
7. Copy the reticule shape part from the 1playerhud file and remove the color lines also the event color. Change the msh name to yours.

bingo, but now the original reticule is there again.

Edit: here is the part for my reticule in the in-game req if that's any help.

That looks really good. But i hope for you that is your 1playerhud.hud file and not your ingame.req file.

So i think it's easyer to explain on an example.
Here is the ingame.req file from my RC mod:
In the texture section you find all my hud icon's tga names and the clip segment, but this is experimentive
Than in the model section you find my hud icon's msh names and at the beginning these: So the first 5 msh names are from the stock reticule. The next 4 are my custom. Becaue i don't have an reticule yet, they are just copies of the others But that will be the same.
Than you need to make option files for the old hud msh, or add an invisible msh and call it hud_main_reticule_bullseye, hud_main_reticule,.... I made the option thing.

So you need to have in your common/msh folder the old reticule's msh name, the new one, your new msh's tga name and an option file for the old msh with "-scale 0.0" in there. You remember the way to scale an msh file.

OK now the 1playerhud file:
So here are things from my HUD, the weapon informations, healthbar,.... scroll down to the important part the reticule (green).
I added an new group around the old one to disable the reticule from zooming, you won't need that if you don't want the reticule to be removed. than the red part is simply copied from the original hud file. it does the same that the stock hud did but with my msh. Because you are not using the teamcolored reticule you wom't need the color lines.

And now comes the tricky thing. you add the ReadDataFile("dc:ingame.lvl") to your maps lua file and that just above the ReadDataFile("ingame.lvl") line.

So what does BF 2 now:
Battlefront loads your addme, missin,.... comes to your lua file. and than loads your custom ingame.lvl. Than BF allready knows all the things from the ingame.req file. After BF finished that it loads the stock ingame.lvl file and than there is again an hud_main_reticule.msh file and because BF allready knows one (your scaled to 0 one) it simply does nothing and only loads things it does not already know.
That's why you also can delete all things you will not modify from your ingame.req and 1playerhud file.
So infact BF2 has two reticules. your one and the stock one scaled to 0 so you cannot see it.
So when you want just and new reticule msh, but with the teamcolor and also at the same position,... you can also name your reticule just like the stock and only load the new msh with the old name. than you'll have one reticule at the stock position, but the new msh file in there


I hope this was understandable

The '-vertexlighting' option switch doesn't do squat unless you lit the mesh in XSI and exported it with a Color At Vertices Map property.

The game is most likely getting the original hud from the original ingame.lvl. If something doesn't exist in one lvl file and exists in the other it will appear. If you want to change the reticule and want to make a completely new one you will need to make the original meshes invisible, you can't just remove it from your custom hud file because the orginal ingame lvl file still has it. So what you need to do is export nulls named what the original reticule was called and load it in your ingame.req

that won't work:

Munge log:
I'll just make a tiny 0.01 square or do the option file like Anakin said.

JimmyAngler wrote:

Hidden/Spoiler:

ok so here's what I did. I made my reticule mesh and exported it once as hud_main_reticule_halo and another time as hud_main_reticule_halo_outline. I deleted the original hud_main_reticule and hud_main_reticule_outine from my msh folder. I added my texture to the msh folder as well and went into my in-game req to add it all. I deleted the hud_main_reticule and hud_main_reticule_outine and added hud_main_reticule_halo and hud_main_reticule_halo_outline under the model section. I added the tga file of hud_white_halo under the texture section. In the player1hud file found in Common/hud/PC/ I deleted the color (0,0,0) thingy and the Color event stuff for both of the two changed meshes. I also changed the msh name to mine as said in the tut above. finally I checked my LUA to make sure that the ReadDataFile (dc:ingame.lvl [+stuff_I_forgot] was above the original one without the dc:.
I munged the common and copied and pasted the ingame file into my folder's Lvl_pc folder. I have my reticule there colored white correctly, but also the original in front of it. The original changes colors along with the rolling over of friend/foe. I cannot find where It is getting the old reticule from.

So and this is exactly what you told bf to do.

I think you haven't read my post carfully.

Anakin wrote: [...]
So the first 5 msh names are from the stock reticule. The next 4 are my custom. Becaue i don't have an reticule yet, they are just copies of the others But that will be the same.
Than you need to make option files for the old hud msh, or add an invisible msh and call it hud_main_reticule_bullseye, hud_main_reticule,.... I made the option thing.

So you need to have in your common/msh folder the old reticule's msh name, the new one, your new msh's tga name and an option file for the old msh with "-scale 0.0" in there. You remember the way to scale an msh file.

[...]

So what does BF 2 now:
Battlefront loads your addme, missin,.... comes to your lua file. and than loads your custom ingame.lvl. Than BF allready knows all the things from the ingame.req file. After BF finished that it loads the stock ingame.lvl file and than there is again an hud_main_reticule.msh file and because BF allready knows one (your scaled to 0 one) it simply does nothing and only loads things it does not already know.
That's why you also can delete all things you will not modify from your ingame.req and 1playerhud file.
So infact BF2 has two reticules. your one and the stock one scaled to 0 so you cannot see it.
So when you want just and new reticule msh, but with the teamcolor and also at the same position,... you can also name your reticule just like the stock and only load the new msh with the old name. than you'll have one reticule at the stock position, but the new msh file in there


I hope this was understandable

JimmyAngler wrote:that won't work
I'll just make a tiny 0.01 square or do the option file like Anakin said.

Yeah, that will do or an invisible mesh (another thing he suggested). I guess nulls don't work then.

Anakin wrote:I think you haven't read my post carfully...

BF2 loads your custom ingame.lvl. Than BF allready knows all the things from the ingame.req file. After BF finished that it loads the stock ingame.lvl file and than there is again an hud_main_reticule.msh file and because BF allready knows one (your scaled to 0 one) it simply does nothing and only loads things it does not already know.
That's why you also can delete all things you will not modify from your ingame.req and 1playerhud file.

Nedarb7 wrote:If something doesn't exist in one lvl file and exists in the other it will appear.

What Anakin and I were trying to tell you was this:
If you have two lvl files loaded in your LUA that contain the same contents this is what will happen, the second can do nothing but add any content that does not exist in the second (besides textures). That is why in all the tutorials on the FAQ that have to do with overriding anything besides textures in the LUA the custom one is loaded first, so we can override the original. The first is dominant. That's the reason why it didn't work to simply remove a few chunks from the hud to remove the stock reticule, because the stock ingame was adding it again since it didn't exist in the custom.

Anyways, hope you find this helpful for future modifications.

OHMYGOOSHNESS!!!

back again *sigh*

I have created everything right I thought. now It is loading the original without my custom.
Here is everything I have.

All of these files are in the mshs folder.
my in-game req: my 1playerhud:

Mh that's strange.

So you can remove 2playerhud, 3playerhud, 4playerhud and hudtransforms if you changed nothing.

Than there are two 1playerhud.hud files. On in the hud folder and one in the hud/pc folder. What did you change??

There are some differences between both and i really haven't found out what bf toke to munge. In my view everytime an other. So i copyed the one from the pc folder in the hud folder, override, and deleted the whole pc folder.
Try this and do an complete clean.

Also you should scale to 0.0 not 0.1 after the 1playerhud also scales it would be still shown. Just 0.0 will make it invisible.

not quite sure I understand this:

Also you should scale to 0.0 not 0.1 after the 1playerhud also scales it would be still shown. Just 0.0 will make it invisible.

I changed the 1playerhud in the pc folder and that's the one I posted.
I think I changed a little in the other so It looks like this:

Your models wont do you any good if you get rid of this (highlighted red):

JimmyAngler wrote:ucft
{


REQN
{
"texture"
"hud_white_halo"

}



REQN
{

"model"
"hud_main_reticule"
"hud_main_reticule_halo"
"hud_main_reticule_outline"
"hud_main_reticule_halo_outline"

}

REQN
{
"config"
"hudtransforms"
"1playerhud"
"2playerhud"
"3playerhud"
"4playerhud"
}

}

*facepalm*
Thanks to all (Anakin + Nedarb7) I have now the knowledge of the reticule!

nice error. Haven't seen it