Hi Guys,
I realized that I was not using State Events in my tracks and that was causing me to have a lot of extra code that wasn't required.
For example, if I wanted to toggle the 'Enabled' property of a data source, I would use a trigger, send that to a set value event, set a variable data source from 1 to 0, and then map this data source to the 'Enabled' property of the other Data Source.
I realized that this can be simply replaced by a State Event.
What I am wondering though is the limitations of the state event.
For example, I have a custom camera that I want to use as my game camera for a short duration of the track. If I set the 'Use as Game Camera' value ON, even if the camera itself is DISABLED, it will still use the camera as the game camera.
Since I can't map direct properties to state events, I had to use the long procedure above to toggle the game camera.
Is there anything I am missing here or are state events not quite as 'useful' as a set value > variable data source combination?
I made a camera follow my rider for a bit by setting it up as an object and using object position to make the camera follow the rider. It works the same as any other object.
The camera I am using is static, as in it doesn't move. I just want to switch to that camera on command (not on a range or anything) and then switch back after a time delay.
To do this, I need to turn the custom camera into the 'Game Camera' for a few seconds. However, the state event cannot enable the 'Game Camera' property, and even when the 'Enabled' property for the camera is OFF, the Camera will still be used as the game camera if the 'Use as Game Camera' property is on.
I guess in a more general sense I want to know if the State Event is as versatile as a [Set Value / Variable Source] combination.
You're looking for the camera event. Can be enabled and disabled with the state event
Use a trigger to send impulse (or interval trigger if you want it at a specific time?) that connects to camera event, which connects to the camera you want to 'enable' When you want it off, have a trigger state 'off' to the camera event.
Hope that helps
theirs an option for the camera to activate when the rider hits its range no need for any events,the range should do this, but my camera is limited, you might wanna rewatch the camera tutorial
I understand what the camera event is, but that's not necessarily what I am looking for.Originally Posted by Jarr3tt88
I want to switch the camera to be the GAME camera when I hit a trigger. Not just enable the camera, but make it the GAME cameran advanced camera settings).
If you have GAME camera enabled, but the camera itself is DISABLED, you are still stuck with that game camera at all times (this seems like it shouldn't be this way)
Therefore, with GAME camera permanently enabled, it doesn't matter what the state of the CAMERA is, as it will ALWAYS be used as the game camera.
You cannot use a State Event to toggle the GAME CAMERA property, so I feel like the state event isn't as useful as it could be. This is the purpose of my post. I feel that a simple Set Value Event tied to a Variable Data Source, that sets the source to a 1 or a 0, respectively, is far more useful than a state event. But I wanted to know if my findings were actually true or not.
I don't want the camera to be used at all when I am in it's range, so I set the range to 0. I simply want to switch to that camera on command, and then turn it off on command.Originally Posted by sparkierjonesz
I must not be clear with what I am trying to ask, sorry guys!
Thanks for the help though, I think I will still use set value events as they are extremely versatile and can be used to toggle any/every property of an item.
And why does it matter if its a game cam vs custom cam? Not seeing a difference...
The view would only 'cut' to the custom camera if the rider is in the 'range' of this camera.Originally Posted by Jarr3tt88
By setting the camera to be the game camera, it will cut to this camera instantly regardless of the range based on the data source that is mapped to this property.