Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Filter it (right hand side menu) for Errors, Warnings or Critical events, then check for anything it finds from the time-frame of these crashes.
Any log entries you find may provide more information about the cause of the crash.
only a few basic errors, nothing SFM related.
Well, another standard fix that you haven't specifically mentioned is resetting the game configurations on the SFM SDK menu.
Idk what to do man
i had almost 300gb worth of data there.. And SFM STILL took it all. Now i guess i over-saturated it.
And the servers could be an issue, but i never had an issue last saxxy
anyway, i will try
Had to move a LOT of stuff as backup.
Those models should not be in your usermod folders at all. 90% of these SFM problems are caused by ppl adding custom content to the usermod folder. Your custom models, materials, particles and sounds should be wrapped up in individual mod folders under the games folder and added to your gameinfo.txt file using the "Edit Search Paths for Selectexd Mod" feature of the SDK.
The Event Viewer is a neat and handy tool that can be used for diagnosing ANY application that crashes really.