Comments:
GE 4.xx clients send incorrect <lookatRange> values when terrain height is
above sea level
older forum post the last time I messed with this. Note that the links in this
post are no longer active.
Relevant Application(s):
All clients since 3.xx
Steps to Reproduce:
1) Open GE and type in zip 80203, fly to Denver with terrain NOT checked
2) Open Barry Hunter's View Based Network Link Echo double click and you will
see an eye alt of 1km and <lookatRange>=1000. This is correct.
3) Check terrain, click network link twice. Eye alt will be 2.62 km (1617m
terrain height + 1000m range). The <lookatRange> value now equals 2617. This is
the bug, range should still be 1000m
Supporting Files:
PHP is not enabled in the file section. Use link in step 2.
Reported By: crispyjones
Original issue reported on code.google.com by api.roman.public@gmail.com on 14 Aug 2008 at 10:44
Original issue reported on code.google.com by
api.roman.public@gmail.com
on 14 Aug 2008 at 10:44