I believe there's gonna be some more information coming about the new features in the editor that wasn't covered in the previous tutorials, after the game has been launched on all platforms. In a nutshell the object array (Objekt-liste) can be used to target objects using the object getter (objekt-holer) by picking objects into the array, picking the desired array into the object getter and using the index number in the getter (objects in the array have the index number inside them when picked in array). Now events can target at the object getter which redirects the event to a certain object in the index. Object pointer(objekt-zeiger) is quite the same but is for more simple tasks, can be nested and targeted to all objects at once.
If you're changing them all from the same one colour to the same different colour, it seems like you'd be better off just tying them all to one single vector that you change.Originally Posted by nannerdw Go to original post
If they are all a multitude of colours being changed into a multitude of different colours I can't see how the arrays would be used then either, at least not to change them all at the exact same time as you say you want to, you'd be rotating through objects in the array then changing the vector, rotating, changing the vector, rotating, changing etc.
That means that each change would require at least one tick gap before moving to the next section in the array, meaning it wouldn't be an instant all at one change. In that situation I'd use a single vector for each group of objects that are performing the same colour change and just set the vectors all at the same time, unless I'm misunderstanding what you're trying to do.
I'm changing each individual object to a different color. When I tried it in Evo, I was able to run the code loop just fast enough to color about 25 objects per clock tick. That was too slow, so I changed it to 75 individual vector data sources holding the color values. It took forever to set up, but it ran almost instantaneously.
So you have 75 objects all of varying colours, each one being changed to a different colour, and none of the objects are the same colour as another and/or being changed to the same colour as another?
If that's the case then an array probably won't help as if I properly understand how the array and getter work, you'd still need 75 vectors and 75 object getters getting each object from the array for each vector to tie into so you may as well just tie the vectors directly to the objects and skip the array.
Coloring 75 objects with color event continuously is generally not a good idea because it'll increase the dynamic modifications count. It's better to have a color vector for each object, BUT you can point the object pointer at the vectors instead and use the copy vector event for example.
Here's a rough example of coloring 10 blocks (with the same colors in this case) each tick using the object pointer and copy vector event.
![]()