[king kong]

Originally Posted by Skyy There's obviously a language-barrier here or you simply don't understand what's being asked. Anyone reading your response to my post would probably be even more confused if they were coming here for the same problem. Tickrate enabler is supposed to unlock client rates and while it sets the server tickrate successfully, it does not do the latter as advertised. As client rates are still locked to 30,000, something is wrong with the current version of Tickrate Enabler on linux. I'm going to wait for a response from someone (probably satanic_spirit) who knows this stuff.

Maybe I misunderstood your question. It seems that this is only the case with Linux.

https://forums.alliedmods.net/showpo...2&postcount=52

https://imgur.com/a/HWZk2vH

[Skyy]

Originally Posted by king kong Maybe I misunderstood your question. It seems that this is only true in Linux. https://forums.alliedmods.net/showpo...2&postcount=52 https://imgur.com/a/HWZk2vH

Yeah, after re-reading my post, I could have probably worded it better.

Yes, this is it. So, it is true; Tickrate Enabler does not unlock min/max rates on linux. RIP.
Guess I'll have to look into changing it to a windows server. That sucks.

[Lux]

Originally Posted by king kong Maybe I misunderstood your question. It seems that this is only the case with Linux. https://forums.alliedmods.net/showpo...2&postcount=52 https://imgur.com/a/HWZk2vH

Appears to function fine on linux

[Spirit_12]

I'll have to side with Lux. As he showcased it works on Linux and has been working on my server as well.

[Skyy]

Originally Posted by Lux Appears to function fine on linux

Yes, the correct values are shown in console when using status, but not on net_graph and when setting a rate above 30,000, it gives the red notice.

[Spirit_12]

My netgraph shows 60 60 and I'm using the build from Accelerator's repo.

Also that message that you are getting might just be client side. I would suggest looking at netgraph.

[Skyy]

Originally Posted by Spirit_12 My netgraph shows 60 60 and I'm using the build from Accelerator's repo. Also that message that you are getting might just be client side. I would suggest looking at netgraph.

I'm actually not sure how to really read this graph, though I want to think that it's just a client-side notice and the rates are being properly set, since the inbound at one point jumped to 56 k/s while the out was > 30 k/s.

I think this graph is telling me I still have some optimizations that I can make to my code, which is great news! The day it's no longer refactorable is the day my heart breaks a little bit.

[Spirit_12]

What are your client side rates set to?

[suptob]

L4D1 had an update today and it looks like this plugin is broken on my updated Linux server, I'm getting the following error on boot up:

"Patch Failure: CVomit::UpdateAbility() Patch Offset incorrect."

Any idea how to find the correct offset or get this updated?

Edit:
I've been messing around with IDA/Ghidra to figure out the new offsets that have changed on the server and engine file. I've put them down below on all the changes I found, I'll try and compile it later tomorrow to see if it works.

_ZN6CVomit13UpdateAbilityEv
====
Old Start = 002A3C26
Old End = 0x2a3FAC
New Start = 002A8932
New End = 002A8CF3
g_FrameTimeReadOffsets[] = 0x3C1


ZN8CNetChan11SetDataRateEf
====
Old Start = 0015274e
Old End = 0015276C
New Start = 00160bc2
New End = 00160be3
CGAMECLIENT_PATCH_OFFSET = 0x21


_ZN11CGameClient7SetRateEib
====
Old Start = 00191d3a
Old End = 00191D87
New Start = 0019fede
New End = 0019ff2a
CGAMECLIENT_PATCH_OFFSET = 0x4C


NOT CHANGED _Z15ClampClientRatei
====
Old Start = 0019357a
Old End = 001935BA
New Start = 0019ec0e
New End = 0019ec41
CLAMPCLIENTRATE_PATCH_OFFSET = 0x40