SteamVR Home September Update

There is a boxing ring added in this update, which uses TF2 assets.

Since SteamVR Home uses the Source 2 engine, these assets must have been ported over to Source 2 before they could have been used.

So... that means there are TF2 assets that have been ported to Source 2.

This could mean two things:

1. They just did this solely for a minor boxing minigame within their VR app.
   
2. TF2 is being ported to Source 2 and the SteamVR Home team decided to make a boxing minigame by borrowing some of the assets.

In addition to the Pyro Update being the biggest update to TF2 ever in terms of content, I guess a Source 2 port would also explain the wait.

On PCs, the ConVar default is 1, however, the value for PCs is defined by the dxsupport configuration, so depending on your dxlevel and hardware, the value may be 0 or 1 by default.

No, it is not VSync. Hardware sync waits per frame for the GPU to execute the commands in the command buffer and then stops waiting if the execution takes too long. Sure, it is some extra work and waiting, but it prevents the hardware from drifting behind too many frames from what the engine has requested. Most of the performance impact of hardware syncing depends on how poorly the driver behaves, not the extra work done from hardware syncing alone. And as you can imagine, this is partially accounted for in the dxsupport configuration per device.

VSync isn't related to it, so mat_vsync doesn't affect HW sync. The material system queue modes 0 and 1 directly call it at the beginning of the frame, while mode 2 calls it in a queued call (for threading reasons).

This depends on your drivers and hardware, and only happens in specific rendering situations. These errors happen when the frame sync query object is lost and the driver isn't able to recover properly. (again mostly accounted for in the dxsupport configuration per device).

I hope my explanations above were sufficient enough to come to the conclusion that configs and users probably have no business setting this convar themselves. It is best to trust what Source thinks is best for your hardware and only if you find it problematic, you should you change the value.

Good question, by the way.

You can try the -small launch option. This will allow for resolutions smaller than 640 height and 480 width.

You forgot to comment out the settings listed under remove.

I was asking you to use -default to check if it was an issue from within the config, not as a permanent solution.

This should have been fixed since 4.1.7, by setting net_queued_packet_thread to 1, and then to 0 since 4.2.0. Have you updated?

It is in the custom folder for easier management and updating of files and so it doesn't mess with people's files and possibly Steam Cloud Sync. You should be able to have exec comfig in your autoexec and then put the mastercoms folder in custom, and then delete the autoexec.cfg in the cfg folder in the mastercoms folder. But yes, it is possible but not recommended to manually copy the cfgs to your cfg folder.

EDIT: you'll also be missing out on file overrides in the custom folder for the texture preload list, as well as future changes to DirectX settings and shaders.

Also, I understand people might be more comfortable with Comanglia's config, so I've gone ahead and listed conservative changes to his config, along with explanations for the changes. These changes are very conservative and are not fully optimized. They also do not include new additional settings I've included in my config.

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.