-= Gametoast.com =-

The point where the shoots come out is hardcoded as well, it's always at the height of a jawahead.

Syth wrote:Also hardcoded:
types of item dropped when unit dies
no 1st person for land vehicles
the reticle

That first one is wrong, you can tweak them. Check out the default unit .odfs.

The last two I'm fairly sure are modifiable, but I've never tried them myself.

And yeah, xwingguy was mistaken about unlimited local teams. I think that AceAzzameen5 will confirm that, too.

You cant add a 1st person for vehicles, i've looked into this. You can for turrets positions on the vehicles, but not the pilots position. There is no button to activate 1st person on vehicles.
I also tried to change the reticle before, theres no working odf code to change it.. but i never tried changing the geometry for the reticle in the ingame level.

There was a thread about the items dropped from units, and no one was able to change them with out a crash.. only the percentages that each one might appear.

You can't change the default dropped items or make new ones being dropped I think, but I've seen new items in some maps in dispensors. That's different though, I know. But my point is the dead unit droppings must be hardcoded then.

I think Mav played with this so he should know the details, but I think I remembered correctly.

Syth wrote:You cant add a 1st person for vehicles, ive looked into this. You can for turrets positions on the vehicles, but the the pilots position. THere is no button to activate 1st person on vehicles.
I also tried to change the reticle before, theres no working odf code to change it.. but i never tried changing the geometry for the reticle in the ingame level.

I'll trust that you say that you can't add a first person, but I'm surprised to hear that the Forcemode and FirstPersonFOV .odf lines do nothing, since psych0fred's ODF parameters doc would have lead me to believe they would.

But the other two things should be able to be changed through ingame.lvl modification. They're listed in the ingame.req (here's the excerpt in which you can see both), so there's no reason why they shouldn't be modifiable with a dc:'ed ingame.lvl:

You can't change all of the values needed to change CPs color, only most of them. They still show on the map as red/blue

A Planning Hub can only have a Maximum of 8 connections connected to it.

MasterSaitek009 wrote:

da_great_ghost wrote:In Boras II: Stunt Corse v3 Dann made the sniper have the abilty to have more than 1 auto turret at 1 time.

More than one turret out at a time? Or more than one type of auto turret for a unit class?

more than 1 turret at a time.

I've been watching this topic and am not sure what to make of it. There has been (and still is) a lot of wrong info posted. Only a couble of the fixes actually have code/info posted proving that the item was wrong and none of the other listed items have proof posted as to why they are the way they are.

I would say that any item on the list should have a section showing the code/document quote/or other info that proves the item is truly hard coded to that value. If you can't post the steps to show that one above the limit doesn't work, then it shouldn't be included.

I wouldn't even consider a third of the items on the list to be hard coded values. Not to be mean, but it almost looks like people are saying random things and they are all being stuck onto a list.

[RDH]Zerted wrote:I've been watching this topic and am not sure what to make of it. There has been (and still is) a lot of wrong info posted. Only a couble of the fixes actually have code/info posted proving that the item was wrong and none of the other listed items have proof posted as to why they are the way they are.

I would say that any item on the list should have a section showing the code/document quote/or other info that proves the item is truly hard coded to that value. If you can't post the steps to show that one above the limit doesn't work, then it shouldn't be included.

I wouldn't even consider a third of the items on the list to be hard coded values. Not to be mean, but it almost looks like people are saying random things and they are all being stuck onto a list.

What's missing/incorrect? I know if I've mentioned something it's either from first-hand experience (i.e. I can't give you a doc that specifies that 70 regions is the max, but I know the game will crash at higher than that and there are no adjustable memorypools for it) or I've provided support from fred's docs. Most of the other postings seem to be agreed-upon limits that we've found through testing.

And yes, "hard-coded" is being thrown around sort've willy-nilly, but the gist is that the things mentioned above are ingame limits.

Maybe a more suitable thread name be "Not unmodifiable stuff" or something like along those lines

@ Mav -
I never really considered the forcemode line. I will test it, im not sure if i already have before though but i will just to make sure.

EDIT: I added it to the IFT-X and it didnt do anything
EDIT2: Yes it did i lied (actually i acidentley put forcemode = 1 rather 2). SO you can force 1st person in vehicles.

[RDH]Zerted wrote:I've been watching this topic and am not sure what to make of it. There has been (and still is) a lot of wrong info posted.

That would be my fault. But, that is also part of the purpose for this thread, not so much posting known limits, but instead discussing those things that might be limits. The suggestions don't have to be perfect(as we have seen by many of my posts). They just have to throw the idea out there so that more experienced people can prove or disprove it.
Alone I don't know everything about the BF2 engine, neither does anyone else. But every modder has unique info that someone else might not have. So when you add together all of our ideas and a large helping of discussion, we can all contribute to and learn from this thread.

If you do notice any wrong info please, point it out. I would be greatly appreciative.

I do agree that the name needs to change. Hardcoded values is kind of non-descript.
How does "BF2 Engine Limitations" sound?

You can't make corpses stay in the map once a unit dies

There are a few ways (adding health regen, changing AI damage thresholed, etc...) to prevent taking damage while underwater, though they don't prevent the screen from flashing. However, Droidekas haveChanges made to a unit classes via the Lua do not always require the unit to respawn inorder for those changes to take affect. I'm not going to make a video showing this, but its true.

Droidekas are a type of vehicle and have 1st person views, so vehicles can have 1st person views. In addition to that, the docs say they can too.You can have less than 9 selectable units per team. Just add less than nine units when settting up that team.

