UMEGA
Account Details
SteamID64 76561198208693025
SteamID3 [U:1:248427297]
SteamID32 STEAM_0:1:124213648
Country United States
Signed Up September 22, 2018
Last Posted September 30, 2018 at 3:59 AM
Posts 9 (0 per day)
Game Settings
In-game Sensitivity
Windows Sensitivity
Raw Input  
DPI
 
Resolution
 
Refresh Rate
 
Hardware Peripherals
Mouse  
Keyboard  
Mousepad  
Headphones  
Monitor  
#9 The Random Crashes Are Back! in Q/A Help
Joe_ShroeTry these too if the other suggestions don't work:

-disabling html MOTD in advanced options (performance options)
-removing custom hud folder
-removing graphics configs
-disabling HDR in video settings
-disabling player models in advanced options (HUD options)

I also did that!

posted about 6 years ago
#7 The Random Crashes Are Back! in Q/A Help
gemmUMEGAgemmafter deleting cfg did you do -autoconfig and host_writeconfig and try again with a different cfg? kind of a shot in the dark but it could be happening only with a specific set of cvars/hardware that you could find a workaround forwhat do you mean? im not that good with console commands.
clear your cfg folder (probably should uncheck steamcloud too in steam settings for the game), verify, launch the game with -autoconfig, then type host_writeconfig in the dev console. then restart and remove the launch option, it'll reset all your game cvars. btw Bonnie is EXTREMELY cute.

most binds should be fine to replace if you have custom ones

Thanks I will try!

posted about 6 years ago
#5 The Random Crashes Are Back! in Q/A Help
gemmafter deleting cfg did you do -autoconfig and host_writeconfig and try again with a different cfg? kind of a shot in the dark but it could be happening only with a specific set of cvars/hardware that you could find a workaround for

what do you mean? im not that good with console commands.

posted about 6 years ago
#4 The Random Crashes Are Back! in Q/A Help
glassi agree hard crashes have been much more common for me after the recent update. right when i join a server.

you could email valve that info, i guess.

I already did!

posted about 6 years ago
#1 The Random Crashes Are Back! in Q/A Help

About two weeks ago the game started to crash sometimes when i entered a match, without giving any crash messages, and i searched for a solution since than. I couldn't find one, I tried Verifying game files, reinstalling, deleting the cfg media sound and custom folders, and I looked for help on other forums.
This time though, I finally dug out a crash message! in the windows event viewer:

The program hl2.exe version 0.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 7a8
Start Time: 01d457c00302ec03
Termination Time: 245
Application Path: D:\Video Games\SteamLibrary\steamapps\common\Team Fortress 2\hl2.exe
Report Id: 4c84ae5b-ff8d-4a80-b8c0-a0ccd73d04ed
Faulting package full name:
Faulting package-relative application ID:

Here is the full image: https://imgur.com/gallery/8flLuI0
If anyone can help, I would really appreciate it!

Edit: it stopped for a while and than returned so thats why the title says the crashes are back.

posted about 6 years ago
#15 Medic Autoheal in Q/A Help

beep.

posted about 6 years ago
#5 How to fix broken viewmodels? in Q/A Help
Firehonestly i dont see the problem you have, could you explain it further?
viewmodel_fov xy
is the command to set your viewmodel fov if youre looking for that.

i said that thats what i found when i searched for how to fix my problem. the problem is the hand in the left side of the screen. and if youre just trolling then lol.

posted about 6 years ago
#1 How to fix broken viewmodels? in Q/A Help

I know that there are probably tons of threads asking this but all i can find is 9 year olds showing you how to set your viewmodel fov to 90. What i mean by broken viewmodels is stuff like this https://imgur.com/gallery/3Z06ZFP
How do i fix it? is there something to put in the custom or cfg folders to make it invisible? btw i have transparent viewmodels but that definitely isnt causing the problem.

posted about 6 years ago