|
| 1 | +## [1.2.1] - 2023-11-15 |
| 2 | + |
| 3 | +### Build |
| 4 | + |
| 5 | + - BIFROST-9103 - Replace pxr by PXR_NS |
| 6 | + - BIFROST-9093 - Uses cpp2json executable instead of the deprecated amino_cpp2json_foreach one. |
| 7 | + - BIFROST-8182 - Remove -Wno-unused-macros on Windows targets |
| 8 | + - BIFROST-8182 - Clang-tidy support: Add the cmake target "bifrost_usd_clang_tidy" to the build. |
| 9 | + |
| 10 | +### Feature |
| 11 | + |
| 12 | + - BIFROST-8077 - Add support for half and matrix attribute types |
| 13 | + |
| 14 | + - BIFROST-8574 - Add anchor_path parameter on add_reference_prim and add_payload_prim |
| 15 | + |
| 16 | + By specifying an "anchor_path", the identifier of the referenced layer will not include such anchor path in the reference list. |
| 17 | + |
| 18 | + - BIFROST-8424 - Add slider and color picker on ops |
| 19 | + |
| 20 | + - BIFROST-9008 - Add set_layer_permission node |
| 21 | + |
| 22 | + To be used for the very specific scenario when you need to reference a layer |
| 23 | + that needs to be modified by an other runtime than Bifrost. |
| 24 | + |
| 25 | + For example, if a stage generated by Bifrost references a "file based" layer |
| 26 | + storing some USD materials who should be authored in the LookdevX Editor, |
| 27 | + it would not work by default. This is because in order to keep the referenced layer |
| 28 | + "file based", the "read only" mode would need to be enabled in the open_layer node. |
| 29 | + If not in read only mode, the opened layer ("file based" layer) would be automatically |
| 30 | + copied into an anonymous layer by Bifrost USD (to avoid side effects) and so would not |
| 31 | + be editable in LookdevX in a persistent way (as the layer identifier would change at |
| 32 | + every execution of the graph). |
| 33 | + |
| 34 | + The node graph to open a layer in Bifrost and let it be editable outside should look as following: |
| 35 | + open_layer (with read_only "on") -> set_layer_permission (with read_only "off") -> add_reference_prim |
| 36 | + |
| 37 | + The open_layer node will call the BifrostUsd::Layer constructor that is "opening or finding" the USD layer |
| 38 | + using the file path as an identifier (and will not create an anonymous layer, because of the read only mode). |
| 39 | + The set_layer_permission will allow the layer to be editable and will not output an anonymous layer. |
| 40 | + |
| 41 | + - BIFROST-8788 - Use for_each in define_usd_mesh |
| 42 | + |
| 43 | + - BIFROST-7769 - use getEnv*() functions from public Executor SDK |
| 44 | + |
| 45 | + - BIFROST-8199 - Use ConfigEnv instead of Object to get config from environment |
| 46 | + |
| 47 | + - BIFROST-3401 - Use new API for FileUtils::getRelativePath. |
| 48 | + |
| 49 | +### Bugfix |
| 50 | + |
| 51 | + - BIFROST-9067 - Fix connection order when creating an add_to_stage node 'on the fly' |
| 52 | + |
| 53 | + - BIFROST-8826 - fix random test failures on Windows |
| 54 | + |
| 55 | + - Layer::exportToFile() now uses SdfLayer::New() instead of CreateNew(). |
| 56 | + This prevents a temporary and default file to be created on the disk |
| 57 | + before the final exported file is actually written. On Windows, when |
| 58 | + Pixar USD is writing an initial file and almost immediately attempts |
| 59 | + to replace its content by renaming another file to such initial file, |
| 60 | + an "access denied" error can occasionally occur; eliminating the |
| 61 | + temporary file on the first place by not calling CreateNew() avoids |
| 62 | + this error. |
| 63 | + - Each unit test file now outputs its exported files into its own unique |
| 64 | + folder, avoiding completely the possibility that two concurrent tests |
| 65 | + from different test files would attempt to export to the same file. |
| 66 | + These unique output folders are deleted as a first phase for each test |
| 67 | + file, allowing tests to assume and check that an output file is not |
| 68 | + already on disk before it is being exported. |
| 69 | + - Some tests were previously just lucky to succeed, as they were |
| 70 | + exporting a root layer and sublayer to disk, but the sublayer was |
| 71 | + actually exported into the default output folder, not into the expected |
| 72 | + folder, and since the sublayer file was already saved to disk by |
| 73 | + another test case, the test assumed that everything went fine. Such |
| 74 | + test cases are now fixed or were removed (if not fixable). |
| 75 | + - Tests do not export initial files first, then replacing these by final |
| 76 | + file content, and finally checking the final file for some expected |
| 77 | + content. This was also occasionally causing "access denied" errors, as |
| 78 | + described above. |
| 79 | + - add README.md in test folder |
| 80 | + |
| 81 | + |
1 | 82 | ## [1.2.0] - 2023-05-12
|
2 | 83 |
|
3 | 84 | ### Build
|
|
28 | 109 | - BIFROST-8426 - Inconsistent UI in define_usd_prim
|
29 | 110 |
|
30 | 111 | - BIFROST-8273 - fix sublayers not saved if relative_path is on
|
31 |
| - - Use the layer's save file path (m_filePath) instead of the sdfLayerIdentifier in the recursive call to Layer::exportToFile(). |
32 |
| - - Add new more complete unit test for export_layer_to_file() that covers multiple cases for relative and absolute paths to sublayers. |
33 |
| - - removed call to changeDir() that has side effect and is not required anymore for unit tests. |
| 112 | + - Use the layer's save file path (m_filePath) instead of the sdfLayerIdentifier in the recursive call to Layer::exportToFile(). |
| 113 | + - Add new more complete unit test for export_layer_to_file() that covers multiple cases for relative and absolute paths to sublayers. |
| 114 | + - removed call to changeDir() that has side effect and is not required anymore for unit tests. |
34 | 115 |
|
35 | 116 |
|
36 | 117 | ## [1.1.0] - 2023-03-29
|
|
48 | 129 | ### Feature
|
49 | 130 |
|
50 | 131 | - BIFROST-7955 - Add applied schema nodes
|
51 |
| - - add_applied_schema: This node adds the applied API schema name to the apiSchema metadata of the prim |
52 |
| - - remove_applied_schema: This node removes the applied API schema name from the apiSchema metadata of the prim |
| 132 | + - add_applied_schema: This node adds the applied API schema name to the apiSchema metadata of the prim |
| 133 | + - remove_applied_schema: This node removes the applied API schema name from the apiSchema metadata of the prim |
53 | 134 |
|
54 | 135 |
|
55 | 136 | ### Bugfix
|
56 | 137 |
|
57 | 138 | ## [1.0.0] - 2022-12-12
|
58 | 139 |
|
59 |
| - - Initial release |
60 |
| -- 2022-12-12 |
61 |
| - |
62 | 140 | - Initial release
|
0 commit comments