On 12/03/11 20:41, Erwin Coumans wrote:
Hi,
I just committed the latest Bullet 2.78/trunk version in
Blender/extern/bullet2
and also added those few lines that enables the export of .bullet files
using BGE
python script command
PhysicsConstraints.exportBulletFile(char* fileName)
I
Hi all,
I'm getting regularly wonderful emails from users, professionals,
universities, and so on.
For some theason I was a while silent when reading the below mail. So
I'll share it with you.
Whenever we discuss big plans, conquering the world, making films,
it's always good to look back
dummy question, but this update still needs BGE to run the simulation right
? is the capsule feature is there now ? I have seen some video on youtube
with it.
cheers
F
2011/3/12 Erwin Coumans erwin.coum...@gmail.com
Hi,
I just committed the latest Bullet 2.78/trunk version in
Hey Ton,
this is a really nice e-mail.
Seeing that Blender is used by people all over the world, with different
social background, poor or rich is great!
Thanks for sharing the mail!
It's the reason why we donate time and energy into free software.
Because it's for everyone. :)
Thomas
Am
I keep saying that we need to move for a unicode friend font, but
people don't listen to it. I'm sure our Japanese friend would love it
:p
But seriously, it's a really nice message passed along. I'm sure
people have different motivations, but there is likely a common
ground. It's not about the
Hi,
I've cleaned most of the wiki todo list, where possible marked issues
as 2.5 target and as general todo. Items marked as 2.5 target we
will work on during april/may still.
Could the various maintainers of Blender code check this as well,
prioritize and categorize. Or remove items when
Hi.
Will 2.57 have a stable API?
Yes.
But depends on definition of stable too. Is a matter of documenting
it well. Most of it can be called stable and frozen, some parts might
need bug fixes, and some parts are in WIP or unfinished.
-Ton-
Hi,
I think we should make major modifications to the release cycle, to
avoid problems that we've been having with 2.5 and also releases
before that. In my opinion a migration schedule for new features as we
have done before does not work, because it's unpredictable when
developers will be
Hi Brecht,
I strongly believe we should switch to short, fixed release cycles,
and be much more strict in only accepting functionality in trunk that
is reviewed and can be stabilized in a short time.
Fully agree! :)
-Ton-
Double thumbs up from my end also.
There's a lot to be said about stricter discipline for commits to trunk.
Martin
--- On Sun, 3/13/11, Ton Roosendaal t...@blender.org wrote:
From: Ton Roosendaal t...@blender.org
Subject: Re: [Bf-committers] Roadmap for 2.5x - 2.6x - beyond
To: bf-blender
+1 Here, sounds very reasonable!
On 03/13/2011 03:52 PM, Brecht Van Lommel wrote:
Hi,
I think we should make major modifications to the release cycle, to
avoid problems that we've been having with 2.5 and also releases
before that. In my opinion a migration schedule for new features as we
Hey,
I completely agree with that and be happy that you bring it up now. :)
This 8 weeks release schedule sounds good and doable.
Our main problem was never the amount of new features, it was good
testing and quality. Hopefully this will improve with such a new system.
Very strong +1
Am
Hi all,
1) Blender 2.5 project
- All signs still positive for 2.57 out of beta release within 2-3
weeks.
- Meeting confirms we'll need RC builds, preferably a week before
official release.
- Ton suggests to already make 'official' test builds this week.
Having regular builds for testing
Hi all,
In the meeting Ton proposed to do official automated builds, that are
built and uploaded every day or every few hours. These should
effectively be the same as release builds, and could even be used as
official releases.
To start, some questions for platform maintainers:
* Do you have
Hi there, as the maintainer of GraphicAll's Instant Builds(tm) I'd
like to share my experience: IT'S AWFUL!!!
kidding apart, if you guys want to setup an autobuild system it
probably needs a smart way for it to report when builds fail. I've
thought of checking what was the revision that broke it
Blender used Thinderbox back in the NaN days. What happened to that? Is Hans
Lambermont still around for advice?
Thanks,
Erwin
Sent from my iPhone
On Mar 13, 2011, at 12:37 PM, Daniel Salazar - 3Developer.com
zan...@gmail.com wrote:
Tinderbox
___
Hi,
quick mail to say that in wiki it is now possible to write formulas
using latex, see:
http://wiki.blender.org/index.php/Meta:Guides/Style_Guide/Formulas
We've made this in the hope that developers will be more comfortable
documenting algorithms used in blender :)
Regards,
Luca
If that does happen you should expect A LOT more traffic since people will
often download the latest version. Seeing, however how often compatibility
changed between recent releases I think that most professionals will stick
to 'official' releases.
+1 on the automated notifier for broken builds.
@Mats Holmberg / @Francois T et al:
Is there a way we can establish a set of tests to definitively test this patch?
Obviously matching a scene to real world units against a test
photograph is a possible option here, but I'm wondering if there is
something else we can do?
Sincerely,
TJS
Whilst mucking about retiming, I noticed that I was unable to get any
sort of output shift on frame input to output ratio using the Time
Remapping Old and New values.
Has anyone tested it recently and gotten it to work? If so, what dark
alchemy did you invoke?
Sincerely,
TJS
Was told on #blendercoders that patch review was undergoing changes, so I'll
post this small patch here.
See http://blenderartists.org/forum/showthread.php?t=211495
and
http://projects.blender.org/tracker/index.php?func=detailaid=26495group_id=9atid=127
hi.
+1
I'm very pleased to see a step in this direction. I did automated builds of
blender for a while at my former job. Without a continuous integration
framework, however, the automated builds were not as useful as I (and a few
others) had imagined. Graphicall has been providing a good way
Hi,
First let me say, doing the whole continuous integration web service
thing is not what I signed up for. It's valuable, but someone else
will have to volunteer for that.
Mainly my motivation is getting good reference builds for bug
reporting, and finding and solving build and installation
I can do automated builds for FreeBSD 8.2-RELEASE i386, and soon
amd64. As of Friday python32 for BSD/amd64 was still a link to
python31, but BSD/i386 has proper python32.
I can also have a system in place to detect build failures.
If BF does go the VirtualBox route (which I'd prefer since that
Since the last fairly big API changes with registration I've been
trying not to make API breakages.
Matt requested we log API which may break scripts so script authors
don't need to trawl through commit logs to find out what updates they
need to make.
This was the plan all along but being in beta
On Mon, Mar 14, 2011 at 4:16 PM, Campbell Barton ideasma...@gmail.com wrote:
Now things are more stable I started a wiki for this:
http://wiki.blender.org/index.php/Dev:2.5/Py/API/Updates
Thank you *very* much, this will be a big help!
cheers
Matt
26 matches
Mail list logo
