From: Braun, Tom (tom.braun++at++lmco.com)
Date: 08/09/2000 05:24:40
Hello all,
I have been struggling for quite some time with a problem that I have with
Performer giving me invalid isector intersection values when it intersects
with the terrain. Most of the time the intersection values are correct.
However, there are places in my database where it seems like isect is not
filing in the hits[] array. I say this because, during the times when I get
invalid results, I view the hits[] array before and after isect is called
and the values do not change. This hits[] array is passed into MQuery and
MQuery gives me predictably invalid "points" intersection values. However,
isect returns a 1 meaning that my isector has intersected with the terrain.
There is nothing noticeably different about the places that my TerrainHeight
routine works and where it doesn't work. My routine may not work at one
location, but if I move my intersection segment over by 0.5 meters, it will
again give me valid HAT values. I have also independently verified in
MultiGen that the location where I set my segment is, in fact, above
terrain. By the way, all of my terrain is flagged as terrain in MultiGen.
I'm hoping someone else may have run into this problem as well.
Thank you in advance for any help you can provide. I have included a code
snippet at the end of this email.
Tom
This archive was generated by hypermail 2b29 : Wed Aug 09 2000 - 05:28:21 PDT