top down camera

[hondobondo]

I am working on a gauntlet style mod. i can make the camera look down, but mouse look breaks that. if i disable mouselook, i still can't get aim to work. he just shoots at the ground. is there a way to fix the aim to just shoot straight ahead? i use normalize((self.origin+v_forward*500) - self.origin) but that makes him shoot however the mouse is aiming. how do i get him to just shoot from the origin+view_ofs to a point say 100 units straight ahead?

[Spike]

m_pitch 0
Evil, I know, but it stops mouselook from doing anything in pretty much all engines.

Clear out self.v_angle_x on the server before doing makevectors. This will set their angles as pure yaw (and a bit of roll, but that doesn't affect forwards), meaning that forward really is forward, even if their client ignored the m_pitch thing, and will always be properly normalised too.
The alternative is to 'tweek' the v_forward vector and set v_forward_z=0, but that's ugly, and breaks in certain clients/settings. And it needs normalising as well.

Clearing out their pitch is the more correct way to do it.

normalize((self.origin+v_forward*500) - self.origin)
is more simply written as:
v_forward
just so you know. :)

So yeah...
self.v_angle_x = 0;
makevectors(self.v_angle);
source = self.origin + self.view_ofs;
target = source + v_forward*500;
you prolly want a traceline here
impact would then be at trace_endpos but then you knew that already. mneh

[MauveBib]

WriteByte (MSG_ONE, 10); // 10 = SVC_SETVIEWANGLES
WriteAngle(MSG_ONE, vec_x); // tilt
WriteAngle(MSG_ONE, vec_y); // yaw
WriteAngle(MSG_ONE, vec_z); // flip

[hondobondo]

totally owe you both. graces

[hondobondo]

m_pitch 0
Evil, I know, but it stops mouselook from doing anything in pretty much all engines.

Clear out self.v_angle_x on the server before doing makevectors. This will set their angles as pure yaw (and a bit of roll, but that doesn't affect forwards), meaning that forward really is forward, even if their client ignored the m_pitch thing, and will always be properly normalised too.
The alternative is to 'tweek' the v_forward vector and set v_forward_z=0, but that's ugly, and breaks in certain clients/settings. And it needs normalising as well.

Clearing out their pitch is the more correct way to do it.

normalize((self.origin+v_forward*500) - self.origin)
is more simply written as:
v_forward
just so you know.

So yeah...
self.v_angle_x = 0;
makevectors(self.v_angle);
source = self.origin + self.view_ofs;
target = source + v_forward*500;
you prolly want a traceline here
impact would then be at trace_endpos but then you knew that already. mneh

that works. now for the fun stuff. i can probably have a working beta with monsters and a map or two by monday

[Boss429]

slightly off topic, but is m_pitch a cvar?

[mh]

Yup, but don't even think about setting it's value through QC unless you're doing something like this that has a specific requirement, OK?