Panda3d Collisions made simple

[MMichaud]

I dont think I am explaining my troubles correctly. I’m not a n00b when it comes to programming. I have know Python for 3 years now and know Java pretty extensively too. I’m only new to the 3D scene. I dont know how to edit the model files so that they are collision-able.

“heartCollider = heartModel.find(”**/collider_heart")"

where is it looking for “/collider_heart"? How do I give my models a "/collider_heart” (obviously without the “heart”)?

[astelix]

@MMichaud

I dont think I am explaining my troubles correctly. I’m not a n00b when it comes to programming. I have know Python for 3 years now and know Java pretty extensively too. I’m only new to the 3D scene. I dont know how to edit the model files so that they are collision-able.

“heartCollider = heartModel.find(”**/collider_heart")"

where is it looking for “/collider_heart"? How do I give my models a "/collider_heart” (obviously without the “heart”)?

no fear that when you said “newbie” I got indeed you’re just a panda3D newbie, not a newbie in everything
Anyhow, not getting what you’re asking for reveals you haven’t read or got the infos I provided in the models.blend file in the beginners package that cite:

=================
Settling the colliders
The logic view is the place where to ‘tag’ a mesh as collider, so select the heart collider ‘collider_heart’ from the outliner below and then select the logic panel to the lower left: you’ll see a property named ‘Collide’ with a string value of ‘Sphere descend’ - this is the way to make the panda3D loder know that this is a sphere-shaped collider. Look into the panda3D manual for more infos and to know how many other shapes [are] available.

so now I’m asking you: did you opened the models.blend file and read that? And if yes, what it is not clear to you there, so that I try to make it clear the better?

[MMichaud]

I did not open models.blend. How did you make the sphere in Blender?

Other than that last question I think I understand everything now. That was really the last piece of the puzzle. Thank you so much for you help I really appreciate it.

[astelix]

@MMichaud

I did not open models.blend. How did you make the sphere in Blender?

can’t help you out here fella, by lack of time - here you’re on you own - I assumed Blender knowledge in this tutorial so you gotta check the blender documentation on Blender’s website I guess. Keep up

[MMichaud]

Well I know how to make spheres, I’m not a moron. But how do you specify a certain object to being for collision purposes?

[astelix]

@MMichaud

Well I know how to make spheres, I’m not a moron. But how do you specify a certain object to being for collision purposes?

why do you assume I’m offending ppl like that? I’m here trying to help you not to making you see as a moron, but you are doing no effort to look otherwise. If you inquire me with:

I did not open models.blend. How did you make the sphere in Blender?

what do you think I understand off that sentence?
Then you said:

But how do you specify a certain object to being for collision purposes?

I already pointed you above. Can’t see how to be more clear than that. The last suggestion I can do above this topic is to read again more carefully the beginner step1.py and to look again inside the models.blend file with the same care and you’ll certainly succeed.
good luck

[Anon]

@MMichaud

Well I know how to make spheres

…

@MMichaud

How did you make the sphere in Blender?

Did you by any chance mean how to make a COLLISION sphere? Because what you wrote was a bit confusing.

@MMichaud

I did not open models.blend.

You should have, the text in the Text Editor view explained what you wanted.
Basically,

1. select your object (the sphere)
2. go to the Logic Panel (from Buttons Window):
   
3. 

If you want to set your object to be exported as a panda collision object, youll need to Add Property ,change the Types to String ,write ‘Collide’ as the name and on the left window from the Name window, add the parameters. I think you can change their order but write them separeted with spaces (no commas). ‘Sphere’ parameter tells the chicken exporter to export it as a sphere collision geometry, dont remember what ‘descend’ does , but the chicken manual found in the chicken archive explains that:

To append an object type or a tag to your object, simply go into the logic panel and use the Add Property button. A string property with the name ObjectType will be exported as the object type (which is shorthand notation for any egg syntax; the defaults are defined in your Confauto.prc file but you can define new ones if you like). A typical usage of this might be an ObjectType of barrier to export collision geometry. Alternativly a string property with the name Collide will be exported as a collide tag in the egg file, so an alternative to setting the ObjectType to barrier is to have a Collide tag with Polyset. Keep, Descend etc. can of course be used. Any other property will be exported as a normal Panda tag.

…okay, maybe it doesnt?..

The html doc can be found in bpydata/chicken/doc.html

[drozzy]

Haha! I found more resources! Great stuff. Should keep me busy for a while…

@MMichaud

Well I know how to make spheres, I’m not a moron. But how do you specify a certain object to being for collision purposes?

I think you should show more respect here. Otherwise you won’t get any questions answered.

[MMichaud]

I apologize for sounding disrespectful. I highly revere this dude, he has helped me more than I can say. I think I’m good for now. Thank you again for your help, you’re a saint.

[astelix]

@MMichaud

Thank you again for your help, you’re a saint.

haha that’s what my woman say every time she made something that needs to be forgiven, but that’s not your case MMichaud and you never sounded disrespectful to me. Just a little lazy to read manuals and comments, a very used habit by coders, especially young ones (like I was) - that’s what I tried to point you out so far.
keep up dude

[drozzy]

I have a question:
How come you don’t set any INTO or FROM flags in step0.py tutorial?

Is it because all objects are automatically assumed to be INTO, unless they are added to CollisionTraverser?

[drozzy]

Also I have a question, why is it that I get “name base is not defined” error if I do my imports like this:

import snipstuff
import direct.directbase.DirectStart

but it works if I do them the other way?

import direct.directbase.DirectStart
import snipstuff

EDIT: I think I figured this one out… DirectStart initializes a whole bunch of global variables (including base), and snipstuff accesses base - so it has to be imported after DirectStart.

[drozzy]

Also, in the traverseTask function, why do you need a for loop, it never runs more than one iteration:

def traverseTask(task=None):
  # as soon as a collison is detected, the collision queue handler will contain all the objects taking part in the collison
  for i in range(collisionHandler.getNumEntries()):
    # we'll turn on the lights, to visually show this happy event
    snipstuff.dlight.setColor((.5, .5, .5, 1))
    snipstuff.info_message("Smiley is now touching Frowney!")
    if task: return task.cont

  # If there are no collisions the collision queue will be empty so the program flow arrives here and we'll shut down the lights and clear the text message
  snipstuff.dlight.setColor((.0, .1, .0, 1))
  snipstuff.info_message("")
  if task: return task.cont

Can’t we just replace it with this?:

def traverseTask(task=None):
  if collisionHandler.getNumEntries() > 0:
    snipstuff.dlight.setColor((.5, .5, .5, 1))
    snipstuff.info_message("Smiley is now touching Frowney!")
  else:
    snipstuff.dlight.setColor((.0, .1, .0, 1))
    snipstuff.info_message("")

  if task: return task.cont

[astelix]

yo, cool down you submerged me with questions!
one thing at a time:

@drozzy

How come you don’t set any INTO or FROM flags in step0.py tutorial?
Is it because all objects are automatically assumed to be INTO, unless they are added to CollisionTraverser?

It is all wrote - citing line 50:

# ...and then we add it to the panda collision routines telling also that this is handled by the collision handler defined above. Afte issued this command the smiley become a true FROM collider object.
base.cTrav.addCollider(smileyCollider, collisionHandler)

and this is line 53:

#** This is the frowney model that will intereact with the smiley - it is shaped and settled exactly as smiley so there isn't much to say here, other than this time we won't add this object to the main traverser because we wanna assign to him just a INTO role.

I find not hard to admit my English is not awesome but: is it so bad or rather you guys really do not read what I wrote there?

About the second post yes you figured that alone correctly.

The third answer is obviously yes, but it is true just for that situation and that solution is off the logic of that routine. However you found indeed a piece of code screwed I must fix even if works right now, because may confuse ppl. To see a better CollisionHandlerQueue sample jump to step3.py

[drozzy]

Thanks for responses!

@astelix

It is all wrote - citing line 50:

# ...and then we add it to the panda collision routines telling also that this is handled by the collision handler defined above. Afte issued this command the smiley become a true FROM collider object.
base.cTrav.addCollider(smileyCollider, collisionHandler)

and this is line 53:

#** This is the frowney model that will intereact with the smiley - it is shaped and settled exactly as smiley so there isn't much to say here, other than this time we won't add this object to the main traverser because we wanna assign to him just a INTO role.

I find not hard to admit my English is not awesome but: is it so bad or rather you guys really do not read what I wrote there?

I guess the words “true FROM collider” confused me. I guess something like this would’ve been more clear:

# ...and then we add it to the panda collision routines telling also that this is handled by the collision handler defined above. After this command the smiley becomes a FROM collider object.

and:
Code:

#** This is the frowney model that will intereact with the smiley - it is shaped and settled exactly as smiley so there isn't much to say here, other than this time we won't add this object to the main traverser. This makes him an INTO object.

It’s just I was expecting you to set some kind of BIT masks here (like in some panda sample tutorials). But now I am more clear - all objects are INTO objects by default, and if you adding them as colliders, they also become FROM objects.

Thanks!

[astelix]

@drozzy

Thanks for responses!

you’re welcome

@drozzy

I guess the words “true FROM collider” confused me. I guess something like this would’ve been more clear…

suggestion taken and snippet fixed - keep pointing kinda discrepancies if you’ll find others (I bet you will )

@drozzy

It’s just I was expecting you to set some kind of BIT masks here

you’ll find bitmasks in following steps - go ahead, you passed the novice levels bigtime

[drozzy]

Well I’m on step5 of beginner and absolutely love it.
I can actually write collision from scratch now and understand how it works (more or LESS!)

Another minor point: Took me a while to figure out what “ASA” means. I assume it’s “as soon as”?
Maybe global find-and-replace of ASA with explicit wording will be nicer

Also I have a bone to pick with you over something completely silly! In the tutorial step4.py you say that you “slim” the code by pointing both accept calls to the same function:

def collideEventIn(entry):
  colliderNode = entry.getIntoNode()
  if colliderNode.getName() == 'smileycnode':
    smileyModel.setColor(1,1,1,1)
    heartModel.setScale(1.5)
  elif colliderNode.getName() == 'frowneycnode':
    frowneyModel.setColor(1,1,1,1)
    brkheartModel.setScale(1.5)
#... and this when they leave each other alone.
def collideEventOut(entry):
  colliderNode = entry.getIntoNode()
  if colliderNode.getName() == 'smileycnode':
    smileyModel.setColor(.4,.4,.4,1)
    heartModel.setScale(1.0)
  elif colliderNode.getName() == 'frowneycnode':
    frowneyModel.setColor(.4,.4,.4,1)
    brkheartModel.setScale(1.0)

However, when I did it myself, I pointed it to different functions and I had less lines of code

def heartCollisionEnter(event):
    smileyModel.setColor(1,1,1,1)
    heartModel.setScale(1.5)
def heartCollisionLeave(event):
    smileyModel.setColor(1,1,1,1)
    heartModel.setScale(1.5)
def brokenHeartCollisionEnter(event):
    smileyModel.setColor(1,1,1,1)
    heartModel.setScale(1.5)
def brokenHeartCollisionLeave(event):
    smileyModel.setColor(1,1,1,1)
    heartModel.setScale(1.5)

(Ignore the actual parameters).
But I think you should keep it pointing to the same function - because I actually didn’t know that you could do that. Maybe just remove the claim that it’s “to slim the code”.

Then again, this is really stupid thing, and I probably just need to sleeps more…

Thanks again for the tutorial.
Can’t believe this is not sticky!

[astelix]

@drozzy

Another minor point: Took me a while to figure out what “ASA” means. I assume it’s “as soon as”?
Maybe global find-and-replace of ASA with explicit wording will be nicer

that was put on purpose to keep your brain awake and working

@drozzy

Also I have a bone to pick with you over something completely silly! In the tutorial step4.py you say that you “slim” the code by pointing both accept calls to the same function:

But I think you should keep it pointing to the same function - because I actually didn’t know that you could do that. Maybe just remove the claim that it’s “to slim the code”.

Then again, this is really stupid thing, and I probably just need to sleeps more…

no that is neither silly nor stupid - seems you’re not the only one in need of more rest: you indeed catch another glitch and now it is fixed - I suggest you to download again the beginner package and see step4.py how looks now for you.

@drozzy

Can’t believe this is not sticky!

well I appreciate your endorsement but I guess as long as we keep finding these inconsistencies is better avoid it

keep up dude

[MMichaud]

Just as a suggestion: Maybe you should put some note in the documentation that says that models.blend has info about setting up the models so that they can be collision-able. I think that will help to point other super noobs in the right direction.

[drozzy]

I think that’s all in the tutorials. He says you should go dig around in models.blend file to understand how to setup your models correctly.

At least I figured it out
I guess you just can’t rush and have to read everything.

@MMichaud

Just as a suggestion: Maybe you should put some note in the documentation that says that models.blend has info about setting up the models so that they can be collision-able. I think that will help to point other super noobs in the right direction.