-= Gametoast.com =-

Hello all,

I've checked every tutorial, topic, etc. I could find, and I haven't had any luck. I am trying to install fambaas for my map I am making, and every attempt either doesn't have any effect (normal map without fambaas*) , or the error where the CPs aren't there and I can't spawn.
I haven't really found a whole lot on ZE or placing objects in general, so that may be part of the problem.

Any help would be greatly appreciated. Thanks!

Please post your .lua and error log.

The Fambaa assets work fine, make sure you have all of the files required for this object: nab_bldg_fambaa_generator.odf version seen on the left

• uses nab_weap_bldg_fambaa_generator.odf

nab_bldg_fambaa_shield.odf version seen in the middle

• uses nab_weap_bldg_fambaa_shield.odf

nab_prop_fambaa.odf version seen on the right


Files in data_ABC\Worlds\ABC\msh folder:

• fambaa_shield.msh
  fambaa_shield.tga
  nab1_fambaa.tga
  nab1_fambaa.tga.option
  nab1_fambaa_lowrez.tga
  nab1_walk_fambaa.msh
  nab1_walk_fambaa.msh.option

Files in data_ABC\Worlds\ABC\effects folder:

• fambaa_shield2.tga
  fambaa_shield2.tga.option
  fambaa_shield.fx

Files in data_ABC\Worlds\ABC\munged folder:

• nab_walk_fambaa.anims
  nab_walk_fambaa.zaabin
  nab_walk_fambaa.zafbin

The files with 'shield' in the filename naturally go with the shielded version. The prop version doesn't use animations.

You can grab the animations from the SWBF1 mod tools and munge them with the SWBF2 mod tools or just get them from the archive linked in this reply.

OK, I have them all now, but the Fambaas aren't there. Am I supposed to add them in ZE?

EDIT: Well, I tried adding them in ZE, but that resulted in a crash-to-desktop. So I'm not sure what to do...

The image I posted earlier just had all 3 types placed in ZE and it worked fine, you could also spawn them, it just depends on what your end goal is.
Clean and munge, check for any munge errors(not warnings) and fix them, if any. Play your map using the debug exe to see if it works, if it crashes check for severity 3 errors and trace them back to the source of the problem. If you don't understand what an error means then feel free to ask here. Backtrack your edits, use the process of elimination and remove or undo one thing at a time until your map works. No one here knows exactly what you've done or edited up to this point, you are the sole source of information regarding this problem, so double check everything and provide us with as much detail as possible so the community can help you resolve this.

OK, here's what I did:

1. Cleaned
2. Remade my map without fambaas
3. Munged and got this as an error log: (I get this every time I munge a world for the first time, and it doesn't make a huge difference)
4. Added the Fambaas in ZE (in the conquest layer)
5. Munged again, this time no error log
6. Tested using the BF2_modtools.exe, and got a crash to desktop.

bestdude101 wrote:3. Munged and got this as an error log:

For reference, that's called a munge log.

bestdude101 wrote:6. Tested using the BF2_modtools.exe, and got a crash to desktop.

Now go into your SWBF2 directory that contains the addon folder and look for a text document called BFront2. Open that up and paste it here inside spoilers. That's your error log. When your game crashes and you use the debugger, it writes down what went wrong.

I got the error log (this time for real) right here:


I got severity 3 errors, and very few of them actually had the word "fambaa" in them. In fact, many of these errors seem to be for things that should be doing fine, and went wrong when I installed the fambaas.

Make sure you have nab1_walk_fambaa.msh in your msh folder, and also nab_weap_bldg_fambaa_shield.odf and nab_weap_bldg_fambaa_generator.odf in your odf folder.

Unless you added rep_hero_anakin to a custom 'gun' side then it doesn't exist there, same with the nab_bldg_fambaa_generator.

Self explanatory, no odf exist for com_weap_gunturret and com_item_vehiclerecharge. Make sure you're placing odf files in ZE and not the msh files.

Double check your CP names and references, and remove unused hint nodes etc to clean up the error log.

I've done what would fix the error log, and now it doesn't crash, but I get the error with the black map and can't spawn.

Error log:

Double check any edits you made in the LUA, the last error seems to indicate a problem with your CP setup. I still see several severity 3 errors that need attention as well.

Good news! I remade the map, and the fambaas were in and I could spawn.
Now I have two more questions.

1. How can I rotate the fambaas so that they face the right direction?
2. How can I make it so if one fambaa (out of two) gets destroyed, the shield goes down?

bestdude101 wrote:1. How can I rotate the fambaas so that they face the right direction?

If you placed them in ZE, simply select the object and hold X. Then, use either left, middle, or right click to rotate in different directions.

Thanks.

I should probably rephrase my second question: Is it possible to have one shield operated by two fambaas (like in the BF1 campaign)?

It's probably able via lua, but I'm not that good.

I'd recommend looking at stock scripts and BF1 scripts to see how they set the shields up and see what you can do with them.

If have never worked with fambaas (or even played on a map with them) so I'm not sure if there is anything special about them, but sth. like this should do the trick:
I don't know how the shield object is coded but it is possible that KillObject does not work as it requires a destructiblebuilding type.
If it does not work you could try to make it invisible by replacing KillObject("NAME_OF_THE_SHIELD_IN_ZE") with SetProperty(NAME_OF_THE_SHIELD_IN_ZE, "IsVisible", 0).

New Problem: I've created a campaign script (that worked without the fambaas), and here are the problems:

1. The reinforcements don't change, even when one gets killed.
2. The first popup objective says [NULL], which it shouldn't.
3. I can only complete the first objective.
4. None of the markers I added are there.

(Script is too big for me to post)

Here's the error log: