S&box Wiki
Home
/
Edit VIS Optimizations
View
Edit
History
No Category
Developer Overview
The Project System
Publishing To Asset Party
Getting Started With Hammer
Mapping Basics
Mapping Entities
Advanced Mapping Techniques
Getting Started with Modeldoc
Animgraph & Animation
Physics
Modeldoc Nodes
Advanced Modelling
UI Basics
Styles & Stylesheets
Razor Templates
Game Menus
Materials
Built In Shaders
Shaders
Shader Reference
Sounds & Audio
Particles
Getting Started
Learning C#
Making Games
Players
Entities
The Scene System
Physics
Rendering
Camera
Networking
Input
VR
Editor & Tools
Misc
Playing Guides
Console Commands & Variables
Dedicated Server
Preview
Log in to edit
VIS Optimizations
<cat>Hammer.Advanced</cat> <title>VIS Optimizations</title> # What is VIS? VIS is Visibility for short. It's important for your map to calculate visibility of stuff you can see or cannot see. It's not always great when a computer does it, so there are a few entities that may further optimize your map when utilizing them. #Useful Entities `visibility_hint` is a point entity, you can use this to mark an area as **"low-resolution"** or **"high-resolution"** for VIS calculations. **Low-res** would be suitable for large outdoor areas with wide lines of sight. **High-res** is automatically used for inside places in your map (if your outside environment is marked with low resolution hints) `info_visibility_box` is a point entity that is a **visibility culling box** which can be used to hide objects at runtime and can be toggled on and off by the entity Input/Output system. Mainly used to cull stuff that's within the PVS, but is in an area of the map that the player won't see. `info_cull_triangles` is a point entity that is used to prevent **overdraw** from props/geometry sticking outside the regular map boundaries. You surround an area of the map that has props sticking out (which is usually **out of bounds**) with an `info_cull_triangles` box. I hope this cleans up the poor documented nature of these entities. Use them for your own maps when optimization is your priority.
S&box Wiki
Development
Developer Overview
5
General FAQ
System Requirements
The Developer Preview
The Editor Overview
The s&box wiki
The Project System
3
Getting Started - Your First Project
Managing Assets (Importing and Creation)
Project Types
Publishing To Asset Party
2
Creating and uploading projects
Uploading assets
Hammer
Getting Started With Hammer
4
Creating a Door
Creating your first gm_flatgrass
Getting Started With Hammer
Mapping Resources
Mapping Basics
1
Tools Visualisation Modes
Mapping Entities
1
Light Entities
Advanced Mapping Techniques
6
Collaborating With Prefabs and Git
Instances
Prefabs
Quixel Bridge Plugin
Tilesets
VIS Optimizations
Models & Animation
Getting Started with Modeldoc
5
Breakpieces
Guide to Models
Importing Rust Weapons
LODs
ModelDoc FAQ & best practices
Animgraph & Animation
3
Animations without Animgraph
AnimEvents, AnimGraph Tags, Attachments
Animgraph
Physics
3
Cloth Physics
Collisions, Physics & Surface Types
Jiggle Bones
Modeldoc Nodes
1
Custom ModelDoc nodes
Advanced Modelling
6
Bodygroups
Citizen
First Person
IKChains and Stride Retargeting
Morphs
Vertex Normals
User Interface
UI Basics
7
Custom Fonts
Embedding Websites
Enabling Pointer Events
Events and Input
Localization
UI Basics
World UI
Styles & Stylesheets
2
Custom Style Properties
Supported Style Properties
Razor Templates
3
A Razor Overview
Generic Components
Templates
Game Menus
1
Creating A Game Menu
Materials & Shaders
Materials
5
Guide to Materials
Material Attributes
Material Resources
Texture Settings
Using Dynamic Expressions
Built In Shaders
2
Foliage Shader
Glass Shader
Shaders
4
Compute Shaders
Constant Buffers
Material API
Shading Model
Shader Reference
3
Anatomy of Shader Files
Shader Reference
Shader States
Other Assets
Sounds & Audio
3
Guide to Sounds
Sound Events
Soundscapes
Particles
5
Creating animated sprites
Creating your first particle effect
Understanding Particle Editor
Using custom sprites
Using particle systems from C#
Coding
Getting Started
9
C# Learning Resources
Cheat Sheet
Debugging
Event System
FileSystem
Overview
Setting up Rider
Setting up Visual Studio
Setting up Visual Studio Code
Learning C#
1
Threaded Tasks
Making Games
4
Making a Simple AI
Running Multiple Instances of the Game
The Game Loop
Traces
Players
5
Bots
Clothing
Pawn
Pawn Input
Voice
Entities
7
Entities
Entity Components
Entity Prefabs
Entity Tags
Map Placeable Entities
RenderEntity
Usable Entities
The Scene System
1
The Scene System
Physics
2
Custom Physics on a ModelEntity
Hitboxes
Rendering
2
Render Tags
RenderHooks
Camera
1
Camera
Networking
9
Commands
Http Requests
Lag Compensation
Network Callbacks
Networked Types
Networking Basics
Prediction
RPCs
Websockets
Input
3
Input Glyphs
Input System
Speech Recognition
VR
2
VR Input
VR Overlays
Editor & Tools
4
Custom Asset Types
Hammer API
Hammer Gizmos
Hotload Performance
Misc
11
Backend API
ClientData ConVars
Code Accesslist
CPU Performance Profiling
DisplayInfo
Launch Arguments
Mounting assets at runtime
package/find
Precaching
Saved Games
TypeLibrary
Playing
Playing Guides
2
Default Keybinds
Proton
Console Commands & Variables
0
Dedicated Server
1
Dedicated Servers