Hi Julian, don`t worry, I'm sorry for my panic attack, my English is
very basic.
Now I'm working with a previous version and seems that all is ok
Thanks for your great work
El 07/03/15 a las 18:09, Julian Eisel escribió:
Hi Jose,
I already had a look at your report after your updates, but
Hi Jose,
I already had a look at your report after your updates, but was only
halfway able to reproduce (don't want to go into details here). My
plan was to investigate this further first, so I didn't change the
status yet. Anyway, I'm sorry for not coming back earlier to this,
will investigate
Hi, sorry if this is considered high-jacking the thread.
What do you mean by no scopes in the compositor? You can use a viewer node
and use the (fantastic :) scopes of the UV/image editor. What would you
prefer? A scope node that display the scope directly in it's own UI in
the node editor? That
On Mar 7, 2015 5:29 AM, Xavier Thomas xavier.thomas.1...@gmail.com
wrote:
What do you mean by no scopes in the compositor?
I don't consider the scopes of the sequencer nice, I consider them
horrible
and horribly slow; they really should be ported to openGL and reuse the
code of the image
Hi, I'm stuck in delivery of work because of this bug:
https://developer.blender.org/T43908
The bug has been considered incomplete but a second look you will see
that it is not incomplete.
I think it would be a good idea solve it, for Blender community.
Thanks for your great work
I remember a few demos by lukas toenne in which he had prototypes working
with modifier nodes and particle nodes. Actually he was making arrays and
such with nodes... Sadly I can't find the videos right now... but clearly
he should be able to help you a little, maybe share his first attempts.
I would second Troy on that, if you are going for a node as simple as a
vignette, try to make it as accurate as possible which can handle real AC
and could do reverse vignette, and part of this is usually linked to the
Lens model.
Going for a simple node which only do a mask or compute the length
Thanks for that, but there is one particular video with modifier nodes in
which he made arrays of a suzzane that is nowhere to be found :S In fact
the nodes flowed left to right, the one that flows up to down is an old
version :S
2015-03-07 8:54 GMT-03:00 Kévin Dietrich
Sorry Xavier, I didn't mean it that way. I was more referring to the
workflow of having realtime feedback of the scopes in the sequencer compare
to the compositor rather than the scope code itself.
Like Troy says, it more the underlying design of both compositor and
Sequencer where one is meant to
Hi,
Have you considered using the git flow workflow [1]? The idea is that you
keep one branch (probably master) always ready for release. Then you have
an unstable/staging branch called develop. All significant development is
done on feature branches. I've found it to be quite nice in my own
Le 06/03/2015 09:38, Sergey Sharybin a écrit :
We could approach to the issue of applying patches from a totally different
angle tho. Screw it creating branches in the main repository, just whoever
is responsible for that patch could have a local staging branch with all
the commits ready for
I got Alembic building thanks to Martijn's fork on github and got
blender building with support. I've tested that it works within blender
and reads from stored caches. Where is the best place we can ask
questions or give feedback? Here or on the patch tracker?
On 03/05/2015 04:15 AM, Sergey
12 matches
Mail list logo
