Hi people.
Did someone read this ? It's been posted yesterday, and it seams to me
that's a great functionnality to be included in Blender.
The video demo is impressive, and I hope devs will see it that way too :).
Mike.
Le 31/05/2010 13:17, Vincent Nivoliers a écrit :
> Hi all,
> I'm conta
It seems to be this commit (29110)
https://projects.blender.org/plugins/scmsvn/viewcvs.php?view=rev&root=bf-blender&revision=29110
2010/5/31 Daniel Salazar - 3Developer.com :
> I didn't see the commit on the mailing list :o are you sure you
> commited to you branch?
>
> cheers
>
> Daniel Salazar
>
Hi,
Nice work with the new tool. :) I hope you don't mind, I committed a
small change to your branch that fixes compilation for me (there was a
linker error due to a function called convex with more than one
definition.)
-Nicholas
On Mon, May 31, 2010 at 9:31 PM, Matt Ebb wrote:
> if i'm not mi
if i'm not mistaken, you also have to sign up to the bf-blender-cvs mailing
list with the same email address you used for the projects.blender.org account:
http://lists.blender.org/mailman/listinfo/bf-blender-cvs
On 01/06/2010, at 11:28 , Daniel Salazar - 3Developer.com wrote:
> I didn't see
I didn't see the commit on the mailing list :o are you sure you
commited to you branch?
cheers
Daniel Salazar
www.3developer.com
On Mon, May 31, 2010 at 3:04 PM, Raul Fernandez Hernandez
wrote:
>
> and here's the patch
>
> http://www.pasteall.org/13481
>
> Cheers Raul
>
> _
Hi Nick,
I think you may need to set ID_NEW in sca.c::set_sca_new_poins_ob for
your new Object structs as well. (as we are doing for the other Object
structs).
Regards,
Dalai
2010/5/31 Nick Samarin :
> Revision: 29111
>
> http://projects.blender.org/plugins/scmsvn/viewcvs.php?view=rev&ro
That would explode the list. There's far to many combination of container and
codecs for that.
The list already contains the three most frequent choices (xvid, ogg, h264),
the other option should be called ffmpeg (that doesn't mean anything), it
should be called something a bit more meaningful,
I immediately commit after I merge which gives me a version number
close to what I need to use next time. It will be head+1 unless the
repository is really busy :)
But it may help to put the actual number in the comment so I'll do
that too
On May 29, 2010, at 8:52 PM, Dalai Felinto wrote
and here's the patch
http://www.pasteall.org/13481
Cheers Raul
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
Hi guys!
I finally committed the unlimited clay feature to my branch: it have
several design desitions that should be discussed later like the exposing
the mesh tools (though I think are rigth ;) )
A warning: it dosen't work with multires currently, seems that multires
don't initialize few fiel
I'm anxious to integrate this into my branch.
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
Yah Tom but I believe that is for new brushes, the existing brushes
settings are saved on the default blend file. Raul I will have a look
into it after you commit
pura vida
Daniel Salazar
www.3developer.com
On Mon, May 31, 2010 at 2:10 PM, Tom M wrote:
> Raul,
>
> in blender/blenkernel/intern
Raul,
in blender/blenkernel/intern/brush.c
set
brush->detail = .25f;
see the spacing setting for an analogous situation.
LetterRip
On Mon, May 31, 2010 at 12:08 PM, Raul Fernandez Hernandez
wrote:
> Hi :)
>
> Thanks for the really quick repply ... yes, I think I will commit without
> the def
Hi :)
Thanks for the really quick repply ... yes, I think I will commit without
the default value and then an experienced dev could do that, after all is
what open source is about ;)
The default value of 0.05 is very dangerous because it subdivide a lot
the mesh, so 0.25 is a safer value.
I will
If it's the default value, before change the default blend, you can
try with a do_versions.
Change the default blend file always come with problems ;)
On Mon, May 31, 2010 at 4:51 PM, Daniel Salazar - 3Developer.com
wrote:
> BTW this should be done very carefully, if you want you can just
> commi
BTW this should be done very carefully, if you want you can just
commit like it is and I will fix the defaults later?
cheers
Daniel Salazar
www.3developer.com
On Mon, May 31, 2010 at 1:49 PM, Daniel Salazar - 3Developer.com
wrote:
> Hi Raul, those are actually saved in the B.blend.c file
> (/
Hi Raul, those are actually saved in the B.blend.c file
(/blender/source/blender/editors/datafiles and you would need to
generate a new compilable default blend file using the datatoc.py
script included in release
pura vida!
Daniel Salazar
www.3developer.com
On Mon, May 31, 2010 at 1:45 PM, Ra
Hi all :)
I'm about to commit to my branch the Unlimited clay feature for
sculpting, but I'm getting troubles trying to set up the default value
for the new property brush.detail, in the RNA the range is 0.05-1.f where
0.05 subdivide a lot the mesh and 1.0 is quite rough so the default vaue
shoul
On Mon, May 31, 2010 at 3:48 PM, Mike Belanger
wrote:
> Absolutely +1 from me. FFMPEG is currently a minefield for users, even
> developers.
>
> Although, I must warn different encoding settings work on different
> platforms. So the presets would
> best be OS-specific.
My understanding of FFMP
Absolutely +1 from me. FFMPEG is currently a minefield for users, even
developers.
Although, I must warn different encoding settings work on different
platforms. So the presets would
best be OS-specific.
On Mon, May 31, 2010 at 6:50 AM, Thomas Dinges wrote:
> +1 for this :)
> This way we may
+1 for this :)
This way we may also reduce the amount of ffmpeg bug reports. :P
Am 31.05.2010 13:47, schrieb Joshua Leung:
> Yep.
>
> On Mon, May 31, 2010 at 11:44 PM, Thomas Dinges wrote:
>
>> So you mean, put all possible combinations that work and we support,
>> into the list and get rid o
Yep.
On Mon, May 31, 2010 at 11:44 PM, Thomas Dinges wrote:
> So you mean, put all possible combinations that work and we support,
> into the list and get rid of the manual settings for codec/format?
>
> Am 31.05.2010 13:41, schrieb Joshua Leung:
>> +1 to this suggestion.
>>
>> While technically
So you mean, put all possible combinations that work and we support,
into the list and get rid of the manual settings for codec/format?
Am 31.05.2010 13:41, schrieb Joshua Leung:
> +1 to this suggestion.
>
> While technically it might be nice to be able to control these things,
> the fact with FF
+1 to this suggestion.
While technically it might be nice to be able to control these things,
the fact with FFMPEG is that it is only usable with a very select few
combinations, and even then only under strict conditions (any other
combinations either crash immediately, crash on the last frame of
It's confusing indeed. However most uses don't have a clue what FFMPEG
is, which makes it confusing to only have FFMPEG. An alternative might
be to merge the encoding and the output panel and have all file format
in the same list...
/gustav
On Mon, May 31, 2010 at 12:43, Thomas Dinges wrote:
> H
Hi all,
I'm contacting you to know whether you would be interested about a
paper I just got accepted. You can find the paper and video at
http://alice.loria.fr/~nivoliev/Seamless
Currently the code is part of a graphite plugin, you might know the
software since you already worked with Bru
Hey,
today I looked at the FFMPEG buttons again and I have to say, that I
find the workflow very bad.
Scene Buttons:
-You can select between H.264, XVID, MPEG and Ogg Theora in the menu in
the Output Panel.
-Now you get a new Panel, called "Encoding", where we have Presets, and
the 2 menus Forma
Welcome! And big hugs! :-P
On Sat, May 29, 2010 at 4:00 PM, Campbell Barton wrote:
> Luca (mindrones) has been granted svn access to help out with documentation,
> Mainly the sphinx docs which he has already worked with Alex in an
> external svn but other areas of documentation he can help with
We really should just drop the touch sensor and convert to a collision
sensor in do_versions. The touch is old and has been semi-"deprecated" for a
while now. While this strays from your original topic, I thought it was
worth bringing up while you're doing all this logic work.
Cheers,
Moguri
_
29 matches
Mail list logo
