Search Home Members Contacts
About Us
Products
Downloads
Community
Support
Pages: [1]
  Print  
Author Topic: Collision Detection  (Read 3913 times)
anwserman
Customers
Community Member
*****
Posts: 1095


« on: December 07, 2002, 12:20:55 AM »

I now this was in a previous post on the old forum by crrrazydan, but I have a question:  For some odd reason, after abandoning my project for a week or so (playing too much Phantasy Star Online on the Dreamcast mind you  :lol:) I started to run the project again and I was able to go through walls in my BSP file that I wasn't able to do so before - serious bug!  Crrrazydan said that if you have a slow FPS on your system and if you use time-elapsed code this could happen as you might move from point A - B without so much touching the wall, allowing you to go through it. Is there anyway one can fix this bug, and could you post how so?  Getting a new graphics card isn't an option since this card is 'new' towards me.  Hmmm...

-Jeff
Logged

Temp sig, this is a temp sig.
Smiley
bbence
Customers
Community Member
*****
Posts: 944


WWW
« Reply #1 on: December 07, 2002, 03:44:19 AM »

What kind of collosion are you using?
Logged
anwserman
Customers
Community Member
*****
Posts: 1095


« Reply #2 on: December 07, 2002, 11:56:38 AM »

Right now I'm using BSP detectcollision but once the Actor2 probs are gone (unloading the object, along with improved collision detection) I want to move to that.

-Jeff
Logged

Temp sig, this is a temp sig.
Smiley
JohnnyC
Customers
Community Member
*****
Posts: 1488


WWW
« Reply #3 on: December 07, 2002, 12:04:03 PM »

#1 anyone still using tv.timeelapsed - after 1002 posts about this  :twisted:

Use tv.accuratetimeelapsed.

#2 A lot of collision fixes are in rc3  Cheesy
Logged

_________________

John Chewter
Keyne Image
www.keyneimage.co.uk
bbence
Customers
Community Member
*****
Posts: 944


WWW
« Reply #4 on: December 07, 2002, 12:04:52 PM »

Could you post your code maybe? I'm not having the artifact you mentioned. I used to have it but in RCx it's not present. What version are you using by the way? Also I wouldn't suggest using just Actor2-BSP collosion alone if you're using BSP. The BSP built in collosion functions (SlidingCollision, DetectSphereCollision) are much more sophisticated I think. So I advise that you use those.
Have you tried without timeelapsed and substitue it with a value, say 10?
Logged
MP51C
Community Member
*
Posts: 100


« Reply #5 on: December 07, 2002, 12:24:51 PM »

bsp's detectcollision function is VERY slow, collision detection in the scene object is much faster (i found this out the hard way  Tongue )
Logged
bbence
Customers
Community Member
*****
Posts: 944


WWW
« Reply #6 on: December 07, 2002, 12:42:01 PM »

Quote from: "MP51C"
bsp's detectcollision function is VERY slow, collision detection in the scene object is much faster (i found this out the hard way  Tongue )


Is it? And again, it's harder to incorporate a SlidingCollosion just with the scene collosion methods. Just my 2 cents.
Logged
anwserman
Customers
Community Member
*****
Posts: 1095


« Reply #7 on: December 07, 2002, 08:22:23 PM »

Heh another battle goin over collision detection. Oh, my code sample is essentially EXACTLY the same that is in the BSP tutorial that is in the RC2 download directory - i've based my code off of my sample and added, removed parts etc etc.  Anyways,  I'm just wondering.  I've heard many times that the collision detection in RC2 was quite shoddy and RC3 is gonna be the bomb compared to RC2.  So, I'm just quietly waiting for the next download/release of TV.  I'm pumped, stoked etc etc.

Oh, did you know that the game Illbleed, the one on the Dreamcast that I'm making my own version of, is going to be released for XBox?  Its so cool!  I'm really happy.  If you own an Xbox, buy it but I'm not sure when i'd be released.  But I'm happy since I own an XBox!  (Along with my dreamcast, gamecube, genesis, nintendo and gameboy advance - wow I'm a social hermit!  :shock: )

-Jeff
Logged

Temp sig, this is a temp sig.
Smiley
bbence
Customers
Community Member
*****
Posts: 944


WWW
« Reply #8 on: December 08, 2002, 04:15:17 AM »

Quote from: "anwserman"
I've heard many times that the collision detection in RC2 was quite shoddy and RC3 is gonna be the bomb compared to RC2.  So, I'm just quietly waiting for the next download/release of TV.  I'm pumped, stoked etc etc.


You bet! Anyhow as far as I know they haven't changed the BSP collosion detection stuff cos it's working good. Please prove me wrong on that one if it's fudge. Smiley But they've created a new universal collosion detection method useable for pretty much everything.
Logged
MP51C
Community Member
*
Posts: 100


« Reply #9 on: December 08, 2002, 09:40:34 AM »

i'm pretty sure sylvain looked over all collision code again (including bsp), and probably did some rewrites as well  :wink:
Logged
JohnnyC
Customers
Community Member
*****
Posts: 1488


WWW
« Reply #10 on: December 08, 2002, 09:41:31 AM »

Well - just wait for RC3  :wink:
Logged

_________________

John Chewter
Keyne Image
www.keyneimage.co.uk
SylvainTV
Administrator
Community Member
*****
Posts: 4946


WWW
« Reply #11 on: December 08, 2002, 02:19:23 PM »

Yeah, unfortunately it's the best thing to do Smiley
Logged

Regards

Sylvain Dupont
TrueVision3D Developer
sylvain@truevision3d.com

TV3D IRC at http://chat.truevision3d.com or on server irc.truevision3d.com #Truevision3D. Come talk with us !
anwserman
Customers
Community Member
*****
Posts: 1095


« Reply #12 on: December 08, 2002, 03:12:11 PM »

Heh proving bbence wrong or waiting for RC3? Cheesy  (Sorry just had to!)  Though I must say I am really looking forward to RC3!

-Jeff
Logged

Temp sig, this is a temp sig.
Smiley
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.3 | SMF © 2006-2007, Simple Machines LLC
Seo4Smf v0.2 © Webmaster's Talks