---

I've had this sitting around for a while now, with the posibility of including it as core commands in DBPro.

But in order to preserve legacy code, and avoid the complexity of adding it in, it's being released as a seperate TPC DLL.

DLL: SC_Collision v2.05 (DBPro version)

DarkGDK: SC_Collision v2.05c (GDK Version)

+ Code Snippet

Previous versions:

http://sparky152.homestead.com/files/DBPCollisions_v2.02.zip
http://sparky152.homestead.com/files/DBPCollisions_v2.0.zip
http://sparky152.homestead.com/files/DBPCollisions_v1.08b.zip

Edit: Updated the terrain demo for v2: http://sparky152.homestead.com/files/TerrainDemo_v2.zip

Main new features are sphere casting/sliding, and an object collision(a,b) replacement.

---

Wow
Nice job Sparky

Actually, it would be great if there is a command that gives you the possibility to make everything collidable within a specified object number range.
So i.e. if you have your player which is object 10 and your level which are objects 1000 to 5000, there should be a command like:
do_collision(10,1000,5000) or something like that
Pretty handy, and also to avoid the 'need help with collision' threads.

---

Yeah this is a pretty cool system. I've been waiting a while for it to be released. It's probably better off released like this instead of integrated into DBP anyway. Something was bound to get screwed up on integration.

---

I've only just started using v1 of your collision system and I was impressed with its simplicity.

V1 Is Dead! Long Live V2!

---

Lean, clean and powerful. Nice work again man.

---

I love the ability to update the object's state when I want to, instead of it auto updating all of them. NGC has just provided this functionality as well. I have been using Sparky's v2 for a bit now and love it except it uses sphere casting instead of ellips. You can make a work around for that in most cases though This is a really great system, especially since it is free.

---

That's really awesome, but I get an error( "Could not understand command" ) at this line(33):

setupTerrainCollision 1,1,2

In the terrain example. Otherwise, this looks really cool. Nice job!

---

Now that's impressive - the old system had an average of 1ms per cast. Can't imagine how fast it is now Sphere casting looks interesting as well...

---

My mistake, uploaded the wrong terrain demo version. Clear your browser cache and it should work now. The only real difference in the new terrain demo is the commands are now prefixed by 'sc_' hence the error!

Thanks for the comments.


Edit:


The real speed comes from the binary tree structure, but there are always optimizations to be found in the surrounding code

---

HOLY COW! Just tried out the demos. This baby is frikkin' impressive... and the sliding collision is suheeeeeet.

Have a pwngiun on the house

---

When I try to compile I get an error "Subscript must be integer or dword when referencing an array at line 154". This is the Multiple Intersect Demo that I'm doing.

I did put the dll in the plugins-user directory.

---

The dll looks like it's been recognised, otherwise you would have got errors about commands higher up.

What version of DBPro are you using?

---

I should point out that when I start any of the demos, I get a
message. The proggy still runs fine, but it does spit that out every time...

---

This will happen if you have both the old Collision.dll and the new SC_Collision.dll in the plugins-user folder, although not a problem deleting the old one should remove this message.

---

At the risk of sounding like an idiot. Is this dll usable with the DGDK?

---

How silly of me. I thought I had already removed the old version before installing the new one Got rid of the old one and it works swimmingly.

---

Nope, once the DGDK has VS2005 support I'll see if I can find time to look at this.

---

I'm using u6b3. I still have the old collision dll in the plugins directory. Could they be interfering? I wouldn't think so, since the commands names are different.

---

I've tested with 5.9 and u6b3, both work fine here.


That sounds like a compiler issue, the line points to a command not an array. Either it's not recognising that command for some reason or it's reporting the wrong line.

Anyone else having this problem?

---

You have to delete the old dll from the plugins-user folder.

---

This would happen if the DLL wasn't in the right place, and it would be giving this error on a line that you try to return a value from a command.

---

Nope works perfectly here (DBP 5.9).

[edit] All of the demos work here.

---

I removed the old dll from the plugins directory. It works now. My only
problem is that my project needs the old one. I will probobly not be able to use this until I finish it.

---

Why not? You can use very easily convert it over. The old commands are in the new one with extra parameters. Won't take you 5mins to change over.

---

Shouldn't this be, like, stickied or something...?

---

Thought not. Ok.
Preemptive thanks for giving it a look later on.

---

So, anything about that terrain error?

Just to spare you the trouble of finding my other post:

---

And I'll spare you the trouble of finding mine

---

Do these commands replace the inbuilt DarkBASIC collision commands?
I wasn't sure about this with the first version!

---

The do not overwrite them, if that is what you mean.

But SC_ObjectCollision() and SC_IntersectObject() do provide similar functionality to their DBPro commands.

---

lol

I meant are they better then the in-built ones. and easier!

---

The built in commands don't even work properly, at least in u5.9. They're going to be fixed in u6, but no way will they match this baby in speed

---

Sparky, I <EDIT> re-downloaded </EDIT> this the 25th or so. Shouldn't that be the fixed version?

---

Yes it should, I've renamed the file (to TerrainDemo_v2.zip) so it should definately work now. I suspect it was being cached somewhere.

---

Why doesn't TGC use your collision DLL to replace their own, Sparky?

---

Because they would have to go through the trouble to integrate it. And then it would be too fast.

Besides alot of stuff would get borked on the integration. I'm just glad to finally have it to use publicly

Great Job.

---

Perfect sparky!!


Yeah that would speed programs too maybe, depending on how the command is coded within the dll.

Maybe you can think about making a function like essence said?

---

EDIT: Lol wrong thread, anyway great collision sparky!

---

It's not something I want to look into, it would be a lot of work to make such a general command especially for a free dll!

But you should now have the speed and commands to implement a collision system specific to your needs.

---

Sparky has taken care of the integration, though. There would be legacy command concerns, but if Sparky modified his own plug-in for the commands to match, I doubt there would be any problems.

It would have been perfect for v6, as they're modifying the core 3D dll anyway. It would have been solid, fast, and would work. Sparky's done all the work already.

@Essence -
Just assign object 1000-5000 to a collision group. Then, run collision against that group. That's exactly what you're looking for, and the good Sparky has taken care of it for us.

Of course, such a function would be really simple do code yourself, if you don't like groups for some reason. It would just iterate between the bounds and perform collision checks. But I promise, groups are great.