-= Gametoast.com =-

Well I've been trying to mod the BX-Commando Droid into the game and have looked through the guides, other ODF files, conversion pack ODF files, and have still yet to get it to work. I have already added it to the LUA file for the CIS and replaced the sniper with it. Not sure what is the issue here, but the map was working fine with other mods (UT-AT/Clone Assassin) and crashed only after I tried to add the BX-Commando Droid in. I believe the problem is in the ODF myself and here they are... (already extracted the folders from the bx-commandodroid.rar to the needed folders)

cis_inf_droid commando: and the parent class: This is my first time at trying to create my own .odf files for a unit so any and all help is appreciated!

Thanks for the help. Messed around with the weapons and it worked fine after that.

What does your Bfront2.log file say? What does his melee weapon .odf look like? What animations is he/should he be using?

Maveritchell wrote:What does your Bfront2.log file say? What does his melee weapon .odf look like? What animations is he/should he be using?

I have been using a no-CD patch for my BF2 as my CD for it broke several months ago, so I haven't been able to run BF mod tools in the game data directory as I get the insert CD 1 every time I try so I don't think I can get a .log

The melee ODF file:
I wasn't sure what to add for animations, so currently nothing in the cis_inf_droidcommando.odf

You're going to have a tough time debugging your mods without a log; try the BF2_Modtools.exe found here:
http://files.filefront.com/BF2+modtools ... einfo.html

It is the DVD version of the tool; I don't know if it skips the disc check or if it simply has another one. If it works, then please post your log.

If it does not work, then your best course of action for eliminating a problem you can't pinpoint is to narrow the problem down. You have already (presumably) determined that the problem lies with the droid unit (you can confirm this by quickly removing the unit from being loaded and check). You can further eliminate by seeing if the unit works without - for example - the melee weapon.

Maveritchell wrote:You're going to have a tough time debugging your mods without a log; try the BF2_Modtools.exe found here:
http://files.filefront.com/BF2+modtools ... einfo.html

It is the DVD version of the tool; I don't know if it skips the disc check or if it simply has another one. If it works, then please post your log.

If it does not work, then your best course of action for eliminating a problem you can't pinpoint is to narrow the problem down. You have already (presumably) determined that the problem lies with the droid unit (you can confirm this by quickly removing the unit from being loaded and check). You can further eliminate by seeing if the unit works without - for example - the melee weapon.

Thanks lol that really helped. I seemed to have isolated the error which was:

Message Severity: 3
C:\Battlefront2\main\Battlefront2\Source\EntityGeometry.cpp(619)
Entity "cis_inf_droidcommando" missing geometry "cis_inf_droid_commando"

The .msh file (which is the "missing geometry" right?) is cis_inf_droidcommando.msh in the .msh file

Low wrote:Message Severity: 3
C:\Battlefront2\main\Battlefront2\Source\EntityGeometry.cpp(619)
Entity "cis_inf_droidcommando" missing geometry "cis_inf_droid_commando"

The .msh file (which is the "missing geometry" right?) is cis_inf_droidcommando.msh in the .msh file

You have two different geometries listed in your .odf file: "cis_inf_droidcommando" (in properties) and "cis_inf_droidcommand" (in gameobjectclass). What is the mesh file itself actually called?

Maveritchell wrote:

Low wrote:Message Severity: 3
C:\Battlefront2\main\Battlefront2\Source\EntityGeometry.cpp(619)
Entity "cis_inf_droidcommando" missing geometry "cis_inf_droid_commando"

The .msh file (which is the "missing geometry" right?) is cis_inf_droidcommando.msh in the .msh file

You have two different geometries listed in your .odf file: "cis_inf_droidcommando" (in properties) and "cis_inf_droidcommand" (in gameobjectclass). What is the mesh file itself actually called?

Just noticed it was like that in the posted ODF now. I changed that a little while back to:
Still crashes while loading however.

And what is the mesh actually called?

Maveritchell wrote:And what is the mesh actually called?

The mesh itself is cis_inf_droidcommando.msh

Go ahead and browse to data_MODID\_BUILD\Sides\SIDENAME\MUNGED_PC (where SIDENAME is the side the droid is munged into). Find cis_inf_droidcommando.class.req and delete it.

Modify your .odf so that all the Geometries point to the correct model. Add: to your .odf in the "Properties" section (right under GeometryName) is fine.

Add the correct animation files to your SIDENAME\munged folder (these are included with your download).

Make sure to read over the readme that came with the asset download; it makes note of the last two instructions posted above.

...and then munge.

Maveritchell wrote:Go ahead and browse to data_MODID\_BUILD\Sides\SIDENAME\MUNGED_PC (where SIDENAME is the side the droid is munged into). Find cis_inf_droidcommando.class.req and delete it.

Modify your .odf so that all the Geometries point to the correct model. Add:

Code: Select all

AnimationName = "BX"

to your .odf in the "Properties" section (right under GeometryName) is fine.

Add the correct animation files to your SIDENAME\munged folder (these are included with your download).

Make sure to read over the readme that came with the asset download; it makes note of the last two instructions posted above.

...and then munge.

Well I've munged and managed to get to the selection screen in game where you can choose to play as either Republic, or CIS, but once I move my curser it crashes back to the desktop. I'm not sure if this has to do with the new unit ODF, or another issue. Regardless the LUA, current ODF, and debug log.
ODF: and the error log:

You have three "severity 3" errors in your log: two relate to a tank ("rep_hover_hovertank") you're trying to load from the REP.lvl, and one that relates to your melee weapon for your unit.