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
Currently we have multiple separate functions drawing the same collision shapes.This means we currently have quite a bit of variation in how this is being done, what custom properties are being set etc... These should all eventually be combined into one function per shape that can be easily called from anywhere. Something like:
draw_boxcol(half_extents, physmat, type)
draw_convcol(vertices, physmat, type)
draw_capcol(radius, height, physmat, type)
draw_spherecol(radius, height, physmat, type)
If we keep the actual placement of the shapes in the world where it is and just do the basic drawing and applying of properties in these functions, it should be pretty simple to both standardize them, and account for the differences between import/generation and ents vs sectors vs .phys vs meshes
The text was updated successfully, but these errors were encountered:
Currently we have multiple separate functions drawing the same collision shapes.This means we currently have quite a bit of variation in how this is being done, what custom properties are being set etc... These should all eventually be combined into one function per shape that can be easily called from anywhere. Something like:
draw_boxcol(half_extents, physmat, type)
draw_convcol(vertices, physmat, type)
draw_capcol(radius, height, physmat, type)
draw_spherecol(radius, height, physmat, type)
If we keep the actual placement of the shapes in the world where it is and just do the basic drawing and applying of properties in these functions, it should be pretty simple to both standardize them, and account for the differences between import/generation and ents vs sectors vs .phys vs meshes
The text was updated successfully, but these errors were encountered: