Hi there, making a new discussion for this incase anyone else comes across it. Using the 2D first person asset, I'm wondering if its possible to use variables to change the sprite but not the camera... For instance, say if the player places down an item in a scene, I would like it to show a new rendered sprite using a variable (so if the player places down an item in the "north" view, using variables that rendered image is now switched out for a different image). The issue is that the camera seems to be linked to the sprite because it's parented to it, so I'm trying to wrap my head around disabling the visibility of just the sprite without also disabling the camera parented to it. If this is possible, let me know, or else I will try to find a work around... Thanks!!
It looks like you're new here. If you want to get involved, click one of these buttons!
Comments
You'd need to place another sprite over the original one, and give it an Order In Layer that's higher so that it is drawn on top. The Object: Visibility Action can be used to hide/show it at runtime.
Chris-Thanks so much!
I was also having an issue where the navigation nodes are present at all times, even when I have other menu screens popped up or there's no direction to go in (so if there's only North and South and not East and West). I'm not sure how to to turn it off since the navigation is on during gameplay, and it is still showing even when the game is technically paused (or the action causes the game to pause)
The Menu container for the directional buttons is called Navigation - by default, it's set to show automatically during gameplay. You can use the Menu: Change state Action's Lock Menu command to prevent it from showing.
The arrows themselves don't represent compass directions, however - they're relative to the player's "view". Forward, back and reverse are shown dynamically (i.e. based on what movement can occur), but it's assumed that the player can always turn left and right, so those arrows are always shown.
The code that handles all this, however, lies in the template's CameraNode2D script - you can make changes to it that suit your project without affecting AC itself.