| Account Details | |
|---|---|
| SteamID64 | 76561198072250111 |
| SteamID3 | [U:1:111984383] |
| SteamID32 | STEAM_0:1:55992191 |
| Country | Belgium |
| Signed Up | September 18, 2016 |
| Last Posted | February 18, 2025 at 1:44 PM |
| Posts | 128 (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 |
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.
http://www.teamfortress.tv/41302/lod-settings-causes-input-lag
There was a thread about this a week ago and people who used it said it was fine, so I'm a bit confused. Does it add input lag, yes or no?
I haven't updated my drivers in a while. I updated them now and apparently there were updates, but it didn't fix my issue.
The only program I recall updating is Process Lasso. I just tried to launch the game while having it closed and without the core engine running in the background. No results.
I also did the Windows 10 Creators Update about a week ago. However, the problem only started occurring since yesterday so I'm not sure if that has anything to do with my problem.
I already verified game cache but I decided to give it another try. It didn't resolve the issue.
I've tried running the game in dx9. It made no difference.
I emptied my custom folder completely, including my HUD. The problem seems to persist regardless of what HUD I am using, even with the default hud.
I've launched the game with the launch options you mentioned and removed my autoexec. Didn't work either.
Thanks for the help anyway.
Ever since yesterday my game starts to (micro)stutter whenever I'm playing medic and I'm healing people. It only seems to happen while I'm healing/ubering, I haven't been able to recreate the problem on any other class. It doesn't seem to be FPS related though, I tried it on an offline server as well while I was averaging 500 fps and it still occurred, I didn't notice any sudden frame drops. I have no idea what is causing it, any help would be appreciated.
I run TF2 in dxlevel 81 with Comanglia's config. I'm using Hypnotize's updated version of the old yaHud.
Custom stuff:
- Nohats
- No soundscapes
- Yttrium's competitive viewmodels
- Diminished explosions
- No domination sounds