Revision d033c24 by Joshua Leung December 9, 2007, 08:46 (GMT) |
== Armature Visualisation - A few additions == * Added an option to make frame numbers of keyframes draw on bone-paths even when frame numbers for other points are not shown. * Added a new ghosting method, which only shows the keyframes within a range. |
Revision 259c807 by Nicholas Bishop December 8, 2007, 21:53 (GMT) |
Fixed bug #6870, Sculpt mode + wireframe = nothing When sculpt object is in wireframe mode (including if the current view is in wireframe mode) a second copy is drawn only to the depth buffer so that sculpting can take place as normal. |
Revision 15eb4eb by Brecht Van Lommel December 8, 2007, 18:46 (GMT) |
Mesh Deform Modifiers ===================== Tweak for somewhat improved results with dynamic binding, and added a rt value (527) for debugging mdef accuracy. |
Revision 85ee630 by Brecht Van Lommel December 8, 2007, 15:44 (GMT) |
Bone Transform ============== When pressing the g key on a bone that can't be translated, rotation is automatically activated. However, with multiple bone selected, it did this even if some bones can be translated. Now it only switches to rotation if no bones can translated. |
Revision 48b6e01 by Joshua Leung December 8, 2007, 05:20 (GMT) |
interface.c - silencing warnings: - 577: control reaches end of non-void function (in ui_but_copy_paste) - 138: initialization makes integer from pointer without a cast (I'm not sure whether the fix might cause errors on some systems/builds, but it works fine here) |
Revision 8c8cdeb by Nicholas Bishop December 7, 2007, 21:45 (GMT) |
Committed patch #7838, Fix for window header redraw in sculpt mode from aurel. Fixes flickering in the 3D view header after using the interactive brush size tool. |
Revision dc9909a by Campbell Barton December 7, 2007, 19:48 (GMT) |
EnV requests, copy and paste for colorbands, world ambient colorpicker |
Revision 7e0d34d by Martin Poirier December 7, 2007, 14:58 (GMT) |
[#7140] Scrollbar not stopping ok on the bottom of the text editor window Fixed by patch #7849 by Jetze van Beijma |
Revision e605809 by Brecht Van Lommel December 7, 2007, 12:05 (GMT) |
Accidentaly left in a line of debug code, which broke deform modifiers after e.g. subsurf. |
Revision f4e2005 by Campbell Barton December 7, 2007, 11:56 (GMT) |
UV texture blending was being used when materials were disabled. |
Revision be7192c by Joshua Leung December 7, 2007, 10:50 (GMT) |
== NLA - Scale Related Fixes == * Old files now get initialised with the correct scale. The wrong calculation was being used * Added a new tool to Alt-S menu: "Apply Scale" This tool causes all the keyframes in the active strip to be moved to their NLA-scaled times, the scale to be set to 1.0, and the frame ranges recalculated accordingly (to remove any nasty weird errors) * Scale field now draws red when the action-range is < 1, and the tooltip in this case instructs the user how to fix this (by using "Apply Scale"). |
Revision 9723e3e by Campbell Barton December 7, 2007, 09:51 (GMT) |
miscellaneous edits from python development branch merged back into trunk |
Revision ab02e91 by Joshua Leung December 7, 2007, 04:24 (GMT) |
== NLA - Scale Setting for Strips == NLA-Strips now have a new setting: Scale. It determines how much the action-range is scaled for each repeat, instead of the scaling being implicitly determined based on repeats + strip-length. One of the instant benefits of this, is that when increasing the number of repeats, the strip length increases by the right amount. Thus, increasing the number of repeats retains a constant speed. Hopefully we can prevent weirdly scaled actions this way. (i.e. 0.00001 frames long action * 10000 or so) Todo: - Transform code needs to be able to set the scale setting (it doesn't yet) - Add a new option to "apply scaling", to fix up problems with old files that have really bad scaling. Situations when this is needed could get indicated in the interface too... (red background for "Scale" field?) |
December 6, 2007, 21:41 (GMT) |
This is patch: [#7129] Solaris build is linking with c instead of c++ compiler I talked to Jesterking and he may switch this to a more global solution later. I figured in the meantime its ok to commit this and consider the issue resolved. Kent |
Revision 3bbf073 by Ken Hughes December 6, 2007, 20:15 (GMT) |
Python API ---------- Bugfix #7877: fix for lamp.setMode() and lamp.setType(): need to build tuples instead of just int or float objects. |
Revision 37d1190 by Brecht Van Lommel December 6, 2007, 19:44 (GMT) |
Bugfix for IK locked axes with an initial rotation, gave wrong starting angle in some cases, but wasn't always noticeable due to the IK solver changing it anyway. Bugfix for hidden bones in pose mode still being active, and preventing other bones from becoming active. |
Revision 5132296 by Brecht Van Lommel December 6, 2007, 17:43 (GMT) |
Particles ========= - Normalize strand coordinates over the length of the strand, not cut off when with e.g. length texture control. - Weight paint and particle mode x-mirror now works with deformation and shape keys active. - X-ray is now disabled in particle mode, messed up depth tests. |
Revision ff52c8f by Brecht Van Lommel December 6, 2007, 14:22 (GMT) |
Bugfix: the sticky and use rot buttons for the floor constraint were not working anymore after constraint refactor. |
Revision 7f1e032 by Brecht Van Lommel December 6, 2007, 12:46 (GMT) |
Bugfix: rotation difference ipo drivers could give sudden jump. This was actually due to a numerical issue in the matrix to quaternion conversion code (which was from siggraph '85), now uses an improved version. I hope nothing depends on the previous behavior.. though it should only affect corner cases. |
Revision 1e45289 by Joshua Leung December 6, 2007, 10:20 (GMT) |
Constraints Bugfix: IK-constraint "flush_targets" function was causing segfaults on debug builds from certain MSVC compilers. The cause of this, is that ct is freed in the SINGLETARGET_FLUSH_TARS macro already, but ct is accessed in the following line to get the next target (ct= ct->next). Caused by brecht's commit for the pole-target stuff for IK-constraint. Now the SINGLETARGET_FLUSH_TARS macro, and the SINGLETARGETNS_FLUSH_TARS macro will correctly advance the location that ct points to. |
|