Menu
▾
▴
1 Attachments
#162 Scenery and tile manager issues with view distance
Originally created by: kanto... (code.google.com)@gmail.com
Originally owned by: bre... (code.google.com)@gmail.com
What steps will reproduce the problem?
1. add start option --visibility-miles=??
2. add start option --disable-real-weather-fetch
3. start flightgear
What is the expected output? What do you see instead?
In tilemgr.cxx I expect to see
double vis = _visibilityMeters->getDoubleValue();
initialised corectly with "/environment/visibility-m"
This property tree node does not seem to be initialised properly at start when above options are present.
As a result the tile cache is initialised with a wrong size and weird things can sometimes happen.
What version of the product are you using? On what operating system and
what graphics card?
Latest GIT version on Debian Linux stable, Nvidia card.
Please provide any additional information below.
Attached potential patch for options.cxx
Related
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
The patch looks good to me. I'll be adding this to my branch with tile manager improvements, since it's also good for testing the new tile loading.
However, we shouldn't add this to the main branch immediately, since this version still waits for _all_ initial scenery to be loaded before the splash screen is dropped. Maybe this was the reason why the initial visibility wasn't updated early so far, since FG would appear to be loading _extremely_ slowly otherwise (loading all tiles for 50m visibility takes my system several minutes...).
With the new loading strategy FG will no longer wait for all initial tiles to be loaded before starting, so this patch should be fine.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
There is another, more general problem triggering the issue here. When visibility increases (weather change), more tiles may need to be loaded. But when the plane remains idle at one position, nothing is scheduled. Currently tiles are only scheduled when the plane moves into a new "bucket". This also partly caused the problem here (command-line visibility was set "too late"). I'll also add a fix for this, so tiles may be rescheduled when visibility increased above a threshold...
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: kanto... (code.google.com)@gmail.com
Thanks for looking into this issue :)
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Owner: brehmt
Status: Dev
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
Fix is in GIT now. Please test if this works for you.
Labels: Scenery Weather
Status: Fixed
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Status: Temp
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Status: Fixed
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Labels: Milestone-2.4.0