Embedded Files
Tester Settings
These settings control testing operations, both from the Tester panel and depot testers. These testers are piloted or drones that are spawned to evaluate the quality of existing volumes.
They do not impact quick-tests triggered from the toolbar or when generating.
Multi Volume Test
Typically a tester from the Test panel is checking to see if any volume of the current class covers every detected area, or in the case of depots if the depot's volume covers all the detected areas. They're designed to ensure the volume encapsulates the space.
Often, the volumes you're making must be exclusive to the area, i.e. they don't bleed into adjacent rooms. An example could be a gameplay volume that says 'when you enter this room, trigger an alarm'. Obviously you wouldn't want that volume to bleed into the next room or the alarm would trigger early or break gameplay logic.
In cases where volumes must be exclusive it can be helpful to know if a volume overlaps with another of the same class.
By enabling the Multi-Volume Test, then testers will show you locations where a volume overlaps with another volume of the same class.
Multi volume warnings show up as a separate sprite (two boxes with a line through one), and the log info is updated state how many were detected. On depots, the depot text is also updated to include this info too.
Above we can see two volumes that are overlapping as the one on the left has been set to convex. This means in a section of the room on the right, the volumes overlap.
This is an obvious case but often it can be hard to know when this is happening
After running a Testing drone with 'Multi Volume Test' enabled, you can clearly see multi-volume sprites have been added to show where the volumes overlap.
This can be helpful to discover volume issues in busy maps with complex geometry
With multi volume tests enabled, the log includes info on the amount of multi-volume warnings found
Depots tests show the number of multi-volume warnings
While the main Report in the toolbar can't carry out full multi-volume tests, they do carry out a simpler intersection test that can tell you if a volume is overlapping with any other volume of the same class that's also being reported on.
Above we see a report generated on both the above volumes, we can see that they're both showing as intersecting with something (obviously it's each other in this case!)
It's important to note that multi-volume testing requires considerably more CPU while testing, as every volume in the map is tested for overlaps each scan. This is why it's disabled by default. It's usually not a huge issue, and of course all this work is editor-only anyway, but usually multi-volume testing is something you'd want to opt-in to, so the default is off.
Also, volumator takes no actions when multi-volume warnings are detected, they don't impact Validation or depot rebuilds. This is because the appropriate action to take is highly context dependent, so it's best handled by the user.
If you do want to cut away the overlap, there is a Subtract Volume tool in the Edit panel. This will allow you to subtract one volume's shape from another.
Max Warnings and Errors
These are thresholds that will cause the testers to auto-stop if they detect too many issues.
This is designed to ensure the system doesn't get overwhelmed with seriously broken volumes. In cases where you have, say, 200 warnings, it's usually safe to say that the volume is bad and detecting more warnings isn't going to help much!
Obviously you'll want to take into account the volume size when determining this, but it's main job is just to finish up early when things are super bad.
Google Sites
Report abuse