September 27, 2014, 07:38 (GMT) |
replacing step function |
September 27, 2014, 06:31 (GMT) |
Comments: clarify BMLoop |
Revision c7ccbc9 by Lukas Toenne (gooseberry, gooseberry_farm, hair_immediate_fixes, hair_system, temp_constraint_volume, temp_hair_flow, temp_hair_modifiers, temp_motionpaths) September 26, 2014, 21:38 (GMT) |
Fix for scons files missing physics include folder. |
September 26, 2014, 18:51 (GMT) |
Replace region tracker with autotracker in Blender The title actually tells it all, this commit switches Blender to use new autotrack API from Libmv. From the user point of view it means that prediction model is now used when tracking which gives really nice results. All the other changes are not really visible for users, those are just frame accessors, caches and so for the new API. |
September 26, 2014, 18:51 (GMT) |
Major refactor of Libmv C-API Basically the idea is to split it into smaller pieces, because current file became unmanageable. This commit also includes implementation of all C-API for the autotrack pipeline. Pretty much straightforward changes, nothing to be mentioned specially. |
September 26, 2014, 18:51 (GMT) |
Initial commit of unfinished AutoTrack API This starts the creating the new AutoTrack API. The new API will make it possible for libmv to do full autotracking, including predictive tracking and also support multiple motion models (3D planes etc). The first goal (not in this patch) is to convert Blender to use the new API without adding any new functionality. This API currently contanins: - Frame accessor to access frames which are stored in Blender side. - New Tracks implementation - New Reconstruction implementation Currently this API only tested on doing the same frame-to-frame tracking as the old API allowed to do. But it also supports now predictive tracking which is based on the Kalman filter. |
September 26, 2014, 18:50 (GMT) |
Tracking: Cleanup of the bundler script |
Revision 07dac94 by Antonis Ryakiotakis (gooseberry, gooseberry_farm, hair_immediate_fixes, hair_system, temp_constraint_volume, temp_hair_flow, temp_hair_modifiers, temp_motionpaths, terrible_consequencer) September 26, 2014, 17:47 (GMT) |
Yet another attempt to solve OSX issues, restore sequence sounds too, or sounds get added to two sequence and file descriptors leak |
September 26, 2014, 15:57 (GMT) |
Revert "Merge branch 'terrible_consequencer' into testbuild" This reverts commit 18c6c0146627b006ff094e0eb0050f81cdf2a379, reversing changes made to 5d9396c0a41873dff0fe438eaeb21744e13025c1. |
September 26, 2014, 15:51 (GMT) |
Merge branch 'terrible_consequencer' into testbuild |
September 26, 2014, 15:32 (GMT) |
Fix View3d background image display aspect |
Revision ebf005e by Lukas Toenne (gooseberry, gooseberry_farm, hair_immediate_fixes, hair_system, temp_constraint_volume, temp_hair_flow, temp_hair_modifiers, temp_motionpaths) September 26, 2014, 15:25 (GMT) |
Added separate damping for bending springs. The bend damping factor was hardcoded to the same value as the stiffness. Now it has its own factor in the settings and button in hair dynamics. |
September 26, 2014, 14:57 (GMT) |
Cleanup |
September 26, 2014, 14:17 (GMT) |
Fix ocmpilation error with strict flags after the recent commit |
September 26, 2014, 13:06 (GMT) |
BMesh: select similar regions Select operator that takes multiple selected face regions and selects any number of matching regions (when they have distinguishing features to isolate them). UI access next. |
September 26, 2014, 12:23 (GMT) |
Cycles; Camera ray nodes initial commit This commit lays down an initial playground for the camera ray nodes. The idea of this nodes is to be able to have a control over the rays which are being casted from the camera in order to gain several use case scenarios: - Panorama cameras with custom mapping (kinda generalized way doing what Daniel Basso tried to address in T35428). - Distortion rendering, to produce renders which matches the footage precisely, improving motrack work flow in general. - Some possible artistic scenarios. It's the very beginning and loads of stuff to be done, but it's already possible to render a distorted images on CPU using the same exact distortion model as used by the motion tracker. Committing the stuff in order to be able to gather early feedback about how exactly this nodes are expected to work from the artists point of view, and hopefully someone will pick the work up and help finishing it all up. Some technical details: - Camera nodes are using pynodes, so no changes to the blender itself is to be done. This leads some limitations and corners on the usage, but that's probably something to be addressed for pynodes in general. That said, current annoyance is: * Modifying node declaration in the cycles addon doesn't update the files, leading to wrong render results. Not sure how it's expected to be handled actually. * Some operators like Ctrl-X are not re-linking noodles correctly. * Muting is impossible. * Some major update issues, mainly in cycles viewport. This also involves dependency graph stupidness into here. - Nodes are implemented using SVM, which is really easy to use and extend. Would also make it possible to have custom socket types, for example in SVM we can have socket type named "Ray" which would pass all the origin, direction length via a single noodle. In OSL it's not so trivial by the looks of it, so for now we stick to a stupid regular socket types. - Supporting OSL could be a rather tricky business via pynodes and could involve quite some work in here. Also it'll stress OSL with something it wasn't really designed to do, but it might just work. - Since inverting the distortion is an optimization problem which is rather tricky to implement on GPU, only CPU supports camera ray nodes at this moment. - The above thing might be solved if we bake distortion into a grid and use as a lookup table from the kernel. Would also help performance by avoiding solving optimization problem for each single camera ray at each sample. - Some stuff might be totally broken at this moment, use with care and don't forget to back your files up before doing experiments. Real quick example: ftp://ftp.blender.org/sergey/camera_nodes.blend.png |
September 26, 2014, 12:22 (GMT) |
Fix T41956, Soften brush does not work Disallow blur radius zero (versioning error). Also fix gaussian distibution for blurring This is to be included in the final release. |
Revision 06871e6 by Antonis Ryakiotakis (gooseberry, gooseberry_farm, hair_immediate_fixes, hair_system, temp_constraint_volume, temp_hair_flow, temp_hair_modifiers, temp_motionpaths, terrible_consequencer) September 26, 2014, 11:57 (GMT) |
Minor corrections to the types |
Revision ac97720 by Antonis Ryakiotakis (gooseberry, gooseberry_farm, hair_immediate_fixes, hair_system, temp_constraint_volume, temp_hair_flow, temp_hair_modifiers, temp_motionpaths, terrible_consequencer, testbuild) September 26, 2014, 10:17 (GMT) |
New data types for sequencer. Uses struct hierarchies to reduce the data used per strip. Also changed sequence -> strip. Might be better to use NSequence for editing as well. |
September 26, 2014, 09:09 (GMT) |
Fix T41962: Command-line without specified filename doesn't renders Issue was caused by the launcher not dealing with slashes in the way windows expects them to be handled -- last slash of the path considered an escape character for the following qoute. This is definitely to be ported to the 2.72 release. |
|
|
|


Master Commits
MiikaHweb | 2003-2021