I have a button to siphon through an array of cameras and I am trying to make a reverse button for the index but the button with the reverse node acts erratically when pressed, either just going to the next camera like the other button without the reverse node, or not doing anything at all. The “back” button works just fine but when I try to add the reverse node or use a subtract one, it wigs out and doesn’t work right.
Why not just use the index of the array of the cameras?
Use an int for the current camera and wrap it to the amount of cameras.
One button increases the index, the other decreases, finally wrap index to keep in the array bounds.
Isn’t that what this is doing in the event graph? I use the “GET” node to grab the array and use the index to go through it one by one, though I would prefer to be able to select each camera individually, as I think that would be a more user friendly method.
It’s changing the order on every reverse: index 1 would be the second camera but when reversed and moving 1 left it would select the last camera, not the first one.
For the index to wrap around going left do this: (index - 1 + Length) % Length. No need to reverse the array.