<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/8f972cf4f9504d0f97dc83909a99086d&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/8f972cf4f9504d0f97dc83909a99086d-c03a4e6481025add.gif</thumbnail_url><duration>788.875</duration><title>Day 16 - Crash-n-Clash - 03 - Code</title><description>In this video, I walk you through the process of creating a proof of concept for the Crash and Clash tool, focusing on detecting intersections between pipes and walls. We start with a simple project setup, using a filtered element collector to get our pipes and then applying an intersection filter to identify any clashes. I also demonstrate how to adapt the tool for different categories, like floors, to ensure versatility. I encourage you to test this with various elements and scenarios to see how it performs. Please make sure to follow along and implement the changes as we go!</description></oembed>