I believe there are some other use-cases that this restriction
hinders/prevents without additional features in the API.
IIRC, last time this came up, Matt Ebb spoke up regarding his
RenderMan exporter, where selecting a shader file adds its parameters
as properties to the material, or something li
On Mon, Feb 18, 2013 at 2:18 AM, Nathan Vegdahl wrote:
> I believe there are some other use-cases that this restriction
> hinders/prevents without additional features in the API.
>
> IIRC, last time this came up, Matt Ebb spoke up regarding his
> RenderMan exporter, where selecting a shader file a
Hi all,
Here are the notes from today's session in irc.freenode.net #blendercoders:
1) Blender 2.66 release
- Bug tracker is nice low (below 70), but can still use attention.
- Sculpting currently doesn't draw GLSL (and matcap) with masking option.
Sergey Sharybin could look into it, but Nicho
Thanks for the fix Irie!
> Anyway, I don't understand why you did such big changes in Bcon4...
Fair enough. It seemed like the best option of bad options. I'm
currently working with a studio to improve Rigify for their pipeline,
but I have a limited amount of time to be on-site working with the
Hey guys,
I'm fairly new to the Blender codebase, but I am really interested in getting
Alembic into Blender as a personal project. More information at alembic.io
So far I got Alembic compiled on my OSX system, haven't tried windows or linux.
Some things that I noticed right away:
- OpenEXR's d
On Mon, Feb 18, 2013 at 4:58 AM, Nathan Vegdahl wrote:
> Thanks for the fix Irie!
>
>> Anyway, I don't understand why you did such big changes in Bcon4...
>
> Fair enough. It seemed like the best option of bad options. I'm
> currently working with a studio to improve Rigify for their pipeline,
>
It becomes the error when I perform the saving of labor of the item of the
middle of condition operator (?:) in msvc9.
You should set the value of the condition sentence without omitting it.
sequencer_edit.c
line:845,856
PerfectionCat.
___
Bf-committe
Fair enough.
Rigify is a bit unique among the addons, though, in that it is
designed to be extensible via additional rig types. And this is
coming up here, where the version of Rigify in the official repo and
the version on their local machines with custom extensions conflict.
For this use-case,
> However this isnt about py devs writing inefficient code, but my point
> is that allowing bad interactions between drawing UI and managing
> settings is error prone and a UI shouldn't be editing blend file data
> anyway.
> We dont accept this in our C code (as a convention), why allow bad,
> erro
> Is there some way that we could rework addon loading such that local
> versions of addons (e.g. in .config/blender/x.x/scripts/addons)
> override and take precedence over official repo versions? That way it
> is easy to have local versions of addons. With a lot of addons that
> might seem point
10 matches
Mail list logo
