That’s where it was saved by default when I downloaded it. Hence the Frame designations for each file. I rendered the file exactly where it was when I downloaded the file. ![]() I made no other changes or edits to the files. Yes, I realize “Experimental” would have given different results, but I wanted consistency across files. After opening each file, I set the Scene Render Settings to: Cycles, Supported, and GPU Compute. I had a fresh download of all the files from the Blender site. In Blender > Edit > Preferences > System, under Cycles Render Devices, Metal was selected and so were both the CPU and GPU. The only other app I had running was Activity Monitor to verify when the app had finally spun down. Then I upgraded to Monterey 12.3, rebooted twice, and followed the same procedure. I did a restart of the machine, let the CPUs settle down from their post-boot activity and rendered each file one at a time. My machine is a 14" MacBook Pro with an M1 Max (10c CPU, 32c GPU, 64GB).įirst on macOS Monterey 12.2.1 with Blender 3.1. (Quick side note, can a Blender admin please rename the files with meaningful names? Many of them are called blender2.blend, or blender3.blend.) ![]() So, out of curiosity, and excitement for the release of Cycles for the M1 Macs, I ran render benchmarks for all of the Splash Screen files as listed on the Blender Demo Files page.
0 Comments
Leave a Reply. |