-
Notifications
You must be signed in to change notification settings - Fork 18
Troubleshooting
Check the log file first - it contains the exact error message for most issues.
%LOCALAPPDATA%\VioletWing\logs\violetwing.log
The Logs tab inside the application shows the same output.
VioletWing couldn't fetch cs2-dumper.exe from GitHub.
- Check your internet connection
- If you use a firewall or VPN, allow outbound HTTPS to
github.com - If the binary is already cached, VioletWing will use it - check the cs2-dumper version card in General Settings
Error code: E4014
VioletWing launched cs2-dumper but CS2 wasn't open.
- Launch Counter-Strike 2 first, wait until you're in the main menu or a match, then start VioletWing
Error code: E4012
Valve pushed a patch and the memory offsets are stale. Restart VioletWing with CS2 running - it clears the cache and reruns cs2-dumper automatically. If cs2-dumper itself hasn't been updated for the patch yet, check the cs2-dumper releases page.
Error codes: E4013, E4015
VioletWing doesn't have permission to attach to CS2.
- Right-click
VioletWing.exe→ Run as administrator - Make sure CS2 is already running before launching VioletWing
The ESP overlay doesn't support exclusive fullscreen, or pyMeow couldn't attach to the CS2 window.
- Switch CS2 to Windowed or Borderless Windowed (Video settings → Display Mode)
- Confirm the Overlay toggle is on in General Settings
- If running from source, verify
pyMeowinstalled correctly - see Build from Source - Restart both CS2 and VioletWing
NVIDIA driver bug with transparent OpenGL windows.
- Open NVIDIA Control Panel → Manage 3D Settings → set OpenGL GDI compatibility to Prefer compatible
- Restart VioletWing
Intel and AMD GPUs are not affected.
- CS2 must be the active foreground window - clicking away breaks it
- Adjust
JumpDelayin the Additional tab: increase slightly (e.g.0.012) if jumps fire too fast, decrease (e.g.0.008) for tighter timing - Confirm the jump key matches your CS2 jump bind - default is
space
Attack on Teammates is enabled. Disable it in the Trigger settings tab.
- Confirm TriggerBot is enabled in General Settings
- Check you're holding the correct trigger key (or that toggle mode is on and active)
- Verify offsets are current - stale offsets cause fire logic reads to fail
- Check the log for errors tagged
trigger_bot
- Confirm NoFlash is enabled in General Settings
- Restart VioletWing to regenerate offsets
- Verify
FlashSuppressionStrengthis0.0for full suppression
Open a GitHub issue and attach the relevant lines from your log file.