Are you using scenery_center or next_scenery_center? It's been so long I don't recall all the resoning, but next_scenery_center was made available to the view manager so it can get the view position correct even when we cross a tile boundary and the offsets change.
Regards, Curt. Jim Wilson writes: > Hi David, > > Well it looks like this doesn't completely solve the problem. It was working > fine when I had some extra logging running, but now that things are sped up > again, I still see a lesser flicker. It's got something to do with how the > tile manager works and the asynchronism between the model location and viewer > location calculatations. Basically I just need to re-trace the values and > review what triggers recalc() and probably get a change in scenery.center to > do something. > > Best, > > Jim > > David Megginson <[EMAIL PROTECTED]> said: > > > Update of /var/cvs/FlightGear-0.7/FlightGear/src/Main > > In directory seneca:/tmp/cvs-serv3460/src/Main > > > > Modified Files: > > location.cxx > > Log Message: > > Patch from Jim Wilson: > > > > Fix for problem where an incorrect frame or two got slipped in while > > changing tiles. Corrections to authorship in file level comments. > > > > > _______________________________________________ > Flightgear-cvslogs mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-cvslogs -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
