| Account Details | |
|---|---|
| SteamID64 | 76561198309590576 |
| SteamID3 | [U:1:349324848] |
| SteamID32 | STEAM_0:0:174662424 |
| Country | United States |
| Signed Up | June 10, 2016 |
| Last Posted | June 10, 2016 at 12:30 PM |
| Posts | 2 (0 per day) |
| Game Settings | |
|---|---|
| In-game Sensitivity | |
| Windows Sensitivity | |
| Raw Input | |
DPI |
|
Resolution |
|
Refresh Rate |
|
| Hardware Peripherals | |
|---|---|
| Mouse | |
| Keyboard | |
| Mousepad | |
| Headphones | |
| Monitor | |
TechDudeDon't set the launch option.
The in game cvar mat_queue_mode tells the engine whether to enable threading.
Yes I know, but the -threads option is/was supposedly used to force the Source engine to use # of threads (in conjunction with mat_queue_mode).
Example would be someone with quad-core CPU would use -threads 4 to help the Source engine spread out the load over the 4 cores instead of just hammering 1-2.
Hi.
I was curious to know if using the -threads # launch option was still viable these days or should I just let TF2 Source engine handle that by itself without forcing it?