Design forum
cancel
Showing results for 
Search instead for 
Did you mean: 

collision issue also

heathldesign
Enthusiast

hey everyone,

I think i know how collision priorities etc. work, but i still have trouble in certain cases. i have a wall that should collide with a slab and i think it should be automatic, but it's not. so i execute an SEO and it sort of works, but the drywall is not being cut by the structural element of the wall. the skin priorities are set to: Gypsum 300, wood structural 512, and plywood 620. the wood structural is not cutting the gypsum. i can't merge because it's a slab and wall.

and while we're at, it the round thing to the left is a morph and after the SEO there is no definition between it and the slab, even though they are different materials. it really should show as different distinct elements, but the slab must fit the form of the morph.


Screen Shot 2021-12-02 at 14.49.09.pngScreen Shot 2021-12-02 at 14.59.46.png

iMac 27" i7 4 Ghz osx 11.5.2

AC 25, 3002
1 ACCEPTED SOLUTION

Solution
JaseBee
Advocate

Layer intersection numbers need to be the same (and not both 0) for building materials to interact too.

 

Also SEO's don't take into account building material priorities, but merge and trim to roof ect. do.

AC 24 5004 AUS
iMac OSX (10.13.6) 4.2ghz i7
8gb ram/8gb vram

View solution in original post

3 REPLIES 3

Solution
JaseBee
Advocate

Layer intersection numbers need to be the same (and not both 0) for building materials to interact too.

 

Also SEO's don't take into account building material priorities, but merge and trim to roof ect. do.

AC 24 5004 AUS
iMac OSX (10.13.6) 4.2ghz i7
8gb ram/8gb vram

they are both set to 1 in all relevant layer combinations and i tried to trim to roof but it didn't do anything, i guess because the slab is not a roof :). i can't merge because it's a wall to slab. this isn't making a lot of sense to me since walls and slabs alway intersect some way, and the skins will need to collide in different ways. like in this case. pretty normal situation here.

iMac 27" i7 4 Ghz osx 11.5.2

AC 25, 3002

ah, wait. my bad. when the elements are on the actual layers you expect them to be on, then it works. it was the intersection numbers, had the walls on the wrong layer.

thanks muchly Jasebee

iMac 27" i7 4 Ghz osx 11.5.2

AC 25, 3002

Didn't find the answer? Start a new discussion

Labels

Still looking?

Browse more topics

Back to forum

See latest solutions

Accepted solutions

Start a new discussion!