On Mon, Mar 9, 2015 at 4:10 AM, Ton Roosendaal wrote:
> Hi all,
>
> Here are the notes from today's meeting in irc.freenode.net #blendercoders
>
> 1) Upcoming release
>
> - There are a couple of issues open to be fixed, but it's possible to call
> for an RC this week. Sergey Sharybin proposes tha
Sure thing. The packages I had to install I found through failed
compiling attempts, so your required packages might vary.
Install glew-devel, libXmu-devel
Skip bootstrap.py and go straight into cmake-gui
Point ILM libs to /opt/lib/openexr/lib/...
Enable HDF5 and point HDF5_DIR to /usr/bin
D
Hi,
It is, just wiki page needs an update. Plus now we need to port our
bindings to the new API.
On Sun, Mar 8, 2015 at 10:51 PM, Sam Vila wrote:
> Hi Ton,
>
> Just a quick note about the goals for 2.75, one of the points says
> 'OpenSubdiv (We wait for Pixar to release 3.0)'. This is actually
Francois, this is really bad altitude which should be even mentioned in
open source projects like Blender (this might be acceptable in other
open-source project if it's some really nasty security issue found and work
is needed to solve it, without attracting all the bad guys around). This is
not so
Hi Ton,
Just a quick note about the goals for 2.75, one of the points says
'OpenSubdiv (We wait for Pixar to release 3.0)'. This is actually released
on this as far as I know:
http://graphics.pixar.com/opensubdiv/docs/release_notes.html
and:
https://github.com/PixarAnimationStudios/OpenSubdiv
_
Hey Campbell,
thinking about a older comment you made about users will want to only test
the shiny one with all the new features. I kind of agree with that, I would
probably be the first. But who says that this version tested/compiled via
CI should be available to public ?
Like the way only certif
Hi all,
Here are the notes from today's meeting in irc.freenode.net #blendercoders
1) Upcoming release
- There are a couple of issues open to be fixed, but it's possible to call for
an RC this week. Sergey Sharybin proposes that he and Campbell will check on
the status tuesday.
- Open issues:
> A) The VSE was designed for realtime playback. As such, most of the VSE's
> work has legacy low quality 8 bpc code paths.
Anything specific? - All code paths should on floating point images too.
___
Bf-committers mailing list
Bf-committers@blender.org
On Sat, Mar 7, 2015 at 12:57 AM, David Fenner wrote:
> Truth be told, release candidates aren't very well tested anyway. It's when
> a true release comes when true testing begins. I say it as an artist myself.
>
> My personal opinion on this matter is a little more unorthodox, I think
> there simp
Hi,
That's true that real testing starts after the release. But it doesn't we
shouldn't make it so master is as well tested as we possible can do it.
As for the rest of suggestion -- we already had that in more early 2.5x
days. That approach has it's own strong and weak sides. Strong side you
alr
Hey Jeffrey,
can you give a short overview how you managed to build Alembic on Fedora?
That would be awesome!
Thx,
Thomas
On 03/08/2015 07:06 AM, Jeffrey wrote:
> I got Alembic building thanks to Martijn's fork on github and got
> blender building with support. I've tested that it works within b
On Sat, Mar 7, 2015 at 2:11 AM, Sergey Sharybin wrote:
> I would say:
>
> - Being able to filter in dev.b.o is omsething we must have. I've created a
> quick patch to filter differencial revisions by project [1]. It was
> rejected by upstream because phabricator team wants to have general way to
>
12 matches
Mail list logo
