Curtis L. Olson writes: > >Norman Vine writes: >> tarball for new hitlist code >> http://www.vso.cape.com/~nhv/files/fgfs/new_hitlist.tgz >> >> For those of you not using the CVS version of PLib >> you will need a copy of sgdPointInTriangle() >> from the older hitlist.cxx this one replaces > > >I'm finding that I get wrong elevations reported for portions of >airports that span multiple tile boundaries. Such airports are >attached to one particular tile in the scene graph, but they can >extend into neighboring tiles. For instance, KBOS (Boston) sits right >on top of the corners of 4 tiles. However, in the scene graph it is >root below only one tile (chosen arbitrarily for all practical >purposes.)
the routine has the 'smarts' to try the whole graph if and when it doesn't get an intersection in the 'current tile' so the tile boundary thing shouldn't be the problem I'll try testing with KBOS again but I was teleporting there as part of my regression testing because of its unique tile arrangement Yikes good catch :-( Hmm..... hey this still works in my test bed :-) FYI This was developed against my fork of FGFS which I made when the view stuff changed a month or so ago and regression tested against the then current FGFS snapshot where this still works and I didn't move to the current FGFS code or base until this morning when I discovered why YASIM was blowing up so I got fresh CVS snaps and it seemed to work OK against these so I announced it. What has changed !!! Except for the highest level fgCurrentElev() call everything is I believe FGFS independent ie pure SSG code operating directly with the data stored in the scenegraph. Has the FGFS scenery node linkage changed subtly somehow in the last month or so ? FWIW It appears to me as if you get one frame of KBOS at the correct altitude then get pushed into the sky Arrgh I really don't know when or even if I'll get to this as I really have forked the code I am working on and this runs fine there. My apologies for the line noise I'd better just go back into lurk mode I guess Norman _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
