AnAkkkReleased an update to fix the auto updater.
<3
Account Details | |
---|---|
SteamID64 | 76561197960497430 |
SteamID3 | [U:1:231702] |
SteamID32 | STEAM_0:0:115851 |
Country | Netherlands |
Signed Up | October 13, 2012 |
Last Posted | June 23, 2025 at 8:46 AM |
Posts | 733 (0.2 per day) |
Game Settings | |
---|---|
In-game Sensitivity | |
Windows Sensitivity | |
Raw Input | |
DPI |
|
Resolution |
|
Refresh Rate |
Hardware Peripherals | |
---|---|
Mouse | |
Keyboard | |
Mousepad | |
Headphones | |
Monitor |
AnAkkkReleased an update to fix the auto updater.
<3
If possible, retest with a wire, because those are some 90s speeds you're getting currently.
Explain why you think a different router will fix the described problem.
I could suggest some high speed OpenWRT router with proper SQM support, but if your internet line is shit, it won't help a bit.
Is your measured speed truly 8.5 megabytes down and 0.4 megabits up?
To get the best advice, please fully describe how you are connected to the internet. Starting at the wall, connection type, modem, router, switches, cables, powerline adapters, etc.
turbochad69ArieMade by Chris, of chrisconfig fame: https://github.com/cdown/mac-celThis probably won't work on recent osx versions since that IOHIDLib stuff was deprecated in 10.11 or 10.12 (4-ish years ago)
I've last used it in 10.13 when there were still proper nvidia drivers for OS/X
Made by Chris, of chrisconfig fame: https://github.com/cdown/mac-cel
AimIsADickThe mastercomfig documentation leaves out some tips like chaning DNS servers...
I'd hope so, cause he knows what he's talking about.
eu.voice.tf isn't the actual mumble server address I guess? Because that hostname currently resolves to 23.227.167.56 in Dallas and pings like you'd expect from EU.
If it is expected, I can provide you an actual EU server to use instead for this project.
Sometimes, when certain things become self-aware, they need to be incinerated. Like printers, old stuff from the fridge and shitposters.
First of all, the tool that suggests you're being routed through US/BR is using geoip information that seems to be incorrect (also you'd ping much higher than 100ms). But you are suffering from poor routes through Sweden and Poland, which is not ideal if you're from Croatia.
Your Dutch/i3D route (Bolus/KroketBrigade) looks alright:
Zagreb->Vienna->Munchen->Frankfurt->Amsterdam->Rotterdam.
Pretty much what you can expect, mostly a direct route.
Your German/Hetzner route goes via Stockholm adding 2x1200KM to the route:
Zagreb->Vienna->Stockholm->Frankfurt->Nuernberg
Your French/OVH route goes:
Zagreb->Vienna->Bratislava->Warsaw->Amsterdam->Gravelines
This is beyond dumb.
The three German machines are located with two different datacenters. DusselBrigade is myloc.de, Fakkel/NewBrigade are at Hetzner. The two Dutch machines are located at i3D in Rotterdam. Baguette/PhoenixBrigade are with OVH in France. We purposefully use a bunch of different datacenters, so there's always one that pings/routes well.
tl;dr your ISP saved a buck or two on routing
https://i.imgur.com/DE9Gu9O.png
L 03/17/2021 - 20:31:42: "Zucch1n1<6><[U:1:928918444]><Blue>" say "he is prem"
L 03/17/2021 - 20:31:56: "Zucch1n1<6><[U:1:928918444]><Blue>" say "we can create some drama"
L 03/17/2021 - 20:32:57: "Zucch1n1<6><[U:1:928918444]><Blue>" say "I should probably post this somewhere"
L 03/17/2021 - 20:34:11: "SynciNG<4><[U:1:31914324]><Blue>" say "yeah"
L 03/17/2021 - 20:34:17: "SynciNG<4><[U:1:31914324]><Blue>" say "let's that bitch cry more"
Big brain alts
Well....for the first time in 20 years of hosting gameservers, one actually burned to a crisp xD
We have a major incident on SBG2. The fire declared in the building. Firefighters were immediately on the scene but could not control the fire in SBG2. The whole site has been isolated which impacts all services in SGB1-4. We recommend to activate your Disaster Recovery Plan.
Update 5:20pm. Everybody is safe.
Fire destroyed SBG2. A part of SBG1 is destroyed. Firefighters are protecting SBG3. no impact SBG4.
https://twitter.com/olesovhcom/status/1369504527544705025
RIP CroissantBrigade
Update: Welcome PhoenixBrigade, 10 gameservers to replace the ones that are now a puddle of molten metal.
It's a VA panel, most of those have lots of black smearing. The VG248QE you're used to is a TN panel. Get an IPS or TN panel instead (or a Samsung Odyssey VA panel).
100 tick wasn't tested at the time, no, at least on serveme.tf. It should be easier to run, still I'd plan for 50% higher CPU usage, which might be an issue on some machines and VPS-es. Server CPUs are typically many cores at lower clocks, and with HLDS/TF2-server being very single threaded that's an issue for (at least) HL matches at these higher tickrates.
Most people didn't feel 133 tick was a huge improvement, so I expect 100 tick to be at least equally underwhelming. Also, the bugs you describe are the same as for the 133 tick experiment, so the other ones are probably also still there, which I expect to be a deal breaker for the competitive community and leagues.
If you're looking to revive that experiment, I'd just aim for 133 tick instead. Let me know if you'd like a server set up for that in one of the serveme.tf / na.serveme.tf locations, that way you could try and organize some scrims to test it.