There are actually two other limitations in Celestia related to stellar distances . . .
First of all, the size of the root node of the octree structure used for fast visibility processing is 15000 light years. That's an easy value to change, but the bigger problem of floating point precision comes into play . . .
Single precision floating point numbers have 23 bits in the mantissa. This is a precision of about 1 in 8,000,000. At a distance of 80,000 light years, one 'step' is 1/100 light year. Celestia does some special handling of stars closer than one light year to the camera, but outside of that range, it's all single precision arithmetic. At such great distances from the Sun, nearby stars would jump as you moved by them . . . There are several solutions to this that I'm considering. I could simply increase the range for special handling, but this has performance implications. The performance problems could be offset by increasing the special-handling range as the camera's distance from the Sun increased. This isn't very general, but it would work reasonably well with the existing database, where the star density increases toward the origin. The real long-term solution is to allow multiple star databases, each referred to a different center. This is analgous to the way that solar systems are handled now, with the coordinate system for planets 'rezeroed' to the location of central star.
--Chris
