Merge pull request #27 from frenchdog/feature/BIFROST-10390/update_for_bifrost2_11_release

BIFROST-10390 Update for Bifrost 2.11.0.0

Author: frenchdog

.gitattributes

@@ -0,0 +1,4 @@
+#
+# Ignore trailing whitespace check
+#
+*.md -whitespace

CHANGELOG.md

@@ -1,3 +1,44 @@
+## [1.3.0] - 2024-07-29 (Bifrost 2.11)
+
+### Build
+ - BIFROST-10233 - Update Bifrost Hydra to support USD 24.05
+
+
+### Feature
+ - BIFROST-10457 - Add _get_prim_attribute_connections_ operator
+ - BIFROST-9995 - Add USD Skeleton graphs to the Bifrost Graph Browser
+ - BIFROST-10104 - Add new USD icons
+ - BIFROST-10105 - BifrostUSDExamples updates
+
+    Create prim type from Maya USD attribute "USD_typeName"
+    If the Maya attribute "USD_typeName" is present on the DAG node, it will be used to set the prim type in the imported selection.
+ - BIFROST-10105 - Create variants from Maya selection
+
+    Add "Create New Stage with Variants from Maya Selection" menu in Bifrost USD > Create.
+    Add "Import Maya Variants to Stage" menu in Bifrost USD > Modify.
+ - BIFROST-10016 - Expose applied_schema_names on the "define prim" nodes
+ - BIFROST-10356 - New PointInstancer nodes and menu
+
+    New nodes:
+      - _delete_point_instances_
+      - _get_usd_point_instancer_attributes_
+      - _replace_point_instancer_proto_
+      - _set_point_instances_invisible_
+      - _usd_point_instancer_scope_
+
+    New menus:
+      - Bifrost USD > Modify > Hide Selected PointInstances
+      - Bifrost USD > Modify > Add Point Instancer Scope
+
+    Move _define_usd_point_instancer_ into _USD::PointInstancer_ namespace.
+
+- Add _create_mesh_from_usd_geom_subset_ compound (Experimental)
+
+
+### Bugfix
+ - EMSUSD-1195 - Disable UFE observer if Maya API version is less than 2025.2 to avoid crash in the BifrostUsdExamples plugin.
+
+
 ## [1.2.3] - 2024-04-17 (Bifrost 2.10)
 
 ### Build
@@ -48,6 +89,7 @@
  - BIFROST-9056 - Collapse ports grouping on the _define_usd_prim_attribute_ compound.
  - BIFROST-9334 - Remove compound duplicate in _save_usd_stage.json_ file.
 
+
 ## [1.2.2] - 2024-03-27 (Bifrost 2.9)
 
 ### Build
@@ -73,6 +115,7 @@
  - BIFROST-9334 - Fix save_usd_stage compound errors when current edit target is not the root layer
     - Update the _save_usd_stage_ compound. It is now setting the target layer to the root layer before saving and then restore the current target (using the new get_edit_layer operator).
 
+
 ## [1.2.1] - 2023-11-15 (Bifrost 2.8)
 
 ### Build
@@ -184,9 +227,9 @@
  - BIFROST-8426 - Inconsistent UI in define_usd_prim
 
  - BIFROST-8273 - fix sublayers not saved if relative_path is on
-   - Use the layer's save file path (m_filePath) instead of the sdfLayerIdentifier in the recursive call to Layer::exportToFile().
-   - Add new more complete unit test for export_layer_to_file() that covers multiple cases for relative and absolute paths to sublayers.
-   - removed call to changeDir() that has side effect and is not required anymore for unit tests.
+	- Use the layer's save file path (m_filePath) instead of the sdfLayerIdentifier in the recursive call to Layer::exportToFile().
+	- Add new more complete unit test for export_layer_to_file() that covers multiple cases for relative and absolute paths to sublayers.
+	- removed call to changeDir() that has side effect and is not required anymore for unit tests.
 
 
 ## [1.1.0] - 2023-03-29 (Bifrost 2.7)
@@ -204,12 +247,12 @@
 ### Feature
 
 - BIFROST-7955 - Add applied schema nodes
-   - add_applied_schema: This node adds the applied API schema name to the apiSchema metadata of the prim
-   - remove_applied_schema: This node removes the applied API schema name from the apiSchema metadata of the prim
+	- add_applied_schema: This node adds the applied API schema name to the apiSchema metadata of the prim
+	- remove_applied_schema: This node removes the applied API schema name from the apiSchema metadata of the prim
 
 
 ### Bugfix
 
 ## [1.0.0] - 2022-12-12 (Bifrost 2.6)
 
- - Initial release
+ - Initial release

CMakeLists.txt

@@ -70,16 +70,12 @@ set(BIFUSD_PRODUCT_NAME  "\"Bifrost USD pack\"")
 #==============================================================================
 # This target and property needs to be forward declared before utils.cmake.
 # because bifusd_header_parser refers to them. More deps/properties are added
-# to the target later.
+# to the target later, including in setup.cmake.
 #
 if( NOT TARGET ${BIFUSD_PACKAGE_NAME}_config_info)
     add_custom_target(${BIFUSD_PACKAGE_NAME}_config_info)
 endif()
 
