Revision cf28448 by Lukas Toenne (gooseberry, gooseberry_farm, hair_immediate_fixes, hair_system, temp_constraint_volume, temp_hair_flow, temp_hair_modifiers, temp_motionpaths) November 6, 2014, 11:32 (GMT) |
Renamed HairVertexGrid to HairGrid, since it's not actually storing hair vertex data. |
Revision 439c7e0 by Lukas Toenne (gooseberry, gooseberry_farm, hair_immediate_fixes, hair_system, temp_constraint_volume, temp_hair_flow, temp_hair_modifiers, temp_motionpaths) November 6, 2014, 11:28 (GMT) |
Removed unused "collider grid" struct from hair volumetrics. This is a leftover from previous approach of hair collisions (with insufficient results). The hair volumetrics actually implements "collision" with solid objects as well, but uses a Neumann boundary condition on the main grid for this purpose. |
Revision 7432efd by Lukas Toenne (gooseberry, gooseberry_farm, hair_immediate_fixes, hair_system, temp_constraint_volume, temp_hair_flow, temp_hair_modifiers, temp_motionpaths) November 6, 2014, 11:17 (GMT) |
Better grid rasterization method for hair volumetric grids. This is based on the paper "Detail Preserving Continuum Simulation of Straight Hair" (McAdams, Selle, Ward, 2009) The main difference is that hair line segments are used rather than only rasterizing velocity at the vertices. This gives a much better coverage of the hair volume grid, otherwise gaps can be produced at smaller grid cell sizes and the distribution is uneven along the hair curve. The algorithm for rasterizing is a variation of Bresenham's algorithm extended onto 3D grids. |
November 6, 2014, 10:47 (GMT) |
Correct recent refactor (use generic callback) |
November 6, 2014, 10:36 (GMT) |
Depsgraph: Playback doesn't crash now The time source is expected to be in the root depsgraph node for now, so we should add it to there instead of the scene node. This raises some questions: - Who don't we have Scene ID node in the graph so far? - Do we really need a time as an operation node, or it's something more up to the EvaluationContext. Later one raises the bigger design question: what should we try to do with the depsgraph and what is we're gonna to solve with the evaluation context? The answer here should be: everything which describes the (sub)graph state should be in the evaluation context. This way this context will finally become some key which totally corresponds to the (sub)scene state. |
November 6, 2014, 10:35 (GMT) |
Merge branch 'master' into mesh-transfer-data |
November 6, 2014, 10:25 (GMT) |
Depsgraph: Make update for new frame closer to the master as well |
November 6, 2014, 10:15 (GMT) |
Depsgraph: Remove RNA call to rebuild the DAG It is now should happen automatically from the scene update, should be no need in manual tricks now. |
November 6, 2014, 10:14 (GMT) |
Depsgraph: Make scene evaluation closer to the master This means BKE_scene_update_tagged() will now do the same callbacks and sound system updates as the old implementation does and will only replace scene update with new code. This is aimed to solve the following issues: - Adding new objects doesn't abort anymore, this is because old code was rebuilding the depsgraph from the scene update function in cases DAG is NULL. Don't see why not to do the same with the new dependency graph for now. - Callbacks are being executed properly, which should make scripts happy. Well, nobody uses this branch yet, but it's good thing to do and easy to support anyway. - Hopefully rendered viewport will be also happier now because the render engine update is now called for new depsgraph as well. |
November 6, 2014, 10:03 (GMT) |
Merge remote-tracking branch 'origin/master' into depsgraph_refactor |
November 6, 2014, 09:29 (GMT) |
Depsgraph: Solve some compilation issues on my laptop All the changes seems small but still legit to have so everyone is happy. |
Revision fcad67e by Martin Felke (fracture_modifier, fracture_modifier-master, temp-fracture-modifier-2.8) November 6, 2014, 01:33 (GMT) |
fake trigger, disable animated checkbox on collision, (but this should be done by hand, earlier, to get better impact speeds) |
November 5, 2014, 23:43 (GMT) |
Merge branch 'master' into GPencil_EditStrokes |
November 5, 2014, 23:31 (GMT) |
Fix: After using Alt-SelectMouse to select an entire stroke, it would be impossible to select normally again |
November 5, 2014, 23:31 (GMT) |
low- and highres colored smoke |
November 5, 2014, 21:49 (GMT) |
Cycles: Add "Max Bounce" control for lamps With this setting, we can limit the influence of a lamp to a certain amount of bounces. 0 = Only direct light contribution 1 = 1 light bounce ... Differential revision: https://developer.blender.org/D860 You can find an example render in the release logs: http://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.73/Cycles |
November 5, 2014, 20:26 (GMT) |
not initializing density fields |
November 5, 2014, 19:53 (GMT) |
SMOKE: mantaflow in Fluid_3d object, running wavelets |
November 5, 2014, 19:28 (GMT) |
Basic, incomplete version of data transfer modifier (WIP). And some cleanup/fixes/refactor/enhancements found/needed while writing modifier itself. |
Revision 2a18501 by Antonis Ryakiotakis (gooseberry, gooseberry_farm, hair_immediate_fixes, hair_system, temp_constraint_volume, temp_hair_flow, temp_hair_modifiers, temp_motionpaths, temp_widgets_c++_experiment, temp_widgets_files_refactor, temp_widgets_update_tagging, UI-experiments, wiggly-widgets) November 5, 2014, 18:41 (GMT) |
Add mapping to properties for widgets. Still pretty much exploring the best way to move here but currently this works by wrapping objects in RNA pointers, pretty much like buttons do. Also modified the arrow widget for lamps to use the new code. The new "unmbrella" widget works now as expected for lamps - of course fine tuning is also needed. |
|
|
|


Master Commits
MiikaHweb | 2003-2021