Yahud damage font doesn't seem to work, seems to be missing from the file. There are also some minor mistakes in it. Thanks for the sick matchhud btw, looks good.
Also what's this
Account Details | |
---|---|
SteamID64 | 76561198029086781 |
SteamID3 | [U:1:68821053] |
SteamID32 | STEAM_0:1:34410526 |
Country | Finland |
Signed Up | April 19, 2015 |
Last Posted | July 19, 2024 at 8:09 AM |
Posts | 70 (0 per day) |
Game Settings | |
---|---|
In-game Sensitivity | |
Windows Sensitivity | |
Raw Input | 1 |
DPI |
|
Resolution |
|
Refresh Rate |
Hardware Peripherals | |
---|---|
Mouse | |
Keyboard | |
Mousepad | |
Headphones | |
Monitor |
Yahud damage font doesn't seem to work, seems to be missing from the file. There are also some minor mistakes in it. Thanks for the sick matchhud btw, looks good.
Also what's this
carnaticumhttps://youtu.be/067tFHtEa1A?t=22
hud?
Garm3n Q-M
Sounds like a higher pitch/sped up shine from melee: https://huds.tf/forum/showthread.php?tid=2241
In the future consider using this thread: https://www.teamfortress.tv/45899/wut-hud-crosshair-cfg-thread
kunowhat is the hud in this clip?
Sayo
https://www.teamfortress.tv/8247/show-your-hud-modifications/?page=191#5712
During the pregame in casual the team ready status elements appear even though you can't actually ready up. They also stay on screen on some community servers without timelimits. I've looked through hudtournament.res but couldn't find any obvious way to disable them in casual, whereas for mvm or individual readymode you can specify what to do with them with the "if_mvm" or "if_readymode" statements. Is there any way to disable or hide them when they're not usable?
edit: adding "if_competitive" and defining the visibility in it worked.
I think it has to do with resupping, so if in offline or jump servers you have a resupply script running the game will refresh your items and momentarily not keep track of your killstreaks, hence the flicker.
Also use this thread in the future: https://www.teamfortress.tv/19073/hud-editing-short-questions-quick-answers
PepperfishYou're a godsend, thanks for the help. Also, will having multiple different copies of a weapon's config file in different script folders cause conflict errors?
No idea. If you already have a file like that just edit that one instead of getting a new one
You'll need a tf_weapon_scattergun.txt file in your scripts folder to disable the sparks. You can get the file from the vtf crosshair thread for example. Then in the file you need to change "TracerEffect" into something else, I've mine set to "bullet_shotgun_tracer01". Should result in something like this:
_KermitTry setting the zpos of the damage numbers (in the .res file) and CDamageAccountPanel entry in hudlayout.res to 999 or some stupid high number.
Thank you, this worked!
Scoutmanmaybe there is a problem with the color in huddamageaccount.res ?
Both the positive and the negative color are set to "255 255 255 255" in huddamageaccount.res. I've also tried simply replacing the file with the regular M0rehud version along with the actual font files and definitions in clientscheme.res but the issue persists.
Using Grape-M0rehud the damage numbers become blurry and slightly yellow when zoomed in with the sniper rifle:
https://i.imgur.com/Ei2rrg5.jpg
With the regular M0rehud this doesn't happen, even though I used the exact same font. Any idea why this happens and how can I fix it?
https://steamcommunity.com/id/micwoj92
There are some layers to this. For one he has a peculiar name on his strange prof. speks and there's something funny going on in his comments. Make sure to also check his tftv posts and github page for a laugh. Makes me wonder if he's being serious..
The person whose insta he seems to be stalking also belongs in this thread actually (https://steamcommunity.com/id/tanusa)
More evidence: https://www.teamfortress.tv/56288/fps-config-based-on-research-and-not-vpk
Thank you so much, changing the encoding to UTF-8 without BOM fixed it.
mastercomsDid you edit or open the VPK? It can cause encoding issues.
No, I haven't edited or opened the VPK file. I downloaded the newest release and installed it again just to be sure but the unknown command persists.