Battlezone Forums

The ai cannot get aimed up on your model so it never shoots... Scale?

GeometryScale = 1.0

The same size as an ISDF pilot.

Well a few things I suspect could be the case:

1) hp_com exists outside of the pilot's model. Much like how it works with mines, if the hitbox exists in an 'illegal' place, like under the ground, then the AI won't even attempt to shoot at the thing.

2) The model might be 'inside out' (is this a thing?) or something might be wonky with the way the verts and such are set up. The AI thinks that it has to go into the model to get a clear shot, then having gotten 'close enough' it decides that it no longer has to move, but also doesnt fire because it doesnt think it has a clear shot. (maybe use path editor to see what the AI is thinking)

3) The pilot may use a weapon which has a model that duplicates the pilot's own hardpoints (e.g. hp_hand_1, hp_com). I think this can cause problems to happen with the pilots.

Bear in mind that this happens to 4 completely different QF2 pilot model designs (different races).

hp_com_1 didn't even exist before in the model files. GBD suggested I should add it, but it changed nothing (yes, within the model).

None of them are inside out.

Pilot weapons don't have any hardpoints inside their files.

I'm completely lost as to what could possibly cause this. Stock units exhibit the exact same behaviour in regards to these pilots. They either sit there and get shot at, try to ram the pilots or actually shoot at them (for only a few seconds before switching to one of the other behavioural options). It's not my QF2 units at fault.

The pilots don't have anything particularly special (as far as I could tell) in their ODFs.


So, I ask again, what ODF parameters, or what parameters of any kind, cause units to attempt to ram pilots? Does anyone actually know?

If you think its possibly your pilot ODFs, just take ispilo.odf and have it use your model. If the problem persists then its 100% most definitely a model problem.

there's nothing wrong with the stock units, so that leaves your stuff.

try tweaking some of these. also, what team are the pilots on? are they allied with the craft?


[GameObjectClass]
canDetect = 0/1 // can attack other pilots through attack command
canTarget = 0/1 // can target

heatSignature = 0.1
imageSignature = 0.1
radarSignature = 0.1

isStealth = 0/1

[CraftClass]
detectRange = 0/1

As I've said many times, provide a minimal savegame. You can make a test map -- e.g. dunesi.bzn with /nobodyhome , and add your pilot odfs and xsi/msh files versus some stock units. None of your custom textures needed. Then, you can make a private bug on bugzilla (readable only by you and me) and attach map + your pilot odf/xsi/msh. (Or, email me a download link separately.) I'm not going to leak any of your assets. Seriously.

If you want things fixed, then you need to follow my procedures. Same as anyone/everyone else. Writing paragraphs doesn't really get anything fixed. And if you manage to fix it on your end but not submit any files, then you're a selfish person who doesn't want anything really fixed for the next person to poke at this area.

-- GSH

I've also found out that if you link ODF's you more easilly presented with some unexplainable crashes. Can reproduce it, but not properly as I cant pin it down properly.

Possibly could be an animation thing, they can do funny stuff if you don't get em set up just right.

Red Spot wrote:I've also found out that if you link ODF's you more easilly presented with some unexplainable crashes. Can reproduce it, but not properly as I cant pin it down properly.

Do you mean inheritance or something else?