search

ValveSoftware / Source-1-Games

Source 1 based games such as TF2 and Counter-Strike: Source
647 stars 75 forks source link

Achievement get disabled by default when enabling -dev parameter on TF2 and L4D2 #970

Closed UnknownzD closed 11 years ago

UnknownzD commented 11 years ago

By enabling the -dev parameter on TF2 and L4D2 (which I have used to dump the console output to left top corner for development purpose / bug report), the achievement will get disabled by default.

This is because by enabling -dev parameter on TF2 and L4D2, sv_cheats 1 will get automatically enabled by default, and as it turns out, both TF2 and L4D2 has modified some cheat cvars by default (which I guess is usls for TF2) after the game started. In addition, I have no idea why they get modified after the game launched, instead of setting a default value on them.

By default, the following FCVAR_CHEAT variables will be modified after the game being launched (which seems to be used for creating fog at the start screen of L4D2, and seems like TF2 get these changes merged as well). fog_start fog_end fog_startskybox fog_endskybox r_farz

And if an user / developer didn't enable -dev command line parameter on these games, the console will get spammed with following lines instead. Can't use cheat cvar fog_start in multiplayer, unless the server has sv_cheats set to 1. Can't use cheat cvar fog_end in multiplayer, unless the server has sv_cheats set to 1. Can't use cheat cvar fog_startskybox in multiplayer, unless the server has sv_cheats set to 1. Can't use cheat cvar fog_endskybox in multiplayer, unless the server has sv_cheats set to 1. Can't use cheat cvar r_farz in multiplayer, unless the server has sv_cheats set to 1.

So apparently these cvar changes are not important to normal user at all, and if a game developer has enabled -dev parameter, he must have explicitly set sv_cheats 0 in autoexec.cfg to block these cvar changes.

Therefore, I want to ask whether valve / Robin will consider to remove these cvar changes (which are usls for normal user and public build) or not?

In addition, I can recall that the same thing happened for Portal 2 as well, but I am not sure atm.

Best regards, UnknownzD

alfred-valve commented 11 years ago

This is by design, "-dev" automatically sets sv_cheats 1 which then causes achievements to be disabled.

UnknownzD commented 11 years ago

Well actually the problem itself does not sit on the sv_cheats 1 change at all, as sv_cheats 1 does not automatically switch off the achievement until someone changed a CHEAT flagged cvar after setting sv_cheats 1. It is clear the cvar change on fog_start, fog_end and other cheat cvar has caused the problem instead.

But as long as not much user are using it atm, guess it would be fine even if it doesn't get fixed.