<?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/61c7a0a69ccc49b0aecb86a36ceaa84a&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/61c7a0a69ccc49b0aecb86a36ceaa84a-7f20fdf25662344b.gif</thumbnail_url><duration>415.417</duration><title>Day 16 - Crash-n-Clash - 02 Research</title><description>In this video, I walk you through the process of using coding filters to manage wall and pipe intersections in your projects. We start by gathering all pipes using the filtered element collector and then explore both quick and slow intersection filters, highlighting their differences and when to use each. I emphasize the importance of applying quick filters first to improve performance, especially in large projects. Additionally, I provide insights on how to create bounding boxes and outlines for filtering. Please take a look at the coding cheat sheet below to get started with today&apos;s tool.</description></oembed>