Response to the "Action Fake User" issue

or Answer to "Where did my Actions go 2.62?" ...

Wow. I've just gotten back to checking various things afterseveral busy days of being swamped with work and deadlines, and it appears that a massive firestorm has been erupting in multiple places over the past few days. So I'll try to take some time to respond and hopefully "diffuse" the situation a bit without inciting vitriol (fingers crossed).

Blender-Bullet Branch Online

From comments received in response to my "Bullet Todo List" post last week, there were several main themes coming through:
1) Baking, especially via Alembic support, is a very desirable prospect.
2) Phymec's work on fracturing, etc. would be nice to integrate with this (and also BGE)  at some point. This fits in the "fancy stuff" basket
3) Interactions between animated objects and physics sims (and also animating when physics sims work) is an issue that many people care about. IIRC, there is some support for this already, though your mileage with overriding simulated objects mid-sim may vary.
4) Many are just dying to get their hands on this functionality.

This last point I'll address here and now :)

Re: GSoC11 Poll #1

Thanks for all the responses!

It seems that we have some a consensus on many of the issues already:
1) Fake Users are now GONE (as default for newly created actions)!
http://projects.blender.org/scm/viewvc.php?view=rev&root=bf-blender&revision=37156

3) It sounds like the current mapping (keyframes only on normal BKEY select) is the favoured option. So, no changes there.

4) Wow! It's great to hear that it is actually in widespread use. Don't worry, I won't be removing it. Instead, I think I might need to post some docs on it sometime soon, since when I checked a few days ago, there were no results for it anywhere.

It also seems that there are mixed opinions about the pasting behaviour (2). From the responses so far, there are 3 main points:

• There are basically too camps: "Frame Start + Overwrite Range" and "Mix"/Default
• The fact that this operator has such options needs to be made more obvious in some way
• We could do with some way of specifying default preset that you can configure locally