[Bf-vfx] Tomato camera sensor changes

Ejner Fergo ejnersan at gmail.com
Fri Aug 19 13:41:56 CEST 2011


Hi again,

Sorry if I sound angry, I'm not :)

I just don't understand why there has to be so much fuzz about _one_
more setting? It is not 1000 new settings (as we will have anyway as
Blender evolves...) But lets focus just on the camera ;)

We all agree that the Blender camera has been primitive up until now,
and the workflow has been less than stellar for advanced camera work
(using BLenses in 2.4x or manual calculations using formulas). Having
these things integrated is so much better, right? What the sensor
patch presented, was focal length on its own because this is for all
people the most important setting. Then there was FOV values (either
horizontal or vertical). This is purely for information, and will
never be touched by most people so they can ignore it like they ignore
the Degree option today, but it's there for those who need it. Lastly
we got the sensor dimensions. Most people that don't know/care about
cameras will again ignore this and just use the default 32x18 mm
setting. UI wise it was not a mess either (not an overload of
settings).

Lets not make this a bigger deal than it is, because it won't matter
to most that there's (few) settings they will never touch. There will
be more settings as we need them - look at Cycles and the settings it
adds to the camera. Should these be discarded as well because we don't
want to scare away users who is not the target audience?

I appreciate the thought of simplifying things, but I'm afraid we are
past that point in Blender overall. Why do this now to the camera,
which is crippled as it is? I really shouldn't try to justify the
addition of a setting, but feel I need to because of misconceptions.

Best regards,

Ejner


More information about the Bf-vfx mailing list