Re: [Quake-C] Using v_forward vs. Aim () function ?

[<qu...@ca...>]

Quick followup.

I saw a note stating the autoaim was for vertical aiming.
I'd have to spend more time with the engine code than I want to verify 
that.


Like a few things in the engine and quake-c iD likely had some plans to
use the 'x' for a predictor of some kind.

Like if a missile was moving at 1000 units, and the ent was closer than 
500 or 600
units it could be discarded as a selection.


I also should point out that it will pick the smallest deviation from 
v_forward if there
are multiple valid entities within the cone provided by sv_aim and the 
dotproduct test.


Support free code by Six gaming on Patreon: 
https://www.patreon.com/six_gaming




On 2016-09-30 01:04, qu...@ca... wrote:
> Best check that engine code.  For this:
> 
> On 2016-09-29 12:12, je...@qb... wrote:
>> The Quake source code comment says it's missile speed, and the
>> argument is read, but it's not actually used in the function. See
>> PF_Aim in pr_cmds.c This function is loaded with various tasks, so
>> overhead could be an issue if calling it a lot.
>> 
>>> -------- Original Message --------
>>> Subject: [Quake-C] Using v_forward vs. Aim () function ?
>>> From: "Cobalt" <co...@te...>
>>> Date: Thu, September 29, 2016 12:19 pm
>>> To: "QC" <qua...@li...>
>>> 
>>> Recently discovered if you call makevectors and get a v_forward,
>>> you basicly
>>> wind up with the same result as if you did:
>>> 
>>> aim (self, x);
>>> 
>>> What exactly is the ' x ' float for in that function?
>>> 
>>> 
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> - The QC users mailing list -
> Qua...@li...
> https://lists.sourceforge.net/lists/listinfo/quake-c-users
> Project Homepage: [ https://sourceforge.net/projects/quake-c/ ]