Jon Stockill wrote:
It doesn't seem to be displaying it that's the problem - it's getting
terragear to build it. Once you reach a certain polygon density things
start to break down, there's obviously a lot more polygons, but the
road polys just don't seem to show up, and there's a big increase in
the number of polygons that seem to have problems with their texture
coordinates. The resulting scenery was still just about usable on a
GeForce2 MX 400.
As an idea of the processing involved, as I'm sure you're aware by
default the terragear tile builder has a cpu limit of 120s set -
you're not going to get anything at all built with those limits using
this amount of data - it takes anything between 45 minutes and 75
minutes on a 1GHz Athlon with 768MB of RAM.
Jon,
I'd be interested in working with the Tiger data as well. Did you
create any code to parse/chop the data?
If I had a chance to work through the process I might be able to track
down some of these problems/issues.
Regards,
Curt.
--
Curtis Olson http://www.flightgear.org/~curt
HumanFIRST Program http://www.humanfirst.umn.edu/
FlightGear Project http://www.flightgear.org
Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel