Skip to end of metadata
Go to start of metadata

When you are playing the game and one of your responses does not work the way you planned it, you probably want to find out why. The signal history can help you with debugging the issue. This information is already partly covered in the step-by-step tutorial, but let's look into it in detail.

The signal history can be found in the Dynamic Response System (DRS) widget, under the Responses tab.

The Recent button (Pic1) shows you a list of all recently send signals. If your signal is not in this list, it would mean, that it was not sent at all, so the problem is in the game logic. When the list does not gets updated automatically, you need to press the Update button.

After you update the list, you should be able to find your misbehaving response, and select it.

You can view the current setup for the response in the middle of the widget, and you can directly edit it, and test it again by using the Send signal button (Pic3).

But we want to focus the Execution Info on the right side of the widget (of course this is only the default layout, you can rearrange it).

This widget displays the history for the selected signal(s) (you can use multi select to show more than one signal). At the very top, you can specify how many records you want to see in your list, for example, if you specify 1, you will only see the most recent response to the signal.

The below images describes the information that you can get out of this widget:

In this example below, all conditions for the response third time variation 1 and for the response third time variation 2 were met. So the system had to pick a random selection to start.

  • No labels