Open 7-0r opened 6 months ago
Upon checking the beta branch, I noticed that the the 32x and 64x bit exe are not getting installed, only installing the hl2.exe.
Trying to launch the game by entering into the command prompt hl2.exe -game "tf"
ended up with the game crashing after loading for a bit.
``` For FCVAR_REPLICATED, ConVar must be defined in client and game .dlls (sv_use_steam_voice) [TF Workshop] Got 0 subscribed maps, 0 new ProtoDefs post data loaded. ProtoDefs loaded. 31.27 MB used ProtoDefs post data loaded. ProtoDefs loaded. 31.27 MB used maxplayers set to 24 Steam config directory: D:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\platform\config CClientSteamContext logged on = 1 ProtoDefs post data loaded. ProtoDefs loaded. 31.27 MB used ProtoDefs post data loaded. ProtoDefs loaded. 31.27 MB used Cleaning up unneeded replay block data... Replay cleanup done. Unknown command "m_rawinput_onetime_reset" Loading default settings for high sensitivity Creating fallback sound cache at: d:\program files (x86)\steam\steamapps\common\team fortress 2\tf\sound_workshop ProtoDefs post data loaded. ProtoDefs post data loaded. Client out of date -- world version 8835751, current version 8207200 Connection to game coordinator established. CTFGCClientSystem::PostInitGC CTFGCClientSystem - adding listener ProtoDefs post data loaded. ProtoDefs post data loaded. 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. Applying new item schema, version D8C03F67 **WARNING** Failed to apply item schema! Item definition 31289 "#TF_taunt_the_crypt_creeper" failed to initialize taunt data! ```
The crash is Steam-related and was present prior to the 18 April 64-bit update, it's nothing new. It can be worked around by "going offline" in Steam.
this issue is present even on offline mode
As a temporary fix use ficool2/custom_items_games
-insecure
this is the error when i try to launch it