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
I notice this behavour happens most when I render a clip and decide to do other things like screen captures, working with python script based programs like gimp or blender while SFM renders in the background. If I just let SFM render and leave things a lone, the render usually processes without problems. It may be a resource problem.
When it happens, I usually delete the render session (mp4) and the .txt files created durning the bum render, start the render over and walk away from the computer.
in my current project i have scenes i was able to render fine without the blue or other weird glitches by lowering the DoF from 1028 to 512. in a previous project i ended up rendering in a lower resolution entirely to avoid it.