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
It's probably more likely the age of the program showing.
SFM is 32 bit, and by it's very nature has issues that other, more modern software doesn't have.
SFM also has not seen an official update since about 2015, if I'm not mistaken.
Valve seems to have no real interest in updating it or rewriting it to bring it up to current technology specs, so we're stuck with it, or some other animation software that is out there...
Yes, Blender is increasing AMD support with updates, but SFM is abandoned software.
If the problem is not AMD related, that would make me happy, but I still don't know how to fix the problem. Trying to animate with 2 FPS is very difficult.
I think I remember that Zappy (a popular regular here) has AMD GPU. Maybe they can help you better. Best to wait.
It seems logical to me that there may be a problem with the drivers. Graphics card usage drops below 4% in FPS drops.
All I know is that Source Filmmaker's ambient occlusion supposedly looks different on AMD and NVIDIA GPUs, and that (as long as you use a "good enough" GPU,) Source Filmmaker is typically limited by single-core CPU performance.
Like you, all I can suggest is double-checking that Source Filmmaker is using the correct GPU (if the computer has both integrated and discrete GPUs).
I am using Ryzen 5500 and this processor does not have integrated graphics.
Since it's not one of those familiar SFM errors, two things come to mind. The driver is faulty or turned off AMD's automatic CPU Overclocking(CPB) was bad idea.
I struggled with this ridiculous problem for a few months and gave up. But, last week, I deleted my AMD driver because it gave an error and I switched to the Pro driver, which was said to be more stable and same FPS with Adrenalin.
I can now use HIP in Blender and SFM is very smooth.
I can't believe I haven't tried Pro drivers all this time. Darn...
Pro drivers are more stable.