You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SA-MP/open.mp uses section 0x0253F2FF(39056127), compared to the normal collision models that use 0x0253F2FA(39056122). If you add a new section type for 39056127, you can export it the collision into section type 0x0253F2FF. Currently, this means only being able to export either normal collision, or SAMP collision, rather than both.
What's a good way of doing a conditional statement to check between "Normal" collision and "SAMP", so that people can export all supported .DFF and .COL types including SAMP, rather than keeping SAMP as a stand-alone fork?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
SA-MP/open.mp uses section 0x0253F2FF(39056127), compared to the normal collision models that use 0x0253F2FA(39056122). If you add a new section type for 39056127, you can export it the collision into section type 0x0253F2FF. Currently, this means only being able to export either normal collision, or SAMP collision, rather than both.
What's a good way of doing a conditional statement to check between "Normal" collision and "SAMP", so that people can export all supported .DFF and .COL types including SAMP, rather than keeping SAMP as a stand-alone fork?
Beta Was this translation helpful? Give feedback.
All reactions