#include <collisiondatasectordescriptor.h>
Easy to write/read version of SectorDescriptorBlob.
SectorDescriptor contains information about where the NavData comes from. Written in GeneratorSectorBuilder::MakePlainSectorNavData() when generating NavMesh from the generation process Contains m_sectorName and m_generatorRelativeOutputDirectory, it's possible to retrieve the NavData file path that was generated by the Generation by concatenating GeneratorRootDirectory/m_generatorRelativeOutputDirectory/m_sectorName.EXTENSION where EXTENSION is NavData or ClientInput.
Public Attributes | |
String | m_sectorName |
Contains the name of the sector which is also the name of the file This is used to identify Graph-only NavData (in opposition to NavData containing NavMeshElements) since NavGraph has no guid. More... | |
String | m_generatorRelativeOutputDirectory |
Generator relative directory to used by the generator to output NavData, ClientInput, GenIO, related to this sector m_generatorRelativeOutputDirectory is relativeOutputDir in the call to void SetOutputDirectory(const char* absoluteOutputBaseDir, const char* relativeOutputDir);. More... | |
KyGuid | m_guid |
Index of the Lab's database in which the NavData will be added to. More... | |
String Kaim::ColDataSectorDescriptor::m_generatorRelativeOutputDirectory |
Generator relative directory to used by the generator to output NavData, ClientInput, GenIO, related to this sector m_generatorRelativeOutputDirectory is relativeOutputDir in the call to void SetOutputDirectory(const char* absoluteOutputBaseDir, const char* relativeOutputDir);.
KyGuid Kaim::ColDataSectorDescriptor::m_guid |
String Kaim::ColDataSectorDescriptor::m_sectorName |