per polygon hit detection tutorial?
Moderator: InsideQC Admins
21 posts
• Page 1 of 2 • 1, 2
per polygon hit detection tutorial?
by metalmodman » Sat Jan 08, 2011 3:00 am
I think I remember some one posting a link to a per polygon hit detection tutorial for quake one, but I cant find it. Does any one know what I'm talking about?
-
metalmodman - Posts: 50
- Joined: Mon Jun 08, 2009 4:58 am
Re: per polygon hit detection tutorial?
by Team Xlink » Sat Jan 08, 2011 5:17 am
- Team Xlink
- Posts: 368
- Joined: Thu Jun 25, 2009 4:45 am
- Location: Michigan
by metalmodman » Sat Jan 08, 2011 11:57 am
Thank you Team Xlink!
When my coding improves I'm going to try to get this working on dedicated servers and try to do some thing like doom for head shots.
When my coding improves I'm going to try to get this working on dedicated servers and try to do some thing like doom for head shots.
-
metalmodman - Posts: 50
- Joined: Mon Jun 08, 2009 4:58 am
by Team Xlink » Sat Jan 08, 2011 2:59 pm
- Team Xlink
- Posts: 368
- Joined: Thu Jun 25, 2009 4:45 am
- Location: Michigan
by frag.machine » Sat Jan 08, 2011 5:33 pm
I know FrikaC made a cgi-bin version of the quakec interpreter once and wrote part of his website in QuakeC 
(LordHavoc)
(LordHavoc)-
frag.machine - Posts: 2120
- Joined: Sat Nov 25, 2006 1:49 pm
by mankrip » Sun Jan 09, 2011 11:43 am
From what I've seen in the tutorial, it should be easy to make it work only on some entities, which should reduce its processing requirements.
Another optimization would be to not use it on entities hit by tracelines that exceeds a certain distance, so entities that are far away would be processed through the regular hit detection instead.
And there's a kind of bug in that tutorial: It only applies the per-poly detection after the bounding box detection has been done, so if the bounding box is smaller than the model, some parts of the model will never collide against the tracelines anyway.
Another optimization would be to not use it on entities hit by tracelines that exceeds a certain distance, so entities that are far away would be processed through the regular hit detection instead.
And there's a kind of bug in that tutorial: It only applies the per-poly detection after the bounding box detection has been done, so if the bounding box is smaller than the model, some parts of the model will never collide against the tracelines anyway.
Ph'nglui mglw'nafh mankrip Hell's end wgah'nagl fhtagn.
==-=-=-=-=-=-=-=-=-=-==
/ /
==-=-=-=-=-=-=-=-=-=-==
/ /
-
mankrip - Posts: 915
- Joined: Fri Jul 04, 2008 3:02 am
by metalmodman » Mon Jan 10, 2011 12:11 am
ah that would be cool.
Some thing like this right?
It would be great to get this working and all done server side so it doesn't change the clients requirements.
Some thing like this right?
It would be great to get this working and all done server side so it doesn't change the clients requirements.
-
metalmodman - Posts: 50
- Joined: Mon Jun 08, 2009 4:58 am
by mankrip » Mon Jan 10, 2011 1:03 am
Yes, that kind of model.
Physics are always processed server-side, so clients shouldn't be affected by it anyway - even without optimizations.
Physics are always processed server-side, so clients shouldn't be affected by it anyway - even without optimizations.
Ph'nglui mglw'nafh mankrip Hell's end wgah'nagl fhtagn.
==-=-=-=-=-=-=-=-=-=-==
/ /
==-=-=-=-=-=-=-=-=-=-==
/ /
-
mankrip - Posts: 915
- Joined: Fri Jul 04, 2008 3:02 am
21 posts
• Page 1 of 2 • 1, 2
Who is online
Users browsing this forum: No registered users and 1 guest