

Rider parses each message in the same way it does for the Stack Trace Explorer feature. You might be used to log entries being a plain block of text in Unity, but Rider makes them interactive, and allows you to navigate to any source file, class, method or property mentioned in the log entry. Of course, Rider likes to go the extra mile. It will be updated as events are logged in Unity, and allows filtering based on category (error, warning or message). You can also show and hide events based on when they were logged – in play mode, or edit mode. This tool window, which is only available when we are connected to the Unity editor, brings Unity’s Console window right into Rider.

In this post, we’ll take a look at another new feature that will also help reduce the amount of time you spend switching between the Unity editor and Rider – the new Unity log viewer.

Public void OnButtonReleased(VirtualButtonAbstractBehaviour vb)ĭebug.Log("OnButtonReleased for " + vb.name ) / Called when the virtual button has just been released: Public void OnButtonPressed(VirtualButtonAbstractBehaviour vb)ĭebug.Log("OnButtonPressed for " + vb.name ) / Called when the virtual button has just been pressed: Public class SimpleVBEventHandler : MonoBehaviour, Replace the existing VB event handlers on the ImageTargets with this one, which you can customize.

You can then arrange the existing buttons as you need. I recommend that you start with the VB sample, import your own targets and replace the targets in the sample scene.
