Originally Posted By: jcl
This is one of the cases where we sacrificed compatiblity for a bug fix and for our support's sake. Wrong collision boxes of large models are a frequent beginners' problem. This is gone now, and for this we accepted the incompatibility. You can check your bounding boxes by pressing F11 twice, and should be able to fix your script in 2 minutes. Correct movement code, as in 99% of all levels, will still work as before.
(from another thread)

I understand your saying but I do not think that c_setminmax and c_updatehull work right now (my model is 83 quants high):

A7.80:
Click to reveal..

unchanged bounding box:

c_setminmax:

(click to enlarge)


A7.82:
Click to reveal..

unchanged bounding box:

c_setminmax:

(click to enlarge)


and c_updatehull:
Click to reveal..

7.80, c_updatehull with some manually adjusted min/max settings:

7.82, identical code:

(click to enlarge)


And no, unfortunately this problem is not fixable in 2 minutes, the movement has many modes (normal, ball mode, carry a big object, tiny player size, ...) which change min/max and co. I have to accept it but please have a look at the size of the 7.82 collision box!


"Falls das Resultat nicht einfach nur dermassen gut aussieht, sollten Sie nochmal von vorn anfangen..." - Manual

Check out my new game: Pogostuck: Rage With Your Friends