Debugging
Vigil's task flow can be output to the output log using:
Log LogVigil Verbose
Log LogVigil VeryVerbose
Learn how to use the output log to debug Vigil
You can draw Vigil results to the screen using Vigil Draw Debug Results
Learn what the indicator information means here
Tip
You can see these in action here
All Vigil commands are prefixed with p.Vigil so let auto-complete show you what is available
p.Vigil.Selection.Debug draws the shape, by default a Cone, that shows the traces used to find our targets
p.Vigil.Filter.Debug draws the trace, by default a Line, that shows the traces used to filter our Line of Sight
p.Vigil.Scan.Debug simply prints the last number of targeting requests sent to the targeting subsystem to the top-left corner of the screen
Important
Visual Logger is a powerful tool that allows us to rewind events over a timeline
Both server and client information is displayed on separate tracks in the Visual Logger
Visual Logger is the best way of detecting discrepancy between Server and Client
Any prediction issues you are encountering with Vigil should be diagnosed this way
To print Vigil data to the Visual Logger, run this very familiar yet different node Vigil Add Visual Logger Results from your Event OnVigilTargetsReady
Open the Visual Logger:
Play-In-Editor and hit the Start button. Ensure the Vigil [VV] option is enabled or you won't see the results.
And now, simply play, focus on things. Notice the Visual Logger tracks filling with data. When you have enough data click Stop.
Now you can scrub back and forth through the Visual Logger track to see what Vigil did and when, for both the client and server.
