EClark1894 posted at 11:35PM Sun, 31 January 2021 - #4411494

ssgbryan posted at 3:08PM Sat, 30 January 2021 - #4411452

What Wolf said.

Apple is leaving the PC market space.

Says who?

Pessimists ever since the iPod came out.

fbastos posted at 5:44AM Wed, 18 December 2019 - #4373643

I am flabbergasted, and NOW I get the difference between a simpler tool like Blender, DAZ or Poser and a professional rigging tool, that thinks of all details like whether the foot should be touching the front or back in the ground, and handles that for you.

Maya doesn't do this for you. A rig like that is built by hand by a human rigger. There are plenty of tutorials on YouTube on how to rig foot roll in Blender.

fbastos posted at 7:21AM Tue, 17 December 2019 - #4373465

Poser has much more capability than the ones displayed at that movie, and yet trying to replicate the first 30 seconds of the movie in Poser would be a like herculean task, taking hundreds of hours or more.

That's because 30 seconds of animation do take hundreds of hours, even in a professional studio.

bagginsbill posted at 3:32AM Wed, 17 July 2019 - #4357179

Nodes are not dangerous. People are. So is a little knowledge.

You're both right. And both wrong. There is no single bottleneck that applies to all scenes equally. You can have scenes that spender 90% of their render time on shader evaluation, you can have scenes that are 90% ray intersections, you can have scenes that are 90% lighting. Even without going to pathological artificial examples, I've seen pretty much all of that in the wild.

If you want the true answer, Blender now has an integrated profiler for Cycles that will give you a report of how it spent its time: https://developer.blender.org/D3892

Congratulations, Renderosity! All the best for your and Poser's future!

putrdude posted at 1:55AM Thu, 06 December 2018 - #4341273

Also, I was rendering to 6600 x 10200 at 600 pix/in, NOT 1427 x 1080 so that could account for the "takes forever" part.

That's more than 40 times the pixels, so naturally it would render more than 40 times longer.

DramaKing posted at 7:18AM Tue, 25 September 2018 - #4335917

I think it was was the same studio that created VFX for The Man in the High Castle in Blender.

It's a different studio. The one you're thinking of is Theory Studios, "Next Gen" was done by Tangent Animation.

Why so complicated? Here's a simple test. A box, a sphere, a spot light.

zero bounces:

one bounce:

two bounces:

sixteen bounces:

aeilkema posted at 6:51AM Wed, 06 June 2018 - #4331123

Making it even worse is that some of the key players in Poser development refused to move countries (and rightfully so).

We weren't asked to move countries. We were laid off.

That has been possible since Poser (4) Pro. Look in Runtime/Python/poserScripts/SampleCallbacks for examples.

C++.

how do you control how soft shadows are with a spot light using Superfly?

Change the scale of the spot light. Like in real life, the shadow softness in SuperFly correlates with the size of the light source.

You can turn on Branched Path Tracing and try how it works, it's not disabled or anything. You should however keep the individual sample settings to 1 (all the ones on the left side), to prevent the GPU process from getting a time out. If the scene and shaders are too complex however, even low settings cannot prevent the OS from interrupting the GPU render process, and that's why the UI recommends to not use GPU and branched path tracing together.

There isn't a single standard for how tangent space normal maps are supposed to be interpreted. For games, where they are very popular, this isn't a problem, as assets and code go hand in hand. For other programs, it seems like everyone came up with their own recipe and that makes it hard to interchange normal maps reliably.

For what it's worth, normal maps in SuperFly use the "MikkT" tangent space, which is gaining in popularity and source code for generating those tangents is available to everyone.

piersyf posted at 3:06AM Thu, 26 November 2015 - #4241017

Same scene, same settings, rendered in Superfly. Note that the geometry/texture problem is gone. It might interest people to know that this rendered in 5 minutes 17 seconds using GPU (GTX970), and 55 seconds using CPU (i7 hex core). Don't assume GPU will be faster... it depends on what you are rendering.

What was your bucket size? GPU rendering typically benefits from much larger buckets than CPU rendering - try 256 for a start.