Lag Debug UI
Tired of seeing players rubber band? Yeah well me too, so we made this tool to help expose the main causes of the lag plaguing this game. You can repack this mod. Here's an explanation of how it works: RPC is a counter of RPC's being sent to your client along with the associated integer to know the exact RPC that is sent to your client in real time. You can use this to find unnecessary RPC's being sent to clients,… (more)
Tired of seeing players rubber band? Yeah well me too, so we made this tool to help expose the main causes of the lag plaguing this game. You can repack this mod. Here's an explanation of how it works: RPC is a counter of RPC's being sent to your client along with the associated integer to know the exact RPC that is sent to your client in real time. You can use this to find unnecessary RPC's being sent to clients, typically by mistake of the mod creator, or to associate it with lag spikes. Lag spikes are a bit harder, you have to watch clips frame by frame typically as there can be a lot sent at the same time to disguise the problematic one. This is how I exposed the playerlist sync lag. https://feedback.bistudio.com/T177400 TLC is a total entity counter. It includes Base Building items since theyre ItemBase. This one (storage and its cargo) has been a fucking problem for years now, and I've reported it over a year and a half ago: https://feedback.bistudio.com/T169094 Anytime you enter the network bubble of storage, it'll full lag you. Everybody on your screen will rubber band, and everyone will see you rubber band. When this happens with multiple people involved, it's just a lag fest. Input Throttle is a new function added to DayZ. What I've noticed is that anytime it is a non-zero number, there is lag. You can use this as a reference for comparing to the TLC/RPC at the time the IP is non zero. Here is my current feedback tracker reporting the issue as it's been made worse in 1.24: https://feedback.bistudio.com/T179907 By default the UI is visible for players. If you want a hidden by default version, it's in the Extras folder. By default you can press Insert to hide/unhide the UI. Hope we can work together to finally make this game playable at full pop without the constant network lag.
No file I/O on hot paths, no timers created per event, no per-player-per-frame hooks.
Every server-visible override preserves its chain.
less than 0.001% of each server frame at 100 players (0.000 ms/s). Counts hook dispatch and timers only, not what the hooks do inside. Methodology.
Structural load of the 328 scripted mods analyzed, lightest on the left. This mod's bar is lit; 36 others share it. Ranked list.
Event hooks carry 99.8% of this mod's structural load. 0.000 ms/s in all.
1 hook · 0.0002 ms/s
| Event hooksrun when something happens: an inventory move, a hit, an action | 1 hook | 0.0002 ms/s | 99.8% | DayZGame.OnRPC |
Counts how often each hook is dispatched and how many timers stay alive, not what the code inside does. Some rates are order-of-magnitude estimates; the methodology lists which.
Where this mod runs often
Hooks on per-frame and high-rate surfaces, with what their bodies call. Body work, not the hook itself, is what costs frame time.
Which vanilla methods the mod hooks, which of them drop the chain, how often each hook fires, and which risky calls sit inside hot hooks.
How long hook bodies take, network cost, or engine-side load. Measured across live fleets, most server lag comes from the engine and world state, not mod script chains — a light footprint does not clear a mod of lag, and a heavy one does not convict it. Methodology.
Everything else
All 4 overrides
Surface is the dispatch tier the rubric can price (— = unpriced); server is whether the override exists on a dedicated server; super() shows whether the vanilla chain is preserved on a server.
| method | surface | server | super() | where |
|---|---|---|---|---|
DayZGame.OnRPC |
T2 | yes | ✓ | DebugUI.pbo::Scripts\3_Game\DayZGame.c:5 |
MissionGameplay.OnMissionStart |
T3 | yes | ✓ | DebugUI.pbo::Scripts\5_Mission\MissionGameplay.c:5 |
MissionGameplay.OnMissionFinish |
T3 | yes | ✓ | DebugUI.pbo::Scripts\5_Mission\MissionGameplay.c:14 |
MissionGameplay.OnUpdate |
T0 | yes | ✓ | DebugUI.pbo::Scripts\5_Mission\MissionGameplay.c:21 |
Dispatch surfaces and timers the grade prices
| surface | tier | rate (Hz) | rate source | ms/s |
|---|---|---|---|---|
DayZGame.OnRPC | T2 | 8.0 | placeholder | 0.0002 |
Includes 0.000 ms/s from placeholder-rated surfaces.
Load-order constraints (CfgPatches)
What each PBO declares: its addon identity and the addons it requires to be loaded first (requiredAddons). A partial load-order signal from the mod's own metadata.
DebugUI.pbo
RA_DebugUIrequiredVersion 0.1 — requiresDZ_Scripts
census 1.1 · findings 1.1 · hash dc6b4c5671a16455