Hey guys, not sure if anyone's done anything like this for in-game, but I setup a viewmodel on/off script so that you can change which of your slots' viewmodels are on/off depending on which slot you are on while in-game. If you have a keypad or a way to emulate keypad presses, this is the script for you.
I bound all of the buttons that configure your viewmodels to the numpad, and the way that I wrote it makes it quite hard to change the binds. For you that care about performance, I haven't experienced any performance changes with this script personally.
Binds:
https://imgur.com/a/7WzrIAI
Download:
Show Content
https://gist.github.com/armostsscrean/f0ffa7b1776a61de143638bba7f22867
Download this as a ZIP and paste all of the .cfg files into your cfg folder. After this, you will need to put "exec 3slots"in your configs for the characters with 3 slots, "exec 4slots" into the spy's config and "exec 5slots" into the engineer's config file.
Hey guys, not sure if anyone's done anything like this for in-game, but I setup a viewmodel on/off script so that you can change which of your slots' viewmodels are on/off depending on which slot you are on while in-game. If you have a keypad or a way to emulate keypad presses, this is the script for you.
I bound all of the buttons that configure your viewmodels to the numpad, and the way that I wrote it makes it quite hard to change the binds. For you that care about performance, I haven't experienced any performance changes with this script personally.
Binds:
https://imgur.com/a/7WzrIAI
Download:
[spoiler]https://gist.github.com/armostsscrean/f0ffa7b1776a61de143638bba7f22867
Download this as a ZIP and paste all of the .cfg files into your cfg folder. After this, you will need to put "exec 3slots"in your configs for the characters with 3 slots, "exec 4slots" into the spy's config and "exec 5slots" into the engineer's config file.[/spoiler]
A neat idea but seems a little complicated / too much work to use in my opinion. Its much more convenient to use yttrium's competetive viewmodels. In there you can choose if you want to hide shotgun for soldiee but keep banners visible, as they use the same weapon slot. Or you can just use "bind "r" incrementvar r_drawviewmodel 0 1 1" f.ex to hide all viewmodels and turn them back on with 1 button.
A neat idea but seems a little complicated / too much work to use in my opinion. Its much more convenient to use [url=http://www.teamfortress.tv/34834/yttriums-competitive-viewmodels]yttrium's competetive viewmodels.[/url] In there you can choose if you want to hide shotgun for soldiee but keep banners visible, as they use the same weapon slot. Or you can just use "bind "r" incrementvar r_drawviewmodel 0 1 1" f.ex to hide all viewmodels and turn them back on with 1 button.
PaiCA neat idea but seems a little complicated / too much work to use in my opinion. Its much more convenient to use yttrium's competetive viewmodels. In there you can choose if you want to hide shotgun for soldiee but keep banners visible, as they use the same weapon slot. Or you can just use "bind "r" incrementvar r_drawviewmodel 0 1 1" f.ex to hide all viewmodels and turn them back on with 1 button.
Yeah, I didn't know what I was doing with this script and I made it like two years ago (btw it took it took so long to write out) when I had this thought. It's more of something that you would set at the start of a life and then just leave on.
[quote=PaiC]A neat idea but seems a little complicated / too much work to use in my opinion. Its much more convenient to use yttrium's competetive viewmodels. In there you can choose if you want to hide shotgun for soldiee but keep banners visible, as they use the same weapon slot. Or you can just use "bind "r" incrementvar r_drawviewmodel 0 1 1" f.ex to hide all viewmodels and turn them back on with 1 button.[/quote]
Yeah, I didn't know what I was doing with this script and I made it like two years ago (btw it took it took so long to write out) when I had this thought. It's more of something that you would set at the start of a life and then just leave on.