-# Add property to collect the list of generated json files.
-set_target_properties(${BIFUSD_PACKAGE_NAME}_config_info PROPERTIES
-                       BIFROST_USD_PACK_ALL_JSON_FILES "")
-
 #==============================================================================
 # General setup
 # This defines functions and macros that used later on; in particular

SECURITY.md

@@ -0,0 +1,33 @@
+# Security
+
+### Reporting Security Issues
+The bifrost-usd team and community take security bugs in bifrost-usd seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.
+
+### Reporting a Security Vulnerability to Autodesk
+This vulnerability disclosure policy applies to any vulnerabilities you are considering reporting to Autodesk.
+We recommend reading this vulnerability disclosure policy fully before you report a vulnerability and always acting in compliance with it.  
+We value those who take the time and effort to report security vulnerabilities according to this policy. However, we do not offer monetary rewards for vulnerability disclosures.  
+If you believe you have found a security vulnerability relating to the Autodesk's systems or products, please submit a vulnerability report to [Autodesk HackerOne](https://hackerone.com/autodesk) program or [email protected]. Otherwise, submit a report an incident at [Autodesk Trust Center](https://www.autodesk.com/trust/security).  
+In your report please include details of:
+- The software package, website, IP or page where the vulnerability can be observed.
+- A brief description of the type of vulnerability, for example; "XSS vulnerability".
+- Steps to reproduce. These should be a benign, non-destructive, proof of concept. This helps to ensure that the report can be triaged quickly and accurately. It also reduces the likelihood of duplicate reports, or malicious exploitation of some vulnerabilities, such as sub-domain takeovers.
+
+The bifrost-usd team team will send a response indicating the next steps in handling your report. After the initial reply to your report, the security team will keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.
+
+### Responsible Disclosure
+We appreciate the responsible disclosure of security vulnerabilities. Please allow us a reasonable amount of time to address the issue before making it public.
+
+### Supported Versions
+**Version**|**Supported**
+:-----:|:-----:
+1.0.x|:white\_check\_mark:
+0.9.x|:x:
+
+### Learning More About Security
+To learn more about Autodesk Security, please see the [Autodesk Trust Center](https://www.autodesk.com/trust/security).
+
+### Receiving Security Information From Autodesk
+Technical security information about our products and services is distributed through several channels.
+- Autodesk distributes information to customers about security vulnerabilities via https://autodesk.com and [Autodesk Trust Center](https://www.autodesk.com/trust/security).
+- Autodesk may issue release notes and security bulletins detailing security vulnerabilities, workarounds, remediations and any indicators of compromise to aid incident response teams.

bifrost_hydra/README.md

@@ -1,6 +1,6 @@
 
 ## Bifrost Hydra (Experimental)
-Requires a version of the Bifrost SDK that is not released yet.
+Require the [Bifrost Executor SDK](https://help.autodesk.com/view/BIFROST/ENU/?guid=Bifrost_DevHelp_BifrostExecutorSDK_html) introduced in Bifrost 2.10.
 Register a new Hydra Generative Procedural plugin capable of running a Bifrost Graph that will output
 Bifrost geometries to the Hydra Scene Index without using any scene delegate.
 In your Hydra based application (usdview for example), the following variables are needed:

bifrost_hydra/src/BifrostHdEngine/ValueTranslationData.h

@@ -23,6 +23,8 @@
 
 #include <Amino/Core/Any.h>
 
+#include <string>
+
 namespace BifrostHd {
 
 class JobTranslationData;

bifrost_hydra/src/BifrostHdTranslators/GeometryFn.cpp

@@ -32,6 +32,7 @@
 #include <pxr/imaging/hd/retainedDataSource.h>
 #include <pxr/imaging/hd/tokens.h>
 #include <pxr/imaging/hd/xformSchema.h>
+#include <pxr/pxr.h>
 
 #include <iostream>
 
@@ -338,11 +339,20 @@ HdContainerDataSourceHandle GetInstancerInstanceCategoriesDataSource() {
 
 HdContainerDataSourceHandle NewPointInstancerPrimvarsDataSource(
     const Bifrost::Object& object) {
+
+#if (PXR_VERSION >= 2405)
     return HdRetainedContainerDataSource::New(
+        HdInstancerTokens->instanceRotations, BuildInstancerRotateDataSource(object),
+        HdInstancerTokens->instanceScales, BuildInstancerScaleDataSource(object),
+        HdInstancerTokens->instanceTranslations,
+        BuildInstancerTranslateDataSource(object));
+#else
+        return HdRetainedContainerDataSource::New(
         HdInstancerTokens->rotate, BuildInstancerRotateDataSource(object),
         HdInstancerTokens->scale, BuildInstancerScaleDataSource(object),
         HdInstancerTokens->translate,
         BuildInstancerTranslateDataSource(object));
+#endif
 }
 
 HdContainerDataSourceHandle BuildPointInstancerTopologyDataSource(

bifrost_hydra/test/CMakeLists.txt

@@ -58,6 +58,7 @@ set(test_files
 set(lib_config_files
     ${BIFUSD_EXTRA_CONFIG_FILES}
     ${BIFUSD_OUTPUT_ROOT_DIR}/bifrost_hydra_translation.json
+    ${BIFUSD_OUTPUT_ROOT_DIR}/usd_pack_config.json # TODO: remove when BIFROST-9995 is done.
     ${PROJECT_SOURCE_DIR}/bifrost_hydra/test/test_bif_geo_compounds_config.json
 )