SoVolumeRenderDetail(3)
π SoVolumeRenderDetail π
okay bestie, welcome to the SoVolumeRenderDetail(3) page β yes that's the manual name, section 3, library functions, we're in the C++ zone now π
β¨ NAME β¨
SoVolumeRenderDetail β the class that stores ray intersection info as it travels through a volume. it's giving "I remember everything that happened on that ray" energy π¦
πΈ SYNOPSIS πΈ
#include <VolumeViz/details/SoVolumeRenderDetail.h>
Inherits SoVolumeDetail. yes queen, she comes from a whole lineage π
π«Ά Static Public Member Functions
static void initClass (void)β the classic init-the-class moment, does exactly what it says on the tin β¨
Static Public Member Functions inherited from SoVolumeDetail
static void initClass (void)β same vibe, inherited, still iconic π
π Additional Inherited Members
Public Member Functions inherited from SoVolumeDetail
virtual SoDetail * copy (void) constβ makes you a copy, lowkey essential for detail objects πvoid getProfileObjectPos (SbVec3f profile[2]) constβ hands you the profile's start and end positions in object space, twoSbVec3fs intoprofileπint getProfileDataPos (SbVec3s profile[2]=0) constβ same deal but for data positions, asSbVec3spairs, default arg0ngl β¨unsigned int getProfileValue (int index, SbVec3s *pos=0, SbVec3f *objpos=0, SbBool flag=FALSE) constβ grabs the voxel value at index, optionally filling in the data pos, the object pos, and a flag (defaults:0,0,FALSE) πSbBool getFirstNonTransparentValue (unsigned int *value, SbVec3s *pos=0, SbVec3f *objpos=0, SbBool flag=FALSE) constβ finds the first value that isn't transparent and tells you if it found one, with the same optionalpos,objposandflaggoodies (defaults0,0,FALSE) π₯void setDetails (const SbVec3f raystart, const SbVec3f rayend, SoState *state, SoNode *caller)β sets the whole thing up from a ray start, a ray end, theSoState, and whoever called it π§
π Detailed Description π
okay so. SoVolumeRenderDetail stores ray intersection information through a volume. that's the whole assignment and she ate π
An SoVolumeRenderDetail holds the info about a ray intersecting a volume that's been rendered with the SoVolumeRender node. so like, ray goes in, volume says hi, this class writes it all down πβ¨
The detail contains a "profile" of voxel values through the volume, where the profile is defined by a start point and an end point. two little anchors, whole lotta voxels in between π
bestie, for the actual how-do-I-extract-this-stuff instructions, go check the superclass documentation β she's got the receipts on how to pull information about the ray profile π
π Author π
Generated automatically by Doxygen for SIMVoleon from the source code. not a human, just a very diligent robot π«Ά
and that's the whole page, no cap π big mwah to SIMVoleon, Version 2.1.0 β thanks for the lore, see u in SoVolumeRenderDetail(3) whenever you need ray-through-volume gossip π
β¨π
π¦ where this page comes from
- fedora 43: SIMVoleon-devel 2.1.0-9.fc43 Β· BSD-3-Clause
- fedora 43: SIMVoleon-devel 2.1.0-9.fc43 Β· BSD-3-Clause
- fedora 44: SIMVoleon-devel 2.1.0-11.fc44 Β· BSD-3-Clause
- fedora 44: SIMVoleon-devel 2.1.0-11.fc44 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms