Fair enough.
Cheers,
Vic
fmg wrote in Wed Jan 30, 2013 10:46 pm:Skydome scattering now is way better. Close to perfect. Disadvantages are the sometimes unnatural sharp horizon edge, the loss in frame rate and that the water shader don't work. If you have precipitation in the dark this is displayed bright white an looks improper. Nice if the brightness could be adjusted according to the global one. But this would be a long term goal?
fmg wrote in Wed Jan 30, 2013 10:46 pm:1. All numeric-pad keys don't work except enter. This was fixed first time in FG 2.0.0. The bug reappeared with FG 2.6 RC1 and was fixed in the final 2.6 release. Then it come up again with FG 2.8.1.
fmg wrote in Wed Jan 30, 2013 10:46 pm:2. If you resize the FG window after startup FG remains in the previous size and the rest is filled with graphic jam. This came up with FG 2.6 RC1 and was corrected in the final 2.6 release. It won't happen if you use the command from the menu. But then the mac-menu-bar rival the program menu-bar if you go not carefully there with the mouse cursor.
fmg wrote in Wed Jan 30, 2013 10:46 pm:4. Some properties aren't saved though Save preferences on exit is activated. That are the HUD properties (Enable 3D, Transparent, Antialiased) and the Terrain texture scheme setting in the Rendering Options.
fmg wrote in Wed Jan 30, 2013 10:46 pm:5. View options button under Other dialog in the launcher don't work.
fmg wrote in Wed Jan 30, 2013 10:46 pm:6. The new Airport dialog is surely a great improvement in means of a user-friendly GUI but it takes 43 seconds on my system to load it the first time. During this time the sim is blocked. Maybe it is better for the first time to load nearer airports only. Then instead of the <100nm buttons you could have a >100nm button if like to see all. And if you know the airport code already you type it in and go there without loading the whole list? Otherwise I love it. The airport map with the parking positions displayed is great!
But if it could not be speeded up I would like to have the old Place aircraft on ground dialog back as an alternative option.
fmg wrote in Wed Jan 30, 2013 10:46 pm:8. The aircraft preview picture in the GUI-launcher looks like behind gray fog. This was introduced with FG 2.4 and stayed till now.
fmg wrote in Wed Jan 30, 2013 10:46 pm:9. I was not able to type in a path for the terrasync-scenery, nor could I choose one via a dialog by clicking one down-arrow in the scenery-download dialog window.
The new Airport dialog is surely a great improvement in means of a user-friendly GUI but it takes 43 seconds on my system to load it the first time. During this time the sim is blocked. Maybe it is better for the first time to load nearer airports only.
Hooray wrote:you'll probably want to take another look at the thread that sa7k linked to: it contains a patch that I posted, which adds two new fgcommands: profiler-start and profiler-stop - these can be used to get extremely fine-grained performance information on specific parts of FG. You can easily bind them to keyboard hotkeys, or simply use Nasal's fgcommand() to call them during instantiation of the dialog.
That should tell us exactly what's taking so long there, so that we can further optimize things.
Note, that you'll need to install Google PerfTools first: https://code.google.com/p/gperftools/?redir=1
And then apply the patch here: http://www.flightgear.org/forums/viewto ... 50#p166967
Next, open $FG_ROOT/gui/dialogs/airports.xml and add fgcommand("profiler-start"); to the beginning of the Nasal <open> block: https://gitorious.org/fg/fgdata/blobs/m ... xml#line39
Next, add fgcommand("profiler-stop"); to the end of the same block, or if that's not conclusive, to the beginning of the canvas' Nasal (load) section in $FG_ROOT/Nasal/canvas/generic-canvas-map.xml, i.e. around here: https://gitorious.org/fg/fgdata/blobs/m ... xml#line84
You may also want to use Nasal's systime() command to see how long the instantiation actually takes.
Afterwards, you can safely close FG (or run fgcommand("exit")) and inspect the file fgfs.profile created in the CWD from where you started the whole thing.
To actually process the file, use pprof: pprof --text /path/to/fgfs /path/to/fgfs.profile > profiling.results
When doing this here on a really old computer from 2006, I'm getting the following results, which illustrate that James' new SQLite-based NavDB cache is the main culprit here, not the Canvas:
- Code: Select all
47 29.6% 29.6% 47 29.6% sqlite3VdbeExec
22 13.8% 43.4% 22 13.8% __read_nocancel
8 5.0% 48.4% 8 5.0% lseek64
7 4.4% 52.8% 7 4.4% sqlite3VdbeMemRelease
4 2.5% 55.3% 4 2.5% likeFunc
4 2.5% 57.9% 4 2.5% sqlite3DbFree
4 2.5% 60.4% 4 2.5% sqlite3VdbeMemMove
3 1.9% 62.3% 3 1.9% _IO_str_pbackfail
3 1.9% 64.2% 3 1.9% fetchPayload
3 1.9% 66.0% 3 1.9% sqlite3BtreeCursorHasMoved
3 1.9% 67.9% 3 1.9% sqlite3VdbeMemGrow
3 1.9% 69.8% 3 1.9% sqlite3VdbeRealValue
2 1.3% 71.1% 2 1.3% 0063154b
2 1.3% 72.3% 2 1.3% btreeParseCellPtr
2 1.3% 73.6% 2 1.3% memcpy
2 1.3% 74.8% 2 1.3% pcache1Fetch
2 1.3% 76.1% 2 1.3% sqlite3BtreeDataFetch
2 1.3% 77.4% 2 1.3% sqlite3BtreeDataSize
2 1.3% 78.6% 2 1.3% sqlite3ValueText
2 1.3% 79.9% 2 1.3% sqlite3VdbeMemNulTerminate
2 1.3% 81.1% 2 1.3% sqlite3VdbeSerialTypeLen
2 1.3% 82.4% 2 1.3% sqlite3_mutex_leave
2 1.3% 83.6% 2 1.3% sqlite3_value_text
Regarding the intepretation of these columns, see: http://google-perftools.googlecode.com/ ... ofile.html
- Number of profiling samples in this function
- Percentage of profiling samples in this function
- Percentage of profiling samples in the functions printed so far
- Number of profiling samples in this function and its callees
- Percentage of profiling samples in this function and its callees
- Function name
Note that this seems like a known issue according to: https://code.google.com/p/flightgear-bu ... ?id=894#c5
I'd suggest to also post your info there.
Please share your results with us.
When you do post your findings here, please also post your system/hardware specs and any console warnings or errors you may see while using the airports.xml dialog.
HTH
Thanks
zakalawe wrote in Wed Jan 30, 2013 11:21 pm:fmg wrote in Wed Jan 30, 2013 10:46 pm:1. All numeric-pad keys don't work except enter. This was fixed first time in FG 2.0.0. The bug reappeared with FG 2.6 RC1 and was fixed in the final 2.6 release. Then it come up again with FG 2.8.1.
I am confused by this one - do you know which patch fixed it? It's obviously something in osgViewer but I've applied all his patches I can find without luck. Anyway please file a ticket in the tracker and assign to me.
zakalawe wrote in Wed Jan 30, 2013 11:21 pm:fmg wrote in Wed Jan 30, 2013 10:46 pm:2. If you resize the FG window after startup FG remains in the previous size and the rest is filled with graphic jam. This came up with FG 2.6 RC1 and was corrected in the final 2.6 release. It won't happen if you use the command from the menu. But then the mac-menu-bar rival the program menu-bar if you go not carefully there with the mouse cursor.
I don't see this one at all, very strange.
zakalawe wrote in Wed Jan 30, 2013 11:21 pm:fmg wrote in Wed Jan 30, 2013 10:46 pm:5. View options button under Other dialog in the launcher don't work.
I should probably just delete the buttons.
zakalawe wrote in Wed Jan 30, 2013 11:21 pm:fmg wrote in Wed Jan 30, 2013 10:46 pm:6. The new Airport dialog is surely a great improvement in means of a user-friendly GUI but it takes 43 seconds on my system to load it the first time. During this time the sim is blocked. Maybe it is better for the first time to load nearer airports only. Then instead of the <100nm buttons you could have a >100nm button if like to see all. And if you know the airport code already you type it in and go there without loading the whole list? Otherwise I love it. The airport map with the parking positions displayed is great!
But if it could not be speeded up I would like to have the old Place aircraft on ground dialog back as an alternative option.
I thought I'd fixed the delay, does it happen very launch for you? Anyway please file a bug, assign to me, and report any details that make it happen.
zakalawe wrote in Wed Jan 30, 2013 11:21 pm:fmg wrote in Wed Jan 30, 2013 10:46 pm:8. The aircraft preview picture in the GUI-launcher looks like behind gray fog. This was introduced with FG 2.4 and stayed till now.
Another launch feature I'll probably just remove, I don't have time to maintain it
zakalawe wrote in Wed Jan 30, 2013 11:21 pm:fmg wrote in Wed Jan 30, 2013 10:46 pm:9. I was not able to type in a path for the terrasync-scenery, nor could I choose one via a dialog by clicking one down-arrow in the scenery-download dialog window.
You should be able to change it by setting a command line option - but it sounds like you were expecting something else?
zakalawe wrote in Wed Jan 30, 2013 11:21 pm:Thanks for the feedback, please file the major bugs in the tracker, since they may not get fixed this time around. The AOA and save-on-exit issues, you can probably fix yourself and send me a patch - they would be kind of low priority for me!
Hooray wrote in Thu Jan 31, 2013 2:33 am:If you can run fgfs inside a debugger session (i.e. the gdb equivalent on mac?), you could use CTRL + C to interrupt the process while opening the dialog and use "bt" to post a backtrace here, that would tell us what's going on.
Hooray wrote in Thu Jan 31, 2013 2:33 am:Another option would be increasing the verbosity of SQLite, but I'm not sure if that can be accomplished via environment variables or if needs an updated binary.
Users browsing this forum: No registered users and 1 guest