Found out the conversion functions for indices <-> framebuffer only went
up to 18 bits, making selection in zbuffer-select (or vpaint/faceselect
even) not work on large datasets. Provided you have 24 bits display, of
course.
This limit was just dangling in the code since long ago... modern times eh!
with the zblur plugin for faster dof (or other seq.plugins that need the
zbuffer).
I don't think the conversion to a blender zbuffer value is quite correct,
but at least it does produce usable results for zblur without too much
differences with the blender render (at least not for the short tests that I
could do in this short time...)
- Nurbs objects didnt render ray-transp. Was caused by 1) wrong normal calc
and 2) quads with vertices on same locations. Solved it with nice code that
checks illegal quads and turns them into triangles
- Made 'physics engine' variable SUMO default
- Typo in toolbox fix; cyclic isn't F but C
- loopselect doesnt work proper with vertices outside window
- outliner crash on script select (potential showstopper...)
- make curve parent menu, press ESC, crashed blender
All minimal changes in code. no new development, promised!
localview got stuck after an Undo command, it now restores to normal view
when no localviewed objects are there.
Please note again; localview is UI, so actually not saved in the undo...
- onlyshadow material defaulted to black when no shadow calc was used, is
now 100% transparent
- AO 'shadows' were not included in onlyshadow material
- alpha render appeared to be wrong since 2.32... it was gamma corrected
giving difference in OSA render with 'Gamma' on
That alpha issue i am going to tackle once, it is not well functioning, and
might be combined with new 'transmission' colors idea
This was actually a wrong pointer check in fileread that caused no harm
in past, but with UI-less file save it wreaked havoc!
Decided to add undo in sequencer window after all... it also involved
saving Meta strip settings in files. Very nice :)
while its setup to look in $(NAN_FTGL)/include
I added $(NAN_FTGL)/include/FTGL
I've had the mod lying around forever and just never bothered to commit
it but I'm sick of looking at the modified file in cvs update ;)
Kent
- Stephan Gartner reported a crash with Scripts Help Browser script found while porting blender to Linux/x86_64, related to bugs in Blender.Window.Theme module:
two object types were being defined with wrong sizes. My mistake, when I wrote that code I copied/pasted those portions around and didn't check properly. Should be fixed now. Thanks Stephan.
editmesh_loop.c:305: warning: implicit declaration of function `backdrawview3d'
I also removed the config.h stuff from this file, since were not using autoconf
Kent
Lattices seem to have deform lag, when they're animated with Ipos.
Found out this behaviour is already from before 2.25... solved with
removing a where_is_object() from deform code, but dont fully grasp
why.
Tested with good demo file, with motion blur too.
2) No functional changes, just made 2 files compile without warnings;
- added extra ifdefs __NLA_BLENDCON for unused calls
- removed zealot 'const' from function protos and variables, these cannot
work there, and hence gave warnings
- added void pointer casts for array conversions in matrix code
This was caused by a very primitive method of interpolating quaternions.
It was converting quats to mat and back to quat, and then just doing
a linear interpolation. That whilst quaternions are renowned for having
good interpolation possible.
I've experimented with 2 quaternion interpolation methods, and can only
get one to work correctly... the "official" version from Watt brothers
I can't get working, both are in arithb.c now.
Will arrange *close* review with experienced NLAers for it! But testing
here gives fully predictable results.
Also changed;
- added pointer check in drawaction
- changed puldown menu for correct hotkeys for move NLA strips up/down
Original commit message:
"Cosmetic change (after bugreport), scaling in axis (press X,Y,Z) now prints in header "local" too, this to indicate it only does local scales."
The solution was half good, since only object mode is restricted to local axis constraints. Fixed by checking for the Local flag (which was properly set).
