Welcome to mirror list, hosted at ThFree Co, Russian Federation.

git.blender.org/blender.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2022-11-10EEVEE Next: Fix wrong DoF when a non-camera object is the active cameraMiguel Pozo
Related to T101533. Reviewed By: fclem Differential Revision: https://developer.blender.org/D16412
2022-11-10Merge branch 'blender-v3.4-release'Sergey Sharybin
2022-11-10Fix missing wl_display_get_error in the Wayland dynamic loaderSergey Sharybin
Some of the previous commits in Wayland related code added use of this function, but did not update the dynamic loader. This broke compilation of configurations which use dynamic loader for Wayland (which is the official way oh how Blender is built).
2022-11-10Merge branch 'blender-v3.4-release'Sergey Sharybin
2022-11-10Fix strict compiler warningsSergey Sharybin
2022-11-10NLA: Update context menu to include meta strip operatorsJason Schleifer
The meta strip operator is available in the Add menu, but not in the context menu. This patch adds these two operators to the context menu: * nla.meta_add * nla.meta_remove Reviewed By: sybren, RiggingDojo Differential Revision: https://developer.blender.org/D16353
2022-11-10Fix T102151: Output nodes don't work inside node groupsOmar Emara
Using output nodes inside node groups in compositor node trees doesn't work for the realtime compositor. Currently, the realtime compositor only considers top level output nodes. That means if a user edits a node group and adds an output node in the group, the output node outside of the node group will still be used, which breaks the temporary viewers workflow where users debug results inside a node group. This patch fixes that by first considering the output nodes in the active context, then consider the root context as a fallback. This is mostly consistent with the CPU compositor, but the realtime compositor allow viewing node group output nodes even if no output nodes exist at the top level context. Differential Revision: https://developer.blender.org/D16446 Reviewed By: Clement Foucault
2022-11-10Merge branch 'blender-v3.4-release'Sergey Sharybin
2022-11-10SVG: Add more sophisticated test suitSergey Sharybin
This test suit tests SVG on a big files, as opposite of testing one specific aspect of the standard by atomic files.
2022-11-10GHOST/Wayland: report a message when there is a fatal errorCampbell Barton
Help troubleshooting T100855.
2022-11-10Cleanup: minor naming changes, make listener struct constCampbell Barton
2022-11-10Merge branch 'blender-v3.4-release'Campbell Barton
2022-11-10Cleanup: spelling in commentsCampbell Barton
2022-11-10Merge branch 'blender-v3.4-release'Campbell Barton
2022-11-10Merge branch 'blender-v3.4-release'Campbell Barton
2022-11-10Merge branch 'blender-v3.4-release'Campbell Barton
2022-11-10Cleanup: formatCampbell Barton
2022-11-10GHOST/Wayland: add wl_display_listener for debuggingCampbell Barton
Currently only used for logging to help with debugging.
2022-11-10Cleanup: compiler warnings (unused-parameter & missing-declarations)Campbell Barton
2022-11-10Cleanup: formatCampbell Barton
2022-11-10Attempt to fix build error on WindowsRay Molenkamp
Was failing since 1efc94bb2f7b, probably because some include uses `std::min()`/`std::max()` which messes with the windows min/max defines.
2022-11-10Fix uninitialized variable use in asset metadata testJulian Eisel
Wasn't an issue until 1efc94bb2f7b added a destructor, which would attempt to destruct variables at uninitialized memory.
2022-11-10Fix failure in recently added asset library testsJulian Eisel
Mistake in 1efc94bb2f7b.
2022-11-10Merge branch 'blender-v3.4-release'Ray Molenkamp
2022-11-10audaspace: Fix build error with MSVC 17.4+Ray Molenkamp
`DeviceManager.h` uses `std::string` without explicitly including the `<string>` header. While older MSVC implicitly included this header somewhere, the headers for 17.4+ do not leading to a build error.
2022-11-10Merge branch 'blender-v3.4-release'Leon Schittek
2022-11-10Fix incorrect forward declarations, causing warnings on WindowsJulian Eisel
2022-11-10Fix T102385: Set frame node active after joining nodesLeon Schittek
Set the created frame node to be the active node when joining nodes with the `NODE_OT_join` operator. This behavior was unintentonaly changed in rB545fb528d5e1 when the operator's execute function was simplified by utilizing the node tree topology cache. Reviewed By: Hans Goudey Differential Revision: http://developer.blender.org/D16440
2022-11-10Merge branch 'blender-v3.4-release'Richard Antalik
2022-11-09Fix T102256: Gamma Cross blend mode causes stripesRichard Antalik
Function `do_gammacross_effect_float` processed one color channel per loop iteration instead of whole pixel.
2022-11-09Merge branch 'blender-v3.4-release'Hans Goudey
2022-11-09Fix T101972: Crash converting 1 or 2 point NURBS curve to BezierHans Goudey
The conversion is only able to handle NURBS curves with at least three points. This commit just avoids the crash for shorter curves. If this ends up confusing users, an error message could be added in the future.
2022-11-09Merge branch 'blender-v3.4-release'Brecht Van Lommel
2022-11-09Fix T100883: crash with particle instancing and clumpingBrecht Van Lommel
Properly initialize clump curve mapping tables for duplis and other cases where this was missed by making a generic init/free function instead of duplicating the same logic in multiple places. Also fold lattice deform init into this.
2022-11-09Merge branch 'blender-v3.4-release'Brecht Van Lommel
2022-11-09Cleanup: Link to documentation page for asset representation typeJulian Eisel
2022-11-09Fix T101669: Cycles artifacts in bump map bakingBrecht Van Lommel
After barycentric convention changes, the differentials used for bump mapping were wrong leading to artifacts with long thin triangles.
2022-11-09Cleanup: Remove unused class variable, added in previous commitJulian Eisel
2022-11-09Asset System: New core type to represent assets (`AssetRepresenation`)Julian Eisel
Introduces a new `AssetRepresentation` type, as a runtime only container to hold asset information. It is supposed to become _the_ main way to represent and refer to assets in the asset system, see T87235. It can store things like the asset name, asset traits, preview and other asset metadata. Technical documentation: https://wiki.blender.org/wiki/Source/Architecture/Asset_System/Back_End#Asset_Representation. By introducing a proper asset representation type, we do an important step away from the previous, non-optimal representation of assets as files in the file browser backend, and towards the asset system as backend. It should replace the temporary & hacky `AssetHandle` design in the near future. Note that the loading of asset data still happens through the file browser backend, check the linked to Wiki page for more information on that. As a side-effect, asset metadata isn't stored in file browser file entries when browsing with link/append anymore. Don't think this was ever used, but scripts may have accessed this. Can be brought back if there's a need for it.
2022-11-09Cleanup: Miscellaneous cleanups to trim curves nodeHans Goudey
- Fix braces initialization warning - Fixed missing static specifier - Removed two unused functions
2022-11-09Fix T102214: inconsistenty between bake and render with invalid material indexBrecht Van Lommel
When the materal slot index on mesh faces exceeds the number of slots, rendering would use the last material slot while other operations like baking would fall back to the default material. Now consistently use the last material slot in such cases, since preserving backwards compatibility for rendering seems most important. And if there is one material slot, it's more useful to use that one rather than falling back to the default material.
2022-11-09Merge branch 'blender-v3.4-release'Hans Goudey
2022-11-09Geometry Nodes: Trim curve node selection input and correctionsMattias Fredriksson
Correct trim for cyclical curves mentioned in T101379, splitting the curves if the start/endpoint is at the 'loop point'. Correct implementation based on comments in D14481, request was made to use 'foreach_curve_by_type' to computing the point lookups. Included corrections from D16066 as it may not be a adopted solution. Exposed selection input by adding it as input to the node. Note: This is disabled for 3.4 to avoid making UI changes in Bcon3. Differential Revision: https://developer.blender.org/D16161
2022-11-09Improved Korean Font SampleHarley Acheson
Small change to the text sample used for Korean font previews See D16428 for details. Differential Revision: https://developer.blender.org/D16428 Reviewed by Brecht Van Lommel
2022-11-09Fix T102140: Replacement of Noto Sans CJK FontHarley Acheson
Replace our Noto Sans CJK with a version that has Simplified Chinese set as the default script. See D16426 for details and examples Differential Revision: https://developer.blender.org/D16426 Reviewed by Brecht Van Lommel
2022-11-09Fix T102140: Replacement of Noto Sans CJK FontHarley Acheson
Replace our Noto Sans CJK with a version that has Simplified Chinese set as the default script. See D16426 for details and examples Differential Revision: https://developer.blender.org/D16426 Reviewed by Brecht Van Lommel
2022-11-09Fix T102257: Crash when making an Object as Effector set to Guide and trying ↵Germano Cavalcante
to scrub the timeline rB67e23b4b2967 revealed the bug. But the bug already existed before, it just wasn't triggered. Apparently the problem happens because the python code generated in `initGuiding()` cannot be executed twice. The second time the `initGuiding()` code is executed, the local python variables are removed to make way for the others, but the reference to one of the grids in a `Solver` object (name='solver_guiding2') is still being used somewhere. So an error is raised and a crash is forced. The solution is to prevent the python code in `initGuiding()` from being executed twice. When `FLUID_DOMAIN_ACTIVE_GUIDE` is in `fds->active_fields` this indicates that the pointer in `mPhiGuideIn` has been set and the guiding is already computed (does not need to be computed again). Maniphest Tasks: T102257 Differential Revision: https://developer.blender.org/D16416
2022-11-09Fix T102257: Crash when making an Object as Effector set to Guide and trying ↵Germano Cavalcante
to scrub the timeline rB67e23b4b2967 revealed the bug. But the bug already existed before, it just wasn't triggered. Apparently the problem happens because the python code generated in `initGuiding()` cannot be executed twice. The second time the `initGuiding()` code is executed, the local python variables are removed to make way for the others, but the reference to one of the grids in a `Solver` object (name='solver_guiding2') is still being used somewhere. So an error is raised and a crash is forced. The solution is to prevent the python code in `initGuiding()` from being executed twice. When `FLUID_DOMAIN_ACTIVE_GUIDE` is in `fds->active_fields` this indicates that the pointer in `mPhiGuideIn` has been set and the guiding is already computed (does not need to be computed again). Maniphest Tasks: T102257 Differential Revision: https://developer.blender.org/D16416
2022-11-09Cycles: Add basic support for using OSL with OptiXPatrick Mours
This patch generalizes the OSL support in Cycles to include GPU device types and adds an implementation for that in the OptiX device. There are some caveats still, including simplified texturing due to lack of OIIO on the GPU and a few missing OSL intrinsics. Note that this is incomplete and missing an update to the OSL library before being enabled! The implementation is already committed now to simplify further development. Maniphest Tasks: T101222 Differential Revision: https://developer.blender.org/D15902
2022-11-09Merge branch 'blender-v3.4-release'Sergey Sharybin