# Preview 1 LWC update removed UFUNCTION support for TArray of FVector3f, FVector2f

**URL:** <https://forums.unrealengine.com/t/preview-1-lwc-update-removed-ufunction-support-for-tarray-of-fvector3f-fvector2f/502801>\
**Category:** Blueprint\
**Tags:** ufunction, unreal-engine, UE5-0, Blueprint\
**Created:** [February 28, 2022, 12:22pm UTC](https://forums.unrealengine.com/t/preview-1-lwc-update-removed-ufunction-support-for-tarray-of-fvector3f-fvector2f/502801 "2022-02-28T12:22:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![The\_Regurgitator](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/the_regurgitator/32/710746_2.png) [@The\_Regurgitator](https://forums.unrealengine.com/u/The_Regurgitator)\
**Post date:** [February 28, 2022, 12:22pm UTC](https://forums.unrealengine.com/t/preview-1-lwc-update-removed-ufunction-support-for-tarray-of-fvector3f-fvector2f/502801/1 "2022-02-28T12:22:55Z")

</div>

I am working on updating the Runtime Mesh Component plugin for UE5. This plugin works with mesh data buffers, and many of its blueprintable functions use `TArray<FVector>` and `TArray<FVector2D>`. These buffers are internally 32-bit floats, which matched the internal representation of the `FVector` types pre-LWC.

With LWC, there is a significant overhead introduced in `UFUNCTION`s that need to use `TArray<FVector3f>` internally, because only (default double-precision) `FVector` is supported as a function argument and conversion is required. Maybe there should be Blueprint support for single-precision floating point types to improve performance and memory footprint?

---

<div class="post-metadata">

**Author:** ![Starkium](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/starkium/32/1194588_2.png) [@Starkium](https://forums.unrealengine.com/u/Starkium)\
**Post date:** [April 8, 2022, 3:06pm UTC](https://forums.unrealengine.com/t/preview-1-lwc-update-removed-ufunction-support-for-tarray-of-fvector3f-fvector2f/502801/2 "2022-04-08T15:06:56Z")

</div>

`TArray<FVector2f>` isn’t blueprintable, I’m over here trying to figure what to replace that with. `TArray<FBox>` maybe? This is meant to house the data from UV’s. Like why the heck is a `TArray<FVector3f>` blueprint supported and a 2f isn’t?

I’m attempting to port over the vertex animation toolset plugin

---

<div class="post-metadata">

**Author:** ![The\_Regurgitator](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/the_regurgitator/32/710746_2.png) [@The\_Regurgitator](https://forums.unrealengine.com/u/The_Regurgitator)\
**Post date:** [April 15, 2022, 1:48pm UTC](https://forums.unrealengine.com/t/preview-1-lwc-update-removed-ufunction-support-for-tarray-of-fvector3f-fvector2f/502801/3 "2022-04-15T13:48:16Z")

</div>

Hmm it seems full release UE5 may have changed the behavior compared to EA / Preview 1 / Preview 2?