April 14, 2021, 13:28 (GMT) |
Cycles: Make session buffer params non-public |
Revision 60b8890 by Julian Eisel (asset-browser, asset-browser-poselib, asset-system-filelist, temp-pose-flipping-fix-attempt) April 14, 2021, 13:21 (GMT) |
Merge branch 'master' into asset-browser-poselib |
April 14, 2021, 12:25 (GMT) |
FFmpeg: Adjust default proxy settings GOP size and quality are adjusted for h264 codec. These new values are based on result of benchmark on 9 random files: https://docs.google.com/spreadsheets/d/1nOyUGjoVWUyhQ2y2lAd8VtFfyaY1wQNGj1krCCNbk7Y/edit?usp=sharing Reducing quality to 50 reduces proxy filesize by about 2x on average and has no significant impact on decoding performance. Increasing GOP size from 2 to 10 also reduces proxy filesize 2x-3x while scrubbing is only about 8% slower. It is still around 100FPS with 1920x1080 media. This is unfortunately about 50% slower than MJPEG, but this can be improved with `fastdecode` tune applied to libx264 encoder Quite surprisingly h264 codec presets had little influence on proxy building performance as well as proxy filesize. So far it looks that FFmpeg does initialize encoder in different way then Blender. This applies mot only for presets but for tune and profile libx264 setting. Once this issue is resolved, performance of proxies may be optimized further. Reviewed By: sergey Differential Revision: https://developer.blender.org/D10897 |
Revision 017e9d8 by Clément Foucault (eevee-rewrite, temp-eevee-gpencil-rewrite, viewport-compositor) April 14, 2021, 11:21 (GMT) |
EEVEE: Lights: Initial Work in progress implementation Only supports simple point lights for now |
Revision ab55a1b by Clément Foucault (eevee-rewrite, temp-eevee-gpencil-rewrite, viewport-compositor) April 14, 2021, 11:20 (GMT) |
DRW: Make draw_debug.h C++ compatible |
April 14, 2021, 10:49 (GMT) |
cleanup |
April 14, 2021, 10:41 (GMT) |
rename |
April 14, 2021, 10:38 (GMT) |
simplify generic virtual array span |
Revision 9bf6fa9 by Clément Foucault (eevee-rewrite, temp-eevee-gpencil-rewrite, viewport-compositor) April 14, 2021, 10:08 (GMT) |
Cleanup: EEVEE: RenderPasses: Use iterator |
April 14, 2021, 10:06 (GMT) |
simplify virtual array spans |
April 14, 2021, 09:15 (GMT) |
Merge branch 'master' into virtual-array-attributes |
April 14, 2021, 08:14 (GMT) |
Fix T87479: GPencil SVG export outside of camera When trying to export a GPencil object to SVG from outside the camera view, the expoted file would contain invalid data. This was because the calculation of the bounding box did not have any objects to iterate over. The fix makes sure we create the object list before trying to calculate the bounding box. Reviewed By: antoniov Maniphest Tasks: T87479 Differential Revision: https://developer.blender.org/D10975 |
April 14, 2021, 07:51 (GMT) |
Cycles: Rework passess data access The idea is to move pass access away from RenderBuffers to a place where list of passes is known. Most obvious choice is the Session. A bit of trickery comes from the fact that in theory PathTrace might have multiple RenderBuffers (in the case of multi-device render). So the pass access happens via session into the PathTrace. There is a helper class which pre-calculates various offsets which can be re-used by updates form multiple devices. |
April 14, 2021, 07:05 (GMT) |
LineArt: Optimized tiling strategy for ortho and perspective cameras. |
April 14, 2021, 06:27 (GMT) |
LineArt: Spreading load for multithread loading of geometry. |
April 14, 2021, 06:18 (GMT) |
Fix (unreported) compositor resolution propagation broken by some nodes Some operations may use no preferredResolution ({0, 0}) when calling determineResolution on inputs to check if they have resolution on their own. See MixOperation or MathOperation determineResolution implementation. In such cases {0, 0} resolution ends up being set when an input doesn't have own resolution, breaking propagation of the original preferredResolution. They don't mean to set it as resolution, it's just a check. This patch only allows to set valid resolutions (>0). When it's 0 it may be understood as "No preferred or determined resolution" so it should not be set to give output operations another chance of finding a proper resolution by calling determineResolution again with a different preferredResolution. Test file: {F9932526} Reviewed By: #compositing, jbakker Differential Revision: https://developer.blender.org/D10972 |
April 14, 2021, 02:41 (GMT) |
Cleanup: Whitespace and unused includes |
April 14, 2021, 02:33 (GMT) |
New implementation of the UI in a sidebar Includes panels and drag and drop |
April 14, 2021, 02:19 (GMT) |
Cleanup: remove unused BLANK_PYTHON_TYPE define |
April 14, 2021, 02:11 (GMT) |
Cleanup: spelling |
|
|
|


Master Commits
MiikaHweb | 2003-2021