# pcg select attribute node loses properties

**URL:** <https://forums.unrealengine.com/t/pcg-select-attribute-node-loses-properties/2664406>\
**Category:** Programming & Scripting\
**Tags:** bug, unreal-engine, procedural, Blueprint\
**Created:** [October 11, 2025, 2:58pm UTC](https://forums.unrealengine.com/t/pcg-select-attribute-node-loses-properties/2664406 "2025-10-11T14:58:35Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aya\_Zyndoulain](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/aya_zyndoulain/32/1109715_2.png) [@Aya\_Zyndoulain](https://forums.unrealengine.com/u/Aya_Zyndoulain)\
**Post date:** [October 11, 2025, 2:58pm UTC](https://forums.unrealengine.com/t/pcg-select-attribute-node-loses-properties/2664406/1 "2025-10-11T14:58:36Z")

</div>

So i have a graph with a spline and an intersection. As you can see in

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/5/1/e/51e7fecd70aa2ce8feec23deae0957de1bef9d8d.png)

the intersection has all the properties needed so if i want the min and max point in position x to get the edge cases of this intersection it would make sense to use the select attribute node.

However

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/1/4/1/141a539459bfd697e556a51eeaba7b690c36d95e.png)

As you can see here the select node suddenly has lost all properties and therefore does not return anything causing the filter attribute that follows to bring everything back unfiltered.

to prove that the properties are vanishing from existence i did another test with the mathematical min node

 ![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/0/7/c/07cc7f9eda720cf01371dceb3d526747a302d2f9.png)

here it clearly tells that the inputs do not have those properties but as you can see in the first image the intersection node does have this property.

Is there a fix to this or does one know a workaround to this ? I would count this sort of behavior as a bug.

One thing i should mention is that this is a PCG graph inside of a blueprint and that the intersection is being generated by getting multiple world actors by tag (but even just taking the first one does not do anything)