Hey, so i'm attempting to add a few custom particles to my map. Created the map particle_manifest file in the map folder and added the pcf to the particles folder as directed. The issue was I couldn't find a particles folder in the Team Fortress folder so created my own at: common/Team Fortress 2/tf/particles.
However when i compile and run the map the console displays;
Code:
Attempted to precache unknown particle system "particle"
CParticleMgr::LevelInit: Manifest 'maps/72hour_2_particles.txt' contains a particle file
'thw_river/.pcf' that's not under the particles directory. Custom Particles must be placed
in the particles directory.
From reading it, it's clear the particles folder I made is in the wrong place, but does anyone know where it should go?
tf/particles is the correct place for the folder. It looks like your name has a / in it which could be screwing things up and making the game read you particle name as a folder.
If that's not the problem, what is the name of your pcf?
The last one there being the custom one I made. Both that file and particle_ash.pcf were in the particles folder.
You were right for creating it. Some folders don't exist since a lot of the files are all packed into .vpk files. The particles are there too.
My guess is this:
I'll need to double check, but pretty certain that was an error on my part when copying the console's log into the post. Pretty certain there's no backslash in the actual file name.
The last one there being the custom one I made. Both that file and particle_ash.pcf were in the particles folder.
You were right for creating it. Some folders don't exist since a lot of the files are all packed into .vpk files. The particles are there too.
My guess is this:
you put it in the map folder instead of the particles folder. Change it and see if it works.
Ah thanks, i've give those suggestions a try! Quick (and possible stupid) question though; i've noticed this with other examples, but why do you put an "!" before the file path?
If this is your first time logging in after the migration (Feb 8, 2022), you must reset your password to log in. Follow this guide if you're having trouble