anti-collision groups

[Versieon]

if they collided in a zdepth range, like 1-100, for A, 200-299 for b 400-499 for c and so on, it would be the same as collision groups just that you could keep going up by doubling the previous range as in 1,2,4,8,16,32,64,128,256...However that would create a problem for most scenes, so probobly not going to work

We just need to be able to keep doulbling the current range, like I said before, just with the CollideSet not zdepth
A=1
B=2
C=4
D=8
E=16
F=32
G=64
H=128
I=256
This would give more options, although I would like to be able to just type in a string into a custom collideSet and have Algodoo regard it as its own seperate entity, mabey puting comas in between.
For example: collide set A B and C as well as custom collideSet VAR1 would be writen ∙► (7,VAR1)

[RicH]

We weren't talking about making collideset have a zdepth range, we were talking about having zdepth as a method of collision grouping.

[Versieon]

same thing, more options. I just thought ahead to see if doing each zdepth as its own collision group would work, and it wouldn't, there for the ranges. Its pointless however, so i would go with the last part of the post.

[Chronos]

But Algodoo is a 2D simulator. That would make it seem like it's 2.5D or something. It's fine the way it is now.

[Rideg]

okey but double the amount a collision groups then.

[Versieon]

Yes, that is what I have been saying, I was just formulating how it could work with zdepths, but I don't like that either, thats why i said to go with the last part of the post.

We just need to be able to keep doulbling the current range, like I said before, just with the CollideSet not zdepth
A=1
B=2
C=4
D=8
E=16
F=32
G=64
H=128
I=256
This would give more options, although I would like to be able to just type in a string into a custom collideSet and have Algodoo regard it as its own seperate entity, mabey puting comas in between.
For example: collide set A B and C as well as custom collideSet VAR1 would be writen ∙► (7,VAR1)