[
silkyiet3]
Quote:
19.12.2010: Esteamation causes server crashes with latest TF2 update on Windows srcds.
Cannot confirm - Current TF2 works just fine on Windows with eST
[
IonXP]
Quote:
19.12.2010: ...and latest l4d2 engine update
Confirmed. Current L4D2 on Windows crashes with eST+ CB Control during client connect without BINCACHE and crashes during start-up with BINCACHE
Cause: Misdetection of PostCallbackInternal
Status: Adjusted search range. If it's not found within suggested range then heuristics will fail(CB Control will not be activated) - This will prevent using erroneus locations and malfunction. CB System adjusted to support new steamclient from L4D2 and as of CURRENT TRUNK(03.02.2011) of eST CB-Control works fine without problems.
[
Waats]
Quote:
12.01.2011: Vityan
Notice that KF servers needs to be patched with VUP/UGSP. Otherwise cracked clients will be kicked after a few minutes
Youve referenced quite old post from csmania - It was before ive added KF steamclient support to CB:Control extension(Somewhere btw RC7 and RC8 - dont remember exactly).
[
All]
Current changes for TRUNK:
1) Added support for latest items system for TF2(Credits to bir3yk - our items geek) to SCI/STEAM3.
2) Added support for latest steamclient 2009 from bir3yk with TF2 items to SCI/STEAM3(Client uses new list format).
3) Added support for steamclient 2009 builds of bir3yk with 152-byte tokens(The same old RevEmu 4-Th Gen from eST_STEAM2 module) to SCI/STEAM3.
4) Updated CB-Control heuristics to be more strict(fail if something is suspicious or inconsistent) and added support for newv steamclient.dll libraries(Especially from L4D2).
5) Fixed buffer overflow vulnerability then client provides some item in it's list not present in server's eST XIS-DB. [SECURITY]
6) Fixed erroneus free during NSNet server thread start-up on Windows. [STABILITY]
Known issues:
1)Ppl reported that sometimes they see lot's of filtered "No Steam Logon"(Problems with Steam Connection" messages from one client following each other with high right and then resulting in server crash - The issue should be tracked down(Issue is rare but considered release critical). [STABILITY]
That's all for now. Next version is targeted to be 2.0 FINAL