hi i have been trying to change my CIS side to a new ghost jedi unit for my newly announced map but every time i munge it doesnt appear on my map i posted my LUA can anyone see anything wrong? Also in my munge output it said "Error(InvalidPerimeter)GHO
(GHO is the name of my side that i made that holds my unit)

Strange... Try writing adding this instead of AddUnitClass

cis = {
team = CIS,
units = 20,
reinforcements = 150,
soldier = { "cis_inf_rifleman",9, 25},
assault = { "cis_inf_rocketeer",1, 4},
engineer = { "cis_inf_engineer",1, 4},
sniper = { "cis_inf_sniper",1, 4},
officer = {"cis_inf_officer",1, 4},
special = { "cis_inf_droideka",1, 4},
marine = { "gho_jed_knight_01",1,4}, <-----------------this

not sure if this will work but its worth a try.

Still no luck do u know what that munge thing meant though?

Does the side exist in:
C:\Program Files\LucasArts\Star Wars Battlefront II\GameData\addon\***\data\_LVL_PC\SIDE
And if it doesn't you need to make a munge for it in:
C:\BF2_ModTools\data_***\_BUILD\Sides
If its there is it the same case of your sides' folder?

It's in my world's side folder, not the Addon\lvl PC one and and what do u mean by munge it to a different location then what I have been munging to?

Go to:
C:\BF2_ModTools\data_***\_BUILD\Sides (*** is your maps 3 letter ID)
and copy the ALL folder in it and rename it gho then munge.

Ok I did that now what do I do with the gho folder containing all of the info?

Zeah make sure you have a folder in _BUILD/Sides, not sure why the tur side was brought into this , but could you post your odf for your ghost thing? Im' thinking that when the bungelog mentioned, "invalid parameter" it might have been an odf parameter thing. Just a guess.

Wait, so I create a folder in _Build/Sides named GHO and then make the side there? And the ghost Jedi skin didn't come with an odf, only a tga and msh. I was using the Jedi_knight_01 odf? Is that bad?

Zapattack1234 wrote:Wait, so I create a folder in _Build/Sides named GHO and then make the side there? And the ghost Jedi skin didn't come with an odf, only a tga and msh. I was using the Jedi_knight_01 odf? Is that bad?

So as long as you edit it properly, it should work fine. Although I don't know much about .odfs

Edit it properly? How do u mean?

Zapattack1234 wrote:Wait, so I create a folder in _Build/Sides named GHO and then make the side there? And the ghost Jedi skin didn't come with an odf, only a tga and msh. I was using the Jedi_knight_01 odf? Is that bad?

Nooooooooooo! Don't move your side to _BUILD/Sides. Only go there, make a folder called GHO, and go to any other folder there and copy the two .bat files munge.bat and clean.bat to GHO. Keep all of the odf files and stuff in data_***/Sides/GHO. When you munge select GHO from the sides selector thingy. For the Jed_knight1 odf, make sure you change the GeometryName and Geometry parameters to reference the new msh.

Ok thanks do I put the .bat files in both GHO folders?

I'm pretty sure you have to edit/change what textures or models the character uses in the odf file for a custom character. I'm not really the person to be asking this, so for more detailed info on odfs you should read dann boeing's tutorial

Zapattack1234 wrote:Ok thanks do I put the .bat files in both GHO folders?

Nope, just in the one in _BUILD/Sides

About the models/skins/textures, DarthSolous was pretty much right. You have to change the part under "[Classlabel]" that says GeometryName = "nameofjedimshblablabla.msh" to GeometryName = "yourghostjedimshnameorwhatever.msh" and then under "[Properties]" it will say GeometryName = "nameofjedimshblablabla" or whatever (note that here it doesn't say .msh at the end) change that to GeometryName = "yourghostjedimshnameorwhatever" again make sure here it doesn't have .msh at the end. Now try minting it and trying again.

That is the weird part though, the odf for the Jedi already matches my ghost Jedi's tga msh and option files and I didn't even edit it, and I still get no Jedi when I go to play the level

Zapattack1234 wrote:That is the weird part though, the odf for the Jedi already matches my ghost Jedi's tga msh and option files and I didn't even edit it, and I still get no Jedi when I go to play the level

Weird



Why don't you copy and paste both the standard jedi odf & the odf you're using for the jedi ghost so we can see if there are any differences

Sure I will tomorrow got to get some sleep

Edit:

Here is the standard jedi odf:
By the way the ghost jedi didnt come with an odf Strangely, all of the jedi ghosts files match the ones represented here

Just thought I'd clarify a few things:

-When changing the msh of an object, the one under ClassLabel is the msh that will appear in ZeroEditor. (This is the one that ends in .msh) The one under Properties is the msh that will appear in-game. For example, in this ODF file, sky_dining_ze is the msh for ZeroEditor and sky_dining is the msh for in-game. This applies to units and weapons as well.

-Some people seem to be confused about the process of creating a custom side. There are a lot of ways to accomplish this. However, if the purpose is to add a new unit to a stock side, this is the method I like to use:

1) Copy the folder of the side you want to edit from BF2_Modtools/assets. Paste into data_***/Sides.
2) Enter this new folder, for example data_***/Sides/cis . Place your msh and tga files into the msh folder, and place your odf files into the odf folder.
3) Next, go to your LUA. Under these lines, Add the following:
This will load our unit from our munged, custom side. Notice that we have not edited the line loading from the normal cis side.

4) Finally, add the unit to the team:
Munge, and under SIDES choose CIS. Also make sure to munge Common, for our scripts.



-----------------------
Now a quick addendum:
This method of side editing does have its perks - it allows easy edit to stock units and puts all teh stock assets right there into your folder. Also, there is no need to create and folders in the BUILD directory. It does, however, have a drawback- without .req edits, the side file will be very large. Make sure to eliminate units from your .req that you won't need in the final munged side.



Now, if you WERE going to use the earlier method:

Create your side (the tga, msh, odf) in data_***/sides/GHO. Then, go to the BUILD/Sides and create a new folder named GHO. In this new folder, paste in the .bat files from a different sides's BUILD folder. Don't forget to create your new .req in the new GHO side (data_***/Sides/GHO), which I think is the problem you had at the beginning of this topic.


So the folders would look like:

that is the thing though, the ghost jedi didnt come with an odf file, only a msh and tga. Should i use the standard jedi one that i posted?

Edit-

I also recieve a message during the munge that says:

Mungeing TOJ.req:

System could not find specified path

(TOJ is my world)

Could this be the problem as to why the sides are not updating?