Distance formula and measurement calculations
Moderator: InsideQC Admins
7 posts
• Page 1 of 1
That's a lot of lines of code for just doing 'result = vlen(trace_endpos - self.origin)
Also your scale seems to be odd. The accepted scale is 8 quake units = 12 inches, yours seems to be 6 inches.
Other than that it's nifty I guess
Also your scale seems to be odd. The accepted scale is 8 quake units = 12 inches, yours seems to be 6 inches.
Other than that it's nifty I guess
F. A. Špork, an enlightened nobleman and a great patron of art, had a stately Baroque spa complex built on the banks of the River Labe.
- Sajt
- Posts: 1215
- Joined: Sat Oct 16, 2004 3:39 am
First site i saw it said 16 qu = 1ft, i guess its actually closer to 8. Also for mathematical history purposes i used the real 3d distance formula. So ya I'll change it from devinding by 16 to 8. Also changed the inches from 1 1/3 to 2/3.
Number wise it looked better by 16, mainly because the quake guy hauls ass from 0-60mph when running and by 16 the numbers look more realistic in terms of distance.

Number wise it looked better by 16, mainly because the quake guy hauls ass from 0-60mph when running and by 16 the numbers look more realistic in terms of distance.

- Chris
- Posts: 79
- Joined: Sat Aug 05, 2006 5:31 am
Well, feh's 8 qu = 12 inches is the most accepted one when you're forced to accept a scale, but usually people just leave them at quake units because Quake has no consistent scale anyway.
The 'real' distance stuff you use is the same as vlen(trace_endpos - self.origin).
The 'real' distance stuff you use is the same as vlen(trace_endpos - self.origin).
F. A. Špork, an enlightened nobleman and a great patron of art, had a stately Baroque spa complex built on the banks of the River Labe.
- Sajt
- Posts: 1215
- Joined: Sat Oct 16, 2004 3:39 am
I demand leagues!
But yeah, quakeguy is 32 qu wide and 52 high, so he's pretty fat. quakeunits clearly have a different scale in different axis...
Oh, and regarding that rotating doors tut, I think you have to use self.ltime rather than time if you want velocity / avelocity to work as predicted. Something about movetype_push being absurd...
But yeah, quakeguy is 32 qu wide and 52 high, so he's pretty fat. quakeunits clearly have a different scale in different axis...
Oh, and regarding that rotating doors tut, I think you have to use self.ltime rather than time if you want velocity / avelocity to work as predicted. Something about movetype_push being absurd...
- Spike
- Posts: 2892
- Joined: Fri Nov 05, 2004 3:12 am
- Location: UK
7 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest
