Thu, 08/27/2009 - 10:07
Crazy Particle Glitch

lol.
Oh and if anyone actually knows what causes this I would be very grateful. I've been hosting servers a long damned time and this is the first issue to really stump me.

lol.
Oh and if anyone actually knows what causes this I would be very grateful. I've been hosting servers a long damned time and this is the first issue to really stump me.
I was going to mention how my early attempts at replacing the flamethrower sprite caused exactly this to happen due to valve's somewhat retarded handling of bitstripping, but then I saw that the last post was in august and by now it's either likely gone away entirely or been solved.
However, since it's possibly nine am and I have not slept since saturday, I shall not hesitate to post.
also, boot up your xbox and sign into live!
Did you even bother to check the Valve developer wiki. I'm a skinning noob to be honest, but even I figured it out because I fucking researched.
Also quit stealing Daimao's hats. Everybody knows.
Everybody knows? What are you in fourth grade?
Easy Bake Oven... go clean it.
It's not a skin issue, it's server-wide and completely unrelated to either custom particles (of which there are none) or custom skins (because people running totally vanilla get it too).
And stop listening to hearsay, the hats have always been and will always be freely available to anyone on my server. Period.
Might wanna try and reinstall, I know in the last 2 or 3 tf2 updates there was stuff in them for particle updates. Atleast try and update again maybe.. One of those last few updates may have borked something..
08/21/09 update:
08/13/09 update
Particle files are now protected by sv_pure
http://store.steampowered.com/news/?term=team+fortress+2+update
It's a mix of client and server interaction, I know that much. Something on the server goes wonky and triggers it, but the problem is actually on the client. Restarting your game will fix it, until the server triggers it again. In a related issue, custom models (hats, primarily) will appear with missing textures until the server is rebooted.
I originally thought this was just the whitelist fucking up, but it occurs with sv_pure 0 and consistency disabled. The frequency of bugging out doesn't seem affected by pure setting either.
I actually know what causes this from an internal perspective.... It's either a texture coordinate problem (i.e., the texture coords are wrong, such that instead of drawing one frame of that texture, it draws the entire texture across the quad for the particle) or it's a wrap mode issue (the wrap mode is wrong, so it ends up grabbing the whole texture). As for what's causing it at the earliest level, it could be a few things. The first being that the coords are just wrong in the shader (unlikely), second being that some software is conflicting with TF2 and causing the coords passed from CPU to GPU are wrong (unlikely), and third being that some quirk of the video card itself is causing the coords to be wrong (more likely). The way to fix it usually would be to edit the shader and fix whatever texcoords are going into the texture sample. As for how to fix it in TF2, no idea.