 |
What happens if the mass is changed to 0x7FFFFFFF? |
|
|
The problem comes from mass being signed. 0xffffffff is a mass of -1, i.e. less than nothing. Up to two weeks ago the ZScript parser clobbered any integer value larger than 0x8000000 on Windows because it used a signed int function that clamped the result if it got too large. Sorry, can't revert because the old behavior was broken. You have to lower the mass to 0x7fffffff. |
|
|
That is a shitty solution. This behavior was consistent with the setup from 7 years ago. Basically, you're saying that you can't fix a problem that was created earlier. In other words, retroactive compatibility is the lowest priority. Not a way to promote a long-term way of doing business. While I respect your need to ensure no broken code going forward, this is basically fucking up anything that was previously developed in compliance with parameters of the game engine from an earlier era. I completely disagree, and will need to re-evaluate how I want to handle this. For the record, I think that you're being dictatorial and don't give a fuck for retroactive compatibility. I realize you're on the Paranoiac Team, but you don't seem to be promoting the needs of this project. Regardless, thanks for your input. |
|
|
Incidentally, it turns out that this problem applies just to the Gargantua, so it might be a relatively easy fix. |
|
|
Incidentally, tried the 0x7FFFFFFFF, but the actor still seems to be pushed back significantly with a minor projectile attack. I thought this was an easy fix, but apparently not. |
|
|
It should be 0x7FFFFFFF, with seven 'F' characters instead of eight. |
|
|
@ _mental_ and Edward-san: Thanks for giving me the proper definition. It works just as intended now. |
- Anonymous
