…There are bugs in 2.30 : this has to be expected if one understand that until now we had only snapshots, not even alpha releases.
…There are also things so unexpected that they may look like bugs but are just changes, sometimes real departures.
…Finally there are changes that just could go unsuspected but catch up with you when you don’t expect it.
I’d like for this thread to become the place where we could do a count of these and classify them appropriately : bugs, surprises, hidden aspects.
I don’t intend for this to be for bug report intended for the developpers : they surely have set some more efficient channel for that purpose already. I just wish to create a place where we, the users, can find needed clarifications while awaiting for the debug version 2.31, find workarounds if possible and for the time it takes to get used to all those changes.
I can’t parenat an armature to a mesh any more. mabey my bad but I’m still looking for a way…
If I start adding empties for use in constraints (mechanics) then blender crashes.
It’s stability is questionable at this stage.
I can’t parenat an armature to a mesh any more. mabey my bad but I’m still looking for a way…
If I start adding empties for use in constraints (mechanics) then blender crashes.
It’s stability is questionable at this stage.
I tried it, and it seems to work for me. What OS are you using? Also are you using name groups? Auto-skinning? …?
The default plane is now a cube.
(Big updates for tutorials starting with “get rid of the default plane” in sight. j/k)
Added screen with 4 views.
Button window now vertical and to the right in default single view. New faked timelind at the bottom (headerless audio window if I understand)
Default scene named ‘stage’ : going Shakespearian are we ?
I already had a build of 2.3 fully set up with user prefs, and the new one used it’s bblend file when it installed, so I didn’t get any cube, or 4 screens or anything. Actually, this is the first time I have done an install of Blender where it didn’t start off by rendering to some odd folder that I then had to track down.
I am in the opposite situation and ctrl+u saves somewhere I still have to track and so does Blender it seems as Xkey > erase all brings me back to .B.blend instead of my saved users defaults.
Mkey does not apply to object mode, but it does indeed apply to everything else in edit mode (curves, surfaces, armatures, …)
For symetries in object mode: S, X (or Y) and - 1 (using num input to mirror).
Ack! Seems like I forgot something when transfering from tuhopuu.
You cannot add new bones to an armature in edit mode.
The hotkey code has be cleaned a lot, so it won’t default to a function when hiting a combo with not functionality attached to it (for example, using Ctrl-G for Grab will not work).
Little trick (experiemental code to test something, it doesn’t do anything useful):
Set the rt button to 1 (in the display buttons F10). Ctrl click on a button and drag it.
(First, let me just say that this is my first post, and I am a total Blender newbie. That being said, I did read the manual and the documents about the changes in 2.3, but just now when I upgraded to 2.3, I found this problem and I have no idea what to do about it.)
In 2.3, I find that I can’t control the view with an Apple mouse when I use Blender is OS X. Basically, to simulate a 3-button mouse, you need to use keystroke combinations while moving the mouse and pressing the mouse button. I was just starting to get the hang of it and now I find that I can’t do it in 2.3. It’s, obviously, kind of a big problem!
Was something changed that I didn’t read about? Or, is this just an oversight? Or, most likely, am I missing something really obvious?
It is an oversight from an overworked developper. He will bring the necesserary correction as soon as the cvs is thawde (just a few days.)
In the meanwhile you can use version 2.28 and learn a whole lot more, have a lot of fun still.
Just noticed you can move, dock and minimize windows…great feature ! Only problem is that it’s very, VERY sluggish. It’s also slow switching between, say, render buttons and edit buttons - switching used to be instant, which was much better. I’m running XP, 1.1Ghz, 128mb ram, 16mb graphics card.
It is an oversight from an overworked developper. He will bring the necesserary correction as soon as the cvs is thawde (just a few days.)
In the meanwhile you can use version 2.28 and learn a whole lot more, have a lot of fun still.
Regards
Jean[/quote]
Ah… that is completely understandable! From what I’ve found so far, Blender is great! I still have plenty to explore in 2.28, so it’s no problem.
(I’m just glad that something this fundamental, which I was just getting the hang of, isn’t actually changing!)
A very important change about the default .b.blend file:
On 2.28 they added a blue horizon world seting, so that hitting RENDER doesn’t produce a black screen anymore (quite frustrating for newbies). But on 2.30 they added a light and something that could actually be rendered! (the cube instead of the plane)
