Fixing Missing Textures in Source Engine Mods by Correcting VMT Paths
Learn how a simple case‑sensitivity mismatch in a .vmt file causes missing textures in Source Engine mods and how to fix it with mat_reloadallmaterials.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how a simple case‑sensitivity mismatch in a .vmt file causes missing textures in Source Engine mods and how to fix it with mat_reloadallmaterials.
Learn how to use the SourceEngine Scroll API for efficient deep pagination, see a complete curl‑based example, and understand the limits and common pitfalls to avoid resource leaks or stale data.
A laggy custom weapon in a Source mod usually isn't a weapon bug — it's a misunderstanding of prediction, interpolation, and lag compensation. Here's how the three systems fit together and how to write networked fire code that feels instant.
Learn how to prevent 'physics explosions' and instability in the Source Engine by managing collision meshes, mass ratios, and utilizing debug tools like phys_boxes.
Learn how to build, compile, and test a custom dynamic lighting material in the Source Engine 2013. Follow a concise step‑by‑step guide that covers shader files, material dictionary settings, hot‑reload, and in‑game verification.
Goal Maintain a Source engine server where players and administrators hold only the privileges they need, even as Steam authentication tickets expire and RCON credentials change. SteamAuth Ticket Refresh Steam-issued tickets expire after a configurable interval (≈24 h). The server accepts a ticket until the next map change, then prompts the client to re‑auth
The Source Engine utilizes a tick-based simulation where network updates are decoupled from internal physics steps. When transitioning server configurations from a 64-tick to a 128-tick environment, the increased frequency of world state snapshots alters the granularity of client-side prediction and server-side lag compensation. Because physics calculations
Source engine multiplayer clients acknowledge snapshot sequence numbers to keep state consistent. When a client acknowledges a snapshot older than the server's current baseline, the engine must decide whether to resend the full snapshot or apply a re-baselined delta against an older acknowledged baseline. The exact rule for handling baseline recovery when a