Particle form Janne Karhu: bug can be reported at https://projects.blender.org/tracker/in ... 9&atid=127
Wire Shade in Edit Mode from Eric Forsythe: bug can be reported at : https://projects.blender.org/tracker/in ... 9&atid=127
Key name and Pine status in 3dview object name from Johnny Matthews: bug can be reported at : https://projects.blender.org/tracker/in ... 9&atid=127
Vertex Color Baking from Martin Poirier: bug can be reported at : https://projects.blender.org/tracker/in ... 9&atid=127
guitargeek wrote:A little more cleanup of the loopcut code. Hoping to gain some speed, and letting qread() finish its work instead of breaking. I think this may have been causing trouble.
desoto wrote:This commit sets the info header on the preferences window and the
header prints on the 3d view header to be the same color as the menu text.
This ensures that you can read the text against the color of the header
just as long as the theme color for the menu text is also readable against
the header color. This should make dark themes much better.
ton wrote:Crash fix; rendering AO with envmap on didn't work.
Note that envmaps still render without raytracing.
zuster wrote:- add support for Python Buffer()s of type DOUBLE
theeth wrote:Fixing bones grab in "pose" transform. Bug #3030: http://projects.blender.org/tracker/?fu ... group_id=9
It didn't do initgrabz correctly.
theeth wrote:Transform MMB behavior correction, as mentionned in meeting.
MMB uses global axis, Ctrl-MMB uses user defined. (Alt-MMB cause conflict with the window manager on linux)
(for hotkeys, first press is global, second press is user defined)
ton wrote:Version 1.0 of IpoDrivers.
First note that this is new functionality, unfinished, and only for
testing and feedback purposes. I'll list below what works, and what will
need work still.
This text is also in cms: http://www.blender.org/cms/Ipo_Drivers.680.0.html
An IpoDriver is like an IpoCurve, but instead of a Bezier curve, it allows
to connect a property of other Objects as input for the "channel". For
example, IpoDrivers can be used to have a Shape Key being "driven" by
the rotation of a Bone. Or the RGB colors of a Material get driven by the
XYZ location of an Object.
Editing of Drivers happens in the IpoWindow. Here you can notice that the
channels (right hand window) now have an "active" channel indicator.
To add a Driver, you have to use the "Transform Properties" Panel (Nkey).
Here you can add or remove a Driver to the active channel, and use the
buttons to fill in what kind of relationship you want to establish.
Note that any Ipo Channel can become driven now, but that only Object
transformation or Pose Bone transformation can be used to become a
At this moment, only the local transformation is taken into account.
For Objects that means the location/rotation/scale value without Parent
transform (as shown in "Transform Properties" Panel for Objects).
For Pose Bones it means that only the Pose transform (changes of rest
position) is Driver information (also as shown in Transform Property
Panel in Pose Mode).
Mapping of Drivers
When an Ipo Channel is "driven", the mapping is by default one-to-one.
It is only restricted by already built-in limits for Channels, like
for Material the "R" value can only range from 0.0 to 1.0.
Also note that when mapping rotations, the actual rotation values
in Ipos are scaled down with a factor 10.0. (180 degrees actually has
in the Ipo system a value of 18.0). This is an ancient year zero
convention in Blender... it is a bit hidden, because the ruler
(vertical as well as horizontal) displays the virtual values correctly.
Only the Properties panel shows the actual value.
When you draw an IpoCurve in a Driven channel, this curve will define
the mapping between the Driver output (horizontal) and Driven input
(vertical, as usual).
A nice new option to use is "Insert one-to-one curve" (press I-key,
or in pulldown menu). This will also zoom the display in exactly to
fill the window, allowing easy edit. If you use this option with
degrees, it will map 180 degree rotation to a range of 1.0 unit.
Since the Drivers are integrated in the Ipo system, they will always
be updated whenever an Ipo is evaluated. This happens at least on
For interactive feedback, updates while transforming objects were
added in these cases:
- Driven Object Ipos, by other Objects or Pose Bones
- Driven Shape Key Ipos, by other Objects or Pose Bones
You can also insert Drivers on Action Ipos, but these are only evaluated
on frame change now.
- Drivers can also get a text button, allowing a 1 line Python script
to be executed.
- Make UI for it a bit less hidden... maybe with visualization in 3D?
- Allowing global transform coordinates as Driver too.
- renaming Bones won't rename drivers
- (file) appending the Ipo won't append the linked driver Objects
ton wrote:Driver fix; entering a non-existant object name in driver Panel crashed.
ton wrote:Ipowindow header: Curve menu crashed when no curve was created yet.
ton wrote:Bug fix; action editor, inserting mesh keys crashed. Referencing ipo stuff.
(yes, studio orange is testing
guitargeek wrote:bug #2909
header is redrawn at the end of loopcut to fix part 2 of the bug , my previous commit fixed the first half of it
ton wrote:Bugfix #3046
When using 3d window "unlocked" (own layer and own camera possible), the
dependency updates didn't work, these were only using Scene layers.
Changed the dependency graph call DAG_scene_flush_update()
to accept an argument for all visible layers in a Screen.
ton wrote:Bugfix #3138
Editbuttons "Centre" options didn't correctly use depgraph for linked data.
ton wrote:Bugfix #3133
- Rendering an image with Border didn't check for sizes smaller than 1
Related to this code I found 2 other fixes:
- Themecolor set for drawing in Render Window was not restored correctly,
sometimes causing into wrong Panel (transparency) drawing.
- When rendering an image with Gauss, it now renders by default 1 pixel
extra, which gets stripped. This eliminates the "ugly" darker border
(Yes, let's make Mr. PixelCounter Goralczyk happy!
ton wrote:IpoWindow, Action curve update.
When no Ipo existed yet for an Action Channel (Bone), you could not add
curves with CTRL+click or Drivers. This was due to antique action code
state... it's still messy, no time for big cleanup here yet. At least
this works now.
(Also: removed test prints of previous commit)
ton wrote:New! Edit mode curve now draws solid extrusions, bevelcurves and tapers.
Fix: when unlinking an Action from Armature, the ipo window still allowed
adding drivers, causing crashes.
antont wrote:added getting names of shapes/KeyBlocks to bpy api so mikasaari can continue with his lipsync script (where names of phonemes are as names of shapes/keyblocks).
ton wrote:Adding Drivers in Actions now update live as well.
The main change is that an Action now always updates Poses on transform,
unless you are editing the Pose itself. Please test!
broken wrote:* Added copying curve resolution settings to the copy attributes (ctrl c) menu
ton wrote:NLA window:
Insert a NLA strip makes it size 100 frames if the actual action is smaller
than 2 frames, otherwise you cannot even select it
Downloads:khughes wrote:Added new BPython thin mesh module