Ive downloaded the explosion_original.vpk file and placed it in my custom folder. There are now 2 files there; explosion_original.vpk and explosion_original.sound.cache. However it doesn't actually work in game it still keeps the smoke that comes originally with the game. I run in dx8, not sure if that has an impact on it. Can someone help?
Explosion effects
posted in
TF2 General Discussion
Ive downloaded the explosion_original.vpk file and placed it in my custom folder. There are now 2 files there; explosion_original.vpk and explosion_original.sound.cache. However it doesn't actually work in game it still keeps the smoke that comes originally with the game. I run in dx8, not sure if that has an impact on it. Can someone help?
Are you using vtf crosshairs
Also link the thread you've downloaded the file from
Are you using vtf crosshairs
Also link the thread you've downloaded the file from
Also link the thread you've downloaded the file from
deguAre you using vtf crosshairs
Also link the thread you've downloaded the file from
Yes im using vtf crosshairs.
[quote=degu]Are you using vtf crosshairs
Also link the thread you've downloaded the file from[/quote]
Yes im using vtf crosshairs.
Also link the thread you've downloaded the file from[/quote]
Yes im using vtf crosshairs.
RobbeeI made my custom folders using this tool. It works 100% on dx8 or higher
https://cfg.tf/tools/crosshairs/
https://i.imgur.com/KSR0Rck.png
Thankyou, this worked.
[quote=Robbee]I made my custom folders using this tool. It works 100% on dx8 or higher
https://cfg.tf/tools/crosshairs/
[img]https://i.imgur.com/KSR0Rck.png[/img][/quote]
Thankyou, this worked.
https://cfg.tf/tools/crosshairs/
[img]https://i.imgur.com/KSR0Rck.png[/img][/quote]
Thankyou, this worked.
For anyone else stumbling on this thread through google:
TF2 weapons have txt files assigned to them which contains a lot of their attributes. For example tf_weapon_rocketlauncher.txt
You can change the particles of the explosions of weapons like the rocket launcher to any other particle in the game through this file by changing it to a valid particle in the //buckets section.
These files are also used by the community to get any custom crosshair by using VTF crosshairs (Valve Texture File, a way Valve packages images).
If you install a VTF crosshair pack and a smaller explosion pack seperately you'll have 2 txt files that overwrite eachother. So you'll either have your crosshair or your explosion. Not both.
The tool posted above can make txt files that already contain both.
Alternatively you can merge these together manually (which is what people did before this tool and i still do it manually myself).
Just copypaste //buckets or //crosshairs into the other txt file, save the txt file, remove the other incomplete txt file, restart TF2.
If you have both txt files open it's easy to see the differences between them and what needs to be pasted into the other file
tl;dr: make sure you don't have VTF crosshairs + smaller explosions. They conflict.
If you do, then compare the txt files of explosive weapons and merge them together or use the tool posted by Robbe a few comments above. Look for the //buckets and //crosshair sections in the txt files
For anyone else stumbling on this thread through google:
TF2 weapons have txt files assigned to them which contains a lot of their attributes. For example tf_weapon_rocketlauncher.txt
You can change the particles of the explosions of weapons like the rocket launcher to any other particle in the game through this file by changing it to a valid particle in the //buckets section.
These files are also used by the community to get any custom crosshair by using VTF crosshairs (Valve Texture File, a way Valve packages images).
If you install a VTF crosshair pack and a smaller explosion pack seperately you'll have 2 txt files that overwrite eachother. So you'll either have your crosshair or your explosion. Not both.
The tool posted above can make txt files that already contain both.
Alternatively you can merge these together manually (which is what people did before this tool and i still do it manually myself).
Just copypaste //buckets or //crosshairs into the other txt file, save the txt file, remove the other incomplete txt file, restart TF2.
If you have both txt files open it's easy to see the differences between them and what needs to be pasted into the other file
[b]tl;dr[/b]: make sure you don't have VTF crosshairs + smaller explosions. They conflict.
If you do, then compare the txt files of explosive weapons and merge them together or use the tool posted by Robbe a few comments above. Look for the //buckets and //crosshair sections in the txt files
TF2 weapons have txt files assigned to them which contains a lot of their attributes. For example tf_weapon_rocketlauncher.txt
You can change the particles of the explosions of weapons like the rocket launcher to any other particle in the game through this file by changing it to a valid particle in the //buckets section.
These files are also used by the community to get any custom crosshair by using VTF crosshairs (Valve Texture File, a way Valve packages images).
If you install a VTF crosshair pack and a smaller explosion pack seperately you'll have 2 txt files that overwrite eachother. So you'll either have your crosshair or your explosion. Not both.
The tool posted above can make txt files that already contain both.
Alternatively you can merge these together manually (which is what people did before this tool and i still do it manually myself).
Just copypaste //buckets or //crosshairs into the other txt file, save the txt file, remove the other incomplete txt file, restart TF2.
If you have both txt files open it's easy to see the differences between them and what needs to be pasted into the other file
[b]tl;dr[/b]: make sure you don't have VTF crosshairs + smaller explosions. They conflict.
If you do, then compare the txt files of explosive weapons and merge them together or use the tool posted by Robbe a few comments above. Look for the //buckets and //crosshair sections in the txt files
Please
sign in through STEAM
to post a comment.