This code prints out 'To Team 0-9' before crashing. Are you sure the team limit isn't 9 (0 to 9 is 10, minus 1 for the crashing team = 9 total teams, and it might have even crashed on team 11 before the log could be updated...)? I've never used it, but weapon classes have the ODF key ReticuleTexture. Are you saything this key doesn't work or did you try changing something else?

The docs talk about editing the dropped items. I won't believe that you can't do it until someone posts the steps required to change the items and leads to the corresponding game crash.

FirstPersonFOV, ThirdPersonFOV, and ForceMode are all used on units in the FakeConsole. I've never used them on vehicles, but the docs say they work on controllable objects, support, and units (or is that support units. If so, whats the difference between weapons and support weapons?).

The problem with the docs is that even though most of the info in it is accurate, there's also some info in it that may only pertain to the Xbox/PS2 or is just inaccurate/misprinted maybe?, the tentacle setup info in the BF2_Jedi_Creation.doc is 1 example of this.

Doc says:
The artist needs to include bones named bone_string1 through bone_string# (maximum is 45)

however we have found that naming the bone strings to:
bone_string1
will not work, it must be:
bone_string_1

Also the docs say the max bone strings is 45, but we have since found that the PC will not support that many, it looks like the PC will only support 20.

Doc says:
Note that the max tentacles is 9, and the max bones is 5.

but I have found through testing that only 4 tentacles will work.
5 tentacles with 4 bones each will not work
4 tentacles with 5 bones each will work

I guess what i'm saying is we really don't know what info in the docs is meant for the PC or the other platforms until everything's been tried and tested.

[*]You can only have(What number exactly?) object's in (is it all of the layers added together or just the ones loaded in the Lua?)

This varies depending on the types of objects you have added. Certain objects take up very little listpool memory (like rhen var: citadel walls/floors/etc) and can be added in great numbers. Other objects that are much more detailed take up more, and ones that have attached properties to them take up twice as much (especially cps, which is one of the reasons the CP max is 16). Adding the same object multiple times can also cause problems. But roughly, the max amount of objects would probably be somewhere in the hundreds

[*]Only one auto-turret type weapon per unit.

You can have as many as you want really. This goes for mines, and any dispensable object as well. You define this in the dispenser weapon's main weapon ODF with the function: MaxItems = 4.0 or however many you want.

[*]There are only two weapon channels. Primary and secondary.

WeaponChannel = 0 is primary (only needed if its overwriting something in a Parent odf), WeaponChannel = 1 is secondary.

[*]Each unit can have up to eight weapons. Four primary and four secondary.

It is true you can have 8 weapons total, but you can have as many as 8 primary weapons (8 primary and 0 secondary) and as many as 7 secondary weapons (1 primary, 7 secondary). This includes award weapons.

[*]The grappling hook doesn't work in BF2.

I thought somebody got that to work..

[*]Nine selectable units per team.

All mode Objective types (ObjectiveConquest, etc) but ObjectiveTDM can only have 6 units (7 counting heros if they are enabled) per team. ObjectiveTDM can have 9 per team with AddUnitClass.

[*]You can have a maximum of 16 Command Posts + plus Command Vehicles.

Command Vehicles count towards the 16 CPS, not in addition

SBF_Dann_Boeing wrote:

[1]Only one auto-turret type weapon per unit.

You can have as many as you want really. This goes for mines, and any dispensable object as well. You define this in the dispenser weapon's main weapon ODF with the function: MaxItems = 4.0 or however many you want.

[2]There are only two weapon channels. Primary and secondary.

WeaponChannel = 0 is primary (only needed if its overwriting something in a Parent odf), WeaponChannel = 1 is secondary.

[3]Each unit can have up to eight weapons. Four primary and four secondary.

It is true you can have 8 weapons total, but you can have as many as 8 primary weapons (8 primary and 0 secondary) and as many as 7 secondary weapons (1 primary, 7 secondary). This includes award weapons.

[4]The grappling hook doesn't work in BF2.

I thought somebody got that to work..

[5]Nine selectable units per team.

All mode Objective types (ObjectiveConquest, etc) but ObjectiveTDM can only have 6 units (7 counting heros if they are enabled) per team. ObjectiveTDM can have 9 per team with AddUnitClass.

[6]You can have a maximum of 16 Command Posts + plus Command Vehicles.

Command Vehicles count towards the 16 CPS, not in addition

1) He wasn't referring to number present on the field, he means distinct types.
4) No one's gotten this to work.
5) You can have up to nine distinct units per team in any gamemode.
6) That's what he was saying: 16 (Command Posts + Command Vehicles).

Correct.
Thanks for clarifying Mav'!

MasterSaitek009 wrote:[*]Changes made to a units non-instance property via Lua(SetProperty) only take effect after the unit respawns.
[*]Maximum of eight teams total, including the regular ATT and DEF team 1 and 2.

You mean SetClassProperty(). SetProperty effects objects, and a respawning causes a deletion/creationg of a new object meaning that it no longer has the changed property. However, I would have written that line more like 'Some SetClassProperty() changes only take effect after a respawn'. I think saying 'non-instance property' makes it seem more confusing then it really is.

The code I posted earlier shows that at least 9 teams are possible (people are forgetting about the always existing team 0).

Oh, I thought of one! Flyers cannot strafe. No matter what settings you use, they will not strafe. Psych0fred told me one time early on in the Convo Pack's development that the code was broken when writing the code to make flyers roll.