Age | Commit message (Collapse) | Author |
|
Changes for VC2013
Now, I can build Blender with VC2013 with Cycles, Collada, OpenExr,OpenImageIO disabled. Also, you need VC2008 sp1 installed to make old libs compatible.
|
|
|
|
|
|
Global OpenMP threads override is not a good idea because this would affect
all possible OpenMP blocks running at the same time as simulation.
And that was actually a big on restoring number of threads: code needed to
store current number of threads, not maximal one.
|
|
checks weren't needed.
also remove redundant dot_v3v3 in shrinkwrap constraint.
|
|
BLI_scanfill_begin().
|
|
threadcount to logical threadcount of machine
|
|
todo: default should be logical corecount
|
|
enabled
|
|
|
|
|
|
I am unsure if I did catch all problematic code but I ran out of memorybefore the sim started ;)
|
|
to include a few more that gcc is using too.
|
|
Also changed shebang to '#!/usr/bin/env python', this is more portable across unixes...
|
|
Thanks to Brecht for providing a patch and example blend.
I changed and extended it a bit since there was another bug in that loop.
|
|
keyframe
Also fix:
- Fluid simulation was always lagging 1 frame behind: E.g. the 250th frame in blender showed 249th frame of the fluid simulation.
Change:
- Animated enabled/disabled property only gets counted as "on" if value >= 1
Note that this bugfix should solve many problems with timings of animated fluid sim properties.
|
|
|
|
Fixed as suggested by Campbell, thank you!
|
|
Note: Compile still fails during ceres compile (namespace tr1 problems).
|
|
also fix for building ghost test and fix double free in one of the tests
|
|
- remove duplicate includes
- blender builds with -Werror in C++ for fluids/smoke
|
|
Patch provided by Matteo F. Vescovi, thanks!
|
|
Thank you for submitting!
|
|
and looks like -fpermissive is used in linux too
|
|
to ints. All cases found were harmless and the error behaviour could be turned off by the -fpermissive flag but I'd rather keep that off to detect any real problems should they arise.
|
|
PVS-Studio.
Remark: I think that "!(nbored & CFBnd)" would be correct but it introduced other bugs so, I just quiet compiler warnings leaving the running system untouched.
|
|
Canceling fluid simulation did not work when speed was zero.
|
|
Note: Supporting obstacles which can be enabled/disabled as animated propoerty is not likely to happen. So I marked this as "Won't fix"/TODO.
I also reverted last commit on this bug because it didn't work and disabled the property from UI to avoid confusion.
|
|
Needs testing for sideeffects.
If there are negative sideeffects, revert commit and mark as "will not fix"/"not supported"/"needs UI fix".
|
|
|
|
http://markmail.org/message/fp7ozcywxum3ar7n
|
|
gave wrong results. Note how in this code it already incremented to the start
time and then incorrectly added it again. Patch by Chris Foster, thanks!
|
|
http://projects.blender.org/tracker/?func=detail&atid=498&aid=28748&group_id=9
I'd say better be careful with code so complex as the fluid sim!
|
|
intern/elbeem/intern/solver_relax.h)
|
|
|
|
|
|
a) Enable the possibility to remove the "air bubble" around submerged collision object. This feature is enabled as standard for new files. The code was found in elbeem by nudelZ, coded and provided by Nils Thürey (thanks!)
b) Old baked files gets deleted if a new bake gets started (were overwritten before and resulted in weird old bake + new bake mixture) (idea by nudelZ)
|
|
blender_add_lib now takes a separate include argument to suppress warnings in system includes (mostly ffmpeg & python).
also only build wm_apple.c on apple+carbon configuration.
|
|
|
|
|
|
*nix with non-standard libjpeg/png/zlib locations was broken.
in the case of python this makes it easier to move to find_package(PythonLibs) when 3.x is supported.
|
|
|
|
and endif() which is no longer needed.
|
|
reporting missing headers & C files.
this is important so IDE's using CMake integration always get blender headers. - QtCreator & MSVC for eg, probably others too.
|
|
|
|
by cmake devs.
globbing vs explicit is discussed here.
http://www.cmake.org/pipermail/cmake/2008-December/025694.html
Practical implications are:
- developers need to keep CMakeLists.txt files up to date.
- Users wont get strange linking errors if they build after a file is added, since CMake detects CMakeLists.txt is modified and automatically reconfigure.
|
|
|
|
|
|
|
|
|