-
Notifications
You must be signed in to change notification settings - Fork 1
/
_README.txt
104 lines (86 loc) · 5.9 KB
/
_README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
https://github.com/a-horsey/horsies-viewmodel-editor
Welcome to Horsie's Viewmodel Editor!
To change the settings, open the settings.txt files for each class.
For example, to change scout settings open settings_scout.txt
To apply the settings, run GENERATE.bat
If you're having issues running it, such as seeing errors when generating,
please scroll to the bottom for a list of issues and fixes.
Preloading, Fixed Viemodels and Custom Animations support:
1. Preloading allows you to use these viewmodels in any server, regardless of sv_pure.
This includes fully automated preloading at game start, it's highly recommended but toggleable.
It will not mess with your autoexec or other game files.
2. Fixed Viewmodels is a mod that fixes hundreds of default animations (https://gamebanana.com/mods/206440)
This mod is fully supported and easy to install - just drop the vpk in "fixed viewmodels addon".
More instructions and a direct link can be found in that folder.
All credits for creating it go to the author.
3. This also supports mods that change the viewmodel animations.
Simply drop any viewmodel animations mods in the "custom animations" folder.
I suggest reading "INSTRUCTIONS.txt" in that same folder
The mods will be automatically checked and installed next time you run GENERATE.bat
Incompatible mods will be deleted from the folder.
Here are some of the settings:
1. Changing positions:
You can change the positions of weapons on X, Y and Z axis.
To see what each axis does, please check guide_position.png in this folder.
2. Changing rotations:
You can change the rotations of weapons on X, Y and Z axis.
To see what each axis does, please check guide_rotation.png in this folder.
3. Hiding weapons:
There is a setting for each weapon that lets you hide that particular weapon.
Additionally, you can choose to keep specific animations of that weapon visible.
Such as: draws, reloads, attacks and more. More info below.
4. Making animations static:
When you make an animation static, it makes that animation not move and
behave exactly like the idle animation.
All animations such as draws, reloads, attacks and more can be made static.
5. Removing the left arm:
You can remove the left arm from most weapons by enabling "Remove_left_arm" for that weapon.
This option is present even for weapons with no visible left arm, because it can be used to
remove glitches at high viewmodel_fov values or for some custom animations that add the arm back.
6. Weapon-specific settings:
There are some settings that are specific to certain weapons.
Such as removing shell ejection or some fancy spy knife settings.
More in-depth information:
1. The animations you can keep visible or turn static are:
•Draw animations - these play when you just switched to that particular weapon.
•Reload animations - these play when you reload the weapon.
•Attack animations - these play when you're attacking with the weapon.
•Secondary attack animations - these play when you're doing the secondary attack, usually by pressing mouse2.
•Idle animations - these play when the weapon is idle.
Enabling the option "•More_static_idle" will make the idle not sway when standing still.
(the weapon will still sway when moving, as that is hardcoded)
•Some special animations such as backstabs, backstab detections, shortstop shove etc..
2. A list of some weapon-specific settings:
•Mediguns:
Keep_beam_visible - keeps the heal beam visible if weapon is hidden.
(always visible if attack is not hidden)
•Flamethrowers:
Keep_flames_visible - keeps the flames visible if weapon is hidden.
(always visible if attack is not hidden)
•All spy knives:
Keep_backstab_detection_visible - keeps the backstab detection (knife rising up) visible if weapon is hidden.
Keep_backstab_visible - keeps the actual backstab visible if weapon is hidden.
Instant_backstab_detection - makes the knife instantly rise up as soon as you can backstab someone.
Replace_backstab_with_normal_attack - replaces the actual backstab animation with one of the regular attacks.
Static_backstab_detection - makes the knife not move when you can backstab someone.
Static_backstab - makes the knife not move when actually backstabbing someone.
•Shotguns, scatterguns, sniper rifles:
Remove_shells - makes the weapon not eject shells when reloading/attacking.
•All weapons that shoot bullets (except the sniper rifle):
Keep_tracers_visible - keeps the tracers visible if the weapon is hidden.
(disabling this will cause console errors when shooting, but they're harmless)
Issues and potential fixes:
1. Errors such as "X command not found" or "No such file or directory"
Commands not behaving properly are usually caused by your Windows' PATH and PATHEXT variables being messed up.
It can be caused by programs editing them, usually without your knowledge. And they can affect other batch files as well.
Usually a messed up PATH will only result in errors related to the "find" command. While a messed up PATHEXT will result in
a lot of errors being spammed, like "X command not found".
To check your environment variables, navigate to:
"This PC", right click > properties > Advanced system settings > Environment Variables (under the "Advanced" tab)
From there just check the PATH and PATHEXT variables, the windows defaults are usually:
For PATH: "C:\Windows;C:\Windows\System32;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0"
For PATHEXT ".COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC"
Warning: Be careful when editing PATH, as some programs DO need it. Only make changes if you have to.
2. Other errors
Currently there are no other issues with running it on Windows, at least not that I am aware of.
If you're having problems please open a GitHub issue(ideally this) or leave a comment on Gamebanana.