Explanation of CM_BoxTrace requested
Page 1 of 1

Author:  speaker [ 11-19-2020 04:43 AM ]
Post subject:  Explanation of CM_BoxTrace requested

Never mind, I figured it out.


Could someone please explain the use of arguments in the function CM_BoxTrace? I marked below the arguments in question. What are the possible values and what is their purpose?

trace_t *results,
const vec3_t start,
const vec3_t end, <- how could I know in advance where the trace stops? Or is this a limit?
vec3_t mins,
vec3_t maxs,
clipHandle_t model, <- model of what?
const vec3_t origin,
int brushmask, <- inclusion/exclusion? if yes, what?
int capsule <- ???

I tried to figure it out by following function calls and argument usage but the whole thing seemed to me hopelessly convoluted. All I need is a simple line trace (like the railgun code does) and identification of the endpoint (type of entity hit).


Author:  Ganemi [ 01-05-2022 10:56 PM ]
Post subject:  Re: Explanation of CM_BoxTrace requested

What are you trying to do with this? I tried to get the pill collision code to work but I don't understand it. :(

Maybe I should start with a sphere...

Page 1 of 1 All times are UTC - 8 hours
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group