You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
e9dd032a75
* Updated gem.json for all top-level Gems. All the top level gems now have identical gem.json formats based on the DefautlGem template gem.json. Two additional fields have been added, a type: field and a requirements: field. These fields are for display in Project Mananger. All gem.json files have a default requirements: value of None. Devs are responsible for providing requirements. Gem descriptions and tags have been signed off by developers. Signed-off-by: Cronin <mikecro@amazon.com> * Fixed minor formatting issues with RADTelemetry gem.json Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Adding newline to QtForPython gem.json Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Adding newline to the Twitch gem.json Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Adding newline to AWSCore gem.json Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Adding newline to the AtomTressFX gem.json Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Adding newline to the end of the AudioEngineWwise gem.json Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Adding newline to the end of the CertificateManager gem.json Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Removing extra whitespace in summary of CrashReporting gem.json Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Adding newline to the end of the CustomAssetExample gem.json Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Removing extra whitespace in editorPythonBindings gem summary Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Adding newline to the end of the ScriptedEntityTweener gem.json Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Adding newline to the end of the Gestures gem.json Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Removing extra whitetspace in the summary of the GameStateSamples gem Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Adding newline to the end of the ExpressionEvaluation gem.json Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Updated the ProjectManager PythonBindings.cpp code to reference the newer fields in the gem.json files Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Updating the Gem and Project templates gem.json files to include the "type" and the "requirements" field. Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Updated the default "requirments" field value to be empty string instead of "None" This works better with the ProjectManager GemInfoFromPath function. Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Correcting "summary" field name Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> * Added the requirements text to the AudioEngineWwise Gem This gem requires downloading the Wwise 3rdParty library from AudioKinetic's website Signed-off-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> Co-authored-by: lumberyard-employee-dm <56135373+lumberyard-employee-dm@users.noreply.github.com> |
5 years ago | |
|---|---|---|
| .. | ||
| Code | 5 years ago | |
| CMakeLists.txt | 5 years ago | |
| ReadMe.txt | 5 years ago | |
| gem.json | 5 years ago | |
| preview.png | 5 years ago | |
ReadMe.txt
The Scene Logging Example demonstrates how to extend the SceneAPI by adding additional logging to the pipeline. The SceneAPI is
a collection of libraries that handle loading scene files and converting content to data that the Open 3D Engine and its editor can load.
The following approach is used:
1. The FbxSceneBuilder and SceneData load and convert the scene file (for example, .fbx) into a graph that is stored in memory.
2. SceneCore and SceneData are used to create a manifest with instructions about how to export the file.
3. SceneData analyzes the manifest and memory graph and creates defaults.
4. Scene Settings allows updates to the manifest through a UI.
5. The ResourceCompilerScene uses the instructions from the manifest and the data in the graph to create assets. These assets are ready for Open 3D Engine to use.
The example gem demonstrates the following key features:
- Initialization of the SceneAPI libraries.
(See SceneLoggingExampleModule.cpp)
- Adding a LoadingComponent to hook into the scene loading and react to loading events.
(See Processing/LoadingTrackingProcessor)
- Extension of the Scene Settings UI and ability to set defaults using the BehaviorComponent.
(See Groups/LoggingGroup and Behaviors/LoggingGroupBehavior)
- Adding an ExportingComponent to hook into the scene converting and exporting events.
(See Behaviors/ExportTrackingProcessor)