[chief1983]

Looks like the split is causing problems, so it's probably related to the way it's passed to the split calls, or where the split data is calculated in the first place.  That just may narrow it down to about 3 lines I'd start looking at.  The call after *type_p == 0, or the two lines after // split.  Unfortunately I'm not much help at this point, as I have no idea what all that stuff is going on, but it definitely looks like something that could break on PPC and work fine on x86 if you're not careful.

[sanchox]

cool, at least we are narrowing down the issue.  hopefully someone is out there with some experience and knowledge regarding this sort of a thing.  any recommendations for me in terms of pressing on? 

[sanchox]

you mentioned looking to the call after *type_p == 0    well i looked around and found this
char *type_p = (char *)(Mc_pm->shield_collision_tree+offset);

it shouldnt be a char should it??

[chief1983]

No I think that line is fine.  The line after what I'm talking about is the line where it makes the next set of calls to mc_check_sldc, where it 'splits' and calculates what new data to pass it.  I'm thinking there's something wrong with that, or where it calculates the front/back vars themselves.  Aside from that I have no idea like I said.