ValveSoftware / halflife

Half-Life 1 engine based games
Other
3.67k stars 619 forks source link

CS 1.6 [Build 8245] "-freq" still not working. #2487

Open ghost opened 5 years ago

ghost commented 5 years ago

I tested the parameter "-freq" and came to the following results:

The desktop is set to high resolution, for which the maximum allowed 100hz. The game starts at a lower resolution, for which it is permissible 120hz. In the startup parameters spelled "-nofbo -freq 120"

Total:

CS 1.6 [Build 4554] - 120hz in game. CS 1.6 [Build 8245] - 100hz in game.

Tests were conducted on CRT Mitsubishi Diamondtron NF. Old behavior "-freq" in version 8245 not functioning properly. Please return as it was in the version 4554.

PS> I apologize for the double, but the previous branch is closed with the note "decided", although, as you can see, nothing is actually fixed.

djdallmann commented 5 years ago

Are you in beta? There was a recent change to fix this in beta like a week ago.

mikela-valve commented 5 years ago

I think build 8245 is the latest CS beta, so it looks like that’s right. @djdallmann have you tried setting frequency since the beta? It works for me when I try it with my 60/75Hz monitor but I don’t have a higher frequency one to try it with.

@drogga Could you check if you’re definitely on the beta for both CS and HL1? The fix for -freq is in the engine which is part of HL1, so if you were somehow only on CS’s beta you wouldn’t have the fix. If it says you’re on HL1 beta, try flipping back to public then back to beta and see if that fixes things.

BlackShadow commented 5 years ago

I can confirm -freq option works. I tried multiple Hz's such as: 60,75,144,240 in my 240 Hz monitor and all worked in 1080p or lower res. (tried 1280x1024)

voed commented 5 years ago

Works only with -nofbo option for me.

mikela-valve commented 5 years ago

@voed That's to be expected. -freq will only work by itself when your desktop resolution is supported in the frequency that you specify. -nofbo triggers setting the monitor resolution as well as the frequency.

ghost commented 5 years ago

@drogga Could you check if you’re definitely on the beta for both CS and HL1? The fix for -freq is in the engine which is part of HL1, so if you were somehow only on CS’s beta you wouldn’t have the fix. If it says you’re on HL1 beta, try flipping back to public then back to beta and see if that fixes things.

I tried to reproduce the recommendations you suggested. As a result, I updated Half-Life and Counter-Strike to the current versions of beta releases:

valve

Launch Options for all version -- "-nofbo -w 800 -h 600 -freq 120 -32bpp" Desktop - 1600x900x32bpp [100hz]

Half-Life [beta]

] version Protocol version 48 Exe version 1.1.2.2/Stdio (valve) Exe build: 01:39:08 Jun 2 2019 (8254)

Result -- 100hz [800x600x32bpp] in game.


Counter-Strike [beta]

] version Protocol version 48 Exe version 1.1.2.7/Stdio (cstrike) Exe build: 01:39:08 Jun 2 2019 (8254)

Result -- 100hz [800x600x32bpp] in game.


Counter-Strike [Current Release]

] version Protocol version 48 Exe version 1.1.2.7/Stdio (cstrike) Exe build: 15:58:59 Apr 3 2019 (8196)

Result -- 100hz [800x600x32bpp] in game.


Counter-Strike [Old Version]

] version Protocol version 48 Exe version 1.1.2.6/1.0.0.0 (cstrike) Exe build: 16:05:41 Jun 15 2009 (4554)

Result -- [b]120hz[/b] [800x600x32bpp] in game!

plumch commented 5 years ago

@ghost , tell how did you run build 4554?) share your backup please

deprale commented 5 years ago

@ghost share ur old cs... lol

BUXPb commented 5 years ago

share your backup please Are you calling on him to break the law?