WTF Crits?!?!
January 15, 2008
As many already noticed there is a problem with TFTrue after newest TF2 update. On almost every server TFTrue doesn’t work anymore and you got Crits.
As it looks like only on Windows Server TFTrue is still working perfectly, Kompaniet and syre mentioned they have no problems after the patch and both got Windows-Clan-Server.
Anyway, we hope redcomet will publish a working update pretty fast.
Since that of course you can delay your ETF2L match. We please every team who got a game in the next days to contact your opponent and speak about the issue. If both teams agree to play the game with crits under the current circumstances you can surely do that.
Edit: As it looks like a TFTrue Update will be released in the next 2 days. We recommend to postpone your league games until update is released; it will be no problem to play this week’s game in the upcomming two weeks.
Posted by 
content rss
Pray to our god named Redcomet, curse the devil named Valve!
I think we might have a fix for the “heavy still critting despite of tftrue” bug.
tftrue_crit_chance 0
tftrue_melee_crit_chance 0
tftrue_crit_multiple 3
I think the last cvar – tftrue_crit_multiple – needs to be changed to 0.
If i interpret this settings right, the last cvar just multiplies the dmg a crit will do – with this settings, a critical hit will do 3times the dmg of a normal shot.
If we change this to 0 – every critical shot does the same amount of dmg as a normal hit.
So – even if TFTrue was still buggy and a Heavy could score crits from time to time, they would to exactly the same dmg as non-crit hits.
Can anyone confirm that?
Regards
Riemu
Riemu you also know that tftrue_crit_multiple 0 makes it impossible to kill someone with a headshot right ?
Yeah you are right Riemu, but as lezek said – setting the multiple to 0 also gimps the sniper headshots :(
set MULTIPLY to 1.
If u set it to 1 it still wont allow headshots with sniper.
it needs to be 3 inorder for sniper hs to work properly
Check this link.
It isn’t just Linux servers that are broken by the looks of things.
Quote from the tftrue author:
Ok right off the bat I updated my windows server and the plugin reported that it could not find the first critical strike variable. Meaning that valve changed some of the critical strike code and my scanning does not recognize it. However the only thing broken is that one variable, so your servers will run everything correctly minus the chance for a regular shot to crit. I will post an update tonight. I will also fix the setting tftrue_static_damage 0 in the config problem as well.
Source: http://www.trypants.com
So there should be a fix soon and it does indeed effect windows and linux.
If anyone need a tftrue working server to borrow, we (Kompaniet) can borrow ours for etf2l matches if we’re not using it ourselves. It’s located in sweden on a dedicated 100Mb fiber. Just talk to me in #kompaniet on irc.quakenet.org.
^^ Same with ours. PM me in #phonetic and i’ll setup and rcon for you. It is in use tonight and tommorrw night however.
I thought I’d post the update from redcomet, the tftrue author for those not following on his site:
“sorry for being a bit late, got caught at work today and my virtual machines are not working. So firstly I need to get them working so I can test out the new code and should be all set. (Hopefully new binaries by midnight cst)
EDIT:
Got into the files and looked around and the crit code did change. However it appears that nothing was added or removed, more like code was moved around. I made the new windows offsets, and changes the sigs to be more change resistant, but only so much can be done when they move code around like that and cause the compiler to rewrite these sections.
I will be compiling and testing windows tomorrow and finish linux in the evening after work.
Thank you for your patience”
Great news
Great news indeed..
Another update posted earlier today:-
“Ok well I have the new offsets and the first windows test went fine. I just have to compile both versions now, test each one and it will be done. The second valve update this week killed my previous progress, but now I am just wrapping things up.
Thanks again for your patience”