Upvote Upvoted 250 Downvote Downvoted
1 ⋅⋅ 11 12 13 14 15 16 17 ⋅⋅ 61
mastercomfig - fps/customization config
posted in Customization
391
#391
0 Frags +
zfnCan you please explain for us non tech savvy how the prerelease improves particle performance?

Also for those of us who prefer dx8, are there any changes which we should be making?

It is a few hidden ConVars that are being set for dxlevel 90 and 95, using the dxsupport_override.cfg file. These changes aren't relevant for dx8. What exactly do you prefer with dx8?

-Phantom-One last thing, would you recommend the comp config for toasters? I think somewhere it mentioned this config being for average PCs and using this config on my toaster gave me less fps than comanglia's, though I'm only going off feeling; no official benchmarking.

The max performance preset is good for toasters. You'll also probably want to use the iGPU preset.

[quote=zfn]Can you please explain for us non tech savvy how the prerelease improves particle performance?

Also for those of us who prefer dx8, are there any changes which we should be making?[/quote]
It is a few hidden ConVars that are being set for dxlevel 90 and 95, using the dxsupport_override.cfg file. These changes aren't relevant for dx8. What exactly do you prefer with dx8?

[quote=-Phantom-]One last thing, would you recommend the comp config for toasters? I think somewhere it mentioned this config being for average PCs and using this config on my toaster gave me less fps than comanglia's, though I'm only going off feeling; no official benchmarking.[/quote]
The max performance preset is good for toasters. You'll also probably want to use the iGPU preset.
392
#392
0 Frags +

I seem to experience strange hitches with "net_queued_packet_thread 0"--what are the supposed benefits?

I seem to experience strange hitches with "net_queued_packet_thread 0"--what are the supposed benefits?
393
#393
0 Frags +
stabbyI seem to experience strange hitches with "net_queued_packet_thread 0"--what are the supposed benefits?

net_queued_packet_thread 0 shouldn't be causing hitches unless your CPU or CPU scheduler is being dumb. Without the queued packet thread, split packets are sent without a delay.

[quote=stabby]I seem to experience strange hitches with "net_queued_packet_thread 0"--what are the supposed benefits?[/quote]
net_queued_packet_thread 0 shouldn't be causing hitches unless your CPU or CPU scheduler is being dumb. Without the queued packet thread, split packets are sent without a delay.
394
#394
0 Frags +

what's the default value for net_queued_packet_thread? i'm experiencing a similar problem, dunno if it's that setting or another, but i've only begun having that problem since installing this config.

what's the default value for net_queued_packet_thread? i'm experiencing a similar problem, dunno if it's that setting or another, but i've only begun having that problem since installing this config.
395
#395
2 Frags +
Buttnosewhat's the default value for net_queued_packt_thread? i'm experiencing a similar problem, dunno if it's that setting or another, but i've only begun having that problem since installing this config.

The default value is 1.

Values:

0 - Send packets and split packets immediately
1 - Send packets and the first split packet in a sequence immediately, but queue the rest of the split packets on a separate thread and send them after a delay in between each split packet
581304 - Queue all packets on a separate thread and send them after a delay in between each packet

I tested 0 on Windows and didn't encounter these issues, but if other people experience it, then I'll set it to the default of 1. By the way, what CPU are you using?

Also, stabby, are you using the -NoQueuedPacketThread launch option with net_queued_packet_thread 1?

EDIT: After looking at the documentation about how the Windows network system works, and then crying, I've decided that net_queued_packet_thread 1 is unfortunately necessary for Windows, except in some rare cases.

[quote=Buttnose]what's the default value for net_queued_packt_thread? i'm experiencing a similar problem, dunno if it's that setting or another, but i've only begun having that problem since installing this config.[/quote]
The default value is 1.

Values:

0 - Send packets and split packets immediately
1 - Send packets and the first split packet in a sequence immediately, but queue the rest of the split packets on a separate thread and send them after a delay in between each split packet
581304 - Queue all packets on a separate thread and send them after a delay in between each packet

I tested 0 on Windows and didn't encounter these issues, but if other people experience it, then I'll set it to the default of 1. By the way, what CPU are you using?

Also, stabby, are you using the -NoQueuedPacketThread launch option with net_queued_packet_thread 1?

EDIT: After looking at the documentation about how the Windows network system works, and then crying, I've decided that net_queued_packet_thread 1 is unfortunately necessary for Windows, except in some rare cases.
396
#396
2 Frags +

after installing this, my mumble overlay broke.. is this a common problem?

after installing this, my mumble overlay broke.. is this a common problem?
397
#397
0 Frags +

i didn't have -NoQueuedPacketThread enabled in my launch options and haven't noticed the hitching/stuttering since enabling it, although the problem occurred quite randomly to begin with. could ya link relevant documentation about the windows network stuff + net_queued_packet_thread for other tech savvy chaps to look over? thanks for putting so much work into this config, it's good to know someone is actively testing stuff out and explaining things for the rest of us plebs.

i didn't have -NoQueuedPacketThread enabled in my launch options and haven't noticed the hitching/stuttering since enabling it, although the problem occurred quite randomly to begin with. could ya link relevant documentation about the windows network stuff + net_queued_packet_thread for other tech savvy chaps to look over? thanks for putting so much work into this config, it's good to know someone is actively testing stuff out and explaining things for the rest of us plebs.
398
#398
0 Frags +

No iteration of network settings have had a negative effect for me thus far, however, I do disable smoothing as I only get prediction errors during specific collisions. It might be placebo but sometimes I feel like shots register sooner. I do notice warping but only from people who are blatantly playing on default settings (20 tick).

I would be interested to see odd interp settings scrutinised based on the premise of other people's update rates however.

No iteration of network settings have had a negative effect for me thus far, however, I do disable smoothing as I only get prediction errors during specific collisions. It might be placebo but sometimes I feel like shots register sooner. I do notice warping but only from people who are blatantly playing on default settings (20 tick).

I would be interested to see odd interp settings scrutinised based on the premise of other people's update rates however.
399
#399
0 Frags +
mastercomsIt is a few hidden ConVars that are being set for dxlevel 90 and 95, using the dxsupport_override.cfg file. These changes aren't relevant for dx8. What exactly do you prefer with dx8?

I really like dx8 because of the shorter rocket trails. i cant see shit after firing a rocket in dx9. i wish so badly that dx8 gave better performance. also, i kind of feel like dxlevel 100 is giving me shitty performance compared to 91?

[quote=mastercoms]
It is a few hidden ConVars that are being set for dxlevel 90 and 95, using the dxsupport_override.cfg file. These changes aren't relevant for dx8. What exactly do you prefer with dx8?[/quote]
I really like dx8 because of the shorter rocket trails. i cant see shit after firing a rocket in dx9. i wish so badly that dx8 gave better performance. also, i kind of feel like dxlevel 100 is giving me shitty performance compared to 91?
400
#400
1 Frags +
Buttnosei didn't have -NoQueuedPacketThread enabled in my launch options and haven't noticed the hitching/stuttering since enabling it, although the problem occurred quite randomly to begin with. could ya link relevant documentation about the windows network stuff + net_queued_packet_thread for other tech savvy chaps to look over?

So do you mean you don't get stuttering and hitching with net_queued_packet_thread 0 and -NoQueuedPacketThread?

Buttnosecould ya link relevant documentation about the windows network stuff + net_queued_packet_thread for other tech savvy chaps to look over?

https://docs.microsoft.com/en-us/cpp/mfc/windows-sockets-in-mfc,
https://social.technet.microsoft.com/Forums/windows/en-US/ead342a2-3fbd-48c7-80f8-85b34054e64b/windows-7-suddenly-limits-outgoing-udp-packets?forum=w7itpronetworking, and comments in the Source Engine's net_ws.cpp.

Buttnosethanks for putting so much work into this config, it's good to know someone is actively testing stuff out and explaining things for the rest of us plebs.

thanks sooo much!!! the kind words really mean a lot! <3

VantavimeowNo iteration of network settings have had a negative effect for me thus far

Strange, do you have the -NoQueuedPacketThread launch option and net_queued_packet_thread 0 ConVar set?

Vantavimeow however, I do disable smoothing as I only get prediction errors during specific collisions. It might be placebo but sometimes I feel like shots register sooner. I do notice warping but only from people who are blatantly playing on default settings (20 tick).

I would be interested to see odd interp settings scrutinised based on the premise of other people's update rates however.

cl_smooth does not affect other players, it only affects your own eye location. Interp and update rate won't affect other users, cmd rate will, but only slightly. Ping is the thing that matters the most.

TholeI really like dx8 because of the shorter rocket trails. i cant see shit after firing a rocket in dx9.

Hm yeah, the particles are a lot simpler in dx8. Not sure if those particle files are sv_pured or not, so maybe you could move them over to dx9.

Tholei wish so badly that dx8 gave better performance. also, i kind of feel like dxlevel 100 is giving me shitty performance compared to 91?

Well 91 doesn't exist, 91 will just go to 90. The available settings are 90, 95, 98 and 100. 98 is only allowed on Xbox 360 and I don't think 100 does anything but I haven't investigated it enough.

[quote=Buttnose]i didn't have -NoQueuedPacketThread enabled in my launch options and haven't noticed the hitching/stuttering since enabling it, although the problem occurred quite randomly to begin with. could ya link relevant documentation about the windows network stuff + net_queued_packet_thread for other tech savvy chaps to look over? [/quote]
So do you mean you don't get stuttering and hitching with net_queued_packet_thread 0 and -NoQueuedPacketThread?

[quote=Buttnose]could ya link relevant documentation about the windows network stuff + net_queued_packet_thread for other tech savvy chaps to look over? [/quote]
https://docs.microsoft.com/en-us/cpp/mfc/windows-sockets-in-mfc,
https://social.technet.microsoft.com/Forums/windows/en-US/ead342a2-3fbd-48c7-80f8-85b34054e64b/windows-7-suddenly-limits-outgoing-udp-packets?forum=w7itpronetworking, and comments in the Source Engine's net_ws.cpp.

[quote=Buttnose]
thanks for putting so much work into this config, it's good to know someone is actively testing stuff out and explaining things for the rest of us plebs.
[/quote]
thanks sooo much!!! the kind words really mean a lot! <3

[quote=Vantavimeow]
No iteration of network settings have had a negative effect for me thus far
[/quote]
Strange, do you have the -NoQueuedPacketThread launch option and net_queued_packet_thread 0 ConVar set?

[quote=Vantavimeow] however, I do disable smoothing as I only get prediction errors during specific collisions. It might be placebo but sometimes I feel like shots register sooner. I do notice warping but only from people who are blatantly playing on default settings (20 tick).

I would be interested to see odd interp settings scrutinised based on the premise of other people's update rates however.[/quote]
cl_smooth does not affect other players, it only affects your own eye location. Interp and update rate won't affect other users, cmd rate will, but only slightly. Ping is the thing that matters the most.

[quote=Thole]
I really like dx8 because of the shorter rocket trails. i cant see shit after firing a rocket in dx9.
[/quote]
Hm yeah, the particles are a lot simpler in dx8. Not sure if those particle files are sv_pured or not, so maybe you could move them over to dx9.

[quote=Thole]i wish so badly that dx8 gave better performance. also, i kind of feel like dxlevel 100 is giving me shitty performance compared to 91?[/quote]
Well 91 doesn't exist, 91 will just go to 90. The available settings are 90, 95, 98 and 100. 98 is only allowed on Xbox 360 and I don't think 100 does anything but I haven't investigated it enough.
401
#401
1 Frags +

Hey, idk if this has been asked before but is there any version of this config that has gibs and ragdolls disabled? I was trying to edit it to have them disabled earlier and it wasn't working at all.

Hey, idk if this has been asked before but is there any version of this config that has gibs and ragdolls disabled? I was trying to edit it to have them disabled earlier and it wasn't working at all.
402
#402
1 Frags +

I apologize if this has been asked already, but what setting in this config messes with certain mumble overlays? I know you can fix it with -nod3d9ex launch option but this makes alt tabbing in and out of game slower

I apologize if this has been asked already, but what setting in this config messes with certain mumble overlays? I know you can fix it with -nod3d9ex launch option but this makes alt tabbing in and out of game slower
403
#403
0 Frags +
fyggHey, idk if this has been asked before but is there any version of this config that has gibs and ragdolls disabled? I was trying to edit it to have them disabled earlier and it wasn't working at all.

The default config (comfig.cfg) should disable ragdolls. You can disable gibs with the comp, compquality or maxperformance presets.

wolsneI apologize if this has been asked already, but what setting in this config messes with certain mumble overlays? I know you can fix it with -nod3d9ex launch option but this makes alt tabbing in and out of game slower

What version of the config are you using? 4.3.0 should fix this.

[quote=fygg]Hey, idk if this has been asked before but is there any version of this config that has gibs and ragdolls disabled? I was trying to edit it to have them disabled earlier and it wasn't working at all.[/quote]
The default config (comfig.cfg) should disable ragdolls. You can disable gibs with the comp, compquality or maxperformance presets.

[quote=wolsne]I apologize if this has been asked already, but what setting in this config messes with certain mumble overlays? I know you can fix it with -nod3d9ex launch option but this makes alt tabbing in and out of game slower[/quote]
What version of the config are you using? 4.3.0 should fix this.
404
#404
0 Frags +

I'm still using comanglia's + your launch options + you fixes for comanglia and I get no issues with net_queued_packet_thread 1 and -NoQueuedPacketThread although I believe these nullify each other, no?

I'm still using comanglia's + your launch options + you fixes for comanglia and I get no issues with net_queued_packet_thread 1 and -NoQueuedPacketThread although I believe these nullify each other, no?
405
#405
0 Frags +
fagoatseI'm still using comanglia's + your launch options + you fixes for comanglia and I get no issues with net_queued_packet_thread 1 and -NoQueuedPacketThread although I believe these nullify each other, no?

No, net_queued_packet_thread 1 will queue and delay packets regardless of -NoQueuedPacketThread, but will do this unthreaded if you have -NoQueuedPacketThread.

You should either use net_queued_packet_thread 0 + -NoQueuedPacketThread (which I recommend if you don't encounter problems with it), or net_queued_packet_thread 1 without the launch option.

[quote=fagoatse]I'm still using comanglia's + your launch options + you fixes for comanglia and I get no issues with net_queued_packet_thread 1 and -NoQueuedPacketThread although I believe these nullify each other, no?[/quote]
No, net_queued_packet_thread 1 will queue and delay packets regardless of -NoQueuedPacketThread, but will do this unthreaded if you have -NoQueuedPacketThread.

You should either use net_queued_packet_thread 0 + -NoQueuedPacketThread (which I recommend if you don't encounter problems with it), or net_queued_packet_thread 1 without the launch option.
406
#406
0 Frags +
mastercomszfnCan you please explain for us non tech savvy how the prerelease improves particle performance?

Also for those of us who prefer dx8, are there any changes which we should be making?
It is a few hidden ConVars that are being set for dxlevel 90 and 95, using the dxsupport_override.cfg file. These changes aren't relevant for dx8. What exactly do you prefer with dx8?.

Mainly the particle effects like the rocket trails, pyro flames, sniper scope and other annoyances.

[quote=mastercoms][quote=zfn]Can you please explain for us non tech savvy how the prerelease improves particle performance?

Also for those of us who prefer dx8, are there any changes which we should be making?[/quote]
It is a few hidden ConVars that are being set for dxlevel 90 and 95, using the dxsupport_override.cfg file. These changes aren't relevant for dx8. What exactly do you prefer with dx8?.[/quote]
Mainly the particle effects like the rocket trails, pyro flames, sniper scope and other annoyances.
407
#407
2 Frags +

Calling testers:

add "ConVar.cl_clean_textures_on_death" "1" to section 3 of dxsupport_override.cfg.

Added somewhere around Gun Mettle, I think. When you get a freezecam/die, it removes unused textures.

Calling testers:

add "ConVar.cl_clean_textures_on_death" "1" to section 3 of dxsupport_override.cfg.

Added somewhere around Gun Mettle, I think. When you get a freezecam/die, it removes unused textures.
408
#408
1 Frags +

^ didnt notice any issues with that

however after 4.3.0/4.3.1 (i was on 4.3.0a until just now) there's a lot more visual clutter like blood bursts on death and grass on the maps. is that intended? im still on the comp.cfg preset

edit: adding -dxlevel 95 to my launch options then removing it again fixed it? fucking shit game

^ didnt notice any issues with that

however after 4.3.0/4.3.1 (i was on 4.3.0a until just now) there's a lot more visual clutter like blood bursts on death and grass on the maps. is that intended? im still on the comp.cfg preset

edit: adding -dxlevel 95 to my launch options then removing it again fixed it? fucking shit game
409
#409
0 Frags +
mastercomsfagoatseI'm still using comanglia's + your launch options + you fixes for comanglia and I get no issues with net_queued_packet_thread 1 and -NoQueuedPacketThread although I believe these nullify each other, no?No, net_queued_packet_thread 1 will queue and delay packets regardless of -NoQueuedPacketThread, but will do this unthreaded if you have -NoQueuedPacketThread.

You should either use net_queued_packet_thread 0 + -NoQueuedPacketThread (which I recommend if you don't encounter problems with it), or net_queued_packet_thread 1 without the launch option.

I'll try it out and get back to you.

On a side note, I take it that the game checks for mat_dxlevel and then loads appropiate dx overrides, right? Running -dxlevel all the time makes the game start considerably slower for me.

[quote=mastercoms][quote=fagoatse]I'm still using comanglia's + your launch options + you fixes for comanglia and I get no issues with net_queued_packet_thread 1 and -NoQueuedPacketThread although I believe these nullify each other, no?[/quote]
No, net_queued_packet_thread 1 will queue and delay packets regardless of -NoQueuedPacketThread, but will do this unthreaded if you have -NoQueuedPacketThread.

You should either use net_queued_packet_thread 0 + -NoQueuedPacketThread (which I recommend if you don't encounter problems with it), or net_queued_packet_thread 1 without the launch option.[/quote]

I'll try it out and get back to you.

On a side note, I take it that the game checks for mat_dxlevel and then loads appropiate dx overrides, right? Running -dxlevel all the time makes the game start considerably slower for me.
410
#410
0 Frags +
fagoatseI'll try it out and get back to you.

On a side note, I take it that the game checks for mat_dxlevel and then loads appropiate dx overrides, right? Running -dxlevel all the time makes the game start considerably slower for me.

Yeah you only need mat_dxlevel 95, not the launch option. I already have it in the comfig.cfg. And thanks.

[quote=fagoatse]
I'll try it out and get back to you.

On a side note, I take it that the game checks for mat_dxlevel and then loads appropiate dx overrides, right? Running -dxlevel all the time makes the game start considerably slower for me.[/quote]
Yeah you only need mat_dxlevel 95, not the launch option. I already have it in the comfig.cfg. And thanks.
411
#411
0 Frags +
mastercomsfagoatseI'll try it out and get back to you.

On a side note, I take it that the game checks for mat_dxlevel and then loads appropiate dx overrides, right? Running -dxlevel all the time makes the game start considerably slower for me.
Yeah you only need mat_dxlevel 95, not the launch option. I already have it in the comfig.cfg.

Nice timing :)
Anyway, I tried net_queued_packet_thread 0 with the -NoQueuedPacketThread switch and all is good. I'm on windows 10 btw.

[quote=mastercoms][quote=fagoatse]
I'll try it out and get back to you.

On a side note, I take it that the game checks for mat_dxlevel and then loads appropiate dx overrides, right? Running -dxlevel all the time makes the game start considerably slower for me.[/quote]
Yeah you only need mat_dxlevel 95, not the launch option. I already have it in the comfig.cfg.[/quote]


Nice timing :)
Anyway, I tried net_queued_packet_thread 0 with the -NoQueuedPacketThread switch and all is good. I'm on windows 10 btw.
412
#412
0 Frags +

Dunno if it's placebo but when I set net_queued_packet_thread to 1 I had some weird hit reg. Now that I have net_queued_packet_thread 0 it seems to be fine although I havent tryed experimenting with the said launch option.

Dunno if it's placebo but when I set net_queued_packet_thread to 1 I had some weird hit reg. Now that I have net_queued_packet_thread 0 it seems to be fine although I havent tryed experimenting with the said launch option.
413
#413
1 Frags +
fagoatseNice timing :)
Anyway, I tried net_queued_packet_thread 0 with the -NoQueuedPacketThread switch and all is good. I'm on windows 10 btw.

Alright, sounds good. Seems like we will have to find out if stabby was using -NoQueuedPacketThread.

osvaldoDunno if it's placebo but when I set net_queued_packet_thread to 1 I had some weird hit reg. Now that I have net_queued_packet_thread 0 it seems to be fine although I havent tryed experimenting with the said launch option.

Well you should also have the launch option if it is at 0. It saves memory and CPU which is being idly wasted.

Also, no, it isn't placebo. When packets are bigger than net_maxroutable, which is maxed out at 1260, Source divides them up into smaller chunks called splitpackets. These splitpackets are delivered in a sequence and with net_queued_packet_thread 1, each splitpacket after the first splitpacket is sent on another thread out after a delay that depends on your rate setting and the splitpacket size. If you have it set to 0, then the splitpackets are sent at the end of the frame immediately.

[quote=fagoatse]
Nice timing :)
Anyway, I tried net_queued_packet_thread 0 with the -NoQueuedPacketThread switch and all is good. I'm on windows 10 btw.
[/quote]
Alright, sounds good. Seems like we will have to find out if stabby was using -NoQueuedPacketThread.

[quote=osvaldo]Dunno if it's placebo but when I set net_queued_packet_thread to 1 I had some weird hit reg. Now that I have net_queued_packet_thread 0 it seems to be fine although I havent tryed experimenting with the said launch option.[/quote]
Well you should also have the launch option if it is at 0. It saves memory and CPU which is being idly wasted.

Also, no, it isn't placebo. When packets are bigger than net_maxroutable, which is maxed out at 1260, Source divides them up into smaller chunks called splitpackets. These splitpackets are delivered in a sequence and with net_queued_packet_thread 1, each splitpacket after the first splitpacket is sent on another thread out after a delay that depends on your rate setting and the splitpacket size. If you have it set to 0, then the splitpackets are sent at the end of the frame immediately.
414
#414
-1 Frags +

So like. How exactly do i install this? i have only used comanglias config before this and all you needed to do was put autoexec in cfg folder but this has multiple cfgs and folders so dofak i m ment to do...

So like. How exactly do i install this? i have only used comanglias config before this and all you needed to do was put autoexec in cfg folder but this has multiple cfgs and folders so dofak i m ment to do...
415
#415
2 Frags +
unskilledafter installing this, my mumble overlay broke.. is this a common problem?

I think the problem is usually anti aliasing, try to mess around with that.
This is what it says in comfig.cfg:

//mat_antialias 0 // Do not do antialiasing (commented due to HUD and overlay glitches, set it once and then comment it out)
neocortexSo like. How exactly do i install this? i have only used comanglias config before this and all you needed to do was put autoexec in cfg folder but this has multiple cfgs and folders so dofak i m ment to do...

She says how to do it in the OP:

mastercomsIn the ZIP, just open the tf2cfg folder and extract the mastercomfig folder to tf/custom. Launch options, helpful comments and customization options are in comfig.cfg located in the tf/custom/mastercomfig/cfg folder.
[quote=unskilled]after installing this, my mumble overlay broke.. is this a common problem?[/quote]
I think the problem is usually anti aliasing, try to mess around with that.
This is what it says in comfig.cfg:
[code]//mat_antialias 0 // Do not do antialiasing (commented due to HUD and overlay glitches, set it once and then comment it out)[/code]


[quote=neocortex]So like. How exactly do i install this? i have only used comanglias config before this and all you needed to do was put autoexec in cfg folder but this has multiple cfgs and folders so dofak i m ment to do...[/quote]
She says how to do it in the OP:
[quote=mastercoms]
In the ZIP, just open the [b]tf2cfg[/b] folder and extract the [b]mastercomfig[/b] folder to [b]tf/custom[/b]. Launch options, helpful comments and customization options are in [b]comfig.cfg[/b] located in the [b]tf/custom/mastercomfig/cfg[/b] folder.[/quote]
416
#416
3 Frags +

Please don't downfrag people who just want help!

(also sachiko, she*)

Please don't downfrag people who just want help!

(also sachiko, she*)
417
#417
1 Frags +
mastercoms(also sachiko, she*)

Sorry! I didn't know. I just corrected it.

[quote=mastercoms](also sachiko, she*)[/quote]

Sorry! I didn't know. I just corrected it.
418
#418
2 Frags +

Calling all testers with CPUs that have more than 4 real cores: add -threads core count - 1 to launch options

Calling all testers with CPUs that have more than 4 real cores: add -threads core count - 1 to launch options
419
#419
2 Frags +
mastercomsCalling all testers with CPUs that have more than 4 real cores: add -threads core count - 1 to launch options

ryzen 5 1600 @3.8GHz
technical stuff

Show Content
-w 1920 -h 1080 -novid -console -full -dev -nosrgb -nouserclip -nops2b -softparticlesdefaultoff
tf2 running in dx 81, on hdd
windows 7

gtx 550ti, stock clocks, 306.97 drivers
graphics config: a combination between comanglia's and dolphin's
cfg folder: https://mega.nz/#!ofwSUCzQ!Q10F5fNA4ceThddaB5qYLbUa5MqsZRrWryPzAPZjhbo
custom folder: https://mega.nz/#!cfhDFY7a!TAz0efTKrat0fhgIQYMhxXMyW2PaYj6AaPnZbo4pZUc

benchmarks

Show Content
2639 frames 13.191 seconds 200.06 fps ( 5.00 ms/f) 17.898 fps variability
w/o -threads

2639 frames 12.990 seconds 203.16 fps ( 4.92 ms/f) 13.747 fps variability
-threads 6

2639 frames 12.854 seconds 205.30 fps ( 4.87 ms/f) 14.045 fps variability
-threads 12

2639 frames 13.480 seconds 195.77 fps ( 5.11 ms/f) 12.310 fps variability
-threads -1

2639 frames 17.287 seconds 152.66 fps ( 6.55 ms/f) 8.512 fps variability
-threads 1
[quote=mastercoms]Calling all testers with CPUs that have more than 4 real cores: add -threads core count - 1 to launch options[/quote]

ryzen 5 1600 @3.8GHz
technical stuff
[spoiler]
-w 1920 -h 1080 -novid -console -full -dev -nosrgb -nouserclip -nops2b -softparticlesdefaultoff
tf2 running in dx 81, on hdd
windows 7

gtx 550ti, stock clocks, 306.97 drivers
graphics config: a combination between comanglia's and dolphin's
cfg folder: https://mega.nz/#!ofwSUCzQ!Q10F5fNA4ceThddaB5qYLbUa5MqsZRrWryPzAPZjhbo
custom folder: https://mega.nz/#!cfhDFY7a!TAz0efTKrat0fhgIQYMhxXMyW2PaYj6AaPnZbo4pZUc
[/spoiler]

benchmarks
[spoiler]
2639 frames 13.191 seconds 200.06 fps ( 5.00 ms/f) 17.898 fps variability
w/o -threads

2639 frames 12.990 seconds 203.16 fps ( 4.92 ms/f) 13.747 fps variability
-threads 6

2639 frames 12.854 seconds 205.30 fps ( 4.87 ms/f) 14.045 fps variability
-threads 12

2639 frames 13.480 seconds 195.77 fps ( 5.11 ms/f) 12.310 fps variability
-threads -1

2639 frames 17.287 seconds 152.66 fps ( 6.55 ms/f) 8.512 fps variability
-threads 1
[/spoiler]
420
#420
0 Frags +

The default setting is your cores - 1, at a max of 3, just FYI.

The default setting is your cores - 1, at a max of 3, just FYI.
1 ⋅⋅ 11 12 13 14 15 16 17 ⋅⋅ 61
Please sign in through STEAM to post a comment.