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
Entity_GetAbsOrigin uses m_vecOrigin rather than m_vecAbsOrigin for some reason. We've only recently discovered that when used on a func_door_rotating, it returns the world origin (0, 0, 0). Are there any historical reasons for this function using m_vecOrigin rather than m_vecAbsOrigin? From the SDK, CBaseEntity::GetAbsOrigin uses m_vecAbsOrigin instead.
UPDATE: (If it wasn't obvious, the latter prop solves this case, causing to return the correct origin)
The text was updated successfully, but these errors were encountered:
Adrianilloo
changed the title
Entity_GetAbsOrigin returns NULL_VECTOR for func_door_rotating
Entity_GetAbsOrigin returns zero for func_door_rotating
Nov 20, 2021
Entity_GetAbsOrigin
usesm_vecOrigin
rather thanm_vecAbsOrigin
for some reason. We've only recently discovered that when used on afunc_door_rotating
, it returns the world origin(0, 0, 0)
. Are there any historical reasons for this function usingm_vecOrigin
rather thanm_vecAbsOrigin
? From the SDK,CBaseEntity::GetAbsOrigin
usesm_vecAbsOrigin
instead.UPDATE: (If it wasn't obvious, the latter prop solves this case, causing to return the correct origin)
The text was updated successfully, but these errors were encountered: