Re: [Flightgear-devel] Screenshot improves
Ok, I agree with your comments. Thanks for the commit. Le dimanche 27 avril 2008 à 00:44 +0200, Melchior FRANZ a écrit : * Nicolas -- Tuesday 08 April 2008: After precipitation patchs, I post a new patch about screenshot management. With this patch, you can choose the directory destination for the screenshots. Committed, thanks. Example: --prop:sim/paths/screenshot-dir=/tmp I moved it into a property dir /sim/paths/, because I want to move other path specs there as well, such as fg-root, fg-home, fg-current. /sim/ is much too crowded since quite a while. I did not commit the error handling. If a user pressed F3 to save a unique situation, then an error message is not welcomed at all, only because the path was undefined or set wrongly (which should have been known from the beginning). In this case fgfs must save the screenshot elsewhere ($FG_HOME) and tell the user where. Only if that fails will it output an error message. m. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Screenshot improves
Am Sonntag 27 April 2008 schrieb Melchior FRANZ:
* Nicolas -- Tuesday 08 April 2008:
After precipitation patchs, I post a new patch about screenshot
management. With this patch, you can choose the directory destination
for the screenshots.
Committed, thanks. Example: --prop:sim/paths/screenshot-dir=/tmp
The commit creates a compile error in gui_funcs.cxx:554:
if (path.create_dir(0755)) {
...
According to sg_path.hxx 'create_dir' returns nothing (void), thus giving a
conversion to bool error. Please fix.
Thomas
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Screenshot improves
Nevermind. I overlooked the simgear patch. Next time, please put a note into the commit messages that a simgear update is required. Thomas - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Weekly CVS Changelog Summary: FlightGear source
2f585eeea02e2c79d7b1d8c4963bae2d - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Screenshot improves
* Thomas Förster -- Sunday 27 April 2008: I overlooked the simgear patch. Next time, please put a note into the commit messages that a simgear update is required. No. It's basic knowledge that fg and sg are developed in parallel. It has been that way since *years*, and I don't think we'll introduce extra rules for you. Sorry. m. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Screenshot improves
* Thomas Förster -- Sunday 27 April 2008: According to sg_path.hxx 'create_dir' returns nothing (void), thus giving a conversion to bool error. Please fix. I suggest that you update your sg instead. $ cvs log -r1.12 sg_path.hxx [...] revision 1.12 date: 2008-04-26 17:25:31 +0200; author: mfranz; state: Exp; lines: +6 -5; [...] Nicolas: let SGPath::create_dir() return success/failure (for screenshot) = m. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgrun can now reports fgfs failures
* Frederic Bouvier -- Sunday 27 April 2008: Of course, if someone knows how to do it in Linux, I will be more than happy to integrate it. In case you mean a stack-trace, there's a backtrace() function in GNU/libc. See man backtrace (includes example), or this file in the dftd repository: http://dangerdeep.cvs.sourceforge.net/dangerdeep/dangerdeep/src/faulthandler.h?view=log m. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgrun can now reports fgfs failures
Melchior FRANZ a écrit : * Frederic Bouvier -- Sunday 27 April 2008: Of course, if someone knows how to do it in Linux, I will be more than happy to integrate it. In case you mean a stack-trace, there's a backtrace() function in GNU/libc. See man backtrace (includes example), or this file in the dftd repository: http://dangerdeep.cvs.sourceforge.net/dangerdeep/dangerdeep/src/faulthandler.h?view=log I mean a process ( fgrun ) acting as a debugger and detecting failure of a monitored process ( fgfs ) and then generating a meaningful error report It looks like your link is about the failed process prints its stack trace at the time of failure right ? -Fred -- Frédéric Bouvier http://my.fotolia.com/frfoto/ Photo gallery http://fgsd.sourceforge.net/FlightGear Scenery Designer - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgrun can now reports fgfs failures
* Frederic Bouvier -- Sunday 27 April 2008: It looks like your link is about the failed process prints its stack trace at the time of failure right ? Yes. No idea if it can also be used for cases like yours. I have not the least experience with it. m. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgrun can now reports fgfs failures
On 04/27/2008 04:11 AM, Frederic Bouvier wrote: I mean a process ( fgrun ) acting as a debugger and detecting failure of a monitored process ( fgfs ) and then generating a meaningful error report If you want a process that acts as a debugger, why not use a debugger? Of course, if someone knows how to do it in Linux, I will be more than happy to integrate it. On Linux, the options include: A) The super-easy way to do it is to have fgrun invoke gdb, and then tell gdb to invoke fgfs. B) The fancy way to do it is using libgdb http://www.cs.utah.edu/dept/old/texinfo/libgdb/libgdb.html - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Screenshot improves
Let me add that for releases, there is a specific simgear version check when the flightgear configure script is run to avoid these sorts of problems (that's less helpful for MSVC developers who don't run the configure script I guess) but as Melchior said, for cvs versions, simgear and flightgear are developed in parallel. Regards, Curt. On Sun, Apr 27, 2008 at 4:50 AM, Melchior FRANZ wrote: * Thomas Förster -- Sunday 27 April 2008: I overlooked the simgear patch. Next time, please put a note into the commit messages that a simgear update is required. No. It's basic knowledge that fg and sg are developed in parallel. It has been that way since *years*, and I don't think we'll introduce extra rules for you. Sorry. m. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://baron.flightgear.org/~curt/ - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgrun can now reports fgfs failures
John Denker a écrit : On 04/27/2008 04:11 AM, Frederic Bouvier wrote: I mean a process ( fgrun ) acting as a debugger and detecting failure of a monitored process ( fgfs ) and then generating a meaningful error report If you want a process that acts as a debugger, why not use a debugger? Well, the important part of my sentense is generating a meaningful error report. It looks like Linux users are more likely able to compile from sources and start the debugger themselves. But for users that only install binary package, for the moment we have no clue about segfault and unexpected failures that may happen for various reasons. If we can provide a way to collect useful post-mortem debugging info, we will be able to fix those failure more easily. Of course, if someone knows how to do it in Linux, I will be more than happy to integrate it. On Linux, the options include: A) The super-easy way to do it is to have fgrun invoke gdb, and then tell gdb to invoke fgfs. B) The fancy way to do it is using libgdb http://www.cs.utah.edu/dept/old/texinfo/libgdb/libgdb.html Thank you for the link. Not sure how it could help us in the field of collecting data though -Fred -- Frédéric Bouvier http://my.fotolia.com/frfoto/ Photo gallery http://fgsd.sourceforge.net/FlightGear Scenery Designer - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Weekly CVS Changelog Summary: FlightGear data
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-20_00:04:13 (sydadams) /var/cvs/FlightGear-0.9/data/Aircraft/Aerostar-700/Models/Instruments/vsi-3d.xml /var/cvs/FlightGear-0.9/data/Aircraft/Aerostar-700/Models/Instruments/vsi-6.ac /var/cvs/FlightGear-0.9/data/Aircraft/Aerostar-700/Models/Liveries/Black-Gold.xml /var/cvs/FlightGear-0.9/data/Aircraft/Aerostar-700/Models/Liveries/Blue-White.xml /var/cvs/FlightGear-0.9/data/Aircraft/Aerostar-700/Models/Liveries/Green-White.xml /var/cvs/FlightGear-0.9/data/Aircraft/Aerostar-700/Models/Liveries/Red-White.xml Added more view limiters ... Changed electrical system to use lists for electrical switches and outputs ...easier to add/remove items and initialize the system =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-21_03:56:10 (vmmeazza) /var/cvs/FlightGear-0.9/data/Models/Geometry/Nimitz/Models/light-white.ac Add centreline lights =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-21_06:59:23 (jons) /var/cvs/FlightGear-0.9/data/Models/Aircraft/F-15-lowpoly.ac /var/cvs/FlightGear-0.9/data/Models/Aircraft/F-15-lowpoly.xml /var/cvs/FlightGear-0.9/data/Models/Aircraft/F-15-lowres.rgb /var/cvs/FlightGear-0.9/data/Models/Aircraft/KC-135-lowpoly.ac /var/cvs/FlightGear-0.9/data/Models/Aircraft/KC-135-lowpoly.xml /var/cvs/FlightGear-0.9/data/Models/Aircraft/KC-135-lowres.rgb Add new models =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-21_07:04:28 (jons) /var/cvs/FlightGear-0.9/data/Models/Communications/mil-antena-45m.ac Add new models =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-21_07:04:29 (jons) /var/cvs/FlightGear-0.9/data/Models/Communications/mil-antena-45m.xml /var/cvs/FlightGear-0.9/data/Models/Communications/mil-antena-61m.ac /var/cvs/FlightGear-0.9/data/Models/Communications/mil-antena-61m.xml Add new models =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-21_07:05:34 (jons) /var/cvs/FlightGear-0.9/data/Models/Industrial/GenericStorageTank10m-sand.ac /var/cvs/FlightGear-0.9/data/Models/Industrial/GenericStorageTank10m-sand.xml /var/cvs/FlightGear-0.9/data/Models/Industrial/GenericStorageTank20m-sand.ac /var/cvs/FlightGear-0.9/data/Models/Industrial/GenericStorageTank20m-sand.xml /var/cvs/FlightGear-0.9/data/Models/Industrial/GenericStorageTank30m-sand.ac /var/cvs/FlightGear-0.9/data/Models/Industrial/GenericStorageTank30m-sand.xml /var/cvs/FlightGear-0.9/data/Models/Industrial/old-shelter-sand-low.rgb /var/cvs/FlightGear-0.9/data/Models/Industrial/old-shelter-sand.ac /var/cvs/FlightGear-0.9/data/Models/Industrial/old-shelter-sand.xml Add new models =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-21_07:10:25 (jons) /var/cvs/FlightGear-0.9/data/Models/Military/coleman-tow-tractor-odrab-low-poly.ac /var/cvs/FlightGear-0.9/data/Models/Military/coleman-tow-tractor-odrab-low-poly.xml /var/cvs/FlightGear-0.9/data/Models/Military/coleman-tow-tractor-odrab-low-res.rgb /var/cvs/FlightGear-0.9/data/Models/Military/fuel-truck-lowpoly.ac /var/cvs/FlightGear-0.9/data/Models/Military/fuel-truck-lowpoly.xml /var/cvs/FlightGear-0.9/data/Models/Military/fuel-truck-medpoly.ac /var/cvs/FlightGear-0.9/data/Models/Military/fuel-truck-medpoly.xml /var/cvs/FlightGear-0.9/data/Models/Military/fuel-truck-mil-lowres.rgb Add new models =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-21_07:10:26 (jons) /var/cvs/FlightGear-0.9/data/Models/Military/fuel-truck-mil-medres.rgb /var/cvs/FlightGear-0.9/data/Models/Military/h-shaped-appt-building.ac /var/cvs/FlightGear-0.9/data/Models/Military/h-shaped-appt-building.xml /var/cvs/FlightGear-0.9/data/Models/Military/hard-top1-sand.ac /var/cvs/FlightGear-0.9/data/Models/Military/hard-top1-sand.xml /var/cvs/FlightGear-0.9/data/Models/Military/hard-top2-sand.ac /var/cvs/FlightGear-0.9/data/Models/Military/hard-top2-sand.xml /var/cvs/FlightGear-0.9/data/Models/Military/hard-top3-sand.ac /var/cvs/FlightGear-0.9/data/Models/Military/hard-top3-sand.xml /var/cvs/FlightGear-0.9/data/Models/Military/humvee-pickup-odrab-low-poly.ac /var/cvs/FlightGear-0.9/data/Models/Military/humvee-pickup-odrab-low-poly.xml /var/cvs/FlightGear-0.9/data/Models/Military/humvee-pickup-odrab-lowres.rgb Add new models =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-21_07:10:27 (jons) /var/cvs/FlightGear-0.9/data/Models/Military/mil-hangar-60x70-sand.ac /var/cvs/FlightGear-0.9/data/Models/Military/mil-hangar-60x70-sand.xml /var/cvs/FlightGear-0.9/data/Models/Military/radar-mil-1.ac /var/cvs/FlightGear-0.9/data/Models/Military/radar-mil-1.xml /var/cvs/FlightGear-0.9/data/Models/Military/red-light.rgb /var/cvs/FlightGear-0.9/data/Models/Military/textures-light-sand.rgb /var/cvs/FlightGear-0.9/data/Models/Military/us-hush-house-hangar-sand.ac /var/cvs/FlightGear-0.9/data/Models/Military/us-hush-house-hangar-sand.xml
Re: [Flightgear-devel] fgrun can now reports fgfs failures
On 04/27/2008 06:27 AM, Frederic Bouvier wrote: Well, the important part of my sentense is generating a meaningful error report. Meaningful to whom? -- If you mean to the end-user, then I'm totally confused. Please clarify what you want, and why. -- If you mean to developers, then the sort of reports that gdb can generate would seem just fine. If this is a problem, please explain. It looks like Linux users are more likely able to compile from sources and start the debugger themselves. [1] Some are, some aren't. But for users that only install binary package, for the moment we have no clue about segfault and unexpected failures that may happen for various reasons. [2] So, I gather that the point you want to emphasize is not statement [1] but rather statement [2]. The goal is to handle the case of linux users who are *not* adept at debugging. If not, please explain. The only halfway-tricky thing about integrating gdb is to use dup2() a few times so that fgrun can communicate to/from gdb without getting tangled up with fgfs tty input/output. There's no reason why the naive user needs to see the debugging info, so long as there's a way to capture it and send it to the reporting center. If we can provide a way to collect useful post-mortem debugging info, we will be able to fix those failure more easily. So tell me, why is having fgrun automagically invoke gdb not a satisfactory way to collect useful post-mortem debugging info. What features do you want that it doesn't have? - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fgrun can now reports fgfs failures
John, You are talking to a Windows programmer, so maybe things might be evident for you and less for me. The reverse could be also true. John Denker a écrit : On 04/27/2008 06:27 AM, Frederic Bouvier wrote: Well, the important part of my sentense is generating a meaningful error report. Meaningful to whom? -- If you mean to the end-user, then I'm totally confused. Please clarify what you want, and why. -- If you mean to developers, then the sort of reports that gdb can generate would seem just fine. If this is a problem, please explain. I mean meaningful for the development/support team. Something more meaningful than fgfs sucks because it crash ;-) so [2] is assumed, yes. It looks like Linux users are more likely able to compile from sources and start the debugger themselves. [1] Some are, some aren't. But for users that only install binary package, for the moment we have no clue about segfault and unexpected failures that may happen for various reasons. [2] So, I gather that the point you want to emphasize is not statement [1] but rather statement [2]. The goal is to handle the case of linux users who are *not* adept at debugging. If not, please explain. The only halfway-tricky thing about integrating gdb is to use dup2() a few times so that fgrun can communicate to/from gdb without getting tangled up with fgfs tty input/output. There's no reason why the naive user needs to see the debugging info, so long as there's a way to capture it and send it to the reporting center. absolutely. If we can provide a way to collect useful post-mortem debugging info, we will be able to fix those failure more easily. So tell me, why is having fgrun automagically invoke gdb not a satisfactory way to collect useful post-mortem debugging info. What features do you want that it doesn't have I don't have any problem with practical solution ;-) If someone can contribute something, no problem. -Fred -- Frédéric Bouvier http://my.fotolia.com/frfoto/ Photo gallery http://fgsd.sourceforge.net/FlightGear Scenery Designer - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] GUI error
Melchior FRANZ wrote: * Syd -- Sunday 27 April 2008: #sgVec3Slider.cxx sgVec3Slider.hxx \ [...] my question is , is the sgVec3Slider line supposed to be removed or uncommented ? Was meant to be commented out. Now it's removed along with the files. Sorry for the inconvenience. (Didn't notice because I use a different build system. :-) m. Ok , it compiled without errors when I removed it :) Thanks Syd - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Spiele Bild promotes FlightGear
On Saturday 26 April 2008 21:08:15 Georg Vollnhals wrote: Sorry for that - my new O/S OpenSUSE 10.3 has some difficulties with my hardware-clock - at least using Wine changes the time and day and I have to correct that manually. And a time-jump would be nicer backwards regarding my age :-) I have two servers at work with similar time problems. They vanished when I switched clocksource from tsc to hpet (echo hpet /sys/devices/system/clocksource/clocksource0/current_clocksource). Persistent by addint the clock=hpet parameter to the kernel command line. Maybe the same works for you. Regards, Stefan signature.asc Description: This is a digitally signed message part. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Spiele Bild promotes FlightGear
Stefan Seifert schrieb: On Saturday 26 April 2008 21:08:15 Georg Vollnhals wrote: Sorry for that - my new O/S OpenSUSE 10.3 has some difficulties with my hardware-clock - at least using Wine changes the time and day and I have to correct that manually. And a time-jump would be nicer backwards regarding my age :-) I have two servers at work with similar time problems. They vanished when I switched clocksource from tsc to hpet (echo hpet /sys/devices/system/clocksource/clocksource0/current_clocksource). Persistent by addint the clock=hpet parameter to the kernel command line. Maybe the same works for you. Regards, Stefan - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel Thank you Stefan, for the hint :-) I'll try it. It is strange, with OpenSUSE 10.2 it never occured. Have a nice week Georg - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Stefan clock=hpet - was: Spiele Bild promotes FlightGear
Stefan Seifert schrieb: On Saturday 26 April 2008 21:08:15 Georg Vollnhals wrote: Sorry for that - my new O/S OpenSUSE 10.3 has some difficulties with my hardware-clock - at least using Wine changes the time and day and I have to correct that manually. And a time-jump would be nicer backwards regarding my age :-) I have two servers at work with similar time problems. They vanished when I switched clocksource from tsc to hpet (echo hpet /sys/devices/system/clocksource/clocksource0/current_clocksource). Persistent by addint the clock=hpet parameter to the kernel command line. Maybe the same works for you. Regards, Stefan Hi Stefan, this was hard for me .. as a Linux amateur :-/ Although there are so different Linux systems, maybe you can have a look at what I did and give me a feedback - if possible: I googled a lot and found out to put this kernel command line parameter into the GRUB config. Although I am not sure the clock parameter is allowed (I did not find it in a list of these) I first entered it manually when GRUB started and - as the boot-process seemed to work normal I added it to the Grub config file (/boot/grub/menu.lst). This is not named Grub.cfg anymore for my O/S but menu.lst is the right one, I think. I added it to the following lines within menu.lst: default 0 timeout 8 clock=hpet gfxmenu (hd2,0)/boot/message ... At least there seems no negative result when booting. Is that the right way to proceed? Thank you very much in advance for your help Georg - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Stefan clock=hpet - was: Spiele Bild promotes FlightGear
On Sunday 27 April 2008 23:53:01 Georg Vollnhals wrote: default 0 timeout 8 clock=hpet This is wrong. The kernel parameters are following the file name in the kernel line. This is the section I boot on my server: ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 10.3 - 2.6.22.17-0.1 root (hd0,1) kernel /vmlinuz-2.6.22.17-0.1-default root=/dev/system/root resume=/dev/sda1 splash=silent clock=hpet showopts initrd /initrd-2.6.22.17-0.1-default You can check if the parameter does what it should by issuing: cat /sys/devices/system/clocksource/clocksource0/current_clocksource on the command line. If it worked, it should output: hpet If not, it probably reads tsc. Then you'll just have to wait and see if your clock works better. It did for me. And yes, openSUSE 10.2 didn't have that problem on the same server. Hope this helps :) Stefan signature.asc Description: This is a digitally signed message part. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Weekly CVS Changelog Summary: SimGear
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-23_13:13:50 (timoore) /var/cvs/SimGear-0.3/source/projects/VC7.1/SimGear.vcproj Rewrite livery texture replacement to copy StateSet objects Also, add a NodeAndDrawableVisitor that descends into osg::Drawable. That motivation for this is that it's a bad idea to modify state sets that the osgDB::SharedStateManager might be keeping. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-23_13:13:51 (timoore) /var/cvs/SimGear-0.3/source/simgear/scene/model/ModelRegistry.cxx /var/cvs/SimGear-0.3/source/simgear/scene/util/NodeAndDrawableVisitor.cxx /var/cvs/SimGear-0.3/source/simgear/scene/util/NodeAndDrawableVisitor.hxx Rewrite livery texture replacement to copy StateSet objects Also, add a NodeAndDrawableVisitor that descends into osg::Drawable. That motivation for this is that it's a bad idea to modify state sets that the osgDB::SharedStateManager might be keeping. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-23_17:09:23 (fredb) /var/cvs/SimGear-0.3/source/projects/VC7.1/SimGear.vcproj Update MSVC 7.1 projects =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-24_17:06:06 (timoore) /var/cvs/SimGear-0.3/source/simgear/scene/model/ModelRegistry.cxx /var/cvs/SimGear-0.3/source/simgear/scene/model/ModelRegistry.hxx /var/cvs/SimGear-0.3/source/simgear/scene/util/NodeAndDrawableVisitor.hxx Fix new livery code It turns out that the database pager causes the texture image to be unloaded after it is applied, so the image and its file name may not be available for doing the livery substitution. Ask a work around we set the name of the texture to its file name. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 2008-04-25_03:41:29 (mfranz) /var/cvs/SimGear-0.3/source/simgear/scene/model/SGPagedLOD.cxx Till BUSCH: tim recently noticed the database pager was repeatedly loading and unloading the same objects. he also tracked down the problem to missing bounding sphere information in osgDB::PagedLOD. this is a simplicistic approach to fix this: SGPagedLOD will now remember whatever value it sees for getBound() after loading a child. this patch will make database pager run much calmer. 2f585eeea02e2c79d7b1d8c4963bae2d - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
