Elite Force 2 Bridge Crew positioning issue

[killeen21]

From what I have seen in the Funny BC Screenshots topic I'm not alone with this problem so I was wondering if anyone here has found a reliable fix for it.

Whenever a torpedo hits the ship some of my extra crewmates from the Elite Force 2 BC Mod dislocate to the middle of the bridge while being partially stuck in the floor - I have attached a screenshot below.

I noticed that at the exact same spot where they suddenly appear there is an invisible obstacle that I cannot pass while using WalkFX - this does not happen in any other mutator based BC Crew modification - only the EF 2 Crew is affected.

Any suggestions are welcome...
PS: I'm using BC 1.1 with KM 1.0 installed.

[Morgan]

That's a known bug with the EF2 crew.  The team that brought the bots into BC left them in an unfinished "Alpha" state because they went onto Excalibur.  Unfortunately, they're stuck with this issue since modding these bots is forbidden in the readme, and crew bot modding is not the most well known area of modding in BC.

[killeen21]

But there must be some kind of a workaround.
From what I can tell the bug gets triggered when the hit animation for that specific caracter is played.

If I go into the bridge character scripts and remove all hit animations from the ExtraMale & Female characters would that be a possible solution or would I screw things up even more?

[Morgan]

If I go into the bridge character scripts and remove all hit animations from the ExtraMale & Female characters would that be a possible solution or would I screw things up even more?

You can't just remove animations from characters, it's likely that if you do that the game will crash the second one of those characters tries to walk onto the bridge.

As far as I can tell, the main problems with the EF2 bots is that the joints aren't aligned properly and the bots use stock animations, the same ones designed for the stock character bots.  To fix these issues you would need to figure out how to properly align the joints and create new animations tailored to the EF2 crew.  Both difficult and time consuming processes to say the least.  Unless you have the skills and the tools to do this, you're unfortunately left with two options:  switch back to the stock characters or suffer through the EF2 crew's bugs...

[Jb06]

I had this problem when i first started modding and it was to do with an error in the character scripts... So i'd suggest taking a look in them for the solution.

~Jb

[Mario]

I noticed that at the exact same spot where they suddenly appear there is an invisible obstacle that I cannot pass while using WalkFX - this does not happen in any other mutator based BC Crew modification - only the EF 2 Crew is affected.

That would be due to the WalkFX's character collision detection system which I developed for it back in '05. The system works fine actually but the game returns wrong values to the detection system for which there is no workaround. Namely the game believes the characters are in their initial spots and returns a set of XYZ coordinates but visually due to the animations they are in a completely different place.

[killeen21]

OK I solved the problem - I went into the Bridge specific charakter scripts in /scripts/Bridge/Characters/ and in the "# Hit animations" section I commented/deleted the first two and the last one of the hit animation lines in that category - then I repeated the process for all extra characters.

I cannot notice any crashes or other instabilities that might be caused by this but the dislocation bug is definetely gone.

[killeen21]

One problem remains though - the stock bridges don't have editable character scripts - only compiled ones so I'm unable to edit them and the bug still occurs on the Galaxy and Sovereign bridges.

Does anyone know where I can get access to/acquire the character script files for these two bridges or how to create new ones to overwrite the stock scripts?

[Lurok91]

You'll find them in the SDK here:

http://bridgecommander.filefront.com/file/;2455

[killeen21]

Thanks - that worked.