A question about the bounding box. My player has the bounding box, so he is non-passable when he is not in the vehicle. The vehicle also has the bounding box, so when I get in the vehicle it behaives unpredictably, thus I make the player passable, when he enters the vehicle
if(my.x == vehicle.x){ set(my,PASSABLE);}
though when I get out of the vehicle again, I cannot make myself unpassable again? Is there a flag opposite to PASSABE?
Another question: if I for example make the player unpassable all the time, even if I enter the vehicle, I don't care about its weird behavior, though when I get out from it, the player's bounding box is changed, it is much bigger now....why so? I try to adjust his bounding box again, c_setminmax(me), then vec_set(my.min_x.....) and so on, but the bounding box does not change to its normal scale. Even if I put the c_setminmax in the loop, the bounding box changes to the normal scale, but it attempts to change to that bigger scale every frame... So the player looks as if he is jumping slightly all the time.... How to fix it? Any ideas?
Thanks in advance

Why you can't get unpassabble?
Are you using reset(me,PASSABLE) to make the player unpassable, or how do you do it?
muffel

reset(me,PASSABLE);

Are your SURE you are using "reset(me,PASSABLE);" when the
ME pointer is set to the player (rather than the car)?

Easy mistake to make. Done it many times myself...

Never mind about the passable problem, I figured it out already, rather tell me please waht might be wrong with the bounding box? Why does it change its scale?

ohh you forgot this i guess..
When you set the new values for the bounding box, as you stated above, you have to call update_hull(entity) i guess thats the name of the function.. other wise the bounding box wont get to its normal size so to say.

Emmm... better to say I didn't know about this Anyways thanks, I'll try....

Yeah sometimes it happens to me too...

dot forget to feedback.

I am "feedbacking": well, I think you mean c_updatehull , thogh , I don't think I need it, it takes a lot of fps and it is basically for changing the bounding box if the animation changes, e. g. if the player ducks ,then lies, then stands. So it will change the bounding box each frame as the player is running, which I don't need. I tried to write some new values for the bounding box and put the c_setminmax in the loop, and it now works fine... I think it was the engine bug or something... I hope it won't happen again, unless I understand why yhis happens.

but if you change the c_setminmax i guess it requires the c_update too? no? each time you change the hull you must update the hull to fit that values, at least thats what i thought