Jim Wilson writes: > >Norman Vine <[EMAIL PROTECTED]> said: > >> Andy Ross writes: >> > >> > Just adding an offset to the camera is what's already being >> >done, and it runs into precision problems. The trick is to make sure >> >that the camera is *never* moved to the scenery centroid before >> >rendering the model. >> >> Right --- >> So why not leave the camera at 0,0,0 and add an additional offset >> to the 'tile-offset' >> > >When I first saw this suggestion what came to mind was using camera at 0,0,0. > Applying the offset (difference between our current "view position" and the >scenery center) to the scenery. And applying the difference between our "view >position" and the model origin (aircraft position) to the model. But I guess >I'm a little confused on how this would be done. Would we apply the same >rotation matrix with an adjusted translation vector?
Yes, but this is the easy part :-) Not really sure yet how to get the Terrain Intersection routines working with an 'offset' from the tile_center, and the since the scenery tiling is NECESSARY due to 'precision issues', we can'y adbandon it. I know it should just be another translation but I can't seem to get it working right < thinking publically > Since the scenery tiles are in are in a tile-relative coordinate space we should just have to add vdiff = ( scenery_center - abs_view_pos ) to the scenery_center in the ssg_prep_tile() call and subtract vdiff from the scenery_center in the scenery intersection routines < / > Norman _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
