Nothing wrong with the late payment arrangement, that way more teams can play and banny gets more money at the end of the season.
Account Details | |
---|---|
SteamID64 | 76561197960497430 |
SteamID3 | [U:1:231702] |
SteamID32 | STEAM_0:0:115851 |
Country | Netherlands |
Signed Up | October 13, 2012 |
Last Posted | November 21, 2024 at 11:14 AM |
Posts | 722 (0.2 per day) |
Game Settings | |
---|---|
In-game Sensitivity | |
Windows Sensitivity | |
Raw Input | |
DPI |
|
Resolution |
|
Refresh Rate |
Hardware Peripherals | |
---|---|
Mouse | |
Keyboard | |
Mousepad | |
Headphones | |
Monitor |
mane..although I had to keep the tftrue.vdf file in order to make it work.
The .vdf file makes your server load the plugin, so you'll need it to make it work.
albaCan someone explain why Bottas got a 10 place grid penalty for 5th engine while Verstappen starts last with his 4th engine? Is it a new spec engine Verstappen is gonna be running or something? Also Latifi starting 18th and he took the penalty quite late right?
VER took 6 new elements, causing a grid drop of more than 15 places, which means you start at the back of the grid.
BOT took 3 new elements, causing a 15 place grid drop.
This was looking like the most boring qualifying this season, and then Russel put on the slicks
AlexKikLinks is not working(
Update the links!
https://github.com/F2/F2s-sourcemod-plugins
All here, as a package or individually
_flac(as any one persons poor connection can effect everyone elses experience)
I think this is a common misconception, the high ping of one (or even most) other players won't affect your experience by itself. John Carmack got it mostly right back in 1996.
The "teleporting timmy" example is way more annoying for other players, but a ping limit doesn't fix that.
The rule shouldn't exist at all.
hpqoeuif you're running a linux server just crontab it instead of something external. windows has something similar where you can schedule services
A linux-based TF2 server started with -autoupdate will auto-restart if you send a kill signal. So the simplest thing to make the above suggestion work is to add a crontab entry that runs:
killall srcds_linux
maneI'm not surprised. From what I heard, tf2 logs are fist being locally saved in your server directory and then uploaded to logs.tf, right? Is the log file like in the root 'tf' folder or where should I find it?
In
tf/logs
S4mskiLMFAO
Valterri it's James please abort
Fuck you I'm taking this fastest lap
He backed out in S3 :( Sadly, couldn't do it despite being cut from the team
justjazzand if so where can i donate for them to get better servers
I think most or even all of the demos are stored on Hetzner servers in Germany. Some ISPs love to fight with them over bandwidth and refuse to set up peerings, causing slow speeds for that ISP's customers.
taviChampionship battle about to get more intense now isnt it. I dont think you can blame either of them for the collision though
I think you can blame the driver that was behind, on the dirty side of the track, missing the apex, understeering into his opponent.
Hehe, those are some cool queries, I was hoping you were just missing some indexes or something, but it looks like you got all that covered.
An on-the-fly aggregation like the peers is always going to be challenging, especially since you're trying to find the top 100 players most played with/against.
One thing I would consider, is to move "log_wlt" and "player_last" from views to materialized views (unlike a view these need their own indexes). You could update these materialized views (concurrently) after a new batch of log files is imported. This might improve part of the peers query.
Forty-BotA little update:
I'm migrating the database from SQLite to PostgreSQL. I started this last week, and did the switchover this past weekend. However, some of the queries are now taking way longer than they used to. I am currently working on this. Availability might be a bit spotty until I can get to the bottom of things. I am also trying to get log importing back up, but that is going much slower than before too. Please be patient for the next few days :)
In the longer term, performance was and is a big problem with the site, even before switching databases. I would love if some more experienced developers could look over my schema/queries and help out.
I'll take a look if you share some slow queries (use postgres' slow query logger) and the entire DDL (pg_dump --schema-only) and put it in a github gist.