WMO/Rendering: Difference between revisions
Jump to navigation
Jump to search
Line 13: | Line 13: | ||
This queried color value is then fed in to the standard lighting logic. | This queried color value is then fed in to the standard lighting logic. | ||
=== Query with C3Segment === | |||
The following function is used to query lighting when the exact poly is not yet known. It uses a <tt>C3Segment</tt> to perform a ranged query against the BSP tree for relevant tris. | The following function is used to query lighting when the exact poly is not yet known. It uses a <tt>C3Segment</tt> to perform a ranged query against the BSP tree for relevant tris. | ||
Line 63: | Line 63: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
=== Query with C3Vector and poly index === | |||
The following function is used to query lighting when the relevant poly is already known. | |||
<syntaxhighlight lang="cpp"> | <syntaxhighlight lang="cpp"> |
Revision as of 03:37, 5 October 2017
Lighting
Lighting for interior WMO groups is prebaked into vertex colors.
CMapObj::QueryLighting
In order to light entities like units, game objects, etc that exist within interior WMO groups, the game does the following:
- Query for the closest MOPY.
- Obtain the 3 relevant MOCV values for the MOPY.
- Create a CImVector color by interpolating the values based on the position of the entity relative to the MOPY (ie barycentric interpolation).
This queried color value is then fed in to the standard lighting logic.
Query with C3Segment
The following function is used to query lighting when the exact poly is not yet known. It uses a C3Segment to perform a ranged query against the BSP tree for relevant tris.
bool CMapObj::QueryLighting(CMapObj *this, uint32_t groupIndex, const C3Segment *seg, CImVector *color, bool *a5) {
CMapObjGroup group = this->groupList[groupIndex];
if (!this->unk6[16] || !(group->unk14 & 1) || group->flags & (SMOGroup::EXTERIOR | SMOGroup::EXTERIOR_LIT)) {
return 0;
}
World::TriData::resultFlags = 0;
World::TriData::nBatches = 0;
World::TriData::nTriIndices = 0;
World::TriData::nVertexIndices = 0;
World::TriData::nMatrices = 0;
float hitT = 1.0;
// Query the BSP tree for the group to find appropriate tris
bool triRes = CMapObjGroup::GetTris(group, seg, &hitT, 0, 0x8, (int)&a2 + 3, 0);
if (!triRes) {
return 0;
}
// Obtain point matching intersection between segment and tri
C3Vector point;
point.x = seg->start.x + hitT * (seg->end.x - seg->start.x);
point.y = seg->start.y + hitT * (seg->end.y - seg->start.y);
point.z = seg->start.z + hitT * (seg->end.z - seg->start.z);
unsigned __int16 hitPoly = word_CD8094;
bool lightRes = CMapObjGroup::QueryLighting(group, &point, hitPoly, color, a5);
return lightRes;
}
Query with C3Vector and poly index
The following function is used to query lighting when the relevant poly is already known.
bool CMapObj::QueryLighting(CMapObj *this, uint32_t groupIndex, const C3Vector *point, uint16_t polyIdx, CImVector *color, bool *a5) {
CMapObjGroup group = this->groupList[groupIndex];
if (!this->unk6[16] || !(group->unk14 & 1) || group->flags & (SMOGroup::EXTERIOR | SMOGroup::EXTERIOR_LIT)) {
return 0;
}
// Since the point and poly are already known, there's no need to query the BSP tree
bool lightRes = CMapObjGroup::QueryLighting(group, point, polyIdx, color, a5);
return lightRes;
}