I don't know if I am sending this message twice or not, because I was not
subscribed to the mailing list before. Forgive me if I am.
In past versions of Blender the xaxis mirror used to be located under the bone
properties menu. A location that I believe makes sense. Over time, as the
Blende
Hi,
> Afaik, this is not desired into Blender currently…
As an open source project we should say "this is not supported becase we don't
have stakeholders who are providing active development in this area.
-Ton-
Ton Roosendaal - t...@bl
Hi all,
Here are the notes from today's meeting in irc.freenode.net #blendercoders
1) Release review
- The 2.72 release is now official! We even have a release log on blender.org:
http://www.blender.org/features/2-72/
Special thanks to Marco Ardito!
- Still open to do credit list (I will do
Hi Daniel, of course I know you can change that on the menu, what I'm
saying is that BI is a feature complete render engine (maybe not the best
quality ever but it's complete), Cycles is not complete, one more example:
The render passes in cycles are most of the time unusable, try to get an
object
If you look at it like this, you will always find something missing. Cycles is
not Blender Internal, it’s a totally different type of engine.
Both have pros and cons. That is not a reason to postpone the default switch.
Am 05.10.2014 um 23:17 schrieb Sam Vila :
> Hi Daniel, of course I know you
While all of those are legitimate issues Sam, I agree with Thomas. There
will always be features that're needed for this or that reason. And can we
really ever say something is feature complete? The research and development
is constantly progressing, bringing new, "necessary" features all the time.
Yes, ID passes do not work with motion blur and depth of field, and the
only solution is deep compositing, just like it would be for Blender
Internal if it actually supported these features.
The thing is that you can list many missing features in Blender Internal as
well. No depth of field, no 3D
Done bug reports, done building, would like to help on Triage and eventually
Patches/reviews (soon as I learn how to use GIT).What is the process for
triage? Just commenting on bugs if you find it is real or not on your platform?
On Sunday, October 5, 2014 11:54 AM, Ton Roosendaal
wrot
Thanks for the replies, I just wanted to show some of the features that I
think Cycles would need to be as flexible as BI. If we have a fix for the
passes and the ability to play in a non-physical correct way with some of
the settings then it would be great!
As I said it's great that you can cheat
Triage is
0) Decide if it is a bug or is really a feature request
1) Making sure all of the information needed to reproduce the bug is
present (platform, simplified test file, stacktrace, etc.)
2) Attempt to verify the bug
3) Assigning the bug to a developer with the relevant expertise
LetterRip
It is only the default setting, most existing blender users will not ever
notice any change as they are likely to have a startup file that is tuned
to their liking.
This mostly applies to users who are new to blender. In that category there
are 2 groups for both of which I think you could argue tha
2.5) Check again if this is not a duplicate.
Both this step and assigning will become easier the more you practice.
But even just verifying bugs ( trying to redo the bug based on the
description ) and then if needed just adding all the missing details is
very very helpful.
On Mon, Oct 6, 2014 at
12 matches
Mail list logo
