Alternative to the Camera Move | Forum

Alternative to the Camera Mover for incremental control over time

So far I've been using the camera mover to use analogue inputs (0-1 floats) to incrementally control values, whether its vectors or other scalars.

This is fine and I can continue but it would be great to find a more 'universal' way of doing so.

In UE for example I'd simply store my axis value in a variable on tick (or on held) and then add to that value every tick. I've tried something similar with the holder module in Aximmetry but it doesn't quite work the same way.

Is there a way to do this or should I stick with the camera mover for now?

Cookseyyyyy

Eifert@Aximmetry

Hi,

I am not exactly sure what kind of controller you are using or how you want to use it with the Camera Mover.

But I am guessing your problem is that there are is only one specific module in Aximmetry to store variables for the next tick (or frame). That module is called the Incremental module.

Also, you can do the following trick if the Incremental module is not good enough:

In this flow, the connection between the Copy Transformation and Transformation Concat 2 executed with values from the previous tick. Because in the previous tick the data got stuck in this connection, as the Transformation Concat 2 node were already executed once.

Warmest regards

Cookseyyyyy

Thanks Eifert. I did actually come up with something very simple. As long as the value I'm passing in is a -1 to 1 or 0 to 1 value that springs back to 0 (like a game controller) then it's easy enough to just use a holder and add the held value to itself over time. You can easily reset it by feeding it a triggered value of Zero too...

Cookseyyyyy

This functions a bit like the zoom control data on the Camera mover except it's standalone.

Alternative to the Camera Mover for incremental control over time

Cookie consent