NoMansSky:Cross SCENE Referencing: Difference between revisions
mNo edit summary |
m (Text replacement - "\[\[Category:NMS-Index-.*\]\]" to "") |
||
| Line 3: | Line 3: | ||
}}{{PageTitle|logo=nomanssky|title=Cross SCENE Referencing}} | }}{{PageTitle|logo=nomanssky|title=Cross SCENE Referencing}} | ||
{{NMSPage}} | {{NMSPage}} | ||
{{TOC}}[[Category:NoMansSky General Guides | {{TOC}}[[Category:NoMansSky General Guides]] | ||
== Referencing a SCENE from another SCENE == | == Referencing a SCENE from another SCENE == | ||
Currently, we know of two different methods of including one scene in another. The first method is the simplest, and is generally what would be used when adding one scene into another. | Currently, we know of two different methods of including one scene in another. The first method is the simplest, and is generally what would be used when adding one scene into another. | ||
Revision as of 19:06, August 5, 2021
Cross SCENE Referencing
Referencing a SCENE from another SCENE[edit | edit source]
Currently, we know of two different methods of including one scene in another. The first method is the simplest, and is generally what would be used when adding one scene into another.
Method 1[edit | edit source]
For a scene that already exists in the game files, the scene file can be edited in a text editor, and a REFERENCE node can be added as a child of some other node in the scene. This child node will need to have some transform, and a SCENEPATH node in the list of ATTACHMENTS. This is the only attachment that this node type may have.
Method 2[edit | edit source]
The second method is more advanced, but seems to get around the problems with the first method.
This method utilises the SELECTABLEOBJECTSTABLE in METADATA/SIMULATION/ENVIRONMENT, as well as, the GcObjectPlacementComponentData struct in an entity file attached to the model.
