• TF2 Sprays dont actually work even with sv_pure -1?? Repost.Old post 3 days ago
    14 replies, posted
Do sprays work for someone? I have been trying to get them to work on my dedicated server but no matter what variant of sv_pure I use, the sprays are not shared between clients. Clients can only see eachothers sprays if the spray has been seen before (on a diff server for example). Otherwise they can only see their own spray and for everyone else its invisible. I have seen people say that this is a common problem, however if that was the case I think there would have been a bigger outcry about it? If anyone knows this problem and can help me find a solution please shoot me a message. However otherwise id just like to discuss why this would be happening. I really enjoy sprays on my servers and the whole point of my server was to remove many of the dumb restrictions valve put on the official ones (and bringing back legacy stuff like replay and 8 bomb sticky jumpers). More info from last post: cl_playerspraydisable is set to 0 sv_allowupload 1 sv_allowdownload 1 is set too.
What's the level of you "mp_decals" ? I think you need to have it over 24 or 200 (wild numbers I know) for sprays to appear. For example: If the value is too low, the spray will appear and then be replaced when another decal pops upl, such as bullet holes. Set "mp_decals 200", then go to a community server, put your spray and fire the Scattergun next to it.
I set it to mp_decals 600. I am gonna try it on a diff server but it doesnt help on mine
Sparys work on valve serves if that is what you are asking the cl_playerspraydisable 0 becouse that comand is only client side server side it only matters if sv_allowupload 1 sv_allowdownload 1 is enabled so basicly this is the only thing thqt matters
Im talking about my own dedicated server... I am trying to get it to work on my own server that I bought.
Can you show us your server's config? (autoexec.cfg, server.cfg, ..)
This might be a bit outdated because I pulled it from a post I made days ago and the server gets changed a lot however it should still be pretty accurate hastebin
I don't think anyone ever figured out the deal with sprays. there's just no pattern.
The config looks fine to me You can try to set the convar "developer" to 1 (on client and server) When you join the server, tell us whether you can see following messages: File 'user_custom/bla.dat' requested from server ip:port. File uploading disabled. Downloading file 'user_custom/bla.dat' from client name failed.
File 'user_custom/31/31ab24c6.dat' requested from client 89.64.55.15:64621. CreateFragmentsFromFile: 'user_custom/31/31ab24c6.dat' doesn't exist. This is what I found. Its not that message but its definitely the error... Seems the upload doesnt even finish or the file isnt being created on the server side??
Can you spot the .dat file in your tf/download/user_custom/ folder? (server and client)
31ab24c6.dat (this is the one from my client) https://files.facepunch.com/forum/upload/114269/fb9509bb-6dee-4cea-9b1f-81671fbee7aa/image.png Un https://files.facepunch.com/forum/upload/114269/7eb2ae41-ac34-488d-8704-e47dd4b9f892/image.png Unfortunately it seems the server doenst even have the folder its supposed to be in? (there is no "31")
Are the convars cl_allowupload and cl_allowdownload enabled (client)?
No they werent! Now I cant confirm this yet cause I cant test it atm with friends but I havent seen the usual error when I joined this time. The "31" folder wasnt there, however there was atleast one added when I hit refresh. Seems like the file atleast arrived at my side for now. Dang shame that its a cl_ command though. If this is the solution wed need a PSA or something about it so people actually know what to set to see sprays and shit on community servers.
Ayy that did actually fix it atleast for me (ppl were able to see my sprays). My friend still had problems with his spray but well have to check if there is a problem with the spray itself (for him the server still said that the data file was missing)
Sorry, you need to Log In to post a reply to this thread.