Skip to content

Conversation

@celisej567
Copy link

While pyrovision is on, overlays freaks out. This happens only in mods, and not in default tf.

2025-12-13_18-42-07.mp4

After this commit.

2025-12-13_18-58-20.mp4

Hardcoded check for gameinfo folder that prevented this was in materialsystem, but mods cant modify this, so check falsely sets mat_supportflashlight as true. Setting mat_supportflashlight in CHLClient::Init for TF fixes this issue for mods.

@ALIEN31ITA
Copy link

You have no idea how i was going crazy over this, apparently this bug DOESN'T HAPPEND to some users, my initial tought was like my Graphic card being faulty (despite not, and being fine around every other single game), and all of this because of flashlights?! 😭

@celisej567
Copy link
Author

celisej567 commented Dec 13, 2025

In fact it DOES depend on GPU. Old gpus and intel. I think thats something regarding dx9 implementation on newer and some older gpus. Flashlight implementation is pretty messy.

@ALIEN31ITA
Copy link

In fact it DOES depend on GPU. Old gpus and intel. I think thats something regarding dx9 implementation on newer and some older gpus. Flashlight implementation is pretty messy.

it's a really crazy Discovery, for context, mine is a RTX 4060 TI, and it's fairly new, so stuff like this kinda makes you worried, but good finding.

//this check is only for tf mods, because pyrovision is only tf thing
#if defined( TF_CLIENT_DLL )
{
ConVarRef( "mat_supportflashlight" ).SetValue( false );
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the wrong way to fix this, fix the issue in the shader rather than disabling flashlights entirely...

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, but I'm very bad at shaders. And since I saw this way to fix this in the materialsystem, I decided that it would be faster for ordinary people to add these lines to fix it on the spot.

@gaelcoral
Copy link
Contributor

gaelcoral commented Dec 15, 2025

What do you mean by "This happens only in mods, and not in default tf"?
Because I also get these artifacts in TF2.
(btw RTX 4060 and Vulkan mode enabled)

Team_Fortress_2_-_2025-06-21_11-51-14_p-m-_1.mp4

@JoriKos
Copy link
Contributor

JoriKos commented Dec 15, 2025

Pretty sure this is the true vision of what Pyro sees.

I had some similar issues outside of Pyrovision that kinda looked similar, shown here. Not sure if it's related. I've also seen this same artifact happen in someone else's game who doesn't use Vulkan, so probably unrelated to that.

@celisej567
Copy link
Author

celisej567 commented Dec 15, 2025

@JoriKos
It is the same artifacts, but Im not sure if they are caused by the same reasons. Ive tested only dustbowl and 2fort, and both had this issues with pyrovision on. I'm not sure, but looks like in your vid there is no provision. Can you give me:

  1. Entire soldier class loadout from this video.
  2. Map name.
  3. Launch options
  4. Screenshot of your Graphics options (advanced as well).
  5. List of mods. if you have them ofc.

@JoriKos
Copy link
Contributor

JoriKos commented Dec 15, 2025

  1. Community Wiki Cap, Self-Made Cap that Charity Donor medal, Strange Lord Cockswain's Novelty Mutton Chops and Pipe.
  2. Rottenburg (mvm_rottenburg)
  3. -novid -no_texture_stream -nosteamcontroller
  4. I use mastercomfig which doesn't reflect accurately in these settings IIRC. It's mastercomfig flat mouse, high preset, null-cancelling movement, and no tutorial. I can provide screenshots if necessary, of course.
  5. For mods it's the old Rocket Jumper/Sticky Jumper models, an older version of NativeHUD, a 2013 backpack appearance restoration (which I can't find the link for anymore), a skybox texture edited to be entirely black (for HLMV purposes), and hit/killsound.

I've only had this bug in that specific spot, at specific view angles, on that map. I've never seen it happen anywhere else.

@celisej567
Copy link
Author

I wasnt able to reproduce the bug on that spot, but if(!!!) its the same issue, this fix should work.

@JoriKos
Copy link
Contributor

JoriKos commented Dec 17, 2025

I should note I found some other spots with this issue, so it's not specific to that spot but just one I found it to happen quite consistently for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants