Only part of a DataTable is read by an Actor

Development Programming & Scripting
1

I have a library of 14 different StaticMeshes and a DataTable which specifies which StaticMesh should be used when and how it should be transformed.

image
image1911×954 267 KB

This is the Blueprint ConstructionScript and…
image
image1920×825 33.4 KB

This is what I get.
Basically - it skips over a large portion of DataTable rows and only reads a few of them. (The elements which are placed, ARE placed correctly though).
The DataTable is clean - and well ordered. Just seems like the script “rushes” though the data tree and GET starts skipping elements.
Does anyone have an idea?

2

A bit of additional information:

data_table
data_table1536×1033 315 KB

Here’s the data table.

  • There are 80 rows in total.
  • 9 are being read, 71 - skipped over.
  • There is nothing special about the ones that are being read (they trend to be at the second part of the DataTable though)
3

Looks like you’re moving some meshes around a few times. You’re changing the location of one and the same object four times with the first four rows in your data table. ( … if I get your script right.)

Creating an Instanced Static Meshes of your indexed mesh + positioning that instance would be one way it could work?

2 Likes
4

Oh gotcha - thank you for the help!

01
012134×930 406 KB

with this - it works like a charm!
02
021024×827 129 KB

Now onto figuring out why for all these elements “complex collision as simple” stopped working…