DtModelInfo is a mapping of a 'model' name to a 'model' id A 'model' can have a number of lods. An 'lod' has an id.
| makVrv::DtModelInfo::DtModelInfo |
( |
| ) |
|
| virtual makVrv::DtModelInfo::~DtModelInfo |
( |
| ) |
|
|
virtual |
| virtual void makVrv::DtModelInfo::setNameAndId |
( |
const std::string & |
modelName, |
|
|
int |
id |
|
) |
| |
|
virtual |
| virtual const std::string& makVrv::DtModelInfo::modelName |
( |
void |
| ) |
const |
|
virtual |
| virtual int makVrv::DtModelInfo::id |
( |
void |
| ) |
const |
|
virtual |
| virtual const DtLodId& makVrv::DtModelInfo::lodId |
( |
int |
lodId | ) |
const |
|
virtual |
Get the lod with id equaling lodId.
| virtual bool makVrv::DtModelInfo::insertLodEntryAndLod |
( |
int |
lodId | ) |
|
|
virtual |
Insert an lod (implicitly an id) This method is thread safe.
The calls to insertLodEntryAndLod can come from different threads and in any order. The atomic and the map together maintain the mapping of the lod id coming from the call to the actual internal DtLodId whose id is generated using the atomic below. The id of DtLodId and the keys for the map may or may not match. The DtLodIds always start from zero and are monotonically increasing The reason for this is this class is typically used by the Indirect rendering engine/GPU directly, and the bookkeeping needed makes this mandatory
| virtual int makVrv::DtModelInfo::currNextLodId |
( |
void |
| ) |
const |
|
virtual |
For internal use/debugging.
| virtual void makVrv::DtModelInfo::printInfo |
( |
void |
| ) |
const |
|
virtual |
For internal use/debugging.
| virtual int makVrv::DtModelInfo::numOfEntries |
( |
void |
| ) |
const |
|
virtual |
For internal use/debugging.
| virtual void makVrv::DtModelInfo::setRange |
( |
float |
startVal, |
|
|
float |
endVal |
|
) |
| |
|
virtual |
Top level min/max range for a model This will get combined with the lod(s) within the model like so: final lod range: ( max(startVal, lodStartVal) , min(endVal, lodEndVal) )
| float makVrv::DtModelInfo::startVal |
( |
void |
| ) |
const |
Top level min/max range for a model This will get combined with the lod(s) within the model like so: final lod range: ( max(startVal, lodStartVal) , min(endVal, lodEndVal) )
| float makVrv::DtModelInfo::endVal |
( |
void |
| ) |
const |
Top level min/max range for a model This will get combined with the lod(s) within the model like so: final lod range: ( max(startVal, lodStartVal) , min(endVal, lodEndVal) )
| bool makVrv::DtModelInfo::rangeValid |
( |
void |
| ) |
const |
Top level min/max range for a model This will get combined with the lod(s) within the model like so: final lod range: ( max(startVal, lodStartVal) , min(endVal, lodEndVal) )
| virtual void makVrv::DtModelInfo::setModelDefName |
( |
const std::string & |
modelDef | ) |
|
|
virtual |
set/get model def name, if any
| virtual const std::string& makVrv::DtModelInfo::modelDefName |
( |
void |
| ) |
const |
|
virtual |
set/get model def name, if any
| std::string makVrv::DtModelInfo::myModelName |
|
protected |
| std::string makVrv::DtModelInfo::myModelDefName |
|
protected |
| int makVrv::DtModelInfo::myId |
|
protected |
| tbb::atomic<int> makVrv::DtModelInfo::myNextLodId |
|
protected |
The calls to insertLodEntryAndLod can come from different threads and in any order. The atomic and the map together maintain the mapping of the lod id coming from outside to the actual DtLodId whose id is generated using the atomic below. The id of DtLodId and the keys for the map may or may not match.
| float makVrv::DtModelInfo::myStartVal |
|
protected |
| float makVrv::DtModelInfo::myEndVal |
|
protected |
The documentation for this class was generated from the following file:
- /data/exports/nrhent7-1/nightly/docs/vrForces.vrf5-0-branch/include/vrvIndirectRendering/DtModelInfo.h
