WebView performance and lifetime
Frame rate
Section titled “Frame rate”The pause menu’s Settings → Multiplayer → WebView Framerate setting limits the frame rate of all WebViews in that client. Changes apply immediately.
The default is 60 FPS. Available values are 15, 30, 60, 90, 120,
144, 165 and 240. Actual frame rate can be lower when the browser cannot
keep up.
The setting is saved in %LOCALAPPDATA%/revo/client.toml:
webview_framerate = 60Restart GTA after editing the file directly. Use the pause menu to compare settings during a session.
The setting controls browser rendering. Client timers and messages sent through the WebView bridge have their own frequency. Lowering the frame rate leaves those updates running at the frequency your scripts choose.
Hide, reuse or destroy
Section titled “Hide, reuse or destroy”| Operation | What happens |
|---|---|
view.visible = false |
Hides the surface and releases its focus. The document, its state and bridge handlers remain loaded. |
view.visible = true |
Shows the existing document without loading it again. |
Assign view.url |
Loads a new document and resets bridge readiness. |
view.destroy() |
Closes the browser and releases the view’s resources and handlers. |
Keep frequently opened interfaces, such as an inventory, loaded while hidden. Destroy a one-time interface once it has finished. Creating another WebView on every opening leaves the earlier ones allocated unless you destroy them.
Hiding a WebView keeps its bridge available. Stop client-side polling and UI subscriptions that are only needed while the panel is open. When showing it again, send the current state so it includes changes made while closed.
Destroying the view removes handlers registered on that view. Clear any client timers and global event listeners you created to feed it separately. For input cleanup, see Cursor and UI focus.
Data updates
Section titled “Data updates”Every bridge call serializes its arguments and schedules work in the receiving runtime. For a HUD, send displayed values when they change. For a large list, send the requested page or changed entries. Group related values into one update.
Keep continuous animation inside the page where possible. For example, send a countdown’s remaining time when it starts or changes and let the page update its display between messages.
After navigation, repeat the page’s ready notification and send its initial state. See Handlers and navigation for listener and pending-request behavior.
Check a slow interface
Section titled “Check a slow interface”Use CEF debugging to inspect the affected page. Compare it while visible, hidden and destroyed. A hidden view still retains its document, so destruction is the useful comparison when checking retained resources.
Repeat the same open/close sequence several times. Check for repeated requests, duplicate event handling and old pages remaining in the debugger’s target list. If hiding the panel leaves client-side updates running, stop those updates as well before comparing the workload.