I don’t know if there is a name for this behavior, but in 2.4X when you are in edge select mode and “turn a corner” and subdivide the quad that is in the corner gets subdivided first with a tri then is subdivided further from the opposite corner to the newly created triangle’s edge to give you 3 quads (all of this happens automatically I am just guessing that the code behaves like this) instead of 2 tris and a quad which is what 2.5 does .
I hope they return this functionality soon as this method allows for adding detail easily without dealing with a lot of tris when modeling .
I think another very helpful thing would be if people recorded screencasts of doing various small projects (modeling, navigating the interface, etc.). I think this would help the developers to see things in a context greater than they may have time to do themselves. Also, some of these contexts could become workflow benchmarks.
Some companies test their interface and workflow by recording users navigating and performing prescribed tasks. YouTube or Vimeo could be used to eliminate the concern of bandwidth and storage space.
I’ve been following Mfoxdogg’s blender 2.5 video tours. One thing that worked in an earlier version (23890) was autokeying (at least for transform). After watching Mfoxdogg’s latest video I see that it works (for linux?).
On WinXP autokeying does not work, even for transforming objects, the new keying sets, etc. I have been testing versions from graphicall 24060, 24064, 24118.
If I have files created in 2.4x that have broken features should this be reported as well?
Specifically, animation/rig/driver things, I know its gone under a major overhaul, somethings are expected to break.
gaiamuse: Thanks for catching. It’s now fixed, but a recent fix for automerge had broken it.
(jay): What in particular?
PyConstraints have not been restored, PyDrivers may break due to API changes. -> I would not report these errors
IK/FK switches have sometimes broken. I’m not sure exactly how/why, since I haven’t seen an easy to test file for the underlying situation yet that does not require some arcane keyframing dance
(I’d like to challenge some riggers to create a new, easier to use solution with the tools in 2.5, and upon failing that, we can discuss what’s still needed…)
Lattices going bad - I’ve heard/seen this happening with Mancandy, though it won’t hurt to have a bug report to remind us of it. Just don’t everyone go at once and report it 5-10 times
Hmmm, my ik/fk switch is working now, but my bone driven shape keys aren’t working. I’ll admit that my rig is pretty sloppy though, there could be underlying issues.
Well, I might just be doing something wrong, but here’s a few things I find odd.
You have to hold “d” down to use Grease pencil. This is just a temporarily hack, right?
The brush select tool in edit mode that was moved to “v” doesn’t scale in size when using the scroll wheel, and it doesn’t stay active after you release the LMB like it should. <-- Sorry, this was already listed as a missing feature
I can’t find “smooth” anywhere, not “set smooth”, but the “Flattens angles of selected faces” from the Mesh Tools of 2.49. <-- Sorry, “smooth” has changed name to “smooth vertex”
Blender 2.50 build Oct.27 (not sure of the exact number)
Linux Ubuntu 64 bit
Curve Shape Keys
Add a bezier curve,
Add a basis, + Key 1, and Key 2,
If you tab into edit mode; the Basis key looks ok, but Key 1 & 2, one of the control points isn’t located the same as the Basis.
If I try to adjust the ‘Value’ setting for any of the keys = instant crash.
Sometimes also just clicking/switching between keys will also crash.
in 4-split, you can’t set a background image for each part… this basically makes it useless for modeling with blueprints. this might be more of a feature request than reporting something as broken, I dunno.
background images are just plain wonky. weirdo stuff like this and this happens. additionally, zooming in on them enough will cause a crash.
zooming in on anything in the image editor has similar issues, to a lesser extent (this includes renders!)
cutting hair particles seems to crash frequently
using a build from today (just a few minutes ago, really) on OS X 10.5.8, have not confirmed 3-5 on linux or windows.
edit: oh, just noticed bevel on the todo. in any case, it’s rather important
Using latest build 24144 and earlier builds also (Windows 32 bit)
In the Graph editor there is no text to show what channel is selected.
The only way to visually see what I selected is to have the properties panel open (N key).
I am thankful I can see what is selected in the properties panel.
I am not sure if it is a bug or not. Is anybody else having this problem?
Also, does this also happen in the DopeSheet or is it restricted to the Graph Editor only? Just trying to narrow down what it might be, since those two use the same drawing code for those names…