This thread started as bug report about a recent problem with dynamic view, but people used it as opportunity to throw in their favorite bugs, although those are apparently unrelated. Let's keep things separated:
Bug #1: "stutters and pauses with 1-2 sec lenght" when dynamic view is enabled (observed by Heiko in a recent build by Thomas). We don't know much about this bug, not even if it's fg/osg or fg/plib and when it started. It didn't happen when I ran fgfs last time (about two weeks ago). Bug #2: Syd added a complaint about the fg/osg *feature* that causes stutters until all scenery objects in 360 degree were loaded. This is annoying, but AFAIK not a bug. Should be resolved nevertheless, and I'm sure Mathias and Tim are aware of it and will change that at some point. (Someone on IRC has a local Nasal script that makes a 360 degree lookaround at the very beginning so that this won't disrupt the flight in the following minutes.) Bug #3: Lee threw in an old bug and repeated the long disproved myth that listeners are the cause. They are not! This bug causes fgfs to freeze for a tenth of a second in 8 seconds intervals beginning a few minutes after startup (but not always). The intervals stay the same, but the freezing time becomes longer and longer over time. This happens now since years and on my machine it can reliably be "fixed" by turning off AI traffic (the c172/pa28 aircraft). I tried to track it down but didn't invest enough time. The fact that this AI part was full of bugs just didn't make it worthwhile. (I just say "tower.cxx". :-) * leee -- 8/31/2007 3:09 AM: > I couldn't establish anything consistant about it but re-writing some of the > nasal I was using, to use less listeners, which were being called every > frame, ameliorated the situation somewhat, iirc, but wasn't an answer. > Listeners are not involved, unless you have very badly written ones on your harddisk (only). When you brought that up last time I added some logging capabilities for listeners and disproved this claim. I monitored all triggered listener code and there were none run regularly. (OK, some were, and they got fixed after that, for example those that listened to /gear/gear/wow, which is set in every frame by YASim.) Of course, if you write bad Nasal code, you can create all sorts of problems, and listeners will reliably run that buggy code. But the problem then is the bad Nasal code, and not the listeners by themselves or the number of active listeners. If you bring this up next time, please add some facts: show us the command line and the listeners that you had to comment out to "fix" the problem. m. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
