Spectator Displays are highly configurable. They are configured through a series of JSON formatted files known as View Definitions, View Configurations, and Event Assignments.
The first step in understanding how a Spectator Display may be configured is to understand Display Events. A Display Event is a specific point of time during a COURSE OF FIRE. For example the start of sighters, the end of sighters, the start of qualification, the end of qualifications, and many more. There are over 50 different defined Display Events. A typical COURSE OF FIRE range script will only use a subset of the defined Display Events, usually only 10 to 20.
When a Display Event occurs, that triggers the Spectator Display to (potentially) change what it shows on screen. The "what" a Spectator Display shows is formally known as a View Configuration. Each Display Event is mapped to one View Configuration, this is knows as the Event Assignments.
A View Configuration in turn lists one or more View Definitions to show. A View Definition lists specific Display Entities. A Display Entity are things like ranked list of athletes, athlete scores, or images to show on the Spectator Display. A Display Entity then has it's own set of configurations.
A View Definition defines a screen that is displayed by a Spectator Display at one moment in time. It defines the Display Entity to show, the Display Entity's configuration, and options to show or hide the top and bottom strip.
A View Configuration defines a series (1 or more) View Definitions to load into the Spectator Display along with optional Marquee Messages (the bottom strip). There is usually one View Configuration for each segment of a match.
Event Assignment mappings can be configured through the Display Configuration Form dialogue.
Orion users are able, and encouraged to write their own View Definition, View Configuration, and Event Assignment files. These are stored in sub-directories under My Matches/DATABASE/Display.
Any file that is starts with the name "Athena" is a default file that comes with Orion. Customers should not edit these files as they may be overwritten in newer versions of Orion. Instead customers should compose their own files.
Shooter's Technology is unable to provide customers support to author their own View Definition, View Configuration, and Event Assignment files. Shooter's Technology however does warrant that Spectator Displays will behave according to this documentation when the files are written correctly.