| Account Details | |
|---|---|
| SteamID64 | 76561198072250111 |
| SteamID3 | [U:1:111984383] |
| SteamID32 | STEAM_0:1:55992191 |
| Country | Belgium |
| Signed Up | September 18, 2016 |
| Last Posted | April 16, 2024 at 1:29 PM |
| Posts | 124 (0 per day) |
| Game Settings | |
|---|---|
| In-game Sensitivity | 2.90 |
| Windows Sensitivity | 6/11 |
| Raw Input | 1 |
DPI |
400 |
Resolution |
1920x1080 |
Refresh Rate |
240hz |
| Hardware Peripherals | |
|---|---|
| Mouse | Logitech G Pro Wireless |
| Keyboard | Wooting One |
| Mousepad | SteelSeries QcK XL |
| Headphones | Audio Technica ATH-M50X |
| Monitor | LG 27GK750F |
If you're new to Python and don't mind spending like $1 or more you could buy the Python dev kit on Humble Bundle currently. There are a couple of guides on how to write pythonic code and PyCharm is a solid IDE, although you might be able to get it for free if you're a student.
You should be more specific about what you're having issues with though
After updating to 6.5.0-b7 my class-specific configs in tf/cfg stopped working. Tried out 6.5.0-b6 right after and still had the issue. They started working again once I went down to 6.5.0-b5. (maxperformance btw)
EDIT: never mind, I did not read the changelog on b6. For anyone else having the same problem:
changelogClass configs added to do occasional memory optimizations while in game. If you have class configs, rename them to add _c to the name. For example heavyweapons_c.cfg.
The dominations label on bx-m0rehud's scoreboard seems a bit bugged.
https://i.imgur.com/ho2LhVl.jpg
Also thank you for updating all of these HUDs, you are a legend
https://clips.twitch.tv/ExquisiteRenownedCasetteBrokeBack
Pyro can use the second Thermal Thruster charge in mid-air under certain circumstances
This started a few days ago and I'm not sure what's causing it, but basically whenever I'm queuing for casual it sometimes puts me in a server but then it fails to connect. It happens at random, at times I can join casual just fine and sometimes the connection fails after four retries (and still tries to put me in the server despite that). I'm not really noticing a consistent trend to it.
I'm not having this issue with community/match/comp servers, just casual.
I use Comanglia's config. I don't think the config is the problem though, I've been using it for a really long time now.
Any ideas as to what might be causing this?
I'm having the same problem. I can open the console but I can't type anything/close it. Occassionally I'm able to write something when I click the console button on the main menu while the console is already open, though. Not sure why.
Not sure if this belongs here but worth a shot, the idea just crossed my mind.
I have some STVs lying around and I forgot to record the first person demo. In this thread Beater said something about theoretically being able to make the spectator HUD look like a first person POV demo, the only problem being that it's not possible to display ammo, damage numbers etc while spectating from STV.
At i61 however you were able to see the ammo of every player on the HUD. Does anyone have any idea how this works? I'm assuming it's a plugin of some sort but I'm still curious if it would be do-able to make something like this. Hopefully this poor Photoshop edit does a decent job of showing what I mean.
mastercomsmegaboyAlso, I have a problem that has to do with this config and joining other community servers that get stuck on parsing gaming info and never retrieves info from the server or getting any further into loading. Just stays there with 3 bars on parsing game info. Any suggestions on how to fix this?Is it just skial servers that have this issue, or all community servers? I've heard from some people it only happens on skial servers. I still don't have a clue what causes this, but you could try removing -reuse -usetcp from launch options. I'll try to look into it more. Does it happen when you do use -default, with no other launch options as well?
I had the same problem with Feliks' config when connecting to Skial servers. The culprit turned out to be net_queued_packet_thread 581304, setting it back to the default (1) allowed me to join Skial again.