installation_guide.adoc

Removing other configs

1. Follow these instructions if you’ve used other configs previously. Make sure to back up your binds settings! == Setup

2. Replace launch options with:

   • -novid -nodns -nostartupsound -nohltv -nojoy -nobreakpad -nosteamcontroller -noquicktime -precachefontintlchars -disable_d3d9_hacks -nomaster -nowatchdog -nocrashdialog -enablefakeip.

   • Linux specific additions: -glslcontrolflow -arbmode.

3. Go to the releases section and grab the newest zip.

4. Open the zip and run 'vusaline_installer.exe'; change the prompted directory if incorrect.

5. That’s it! Go out there and play TF2!

Extra steps

1. Use Team Fortress 2\tf\custom\zzz_vusaline_base\options.cfg to configure Vusaline.

2. Use class configs? Move them to Team Fortress 2\tf\cfg\class.

3. Use a custom autoexec? You can find it as autoexec2.cfg. If you haven’t, you can create it to make aliases and change cvars like:

   • FPS cap:

     • fps_max

     • Keeping it higher than your monitor’s refresh rate is highly recommended

   • Motion Blur:

     • mat_motion_blur_enabled 1 then mess with mat_motion_blur_strength

   • Contrast for fullscreen mode (only):

     • mat_monitorgamma

     • Allowed range: From 1.6 up to 2.6

   • Killfeed time (in seconds):

     • hud_deathnotice_time

   • Killstreak feed time (in seconds):

     • cl_hud_killstreak_display_time

   • If in need of more FPS, set the following for GPUs with a "G3D Mark" of ⇐1365:

     • Turn off anisotropic filtering for textures (makes textures low-res looking & ugly)

     • mat_forceaniso 1

4. Instead of using -high, use Process Lasso or Process Hacker to set hl2.exe’s affinity to always exclude CPU 0 (if you only see 4 checkboxes, avoid this), and hl2.exe’s priority to High.

Avoid the following

• Putting spaces in options.cfg, such as dualcore = 1(incorrect) instead of dualcore=1(correct).

• Using transparent viewmodel support in your HUD:

  • Potential to mess with world props: https://youtu.be/fg5eBkmVS1c

  • Adds another HUD animation, which will impact frametimes.

• Using block_crash_reporting=0 without removing the -nobreakpad launch option.

• The following mods will cause instability:

  • Robot animation fixes (by sigsegv).

• Don’t execute commands you don’t know! It can get you banned on community servers if you execute say "fm_attackmode" (which doesn’t exist, but a cheat used it at some point).