Bge 3.6 #1924
Open
Bge 3.6 #1924
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit 145eb28.
This reverts commit 9bdfb15.
This reverts commit d41021a.
This reverts commit 6805657.
This reverts commit 1b63a29.
…l width" This reverts commit 39a5025.
This reverts commit c89354d.
This reverts commit 76112f1.
…plate" This reverts commit d4217c2.
…cts" This reverts commit 430b271.
This reverts commit 086dada.
This reverts commit a9193a9.
This reverts commit ac6af0b.
This reverts commit feaeb7e.
This reverts commit 7be3a0a.
…-release' into upbge-v0.36-release
…-release' into upbge-v0.36-release
…-release' into upbge-v0.36-release
…-release' into upbge-v0.36-release
As I broke backward compatibility (noticed by BluePrint on dicord)
In 3.6, the legacy to current mesh format conversion of edge creases would crash when loading a file from 4.0, because it expected there to be an `MEdge` array, which doesn't exist in 4.0. This didn't happen previously because edge creases were stored in the same format for 4.0. Other "legacy to current" format conversions have similar null checks, it was just missing here. Pull Request: https://projects.blender.org/blender/blender/pulls/109386
…-release' into upbge-v0.36-release
Currently on Windows some dependencies are built with MinGW/GCC 3.x this commit removes that, in favor of building them with MSVC via msys2. This will make it easier in the future to offer Win/Arm64 builds of blender. Notable changes: - This change drops support for the external libxvid library in favor of ffmpegs built in support for this format. This has been done with permission from the VFX module. Pull Request: https://projects.blender.org/blender/blender/pulls/108983 https://projects.blender.org/blender/blender/pulls/105502 (cherry picked from commit ee1b2f5)
The splash has been done using a demo file from Davide Tirindelli (CC- BY-SA)
With C++ based built-in implementations having both more features and way better performance, it's time to retire the add-ons. Implements #104503 and #104504. Pull Request: https://projects.blender.org/blender/blender/pulls/108440 (cherry picked from commit 23afc61)
Required to make 3.6 files readable by 3.3 once the compatibility changes are backported to the LTS releases. Part of #109151 (PR !110109).
This implements the main aspects of changes to blendfile compatibility as designed in #109151: * Blender files which file minversion is newer than current Blender executable won't be loaded at all. * Blender files which file version is newer than current Blender will triger systematic warning to user: * In the status info bar (lower right corner in default UI). * When attempting to save (overwrite) them. This means that the file minversion becomes a hard limit, and not a soft, warning-only as it used to be. Further more, forward compatibility warning is now systematic (instead of depending on file minversion), and more visible for users. See also https://wiki.blender.org/wiki/Process/Compatibility_Handling for details over the new policy. Technically: * Opening any file with a minversion newer than current Blender file one now triggers an early abort, with an error message reported to the user. This is handled by a new utils called from `blo_decode_and_check`. * Any file newer than current Blender version sets a new `has_forward_compatibility_issues` flag in Main struct at read time. * Status bar info area is turned into a template, which uses this flag to display special warning UI and tooltip when set. * A new confirmation popup appears when user tries to save (overwrite) such a 'newer' blendfile, stating potential loos of data, and proposing by default to 'save as' instead. * The 'quit unsaved' popup has also been updated to 'save as' instead of 'save' when the edited file is has potential forward compitibility issues. NOTE: For 3.6LTS, an additional hot-fix is applied on read file minversion, to ensure that all files from early 4.0 develpment stages remain readable in Blender 3.6LTS after this commit. Part of #109151 (PR !110109).
`BKE_blendfile_is_readable` attempts to open the given file path, and return `true` on success, `false` on failure. Part of #109151 (PR !110109).
…id library. In case a blend file opening fails (in the context of library content listing, e.g. for linking or appending), the File Browser would just show an emtpy window. With the new comnpatibility policy, this will now become a fairly common situation, which requires giving proper explanations to the user. This commit re-uses and extends the system used to display errors messages from the Asset browser. Part of #109151 (PR !110109). Pull Request: https://projects.blender.org/blender/blender/pulls/110568
The wrong RNA pointers were passed (passing the root ones instead of the ones actually owning the rna-path-resolved property). This was likely a harmless mistake, since it only affected RNA collections of IDs, afaik we currently don't have many (if any) of these in non-ID RNA structures. The children collections and objects in a Collection data-block RNA structure e.g. were not affected. But the potential consequence of that bug would have been missing automatic detection of some needed liboverride resyncs.
Older versions of Wayland would crash on startup because of the requested zwp_pointer_gestures_v1 version. Resolve by supporting older versions.
The new notifier triggers `WM_gizmomap_tag_refresh` in `view3d_main_region_listener` which makes sure that gizmos are updated when playback ends.
The build fails without these. Pull Request: https://projects.blender.org/blender/blender/pulls/110609
Commit `c9be925f7d` fixed files for studio, that were saved in incorrect state. This also attempted to fix unaffected files. In affected files `seq->startofs` did overflow. Sound strips are not expected to have negative `startofs` and therefore fix in `c9be925f7d` can be limited to broken files by checking `startofs` value.
Strip was removed from `seqbase` prior to calling `SEQ_edit_remove_flagged_sequences()` which resulted in strip not being actually removed, and it could be seen in timeline while being active.
#109460 was caused by the introduction of implicit sharing for custom data layers (7eee378eccc8f87e17). Due to implicit sharing, the vertex weight layer is now shared between the original and evaluated object in object/weight paint mode, but not in edit mode because of bmesh. For that reason, the original data has to be copied to be able to edit it, which causes its pointer to change. `uiDefButF` can't deal with the situation when the pointer changes on every redraw. The solution is to just use an intermediate variable that is passed to the `uiBut` and to update the vertex weight only when the intermediate value has changed. Pull Request: https://projects.blender.org/blender/blender/pulls/109665
Regression caused by 03f17c4 In that commit it was assumed that the hotkey modifier `S` had no influence if we were already resizing. But this is not the case in tracking. The second `S` has influence and should not be filtered. The solution is to add a conditional only to Trackers transformation. This commit also fixed the canceling of this transformation which did not revert the search area to its original value.
…h_id code. Yet another 'obviously' missing bit in foreach_id processing found and fixed.
Naming is bad and confusing, but the 'expander' code path from readfile can also be used outside of the reading context (see e.g. `BKE_blendfile_write_partial` code). So code cannot assume that it is exclusively working on data freshly read from file. This should be renamed - but should also be probably replaced by proper usage of the more generic 'foreach_id' code anyway, see #105134. Found while investigating #109588.
This reverts commit ffcc828. Seems Windows buildbot wasnt happy about this (it cherry-picked and built fine on linux) Pull Request: https://projects.blender.org/blender/blender/pulls/110973
This is backported from cd74ba6. Pull Request: https://projects.blender.org/blender/blender/pulls/111001
Add a simple check when inserting keyframes to ensure the data is not linked Pull Request: https://projects.blender.org/blender/blender/pulls/109813
When keys were not perfectly on the frame, the index logic would fail and duplicate data across 2 frames. Using `round()` solves this. It does not add subframe support though. Pull Request: https://projects.blender.org/blender/blender/pulls/110059
There were two separate issues occurring here: With some other recent changes to curve handles, an early exit was added when the handles should not display, however, this early exit was not discarding geometry in the Metal implentation, but leaving values undefined. Resulting in random geometry flickering on screen. This may not previously have happened in certain modes if the vertex buffers were zero-initialised up-front (which only happens with certain debug flags). Curve handle geometry generation would render incorrectly when outputting triangleStrips IF the transparent border was disabled. Authored by Apple: Michael Parkin-White Pull Request: https://projects.blender.org/blender/blender/pulls/110719 Pull Request: https://projects.blender.org/blender/blender/pulls/111044
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.