zeSIMON is right, but make sure exec maxperformance is run after comfig. Do you have suggestions on how I can make this more clear?

The mastercoms folder has its own cfg/autoexec.cfg file which overrides your existing autoexec. Delete autoexec.cfg in the mastercoms/cfg folder and add exec comfig to your own autoexec.

Even 0? That's pretty strange. Do you have mat_aaquality set to a non-zero value?

EDIT: 4.2.4 released with better anti-aliasing controls and improved max quality settings for AA and texture filtering.

Glad you find it working well. Antialiasing missing is just an oversight. I'll update it soon to add this.

It enables alpha to coverage, which is used to increase the quality of antialiasing for any overlapping thin objects like foliage, fences and grillwork.

It is run entirely on the GPU, so it will give you a small FPS increase when disabled, depending on your GPU.

Anyway, I actually forgot about this setting, so thanks for this. I'll be adding it to the config soon.

Source 2.

https://www.pcgamesn.com/counter-strike-global-offensive/csgo-next-operation-source-2-ai-cheat-detection

hey there

im fine

thanks

hbu?

What preset is this at? I'd like to see the performance with compquality, if you don't mind.

Also, I've released 4.2.2 which has some networking improvements. Tell me if you feel any difference.

EDIT: 4.2.3

You don't need the .cfg when using exec. Just do exec crosshair_medic.

Not really any noticeable settings, are you having trouble seeing them compared to default?

r_WaterDrawRefraction 1
r_cheapwaterstart 400
r_cheapwaterend 1000

Anyways, 4.2.0 just released. Blaze it (in moderation, or not at all, if that's not your thing).

EDIT: 4.2.1 released with a small fix to sound spatialization

See if

steamdatagram_client_force_relay_cluster mad

fixes it.

EDIT: this command was removed in the steam datagram update a few days ago. not sure how to fix it then.

Glad to hear you've been liking it!!! Thank you for the kind words <3, it means a lot

I've been looking into this.

What is the output of tf_datacenter_ping_dump?

There is not.

It is a routing issue with Steam Datagram, if you're trying on Valve servers. But for a community server, idk. But a lot of people have been having problems lately, I believe.

Realtime is not recommended, as TF2 will be the same priority as OS level tasks.

There is no dxlevel because the default dxlevel determined by the Source Engine for your hardware is usually the best one. However, I am investigating the impact of each dxlevel to see what options the config should control.

Please keep in mind that TF2 already had this functionality, they are now just using a shared implementation across all their games, instead of one put into the main game code. So far, TF2 and Dota 2 have moved to this shared code, while CSGO has yet to do it for theirs, but that will presumably come with the promised Source 2 port.

As for what this indicates for TF2, it could go either way: updating the game code is confusing if they were going to move to Source 2, as it is seemingly pointless extra work but at the same time, it makes the Steam Datagram portable and engine non-specific and allows them to test the external code beforehand.

As for the Pyro Update in general, this update has nothing specifically related to it.