Changelog

• Removed the WZ Meta announcement that showed up when opening the window: that app will no longer be released. WZ Meta no longer appears in the WZ Suite monitor or in the manual either.
• WZ Support (remote support), the new suite app, is now protected too: it's never slowed down while you play, and it shows up in the WZ Suite monitor in «Live».
• Includes everything from 2.0.1 and 2.0.2.

• WZ Suite monitor in «Live» (Expert mode): instead of showing only what WZ Control uses, there is now one box per suite app —WZ Control, WZ Audio, WZ Defender and WZ Creator (and WZ Meta when it ships)— with its CPU, GPU, RAM and disk, and a breakdown of its processes: the engine, the Edge window, PresentMon, LibreHardwareMonitor, ffmpeg… «Disk» is what the app reads and writes per second and «Uses» is the size of its folder. Closed apps are shown in gray. It refreshes every 5 s and only while you're looking at «Live».

• WZ Suite apps are never slowed down. «Background apps while you play» already protected WZ Control, WZ Audio and WZ Defender (their programs, their windows and what they open); now it also protects WZ Creator (its window and the ffmpeg it uses to create videos). In the analysis of what runs on your PC they show up as suite apps, and «Lighter Windows» never suggests removing their startup tasks.
• Shortcuts: when the app opens it only updates the shortcuts that open THIS folder. Before, a test copy in another folder could take over your shortcuts.

• WZ Control 2: all in Rust. The app is now a single program, wzcontrol.exe, with no Python or libraries: it opens faster, uses less memory and CPU, and the installation no longer downloads Python.
• The interface, the features and your data (data/: settings, history, matches, captures, backups) are the same as in 1.31; the local API responds the same way.
• Monitoring measures with or without the game in the foreground; what’s only useful for watching «Live» pauses with the window minimized or hidden, while the overlay and the analysis keep working.
• On exit, PresentMon and LibreHardwareMonitor are closed if WZ Control opened them.
• If other apps are using Windows’ FPS sessions (Intel PresentMon, NVIDIA FrameView, ExitLag…), Live says which ones. Per-core CPU split using context switches when sampling isn’t available.
• The shortcuts and the «Open at Windows startup» task open wzcontrol.exe directly (they update themselves when 2.0 opens).
• No traces of the Python version: updating removes everything from 1.x (the wz folder, app.py, WZ Control.vbs, the Python update installer and the downloaded .zip files of previous versions). Your data (settings, history, matches, captures and backups) stays.

• Clean updates: from this version on, updating removes everything from the previous version and the folder ends up exactly like the new version. Only your data (data: settings, history, matches, captures) and the tools already downloaded (tools: PresentMon and LibreHardwareMonitor) are kept. If something fails halfway, everything goes back as it was. It prepares the move to WZ Control 2 (in Rust).

• Diagnosis (Live and overlay): WZ Suite apps no longer show up as a warning. WZ Defender (and its processes) is shown in green as «WZ Defender active», with its usage in Live. In the overlay, each diagnosis line has its own color (warnings in yellow or red, the suite in green). WZ Control’s windows no longer count inside «Microsoft Edge» either.

• PC Latency in the overlay (optional, in ⚙ Configure overlay → Latency group): the time inside the PC from your click to the screen. It’s NVIDIA Reflex’s when the game reports it and, otherwise, an estimate. It shows in the in-game overlay, in the OBS / TikTok source and in the overlay window.

• Background apps while you play: WZ Suite apps are never throttled. That includes wzdefender.exe with all its child processes, and the windows of WZ Audio and the other suite apps. Before, only WZ Control’s windows were protected, and WZ Audio’s could be throttled as if it were a browser.
• Clicking WZ Defender or WZ Audio no longer makes WZ Control measure that app instead of the game.

• New WZ Control logo: a metal hexagon with an orange edge, a performance gauge and the glowing W. It’s in the window, the tray, the overlay, the manual (and its PDF) and the shortcuts.
• The Desktop and Start menu shortcut updates itself: when this version opens, WZ Control points your existing shortcuts to the new icon and asks Windows to re-read the icons (no need to reinstall).

• Overlay: GPU usage per engine, like Task Manager (optional, in ⚙ Configure overlay → GPU group): 3D, ENCODE (video encoding: NVENC / AMF / Quick Sync) and DECODE (decoding). Useful to see how much a recording or streaming app uses. It’s measured on the card the game runs on and only read when one of the three is ticked.

• Analyzer → Matches: each match in the list has its ✕ to delete it (with confirmation); the «Delete» button was removed from the match sheet.

• Analysis mode: the FULL config file of each match is saved. If you changed something since the previous match, the sheet says so key by key (before → after), for example RendererWorkerCount 4 → 6. Data the game rewrites on its own doesn’t count.
• Configurations: matches are grouped by identical file (a single different setting = another configuration) and numbered in the order you used them. A table with the averages of each one (1% low, stability, stutters, FPS, 0.1% low, spikes, saturated threads, how much the CPU limited, end-to-end, 1% low variation), the best value in each column in green, 🏆 the one with the best overall performance and sentences that explain it. It can be filtered by map. It replaces the per-configuration A/B.
• Compare with any match («Compare with:» selector), not just the previous one.
• Matches from previous versions don’t have the full file and don’t go into the configurations table.

