Some of you who have played BFX may be familiar with this problem.



The hateful, horrible, awful AT-ST view bug! I have no idea how to fix it. It appears to be that the pilot's view point (the gunner is fine) is right between the two feet of the AT-ST. Here's my code:

Are the camera values any different than the default AT-AT?

Have you tried changing the y value for EyePointOffset, TrackCenter, or TrackOffset, yet? If not, see if changing it for any of those yields any results at all. From what I see, the odf appears as it should, but I don't think it'd hurt to see if you can move the camera a little and work from there.

Also, the gunner position has something the main section does not:



Oh, one other thing occurred to me. You could try replacing the main camera values with that of the gunner position to see if that makes it better. This is somewhat counter-intuitive to me, though, since the difference in the y values on the EyePointOffset line in each position would suggest a negative y value would raise the camera. Honestly, I'd say don't try a negative value, since I'm pretty sure it'd set the camera under the terrain, unless someone doesn't know how to graph. I'm guessing this difference has to do with the MountPos line being present. Changing the TrackOffset looks somewhat promising, though, from glancing at the numbers.


Granted, I'm speculating quite a bit, but you don't stand to lose much if I'm wrong.


..................................


*sighs* Excuse the rambling, if you could. I should be asleep by now. Here's the thing; the EyePointOffset looks like it's as it should be given the two different approaches, the TrackCenter is apparently the same for both, and TrackOffset appears to be the only real difference. Hopefully, if I've thought this through correctly, I have this narrowed down to changing the y value of TrackOffset for the pilot to something close to what the gunner uses.

Okay, the problem is not resolved. But I have collected some more information about it.

1. Does not affect every AT-ST on the map. On Hoth, it only affects the one that spawned at the CP nearest to the AT-AT spawn point.

2. Does not have something to do with the view settings. It has something to do with the geometry, or how it's loaded into memory.

How do I know this? When I fired at an affected AT-ST's head, the shot went right through. Collision problem?

It also exhibits this problem:



The head seems to be independent of the body - the weapons are poking right through, as if they are moving and the head isn't. Also, the AT-ST's legs will move up and down, but the head will hover in one place while walking.

Finally, the head hovers in mid-air after the AT-ST has been blown up. The legs fall down, but the head stays in the air and vanishes after a while.

Do you have enough memory set for that walker type? Or probably some other random memory thing you need to set. The atst has bones and is enveloped like a unit, if that helps anything. Perhaps it's something in nature to the freecam glitch where the skeleton gets screwed up. it seems it is just something to do with bone_head or something. From the effects you describe, it's behaving as 1. either bone_head is detaching itself from the skeleton or 2. bone_head is ceasing to exist and the mesh has nothing to be enveloped to. Still quite a mystery.

Good news! I think I've found the source of the problem. I looked in BFront2.log, found two memory pools that needed raising - "WalkerBlend" and "WalkerUnitBlend." That last one caught my eye because of RepSharpshooter's explanation that the AT-ST is structured like a unit. It's munging as I write this. [fingers crossed]