| Age | Commit message (Collapse) | Author |
|---|
|
found at:
http://www.blender.org/documentation/blender_python_api
Easier for linking wiki docs.
|
|
like Japanese or Hindi) generates a very odd segfault! Have really no time to fix now, will try in a few hours, but safer to do this for now!
|
|
Japanese) have not enough room!
|
|
|
|
meshes and world MIS.
|
|
find ldl symbols because order of libraries seems to be critical
for gcc linker.
A bit stupid, but that's how linker works..
Both CMake and SCons shall work fine on linux now.
|
|
|
|
Root of the issue goes to SSBA library which didn't work
properly when using optimization in MSVC. It was worked
around by disabling optimization for libmv, which is in
fact shame and shouldn't have been done.
It seems after some changes optimization does not affect
on SSBA code, but enabling optimization could be risky so
close to release.
For now solved by splitting SSBA to separate CMake/SCons
library, disabling optimization only for this particular
library and enabling optimization for rest of libmv.
Tested on all files which used to fail with optimization
enabled in SSBA and all of them works the same as before.
Tracking speed is significantly higher now.
After release we'll enable optimization for SSBA as well,
so there'll be no crappy build setup. Later we'll replace
old SSBA library with new BA code based on Ceres.
Bundle script would be broken for until then, so better
not to use it.
|
|
these cases, when WITH_INTERNATIONAL is defined we need unicode support).
|
|
thanks to Sv. Lockal for investigating and providing the fix.
|
|
overwritten after.
|
|
This is a pretty rare case that can be triggered by switching rigid body
and constraint groups before simulation was validated.
Code checked for existing physics objects but was missing else block.
|
|
don't interpolate projection, just project all points within the PET radius.
|
|
the program code for better understanding.
|
|
'rootless' armature similar to Maya.
|
|
In rare cases this would allow the simulation to run before being
initialized (if cache is baked and reading cache fails after undo or
loading a file).
|
|
when Proportional Editing mode is active, regardless of influence radius
|
|
autocomplete is now unicode aware, using python api's checks for now. eventually we should have our own.
|
|
|
|
|
|
|
|
thanks!)...
|
|
|
|
|
|
Mesh edge number buttons were removed when the custom-data layers weren't present.
More of a usability regression than a bug.
|
|
recognized as 2d curves).
|
|
converted from shorts are not always exactly unit length.
|
|
|
|
|
|
conflicted with one from IMB_colormanagement.h
|
|
it not execute immediately when opening the popup.
|
|
this was really not nice logic to try to fit into an assert.
|
|
from Martijn Berger (juicyfruit)
applying since this is only corrects header case which is ignored on windows anyway.
|
|
|
|
enough.
|
|
OpenMP block was using shared variable, which for sure leads to
threading issues.
|
|
simply clamp the color to the buttons softrange since color conversion can cause the value to scale outside the intended button limits.
|
|
Before this change only old flag "Premultiply" was used to
detect alpha mode, which is not enough actually.
Now the logic here is:
- If "Premultiply" was enabled it is likely float image with
straight alpha, which shall be premultiplied before usage.
In this case image/sequence Alpha Mode is set to Straight.
- Otherwise use default alpha mode for image format based on
an extension. This could fail in some cases like TIFF, but
this wasn't handled fully correct in older blender anyway.
Initial discovered issue was that EXR images saved in older
Blender versions were set to Straight alpha mode, which is
obviously a straight way to lots of headache.
|
|
made bone roll get compatible angle values with the original roll.
|
|
edit mode
My earlier fix for [#33974] (in r.54061) was causing some problems where
manually specified roll values on horizontal or angled bones were getting reset.
This could be nasty as you might not notice the changes for a while (especially
when using stick bones without axes displayed).
I've now put in place a hacky compromise solution which should catch both of
these situations nicely. For z-axis (i.e. vertical) movements, the r.54061 fix
is used, while for everything else (moving or just touch-n-go), the old setting
is used.
|
|
|
|
style edits and typo corrections.
|
|
This was caused by a floating point precision error. During collision detection, Newton-Raphson iteration is used to find the exact time of the collision. But when using subframes, the initial Newton step was too small. Now the initial step is given in absolute units. When subframes = 0, this should behave almost the same as before.
Thanks to Janne Karhu, Lukas Toenne and Ton Roosendaal for their help with this patch, and to AutoCRC for funding.
|
|
* Issue was caused in r54393.
|
|
text_selected, this didn't work nice with dark themes and text shadows and overall didn't make much sense.
Now, disabled items use a mix of text and menu item background (inner) color. Same results, but allows dark themes with bright selected text to use shadows.
Example case: http://pasteall.org/pic/show.php?id=45697
|
|
alpha was used for them which doesn't work for cleaned footage stored
in EXR file format.
Perhaps we need to support configurable alpha mode for clips, but
that's for later (maybe even after release),
|
|
shall use active layer now for real.
|
|
materials, the typical glBlendFunc(GL_SRC_ALPHA, GL_ONE_MINUS_SRC_ALPHA); blend
function does not give correct destination alpha.
|
|
centers
|
|
quite correct.
- When checking edimode, make sure its mesh editmode.
- Graph editor supports this option but wasn't being checked.
|
