SGL
- Last UpdatedOct 22, 2025
- 2 minute read
The SGL node enables you to load a set of replay logs that were generated by AVEVA™ Everything 3D.
The logs, whose file format is .sgl, but are encoded as XML, can contain definition of primitives grouped together in SGL segments that are natively supported by XR engine and not converted into MWX.
Currently, XR supports only one SGL model hierarchy, in which each SGL segment corresponds to a Scenegraph node in XR. This is the reason why only one SGL node can be present at time, so it will not be possible to add more than one SGL node to the scene.
Platform support
This node is supported on XR-Windows platform only.
|
XR-WIN |
XR-P-WIN |
XR-P-IOS |
XR-P-AND |
XR-P-WASM |
|---|---|---|---|---|
|
Full support |
No support |
No support |
No support |
No support |
|
|
|
|
|
|
Multiple Replaylogs
Similar to SPC format, the SGL node is not connected to a single source file, but to a collection of source files.
The file field represents the directory where the log files are located, while the replaylogs field contains the list of the files in that directory that are managed by the SGL container. That list can be a subset of all the log files available in the folder.
Log files can be loaded and unloaded at runtime.
Container and visibility
The SGL node can be shown or hidden using the visible field.
SGL fields
These are the fields for SGL node. Only the node-specific fields are indicated, not fields obtained by inheritance.
Field inheritance: NodeBase > Mwx > SGL
|
Field |
Type |
Use |
Default value |
Description |
|---|---|---|---|---|
|
replaylogs |
mstring |
Optional |
List of the replaylogs in the file folder to be shown. Replaylogs can be added or removed at runtime to manage visibility. |