Engine traceline?

[Mexicouger]

What would an engine traceline look like?

[Eluan]

It would look like SV_Move...

[gnounc]

____________________________

[Mexicouger]

(-_-)___________________________________________(-_-)

I coulda swore I seen something in the engine concerning tracelines(Using them in the engine, rather than qc)

[Baker]

Explain further what you mean?

I reworked MH's chase-cam fix into a client-side visibility function.

If that is what you are looking for, I can post it here. But explain what you are trying to do? Are you talking server side (QuakeC) or client side?

[mankrip]

MH's method is really the best one. Long story short, regular tracelines only works for server-side physics.

[Downsider]

SV_Move

[Ranger366]

I reworked MH's chase-cam fix into a client-side visibility function.

viewtopic.php?t=2711

hurray

[Mexicouger]

I mean like using a traceline in the engine. I have a traceline that I use in player_pre_think, and I can't find any way to make it false. It really is heavy on the framerate(I lose around 3-4 fps)

So I thought If I just did it in The engine, I might save some memory strains. And the function is to make the crosshairs turn red. when the traceline hits something that takes damage, the crosshair turns red.

[r00k]

Code: Select all

void TraceLine (vec3_t start, vec3_t end, vec3_t impact)
{
   trace_t   trace;
   qboolean result;

   Q_memset (&trace, 0, sizeof(trace));
   trace.fraction = 1;

   //result is true if end is empty...
   result = SV_RecursiveHullCheck (cl.worldmodel->hulls, 0, 0, 1, start, end, &trace);
   
   if (!result)//hit something
   {
      VectorCopy (trace.endpos, impact);   
   }
   else
      VectorCopy (end, impact);   
}


unless you mean what the quakeC traceline looks like in C

Code: Select all

/*
=================
PF_traceline

Used for use tracing and shot targeting
Traces are blocked by bbox and exact bsp entities, and also slide box entities
if the tryents flag is set.

traceline (vector1, vector2, tryents)
=================
*/
void PF_traceline (void)
{
   float   *v1, *v2;
   trace_t   trace;
   int      nomonsters;
   edict_t   *ent;

   v1 = G_VECTOR(OFS_PARM0);
   v2 = G_VECTOR(OFS_PARM1);
   nomonsters = G_FLOAT(OFS_PARM2);
   ent = G_EDICT(OFS_PARM3);

   trace = SV_Move (v1, vec3_origin, vec3_origin, v2, nomonsters ? MOVE_NOMONSTERS : MOVE_NORMAL, ent);

   pr_global_struct->trace_allsolid = trace.allsolid;
   pr_global_struct->trace_startsolid = trace.startsolid;
   pr_global_struct->trace_fraction = trace.fraction;
   pr_global_struct->trace_inwater = trace.inwater;
   pr_global_struct->trace_inopen = trace.inopen;

   VectorCopy (trace.endpos, pr_global_struct->trace_endpos);
   VectorCopy (trace.plane.normal, pr_global_struct->trace_plane_normal);
   pr_global_struct->trace_plane_dist =  trace.plane.dist;   

   if (trace.ent)
      pr_global_struct->trace_ent = EDICT_TO_PROG(trace.ent);
   else
      pr_global_struct->trace_ent = EDICT_TO_PROG(sv.edicts);
}



[Spike]

So I thought If I just did it in The engine, I might save some memory strains. And the function is to make the crosshairs turn red. when the traceline hits something that takes damage, the crosshair turns red.

Thing is though, traceline *is* in the engine. Its a builtin... Meaning its built in to the engine.

do a traceline, check trace_ent.takedamage. easy!

[Mexicouger]

So I thought If I just did it in The engine, I might save some memory strains. And the function is to make the crosshairs turn red. when the traceline hits something that takes damage, the crosshair turns red.

Thing is though, traceline *is* in the engine. Its a builtin... Meaning its built in to the engine.

do a traceline, check trace_ent.takedamage. easy!

Thing is, I have nowhere to put it but playerprethink, Which I hate clogging that up. My intention was to maybe move it to the engine for a speed increase

[mankrip]

Create a float crosshair_time, and use it to only run the traceline check at a fixed time interval, like 0.1 seconds.

[Sajt]

The traceline is already done in engine code. All QC does is call the function. All the overhead isn't in the function call, it's what the function itself (which in the engine) is doing. Moving the traceline CALL to the engine won't solve anything.

In the other thread I posted an example of what mk suggested...

[frag.machine]

So I thought If I just did it in The engine, I might save some memory strains. And the function is to make the crosshairs turn red. when the traceline hits something that takes damage, the crosshair turns red.

Thing is though, traceline *is* in the engine. Its a builtin... Meaning its built in to the engine.

do a traceline, check trace_ent.takedamage. easy!

Thing is, I have nowhere to put it but playerprethink, Which I hate clogging that up. My intention was to maybe move it to the engine for a speed increase

*sigh*

Shoving bad code into the engine won't make things magically works.

traceline is already as optmized as it can be. If your QC code is slowing things down, maybe you should first consider that your code is the culprit. What exactly are you trying to do ?