mat_queue_mode has to do with the graphics card as much as it as to do with the CPU, don't use a low resolution for it.

No, but there might be some more data in tf/sourcebench.csv

Oh, I forgot to update the comments and values for that. Thanks for the catch.

EDIT: 4.4.6 released with this fix and others, as well as some file cleanup.

It isn't used if mat_software_aa_strength and mat_software_aa_strength_vgui are set to 0, so it isn't very useful to be changed in the base config. It is, however, adjusted in the maxquality preset.

The config sets these two values to 0, however, mat_antialias is commented out because it apparently affects some Mumble overlays. The more AA you do, the more work your GPU has to do. CSAA only works on NVidia I think, but it is more efficient than the MSAA that mat_antialias does.

It isn't supposed to activate any animations, only to force cycles in the animation controller. Sort of magic.

Anyway, I have updated the code in the OP to add the default event contents as well as to adjust the time delay to try to make the bug less common.

As in it doesn't decrease the occurrence of the bug or that it breaks m0rehud?

If you launch with only -default in the launch options, does this problem still happen?

It seems like this just makes the bug less likely and does not make it go away completely. I'm testing some stuff to fix those remaining edge cases that still cause the bug to come up.

Do you have Windows 10 installed? https://support.steampowered.com/kb_article.php?ref=6239-DZCB-8600

Also, there is apparently an issue on Windows 10 with mouse input, so if you are getting input lag, try m_rawinput 1.

For keyboard input lag, you should be using in_usekeyboardsampletime 1.

4.4.5 released with a few bug fixes and documentation improvements (one of which is fixing the formatting when using Notepad to view), as well as a small CPU optimization to networking.

It was in the config before because I didn't read the code for how the command is used before I removed it. It is only used for Xbox 360 and even if it was allowed on PC, it forces the value to be no greater than 2.

chocolate

may good frames and bug fixes come to you

Hello everyone, I have found a fix for that longstanding bug where animations linger after death for custom HUDs. For example, low and overhealed HP or low ammo effects. All you need to do to fix this is run stop events for these animations when the HudSnapShotReminderIn event is called. This will reset those animations on freezecam.

For example, the fix for 7hud was (remember to add the default snapshot reminder code unless you've changed that as well):

event HudSnapShotReminderIn
{
    Animate ScreenshotPanel Position "c-83 -50" Linear 0.0 0.001
    Animate ScreenshotPanel Position "c-83 13" Spline 0.001 0.2
    RunEvent HudHealthDyingPulseStop 10.0
    RunEvent HudHealthBonusPulseStop 10.0
    RunEvent HudLowAmmoPulseStop 10.0
    RunEvent HudMedicChargedStop 10.0
}

The RunEvents depend on what your HUD modifies, but I feel like these are the most popular/common animations HUDs use so it should be enough for most HUDs.

Well, I've gotten 10fps more on this config with maxperformance than I got with Comanglia's. Also, I think it is better optimized.

However, I'm obviously pretty biased so might be useful to test for yourself or find other people's thoughts.

love your hud, sevin!! M<3 it is amazing and beautiful

bunt i have one problem: when i die with modifer (hurt or overhealed) the health bar stays on that efeect adn i have to do hud_reladshceme to fix it.

i dint test have time to test with the latest update,sortry if you fixed

So you still experience the issue?