Not a bad speed-up running under Rosetta emulation! Here's hoping they follow thru on native M1 code!

Vincent Bedroom Full 1m30s, adding the jumping skeleton needed another 10 seconds.

No, it's stored in really, really fast cache. Apple has said no such thing about their Intel machines, except they will all be gone soon. This little guy is FAST, and the fan doesn't spin up!

Put a Ryan_Casual on the bridge with the skid_steer_loader and it added two seconds to the render time. Hmmm, what else...

You would be surprised. The old way of counting MB of RAM is dead, the Mac now has only cache memory. Very, very different. Still adding things in my quest to slow this thing down!

I put a steampunk zeppelin skid_steer_loader on the VP bridge, and it rendered with defaults in 24 seconds. I keep adding things to see if I can get it over a minute.

"The GFXBench 5.0 benchmarks revealed that the M1 often outperforms the Nvidia GeForce GTX 1050 Ti and AMD Radeon RX 560. According to Apple, the M1's 8-core GPU can juggle up to 25,000 threads, with the potential to deliver up to 2.6 TFLOPS of throughput." - TechRadar

The Poser M1 is running slick as a whistle!

Been playing with it on a new M1 Mac mini, and WOW!

Aha! Yes, well spotted! The second announcement e-mail was far better than the first. No native M1, but they did say "Yet!"

Those are the minimums and are are not useful for purchasing decisions with the changes going on in the Apple processors.

Just released! No information on what version of OS, and of course nothing on M1 and Big Sur (even if it will run in emulation).

Quote -
More usefully, why don't they break up the work of a render by bucket,.

The four processor restriction per picture is silly too once you have a network render engine.   If you aren't doing animations, then the network rendering concept is useless.

Quote - each core just has it's own little region and just sits there idle as its buddies finish the task...

The way they break up the picture is really annoying.  Why not just break up the picture into a dozen squares and give each processor a block in turn?  I have 12 cores just waiting, and waiting and waiting...

Why does doing a bunch of regions instead of the entire picture at once to get better processing speed not work only because they leave a black line around the rendered area?  Fix that and I'd be happy, since it's what we want with multi-processing (hint hint).

When you go up a menu, why does it reread the entire directory structure every single time, and then go to the top of the menu?   I don't add content all THAT often!

Why can't you turn off some of the undo's, like camera movements?  I move to see what happened when I change something, and then have to undo return to the original view to undo a change?