• Quitting WZ Control closes the overlay window (the 🪟 Show window one), if it was open. When updating it stays open: it shows data again on its own when WZ Control comes back, without cutting your TikTok capture.

• New «🔎 What’s being measured» box at the end of Live: the process the FPS comes from, the card the game runs on, which card the usage and temperature come from, the monitor the game is on and which card it’s connected to. It warns if something doesn’t add up (monitor on the integrated graphics, data from another GPU, wrong app).
• PCs with 2 or 3 monitors: clicking OBS, TikTok LIVE Studio, Discord, the browser, Spotify, Steam or Battle.net on another monitor no longer makes WZ Control measure that app instead of the game.
• Several NVIDIA cards: the one the game uses is measured (before, always the first one).
• The Hz tips and FPS-cap detection use the monitor the game is on, not the primary one.

• Its own icon for the overlay window: a steel hexagon with green, yellow and red reflections and three metric bars. It shows in the title and taskbar of 🪟 Show window, so you can easily tell it apart when picking it in TikTok LIVE Studio’s Window Capture.

• You can now update with the game open. WZ Control doesn’t touch the game: it closes for a few seconds, installs and comes back on its own in the tray, without opening its window on top of the game. The overlay comes back if it was on; the measurement of the current match starts over. It only waits if a recording is in progress.

• Windowed overlay for TikTok LIVE Studio: a 🪟 Show window button next to «HTTP overlay source:». It opens the overlay in its own Edge window in app mode («WZ Control · Overlay», dark background) so you can add it with Window Capture. The window resizes itself to the overlay and keeps updating even if the game covers it. With OBS it isn’t needed: you use the address.

• The window opens instantly again, as always.

• HTTP overlay source: a copy of the overlay in a local page with a transparent background (http://127.0.0.1:8765/overlay), for OBS / Streamlabs (Browser source) or TikTok LIVE Studio, on top of the Game Capture and without screen or window capture. The address and a Copy button are in Live → ⚙ Configure overlay. It uses the same overlay settings and works with the desktop overlay turned off.
• Low usage: one ~1 KB request per second (the structure only travels when it changes), only what changed is redrawn, the chart only when there are new points, and the page pauses if the source isn’t visible. If no source requests it for 6 s, WZ Control stops measuring for it.
• Options in the address: ?zoom=1.5 (size) and ?op=100 (opacity).

• Noticeable stutters: threshold from 25 to 30 ms (it’s still also 4× the normal frametime). Frames of 25 to 30 ms are barely perceptible and were being counted as stutters. It applies to the overlay (STUTTERS), match analysis mode, captures and the diagnosis. «Frametime spikes» don’t change.

• Analysis mode: map by name. When a match ends, «Which map did you play?» appears with the maps of that version of the game (or «Skip»). Black Ops 7: Verdansk and Avalon (large); Haven’s Hollow, Rebirth Island and Fortune’s Keep (small). Modern Warfare 4: Hajin and Verdansk (large); Rebirth Island, Zodiac and Vondel (small). Also «Other large / small map».
• The comparison uses the previous match on the same map and, if there isn’t one, one of the same size; it warns when the maps differ. Matches that only had «large» or «small» are still respected.

• Analysis mode: match end after 10 s without traffic with the server (20 s before). A disconnection of more than 10 s also closes the match.
• Only the game is measured: when it ends, the loading seconds at the start and those of the end-of-match screen, where stutters are normal, are discarded. Always the first 10 s and the last 5 s; plus, within the first and last minute, everything up to the last (or from the first) second with a strong stutter (over 25 ms and 4× normal) or with collapsed FPS. FPS, 1% / 0.1% low, stutters, CPU, GPU and network are calculated without those seconds, and the sheet says how many were discarded.

• Refreshed WZ Meta announcement: combination lab (primary + secondary weapon, compatibility and why), suggested duos (SMG + sniper, SMG + assault rifle, assault rifle + sniper), six features and the Try hard and Competitive styles.
• The announcement shows only once per app start: if you close the window and reopen it from the tray icon, it doesn’t appear. «Don’t show for 3 days» stays the same.

• WZ Meta announcement (the next app: game updates, new weapons, meta weapon, comparisons, technical data and recommendations by play style). It appears when the window opens, after the tour and any other notice. A «Don’t show for 3 days» checkbox (it shows again after 3 days) and a «Send suggestions for the app» button with name and suggestion: saved in data/sugerencias_wzmeta.txt and your email opens with the message ready (if you don’t have an email app, the text can be copied).

• Matches and the RendererWorkerCount analyzer per game version. The version is detected from the running executable: cod25-cod.exe = Black Ops 7; cod26-cod.exe or cod.exe = Modern Warfare 4 (cod26-cod.exe is now also recognized as the game). Each match saves its version, and the RendererWorkerCount value is read from THAT version’s file (not the one chosen in Optimization).
• The analyzer shows the version it’s testing, how it was detected and its file; it applies the values to that version’s file, only counts its matches and warns if you play another version halfway through a test.

• Frame generation warning when optimizing. If it’s on (DLSS/FSR/XeSS Frame Generation in the game, NVIDIA Smooth Motion —new in the check-up—, Multi Frame Generation forced in the driver, AMD Fluid Motion Frames, or generated frames measured by PresentMon), a big notice appears before acceptance explaining what happens to FPS and latency, with two buttons: Remove frame generation (recommended) or Keep it. If it’s kept, the optimization doesn’t touch it. After optimizing it explains why the FPS counter went down.
• Match analysis mode (Analyzer → Matches, turned on with one click): automatic match detection through the Warzone server (45 s stable; minimum 3 minutes), a sheet per match (1% low of the whole match, stability, noticeable stutters, saturated threads, % of time the CPU limited, network, end-to-end), comparison with the previous one in sentences, large/small map tag, automatic A/B per configuration and a new Match item in the overlay (Analysis group).
• Render thread analyzer (RendererWorkerCount): suggests values based on the CPU, applies them with a backup (with the game closed), one match per value, and recommends the best; it warns if the GPU limits and it isn’t worth it.
• Overlay · Stutters: now counts only noticeable stutters in the current match (over 25 ms and 4× normal; it doesn’t count menus, loading or the first 30 s). Before it counted any frametime spike since the game opened.
• Overlay · GPU: below 85 % usage it’s shown in blue (low usage), no longer yellow.
• Window: if Edge isn’t in its usual folder, it’s searched for in the per-user installation and in the Windows registry; if there’s no Edge, Chrome, Brave or Vivaldi opens in app mode (no tabs) instead of a normal tab.
• Demo: a sample game file to see the optimization preview.

• Overlay grouped into containers with a colored bar and title: Performance, Latency, Network, CPU, GPU and, at the end, Diagnosis (what limits + diagnosis). Inside each group the labels are short (USAGE, TEMP, END-TO-END). In «One row» the groups go side by side. The «⚙ Configure overlay» list is grouped too.
• Free overlay position: besides the corner (new: top center and bottom center), fine adjustment with arrows (10 px, Shift = 1 px) or ✥ Move with the mouse (drag and «Done»; it locks on its own after 90 s). The adjustment is saved and never leaves the overlay off the monitor. When the corner changes, the adjustment goes back to 0.
• Live: the «Input lag» card is now called «End-to-end latency», same as in the overlay.

• End-to-end latency: the monitor part now depends on the panel type and its Hz (before: ½ refresh + 2 ms the same for any monitor).
  • Monitor = scan-out to the middle (½ refresh) + processing + ½ of the typical GtG, with values by type and Hz band (OLED, TN, IPS, VA, OLED TV, LCD TV). E.g. at 240 Hz: OLED ≈ 2.4 ms, TN ≈ 3.7, IPS ≈ 4.7, VA ≈ 6.3.
  • The type is detected by model (a list of known gaming monitors: Alienware, ASUS ROG/TUF, LG UltraGear, Samsung Odyssey, MSI, BenQ ZOWIE, Gigabyte/AORUS, AOC, Acer, Dell, ViewSonic, HP, Corsair…) or by the name («OLED», «TV»). If it isn’t recognized, IPS is assumed and it’s marked in yellow.
  • Home → Monitors → Panel: shows the type, how it was detected and the monitor’s ms; you can choose the type by hand.
  • The current Hz of the monitor the game runs on (or the primary one) are used, not the maximum.
• Cleaner overlay: PC Latency (already part of End-to-end latency), 0.1% low, CPU/GPU POWER, RAM, NETWORK and TIME were removed (they’re still in «Live»). Frametime chart, Stutters and Jitter are ticked by default and are added once for whoever already had the overlay configured.

• Overlay: three new items (optional; tick them in «⚙ Configure overlay»):
  • Jitter: how much the ping varies (to the Warzone server in a match; otherwise, to the Internet). Green < 8 ms, yellow < 15 ms, red above.
  • Frametime chart: last 4 s; stutters show as red spikes (> 2.5× normal). Each point keeps the maximum of its segment so a single-frame stutter isn’t lost. With «Frametime» ticked it goes below its value.
  • Stutters: total for the gaming session, colored by those in the last minute.

• The overlay no longer hides by itself. On = always visible, with or without a game open, until you turn it off (button, shortcut or tray). The «Show only with a game or app being measured» option was removed.
• It remembers whether you left it on: when WZ Control opens (also at Windows startup) the overlay comes back on its own.
• With that, window capture in OBS / TikTok Live Studio no longer comes out empty when there’s no match.

• Overlay: «Input lag» is now called «End-to-end latency» and its value always carries ~ (it’s an estimate of controller + PC + monitor).
• The overlay window now has a name: «WZ Control Overlay» (before «tk»). In OBS or TikTok Live Studio it appears as «[pythonw.exe]: WZ Control Overlay». If you had a capture of the «tk» window, pick it again.
• «⚙ Configure overlay» explains that the capture comes out empty while the overlay is hidden (with «Show only with a game or app being measured» ticked and no Warzone open).

• Home: the CPU and graphics card are no longer rated with numbers.
  • Instead of «x.x/10», their tier is shown with a color: Enthusiast (purple), High end (green), Upper mid-range (turquoise), Mid-range (blue) and Entry level (sand). No tier is shown in red.
  • Each one comes with a humorous comment based on its tier (different phrases for CPU and GPU).
• Optimization → System balance: the CPU and graphics card show the same tier and comment; the score bar and the «Fair/Poor» labels were removed.
• The «Old / limited» and «Basic» tiers fall under «Entry level». RAM, drives and the overall PC rating don’t change.

• Fixed: «GPU PCIe link» showed x2, x4 or x8 with cards that are really at x16.
  • Radeon and Intel Arc have a PCIe bridge inside the card; before, the chip’s internal link was read instead of the card’s link to the slot. Now it walks up the card’s devices to the one connected to the slot.
  • With NVIDIA, the direct chip reading (NVML) wins when Windows reports fewer lanes than it does.
  • If only Windows reports fewer lanes (with no way to confirm it), it stays yellow with how to check it in GPU-Z, instead of red.
  • The details say what each source read (Windows / NVIDIA / slot) so reports can be reviewed.

• Overlay: lost packets. New Loss item (ticked by default in new configurations; if you already had the overlay configured, tick it in «⚙ Configure overlay»). It shows the % of the last 60 probes (one per second) that didn’t come back: in a match, to the Warzone server (or the last router that responds); without a match, to the Internet. Green < 0.5 %, yellow up to 3 %, red 3 % or more.
• Dashboard mode was removed (the «WZ Dashboard» window for OBS). The overlay and the «Live» tab stay the same.

• Game to optimize: Black Ops 7 or Modern Warfare 4. In Optimization → Optimize there’s a selector with both games; each option includes that version’s multiplayer and Warzone. By default the one you played most recently is chosen (the config file modified last). The check-up, the list of all the file’s values and «Optimize» use the chosen game’s file.
• Support for Modern Warfare 4’s file (s.1.0.cod26.txt, in the same folder as Black Ops 7’s s.1.0.cod25.txt0 and .txt1). New settings that are checked and optimized: shadow filtering, surface tessellation, shading quality, depth of field (enable, remove on weapon/world and its quality), preferred display mode, Intel XeLL and XeSS Frame Generation. Informational: the game’s audio channels, in-game Windows Sonic and corpse limit.
• Motion blur «Cinematics only» counts as correct (there’s no blur in a match).

• Fixed: right-clicking the tray icon froze for a few seconds and didn’t let you use the menu or quit WZ Control. Before showing the menu, the app checked every Windows process to know whether its window was open. Now that’s checked in the background, only among Edge processes, and the menu appears instantly. «Show» and «Hide» don’t freeze the icon while the window opens either.

• Fixed: opening WZ Control from the tray icon (or the shortcut with the app already running) sometimes didn’t show the window, or brought your browser to the front if you had a page with «WZ Control» in its title open (for example, wzcontrol.app). Now only the app’s window is looked for, and if its Edge got stuck without a window, it’s closed and reopened. You no longer need to close all your browsers.

• Safer updates: the signed version file now says which app it belongs to, and WZ Control only accepts its own. That way it could never be confused with an update for WZ Audio, the new audio app that is also published on wzcontrol.app (with its own section at /audio).

• Fixed: in Live, the «Applications using the GPU» table kept showing the game (with moderate usage) after closing it, even though it no longer existed in Task Manager. When the NVIDIA driver had no new samples, the app repeated the last ones it had received, which included the closed game. Now they’re only repeated for a few seconds, and both tables (GPU and CPU/memory) only show processes that are still alive.
• When the game closes, its row leaves the tables instantly.
• The CPU/memory table detects when Windows reuses a closed process’s number (PID) for a new one.
• The tables don’t show old data when you come back to the «Live» tab: they’re cleared if they haven’t refreshed for more than 8 s.

• Change history with restore points. Every time WZ Control changes something (Optimize, a single fix or Lightweight Windows) a point is saved with the date, the list of changes and the value that was there just before. In Optimization › 🕘 History and restore (and in the Windows tab) you see the timeline and can go back to any point: everything that came after is undone, from newest to oldest. At the end the Initial state (before optimizing) is marked: how your PC was before the app’s first change.
• Before going back it shows exactly which points will be undone. Undone points stay in the list, crossed out and with the date they were undone. With Warzone open, its config file isn’t restored.
• «Revert changes» becomes «Back to the initial state» inside the history; it also restores what previous versions of the app changed. It’s saved in data/historial_cambios.json.

• Fixed: in Windows › Optimize, «Widgets and news» failed with «[WinError 5] Access is denied» on some Windows 11 PCs: Windows protects one of its keys even when the app is administrator. Now each value is written separately; if Windows protects one, the others are applied (the Widgets button on the taskbar is also hidden) and the item counts as optimized. If Windows doesn’t allow changing any, the notice says how to turn it off by hand in Settings. The same applies to the rest of the registry settings in that tab.

• Updates from the app (notify and update with one click). On startup, once a day, WZ Control checks https://wzcontrol.app/version.json. If there’s a new version a green bar appears at the top with See what’s new, Update now and Later. Nothing installs without your click.
• Update now downloads the .zip, checks its SHA-256 and that version.json is signed by the author (Ed25519 digital signature, verified in pure Python: nothing to install), closes the app, replaces only the program files (never data or tools) with a backup, and reopens it. If something fails, it restores the previous version and says so when it opens.
• You can’t update with a game open or while recording a capture.
• Help › Updates: installed version, last check, a Check for updates button and a checkbox to turn off automatic checking. The check sends no data about you or your PC.
• Anyone with a version older than 1.21 updates by hand this last time (copy the .zip to C:\).

• Fixed: Instalar.bat kept asking for administrator rights endlessly on some PCs, even though the user was an administrator and accepted the prompt. The check used net session, which fails if Windows’ «Server» (LanmanServer) service is disabled, so the already-elevated window thought it wasn’t and asked again. Now it checks with fltmc (it doesn’t depend on any service) and, just in case, the elevated copy never asks again: if Windows doesn’t confirm it, it warns and continues. If the permission is refused, it explains how to run it as administrator.
• The app can’t get stuck in a loop when asking for permission either: the elevated copy opens with --no-elevate.

• Fixed: in the top bar, the version number (now 7 characters, e.g. «v1.20.33») overlapped the «Home» tab. The logo block no longer shrinks.

• Everything related to the DLSS Super Resolution model was removed from the overlay and dashboard mode: the «DLSS SR» item, the «Live DLSS model» checkbox (NVIDIA NGX log) and the NVIDIA DLSS indicator checkbox. If the NGX log was left on by a previous version, opening the app restores the values that were in the Windows registry and deletes its log folder. NVIDIA’s indicator (ShowDlssIndicator) isn’t touched.
• The DLSS Override check in Optimization (NVIDIA driver) stays the same.

• Windows › Background apps while you play (optional, off by default). While the game is open it lowers the priority and turns on Windows’ efficiency mode (EcoQoS) for browsers, launchers, cloud sync, animated wallpapers and Adobe apps; optionally, when the match starts, it frees the RAM they aren’t using (EmptyWorkingSet; on by default with 16 GB or less). It checks every 30 s in case new apps open and restores everything when the game or WZ Control closes. It never touches OBS / streaming apps, audio, the game, the anticheat, the WZ Control window or apps deliberately set to high priority. Music and chat/voice come unticked.
• A «Benefit on this PC: high / medium / low» label calculated from the RAM, CPU threads, VRAM and what those apps are using at that moment, explaining why and what you’ll notice (fewer stutters and a steadier 1% low; average FPS changes little; it doesn’t free VRAM).

• Route quality to the server (what ExitLag and similar try to improve). In Live › Warzone server «Route to server: Good / Fair / Bad · +X ms over what’s expected» appears; clicking it shows the details: minimum ping versus what the distance allows, where the delay appears (your network / Wi-Fi, your ISP’s access, a hop in between or the server’s network), whether the route takes a geographic detour, loss that reaches the server, the table of routers along the way and the answer to «Would a route optimizer help you?», plus the history of the last matches in that data center. It’s analyzed at the start of each match and every 5 minutes (or with «↻ Analyze again»), with ICMP ping to each hop in the background; it doesn’t touch the game. A slow or unresponsive router only counts if the delay carries through to the end (effective latency = the lowest of that hop and the following ones), and what each segment should take due to distance is discounted.
• New Route item (optional) in the overlay and dashboard mode («Bad +38 ms», with where the problem is in the dashboard).
• Fixed: since 1.17.28 the Live tab stopped updating because of a leftover from the old «Fullscreen» mode (a JavaScript error on every update). Dashboard mode wasn’t affected.

• Dashboard mode › Diagnosis: long texts are no longer cut to a single line. They’re shown in full over several lines within their strip (at most a third of the height, never on top of the cards). If they don’t fit at that window size, the overlay’s short form is used («⚠ OBS Studio · 11% GPU», «✓ The GPU limits (ideal)»), one line per item, and only then is it cut with «…». No need to resize the window (it matters for OBS / Streamlabs Window Capture). The bar’s title is shortened before the «Normal mode» button.

• Optimizing with the NVIDIA App’s «Game filters and photo mode» on no longer ends in «Optimization with warnings» with the NvAPI_DRS_SetSetting devolvió -104 error. That code is NVAPI_NOT_SUPPORTED: with the NVIDIA App the driver doesn’t allow changing that setting from outside. Now it stays as a manual to-do with the instructions (NVIDIA App → Settings → Features → «Game filters and photo mode», or Alt+Z → ⚙ → Features), its row in Optimization shows «Open NVIDIA App» instead of «Apply» and it isn’t retried on every Optimize. This applies to any NVIDIA setting the driver rejects the same way.

• Home opens instantly: the PC information is saved the first time it’s read. When the app opens it shows what was saved and re-reads it in the background. If something changed (video driver, BIOS, RAM, drives, monitors, Windows, Warzone version…) the notice «Changes were detected in the PC’s configuration» appears with the See changes button (old value → new) and the information refreshes; otherwise, nothing is noticeable. What changes on its own (temperatures, free space, power-on hours) doesn’t count as a change.
• Optimization opens instantly: the last analysis is saved. On entering, the saved one is shown and it rescans in the background («Checking for changes…»). If something changed, the «The following changes have been detected» screen appears with each setting, its old value and the new one.
• Dashboard mode (replaces «Fullscreen»): a ▣ Dashboard mode button in Live. It opens a small window with only the overlay’s metrics (the same ones you choose in «⚙ Configure overlay») as cards, designed to be captured in OBS / Streamlabs (it doesn’t freeze even if another window covers it), and closes the normal window to use less. Very light: it only updates the texts that change, stops polling when minimized and can refresh every 1 s or 2 s. It adapts to the window size. ↩ Normal mode goes back to the usual window.

• Overlay: DLSS SR in a compact form so the overlay doesn’t widen: «M · Perf live», «K ovr», «Auto K/M/L» (in Spanish UR = Ultra rendimiento, Equil = Equilibrado, Cal = Calidad, UC = Ultra calidad; in English UP / Perf / Bal / Qual). The server location is short too: city and country code («Dallas, US»).

• Overlay › DLSS · Super Resolution live: a new «Live DLSS model in the overlay» checkbox. It turns on NVIDIA NGX’s official log to %ProgramData%\WZControl\ngx and reads it every second: it shows the preset and the mode DLSS really uses (e.g. «Preset M · Performance (live)»), even if you change the quality mid-match. It doesn’t touch the game process; unticking it restores the previous Windows registry values.
• Warzone’s config file is no longer used to infer the model. Without the live reading, only what the driver says is shown: the fixed preset chosen or «Recommended: K/M/L depending on the mode».
• A sample of the NGX lines in data/ngx_muestra.txt to fine-tune the reader.

• Overlay › DLSS · Super Resolution: with the override on Recommended / Latest it no longer shows just «Latest». The preset is resolved the same way as the driver based on Warzone’s DLSS mode: Ultra performance → L, Performance → M, Balanced / Quality / DLAA → K (e.g. «Preset K · Quality (recommended override)»), checked against NVIDIA’s DLSS indicator. In other games: «Auto K/M/L depending on the mode».

• Overlay › DLSS · Super Resolution: the NVIDIA App’s «per game» override is now found even if it’s saved under another Warzone executable (cod25-cod.exe, cod24-cod.exe or cod.exe); with other games, that game’s profile is read. If there’s no override, «Game’s model» is shown instead of staying empty. Diagnostics in data/dlss.log.
• New NVIDIA in-game DLSS indicator checkbox in «⚙ Configure overlay»: the driver draws the DLSS preset and version actually loaded (a fix for the N/A in the NVIDIA App’s statistics).

• Measuring any game or app, not just Warzone: with Warzone closed, the app in the foreground that is rendering frames is measured (other games, emulators, benchmarks, 3D programs). The Live panel, fullscreen, the overlay and captures work. At the top you see «Measuring: app.exe». Warzone always has priority. Only the active window is queried (not the process memory): safe with other anticheats.
• Overlay: the «Show only with Warzone open» option is now «Show only with a game or app being measured».

• Overlay and fullscreen: two new optional metrics (unticked by default).
  • Warzone server location (city and country).
  • DLSS · Super Resolution: the model imposed by the NVIDIA override (Preset K/M, «Latest»…) and the game’s DLSS mode, e.g. «Preset M · Performance (override)». It’s read from the driver (NVAPI) and Warzone’s file, without touching the game process. Every 60 s and only if selected.

• Optimization › Requirements: a new BIOS version row with the installed version and date and whether there’s a newer one. ASUS and MSI: it queries the manufacturer’s support page (24 h cache). Other brands or no response: by age. Intel Core 13th/14th gen with a BIOS older than Sep-2024 (without the 0x12B microcode): red. A «See your board’s BIOS» button opens the model’s support page. Can be turned off with bios_check_online.
• Fix: the «Open…» buttons in Optimization (NVIDIA panel, game folder, BIOS, LibreHardwareMonitor) stopped working in v1.12.18 because of the donation link; they work again.

• The beep on stutters (and input lag spikes) comes off by default. If you never changed it, it turns off when updating; if you turned it on yourself from the bar, that’s respected.

• Donations: the link now goes to the Stripe payment page (https://buy.stripe.com/fZu5kwg9Tdts99K3CEd3i00) instead of PayPal, in the bottom bar, the Help tab, the manual and the PDF.

• Donations: a ☕ Support me link next to «App developed by El Viejo Odioso» (bottom bar of every screen), a Did you like WZ Control? · Buy me a coffee card with a message from the author in Help, and the same invitation at the end of the manual and the PDF. It opens PayPal (paypal.me/Experti) in the default browser. ES / EN.
• Manual PDF: the header no longer crops the signature.

• Getting-started tour the first time the app opens: it dims the window and highlights each section with a tooltip (6 steps: hardware on Home, measuring the controller, analyzing the PC, checking and optimizing, lightening Windows and monitoring live or with the overlay). Previous / Next / Skip, arrows and Esc. It’s saved when you finish it (tour_done in data/ajustes.json) and can be repeated from Help. In Spanish and English.

• Overlay: the default shortcut is now Ctrl+Shift+L (Ctrl+Shift+O clashed with Warzone controls). If you had Ctrl+Shift+O saved it changes only once; if you choose it on purpose afterwards, it’s respected.
• Captures: the default duration is 30 s, and the duration and delay you choose in the bar are saved (data/ajustes.json) for later sessions, also when recording with the in-game shortcut.

• Instalar.bat installs everything in a single step and asks for administrator (UAC) when it opens: Python, libraries, .NET 10 Desktop Runtime, PawnIO, PresentMon, LibreHardwareMonitor and shortcuts. It detects and skips what’s already installed; it uses winget and, if it isn’t available, each one’s official download. At the end it says whether something couldn’t be installed.
• The Desktop and Start menu shortcuts are marked «Run as administrator».
• Python is installed for all users and used in the same run (no need to reopen Instalar.bat).
• Fix: the filter that picked LibreHardwareMonitor’s .zip discarded the right file.
• LibreHardwareMonitor is always installed (it no longer asks).

• New Help tab with the full user manual in the selected language (ES / EN), a navigable index, the app’s logos, El Viejo Odioso’s signature and contact information (christian.calvo@outlook.com).
• Download PDF: generates the manual as a PDF (cover, index, logos and signature on every page) in the Downloads folder. If it can’t, it opens the printable version to «Save as PDF».
• The manual lives in manual/manual_es.md and manual/manual_en.md, shows only the current version and date and is updated with every version (scripts/check_manual.py checks that it matches the delivered version).

• Fix: Warzone’s upload traffic (↑) stayed empty on PCs where the network capture only sees incoming packets (it depends on the network driver, «offload», VPN or ping optimizers). Now it’s detected and upload is measured with Windows network events (ETW, Microsoft-Windows-Kernel-Network) filtered to the game process. The tooltip shows the source; if that isn’t possible either, it shows «–» instead of a false value.

• Tray icon: the window only opens with a double-click (a single click no longer does anything).
• Two windows never open: if there’s one already (even hidden or minimized) it’s brought to the front; if it was just launched, it waits for it to appear instead of opening another.
• Opening the shortcut with WZ Control already running shows its existing window instead of opening a new one.

• Fix: turning on the overlay with the in-game shortcut no longer steals Warzone’s focus (before, the game minimized). The overlay window is created hidden at startup and is shown/hidden without activating (SW_SHOWNOACTIVATE / SWP_NOACTIVATE).

• Optimization › System balance: ratings in words (Excellent / Good / Fair / Poor) instead of numeric scores.
• A table of FPS by resolution × DLSS × graphics quality (Minimum, Basic, Balanced, Ultra, Extreme), with tabs.
• The 150 FPS reference was removed: the color now compares against your monitor’s Hz.
• It still shows the recommended resolution (the highest one that fills your Hz).
• FPS model recalibrated upwards and with no discount for background apps: it estimates real in-match FPS.

• The «Revisión» (Check-up) tab is now called «Optimización» (in English, «Optimization»), and all the texts that mention it («guide in Optimization», «above in Optimization», etc.) were updated.

• Live fullscreen: the «Warzone server» box now shows the server’s location below it (city, state/region and country), or «no match» if you haven’t joined one yet.
• Fullscreen: the diagnosis at the bottom is no longer covered by the «App developed by…» credit.

• Fixed: «What limits your FPS» no longer says «CPU» when there’s really an FPS cap (for example the Warzone menu’s 120 limit). Now it detects the cap and says where it comes from:
  • Caps in the game’s file: in match, in the menu, out of focus and the menu/game V-Sync.
  • The NVIDIA driver limit («Max Frame Rate», the same one the NVIDIA App sets).
  • Monitor refresh rate (V-Sync) and the automatic Reflex + V-Sync cap.
  • Unknown caps (RTSS or another app): per-second FPS almost constant at a round value with the GPU not saturated.
• Live, fullscreen and the overlay show «FPS cap · at 120 FPS because of the game menu’s FPS limit» and clarify that it isn’t a bottleneck. The overlay says «✓ FPS cap: 120».
• The game and driver caps are read when you press «Analyze» in Check-up; without analyzing, they’re detected from how the FPS behaves.

• New: Open WZ Control at Windows startup, toggled from Home (checkbox next to «Refresh») or from the tray icon’s menu.
  • It uses an «at sign-in» scheduled task with administrator privileges: it starts without asking for permission (UAC), 20 s after signing in to Windows, straight to the tray and without opening the window.
  • The task has no time limit and also works on a laptop on battery.
• New: in the Analyzer you can delete captures one by one (✕ on each capture in the list) or several at once (tick them and use «Delete ticked»). It always asks for confirmation.

• New: WZ Control runs in the background, without a console window, with its icon in the system tray (next to the clock).
  • Click the icon: shows or hides the app window.
  • Right-click: Show / Hide the window, turn the in-game overlay on or off, and Exit.
  • If you close the window with the X, the app keeps running in the tray (it tells you the first time).
  • «Exit» (in the app or the icon menu) closes everything and removes the icon.
• New WZ Control.vbs launcher (it uses pythonw, Python without a console). Instalar.bat creates the shortcuts on the Desktop and in the Start menu pointing to it, with the logo icon.
• Iniciar WZ Control.bat now opens the app without a console; to see the messages use Iniciar con consola (diagnostico).bat. Without a console, messages are saved in data/wzcontrol.log.
• Options: --no-tray (no icon) and "tray": false in config.json.

• New: «What affects your performance», a simple live diagnosis of what may be interfering with Warzone. It appears in the live Diagnosis, in fullscreen mode and in the overlay («Diagnosis» item).
  • Bottleneck in plain words (graphics card, CPU, both even, or your FPS limit) and how much CPU the other programs use when the CPU is the one limiting.
  • Background apps with significant GPU, CPU or RAM usage, grouped by app (all Chrome tabs count as one) and with a clear name: animated wallpapers (Wallpaper Engine, Lively), recorders and overlays (NVIDIA App, Xbox Game Bar, Medal, Overwolf, AMD Software), streaming apps (OBS, Streamlabs), browsers, RGB software, antivirus, Windows Update, etc. Each one with a short tip.
  • Components at their limit: full VRAM, RAM at 90 % or more, CPU at 95 °C or more and a throttled GPU.
  • Thresholds adapt to the bottleneck: if the GPU limits, other apps’ GPU usage is watched more closely; if the CPU limits, their CPU usage.
• New: the Warzone Control logo in the overlay header (it can be hidden in «Configure overlay»).
• Low impact: the diagnosis reuses data that’s already measured. With only the overlay on, the process list is read every 5 s (every 3 s with Live in view).

• New: fullscreen mode in Live («⛶ Fullscreen» button): only the metrics board with big numbers, Xbox Game Bar style. Exit with Esc or the button.
• New: in-game overlay (RTSS / CapFrameX style). It’s its own transparent window, always on top, that lets clicks through; it isn’t injected into Warzone. It shows with the game in «Fullscreen Borderless» or windowed.
  • Global shortcut to turn it on/off (Ctrl+Shift+O by default, configurable).
  • It’s placed on the monitor where Warzone is; it shows the values with the same color lights as the app.
  • With the overlay on, the monitors stay active even if the app window is hidden.
• New: «⚙ Configure overlay»: choose which metrics to see (FPS, 1%/0.1% low, frametime, input lag, PC Latency, what limits, Warzone ping and network, CPU/GPU usage, temperature and power, VRAM, RAM and time), position, size, layout (list or one row), opacity, whether it shows only with Warzone open, and the shortcut. The same selection is used in fullscreen mode. It’s saved in data/ajustes.json.

• New: the official Warzone Control logo.
  • Emblem in the app’s header (next to «WZ CONTROL» and the version).
  • Window and taskbar icon (the app window’s favicon).
  • Full logo on the initial «Check-up» screen (before pressing «Analyze my PC»).
  • Emblem in the image report for sharing.
  • Icon of the Desktop shortcut created by Instalar.bat (ui/img/wzcontrol.ico).
• The logo files are in ui/img (original with a transparent background, emblem, .ico icon and sizes for the interface).

First numbered version. 1.0 brings together everything built so far (Home, Check-up, Lightweight Windows, Live, Analyzer, NVIDIA/AMD, controller test, full input lag, etc.).

• New: the version appears in the Python console (at startup and with --version), in the window title, in the interface header and in the image report.
• New: if another version is already running when WZ Control opens, the console warns about it.
• Includes the last changes before versioning:
  • Live with the Xbox Game Bar-style panel (numbers only).
  • Input lag: monitor with a fixed formula (½ refresh + 2 ms); the controller uses the frequency measured on Home.
  • RendererWorkerCount: red only if it exceeds the most powerful threads; lower values in green with a suggestion.
  • «Scan again» always returns fresh data.