ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #sourceengine
Learn how to slash VVIS compile times and reduce runtime overdraw in the Source Engine by strategically converting decorative world brushes to func_detail.
Learn how to add per‑pixel normal maps to Source Engine models for richer lighting, with a step‑by‑step workflow, verification commands, and performance considerations.
Learn how to set up and verify model level‑of‑detail (LOD) in the Source Engine, understand its impact on frame rates, and avoid visual popping. A step‑by‑step guide with a QC example, trade‑offs, and practical checks for the game developer.
Source Engine's Entity I/O moves gameplay logic into map data via a string-based async event bus. Covers C++ declaration model, Hammer authoring, runtime dispatch, and debugging tools for typos, coercion bugs, and circular loops.
Players rubber-band but ping looks fine? Learn to read net_graph choke, loss, sv, and var on a Source engine server to isolate whether the cause is client rates, server tick instability, or the network path.
Learn how to pack Source Engine assets into a VPK, add it to gameinfo.txt, verify loading with the console path command, and recover if things go wrong.
Source Engine exposure changes belong in map logic, not client cvars. Use env_tonemap_controller and entity I/O for runtime brightness shifts that work in multiplayer.
Fix Source Engine map leaks with the pointfile, then cut VVIS compile time using func_detail, areaportals and hint brushes.
Explore how the Source Engine uses client-side prediction and server reconciliation to eliminate input lag while maintaining an authoritative server state.