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
You sure you've switched to GPU for rendering? I got render times like that when I use my old Intel quad core for rendering. ^^
Unfortunately no. The render is on the video card. I installed the 497.29 driver again and the render time is basically 30 minutes (instead of 43 hours on the new drivers) https://i.imgur.com/xIhNM9R.png
Regardless of the driver version, the video card is always loaded at 100%
Also Blender always goes unresponsive for a while when I save the project
It's very unstable for me at the moment
Try selecting OptiX in System preference and make sure to confirm your GPU is checked.
Uncheck CPU just to be absolutely sure you are fully using your GPU.
If you know more about this issue, please send your report to the blender developers (https://developer.blender.org/)!
Or your card overheats and is throttled (unlikely, but who knows).
Try rendering the default scene with a massive sample size (so it runs for a while) and see what happens.
Graphics card stays within 70 degrees and never overheats
I've done some testing and may have found what's wrong. I made a scene with several cubes, a volume and a strong light source, and also set a large sample size.
Results:
497.29 driver - 4 minutes 12 seconds (806 MB of video memory used)
527.56 driver - 3 minutes 45 seconds (806 MB of video memory used)
At the same time, the viewport works quickly and responsively in the cycles render mode. Just like I planned
I also ran a test with a complex scene and then everything got much worse:
497.29 driver - 22 minutes 51 seconds (8775 MB VRAM used)
527.56 driver - 35 minutes 37 seconds (8775 MB of video memory used)
The viewport is quite buggy and poorly responsive in both versions of the drivers (but this is logical since the scene is complex). In the viewport, the view mode in cycles on the 497.29 driver works as expected - it gradually develops the picture. On the 527.56 driver, cycles almost doesn't work in the cycles view mode (more precisely, it works, but it's even slower than my four-core processor).
In render mode 527.56 the driver is unstable. I had to wait 11 minutes for the first sample to load. And I'm still lucky. Sometimes the render time can be 44 hours for a single frame (see screenshot in the question)
As a result, we can come to the conclusion that with the new drivers, the blender is unstable when the video memory is almost completely loaded.
I recorded the workflow of all tests on video in an accelerated version: https://drive.google.com/drive/folders/1_oMmj90PLXiojBbORk8W1ynpdzITi6gJ?usp=share_link . I advise you to download the video to your computer so that it does not compress when viewed through Google Drive ...
EDIT: Ok, so you aren't a beginner I checked your profile. So then maybe power supply? Might be your scene that is causing issues. Import everything into a new scene and try it again. In my case lately I've experienced a lot of crashes.
I turned to the developers of the program (https://developer.blender.org/T103450) for help, but that didn't help either.
The only solution is to use driver 497.29 while working in blender. After the work is completed, install the latest version of the drivers back