Re: [Flightgear-devel] ILS problem at EDDB
On 15 Feb 2010, at 01:26, Jacob Burbach wrote: > Start at EDDB and tune nav radio to ils frequency 110.70 > > fgfs: ../../../src/Instrumentation/navradio.cxx:920: double > FGNavRadio::localizerWidth(FGNavRecord*): Assertion `rwy' failed. Ack, my fault, I'll commit a fix against the crash later today. Regards, James -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] SGFile::readline
On Sun, Feb 14, 2010 at 10:47 PM, John Denker wrote:
> The following commit message should be self-explanatory:
>
> commit 224ce694fa8ba7dede0e413b81e5dd52e5e65f15
> Author: John Denker
> Date: Thu Feb 11 21:13:19 2010 -0700
>
>Problem was: readline writes out-of-bounds, corrupts memory.
>Problem was: readline seeks on files that don't support seek.
>Problem was: readline fails to detect seek errors, returns garbage.
>Problem was: readline wildly inefficient, re-reading same data
> again and again.
>
>Add utility to test for read/write bugs.
>Replace readline with a version that is more compact, more
>maintainable, more extensible, more correct, more efficient, and
>able to read from named FIFOs and other things that don't seek.
>
>
> For details (476 lines worth) see:
> http://www.av8n.com/fly/fgfs/readline.patch
>
I took a look at your patch and have a couple of comments. It's true that
readline() is pretty gross; parts of it were written by yours truly. Some of
the grossness is due to a hack which lets a file be treated as an infinitely
repeating stream of bytes, very convenient for demos at SIGGRAPH. Your patch
breaks that hack. I won't argue too strongly that the hack belongs in
SGFile, but I want to have some story for replacing it, possibly in
FGGeneric::process(), before we blow it away.
Having done something like this recently in another project, I think the
code code be more clear with some use of std::string and the STL. Here's a
sketch:
if (length == 0)
throw(...);
while (!eof_flag) {
string::size_type delimPos = _buffer.find(delim);
if (delimPos != string::npos) {
size_t bytesCopied = std::max(length - 1, delimPos - 1);
_buffer.copy(buf, bytesCopied);
buf[bytesCopied] = 0;
_buffer.erase(0, bytesCopied + 1);
return delimPos;
}
char readBuf[256];
int readRet = ::read(fp, readBuf, sizeof(readBuf));
if (readRet < 0)
throw(...);
else if (readRet == 0)
eof_flag = true;
else
_buffer.append(readBuf, readRet);
}
return 0;
>
> ==
>
> The code in sg_file.cxx appears to run parallel to code
> in other places such as sg_socket.cxx I wouldn't be
> surprised if the other places needed fixing, too ...
> but I haven't looked.
>
Tim
--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] mpserver09
Hello, mpserver09 is online again. I have switch my operating system to Debian and than I have had the bug who is fixed in fgmsv0.9.12. So please relay to it. Thanks! Daniel -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 503
Hi, > What about asking (kindly) to the real administrator of this site : > http://wiki.flightgear.org/index.php/wiki.flightgear.org:About No need for that, he already knows about the problem. Actually, he already fixed the problem! As Pete knows, all we're waiting on is a one minute job to be done by Curt: forwarding wiki.flightgear.org to the new wiki server... Cheers, Gijs _ Een netbook met Windows 7? Hier vind je alles dat je moet weten. www.windows.nl/netbook-- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] SGFile::readline
On 02/15/2010 03:19 AM, Tim Moore wrote: > Some of > the grossness is due to a hack which lets a file be treated as an infinitely > repeating stream of bytes, very convenient for demos at SIGGRAPH. Your patch > breaks that hack. I won't argue too strongly that the hack belongs in > SGFile, but I want to have some story for replacing it, possibly in > FGGeneric::process(), before we blow it away. Please try this story: mkfifo /tmp/pipe.flog sleep 100 > /tmp/pipe.flog & while true ; do cat bytes > /tmp/pipe.flog ; done & fgfs --generic=file,in,$rate,/tmp/pipe.flog,$protocol Now that readline does not do seeks, it can read named pipes (FIFOs) just fine, and this opens up all sorts of non-hackish way of solving the SIGGRAPH problem ... and a host of previously-unsolved problems as well. For example, it allows you to switch from one stream of bytes to another without restarting fgfs. Seems like a win/win to me. If this story is not good enough, please clarify the question. Hint: The sleep statement ensures that the reader (fgfs) will not see an EoF at the point where one cat of bytes ends and the next begins. -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 503
Thanks Gijs - I'll just add that Curt has been out of town and it's better to wait for his return before switching the DNS over. Simon On Mon, Feb 15, 2010 at 7:42 AM, Gijs de Rooy wrote: > Hi, > >> What about asking (kindly) to the real administrator of this site : >> http://wiki.flightgear.org/index.php/wiki.flightgear.org:About > > No need for that, he already knows about the problem. Actually, he > already fixed the problem! As Pete knows, all we're waiting on is a > one minute job to be done by Curt: forwarding wiki.flightgear.org to the > new wiki server... > > Cheers, > Gijs > > > De nieuwe Internet Explorer: sneller, eenvoudiger en veiliger dan ooit > Download nu > -- > SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW > http://p.sf.net/sfu/solaris-dev2dev > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 503
On Mon, 15 Feb 2010, Pete Morgan wrote: > Gene Buckle wrote: >> > No, but its "considered" part of "flightgear" as a "platform", no wiki > == no info. mpservers fall in same "category" almost. >> Note that it's "flightgear-bugs", not >> "anything-that-has-anything-to-do-with-flightgear-except-the-actual-simulator-bugs." >> > I could reply to that with is there not a > The wiki is not part of the simulator. Unless of course you live in some alternate universe where a resource issue on the wiki prevents FlightGear from running on your computer. > In the meantime I am perplexed why there is so much stress about an > issue which is occurring, and if its frustrating for you then please > ignore, however it is frustrating for me. > Because you set up a good tracking tool and then promptly flood it with a pile of irrelevant crap so that the people that need use actually use the tool are overwhelmed by the noise. > I dont appreciate being called a "bug troll", however with all respect I I just call 'em like I see 'em. If you don't like that, See Figure #1. > am a fan avid of FG and indeed follow the Geneb simpit site at > http://www.simpits.org/geneb/ as well. (I guess I better NOT complain > about that the mailing list which does not send me updates as its not a > "sim issue"). You know, I re-read that last sentence many, many times. It _still_ doesn't make any sense. g. -- Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. http://www.simpits.org/geneb - The Me-109F/X Project ScarletDME - The red hot Data Management Environment A Multi-Value database for the masses, not the classes. http://www.scarletdme.org - Get it _today_! -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 503
On Sun, 14 Feb 2010, Alex Perry wrote: > Pete, perhaps we need to create a separate queue for > "flightgear-usability-bugs-that-gene-doesnt-care-about". > I'll ignore the snark and point out that a wiki problem is not, under any circumstances whatsoever a "flightgear usability issue". Unless of course your particular copy of FlightGear depends on the wiki in some magical fashion that prevents it from running if the wiki is overloaded. g. -- Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. http://www.simpits.org/geneb - The Me-109F/X Project ScarletDME - The red hot Data Management Environment A Multi-Value database for the masses, not the classes. http://www.scarletdme.org - Get it _today_! -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] SGFile::readline
On Mon, Feb 15, 2010 at 2:41 PM, John Denker wrote: > On 02/15/2010 03:19 AM, Tim Moore wrote: > > > Some of > > the grossness is due to a hack which lets a file be treated as an > infinitely > > repeating stream of bytes, very convenient for demos at SIGGRAPH. Your > patch > > breaks that hack. I won't argue too strongly that the hack belongs in > > SGFile, but I want to have some story for replacing it, possibly in > > FGGeneric::process(), before we blow it away. > > Please try this story: > > mkfifo /tmp/pipe.flog > sleep 100 > /tmp/pipe.flog & > while true ; do cat bytes > /tmp/pipe.flog ; done & > fgfs --generic=file,in,$rate,/tmp/pipe.flog,$protocol > > One good hack deserves another. How do you do that on Windows? > Now that readline does not do seeks, it can read named > pipes (FIFOs) just fine, and this opens up all sorts of > non-hackish way of solving the SIGGRAPH problem ... and > a host of previously-unsolved problems as well. For > example, it allows you to switch from one stream of > bytes to another without restarting fgfs. > > Seems like a win/win to me. > > If this story is not good enough, please clarify the > question. > > It's good that you've removed the lseek from the usual path through readline. But, as I said, your patch breaks a useful command-line option. It would be no big deal to insert an lseek to the beginning of the file in your new readline; if the file descriptor doesn't support lseek, then no harm done. Or you could do something different in FGGeneric. In any case I'm not going to check in this in until that problem is addressed. If don't feel like doing that, perhaps I'll do it myself. > > > Hint: The sleep statement ensures that the reader (fgfs) > will not see an EoF at the point where one cat of bytes > ends and the next begins. > > I'd probably do without the "sleep" and write while true; do cat bytes; done >/tmp/pipe.flog & instead. Tim -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] SGFile::readline
On 02/15/2010 09:22 AM, Tim Moore wrote: >> Hint: The sleep statement ensures that the reader (fgfs) >> will not see an EoF at the point where one cat of bytes >> ends and the next begins. > I'd probably do without the "sleep" and write while true; do cat bytes; > done >/tmp/pipe.flog & instead. 1) That doesn't work at the moment (but see below!). The problem is that when the first cat completes, the reader (fgfs) gets and EoF, and that's the end of the show. > It's good that you've removed the lseek from the usual path through > readline. :-) > But, as I said, your patch breaks a useful command-line option. It > would be no big deal to insert an lseek to the beginning of the file in your > new readline; if the file descriptor doesn't support lseek, then no harm > done. 2) It would be even less of a problem to do the following the specified number of times: -- detect the EoF -- close the file -- reopen the file and start reading again. This has the advantage that it works the same as lseek for regular disk files, and works a whole lot better for FIFO files. It also removes the need for the "sleep" and simplifies scenario in item (1) above. -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] CVS:data/Input/Joysticks/SpeedLinkblack-widow.xml, NONE, 1.1
Frederic Bouvier wrote: > Le 13/02/2010 00:05, Vivian Meazza a écrit : > >> Melchior >> >> >> >>> * Vivian Meazza -- Friday 12 February 2010: >>> >>> Tell me what Vista calls it in English, and I'll add it. >>> You completely miss the point. "Microsoft-PC-Joysticktreiber" is a generic >>> name that will probably be detected by plib <1.8.6 for *all* joysticks on >>> MS Vista in German language. So why on earth should fgfs choose that >>> particular >>> "SpeedLinkblack-widow" js driver for *all* joysticks? We have a generic >>> "default" >>> js for a reason, and that one doesn't assume 6 axes and 8 buttons. The fix >>> is >>> to remove that entry. >>> >>> >>> >> Already done - but thanks for the tip anyway - I had forgotten that >> particular Vista stupidity >> >> > > FYI, I sent a patch to a Plib maintainer (if there is still one) to fix > joystick detection in plib under vista/7. fgsetup-2.0.0.exe should > detect joyticks correctly. At least it works for me under Windows 7 64-bit. > > The patch submitted is attached > > -fred > > Fred, I don't see that patch on the Plib-devel list (plib-de...@lists.sourceforge.net). It might get more notice there. Or not. -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] sub-option documentation : repeat
On 02/15/2010 09:22 AM, Tim Moore wrote: > a useful command-line option. The "repeat" sub-option would be even more useful if it were more widely known. It is not mentioned in --help --verbose and not mentioned in getstart.pdf. It would be nice if somebody would a) At least mention README.IO in getstart.pdf and also in --help --verbose. b) Also perhaps expand the discussion of --generic in getstart.pdf to include the full range of sub-options, perhaps by incorporating the relevant passage from README.IO. -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] SGFile::readline
On Mon, Feb 15, 2010 at 5:43 PM, John Denker wrote: > On 02/15/2010 09:22 AM, Tim Moore wrote: > > >> Hint: The sleep statement ensures that the reader (fgfs) > >> will not see an EoF at the point where one cat of bytes > >> ends and the next begins. > > > I'd probably do without the "sleep" and write while true; do cat bytes; > > done >/tmp/pipe.flog & instead. > > 1) That doesn't work at the moment (but see below!). > The problem is that when the first cat completes, > the reader (fgfs) gets and EoF, and that's the end > of the show. > > I believe that the way I've written it causes the redirection to apply to the whole for loop, so the file isn't closed after each "cat" command. My simple-minded tests confirm this, but perhaps I'm missing something. > > > > It's good that you've removed the lseek from the usual path through > > readline. > > :-) > > > But, as I said, your patch breaks a useful command-line option. It > > would be no big deal to insert an lseek to the beginning of the file in > your > > new readline; if the file descriptor doesn't support lseek, then no harm > > done. > > > 2) It would be even less of a problem to do the following > the specified number of times: > -- detect the EoF > -- close the file > -- reopen the file and start reading again. > > This has the advantage that it works the same as lseek > for regular disk files, and works a whole lot better > for FIFO files. > > It also removes the need for the "sleep" and simplifies > scenario in item (1) above. > > That would work too. -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Modifying OSG lib checks in FG configure.ac
On Sun, 2010-02-14 at 15:22 +0100, Erik Hofman wrote: > John Denker wrote: > > In this case it appears that adding about five lines > > of code to acinclude.m4 will remove the need for at > > least five paragraphs of documentation. It turns > > out to be quite possible to each the configuration > > system to search lib64. > > Both patches have been committed to CVS. > Hi John, Erik, Re: README.OSG ` Thank you Erik for adding the README.OSG updates to FlightGear. You might note this file was previously also 'mirrored' in SimGear, but maybe it is sufficient that it is at least in FG. Thanks. Even if I do say so myself, I think it now gives 'quality' information to the user, should they run into an OSG shared library problem. And thank you for adding the patch to FG configure.ac. Now tests/gl-info runs fine. Re: Patching acinclude.m4 Concerning the SG acinclude.m4 changes, I guess I am really misunderstanding something here ;=(( Sorry if this is true... 1. The change has been done only to SimGear acinclude.m4! Why to SimGear? Is there, was there a problem in SimGear? What is the problem being overcome in SG by this patch? I _THOUGHT_ all this discussion was about FlightGear! And the fact that, by default, cmake of OSG, installs the OSG libraries in $prefix/lib64 when in x86_64!!! SimGear is a set of static libraries only, thus NEVER needs to 'find' OSG libraries. Libraries do _NOT_ link with other 'libraries'!!! As far as I can see, NONE of the SG 'test' executables, like decode_binobj, lowtest, socktest, tcp_client, waytest, TestRenderTexture, testserial, etc... require linking with OSG libraries. SG libraries do NOT need OSG libraries... includes, yes, but libraries, no. The problem I read was when LINKING FG, specifically a FG tests program, but it would be the same when later linking fgfs itself, with OSG libraries. How can changes to SG effect this FG link failure? BUT UGH: Just did a full SG cvs update, and this acinclude.m4 patch _BREAKS_ the SG build for me! I do like the more 'informative' output though ;=)) 2. But even if we now modify FG's acinclude.m4 to correctly find OSG libraries in $prefix/lib64, then you only move the problem back to when trying to RUN gl-info, or fgfs, or any others program dependant on OSG shared libraries. So, to 'run' anything which includes these OSG shared libraries, the user must KNOW about one, or all, of :- (a) Using 'export LD_LIBRARY_PATH=...', like export LD_LIBRARY_PATH=/path/to/lib[64][:/other/paths] (b) Making and using a lib -> lib64 link, if the $prefix is unique, and does not contain a 'lib' folder (c) Using /etc/ld.so.conf and ldconfig, to setup the $prefix/lib64 in the ld cache. (d) And maybe other solutions... So yes, such a patch to FG could make the build appear 'easier', but still leaves the 'user' with a later, perhaps bigger problem to overcome ;=((. And again, these user 'options' are now enumerated in the README.OSG. 3. _ALL_ of this can be _AVOIDED_ completely if the user knows about, and uses the OSG cmake option - '-D LIB_POSTFIX=' seemingly the single root cause of ALL THIS!!! Using this puts the OSG shared libraries in the 'standard' place, namely $prefix/lib. If this option is used, then :- (a) SG will build using --with-osg=$prefix to allow it to find OSG $prefix/include. This has never been a problem, has it? (b) FG will build using --with-osg=$prefix to allow it to find _BOTH_ OSG $prefix/include _AND_ equally important, $prefix/lib (c) Executables using OSG shared libraries can be run without any special provision, if OSG installed in /usr/[local/]lib, or with a simple /etc/ld.so.conf change if otherwise, or using LD_LIBRARY_PATH for a temporary solution. All that by adding one parameter to cmake when building OSG libraries from source. Does not seem a _BIG_ thing... 4. While I too thought of, and mentioned 'fixing' the auto-make to deal with this non-standard OSG install into 'lib64', I later canceled it, due to it being only _PART_ of the problem. It does seem cmake OSG is the root cause, and I really question what should be done in FG make process to 'fix' this, other than fully explaining possible 'fixes' in README.OSG, which is now done ;=)) BUT, ok, I too 'like' the idea of improving the FG auto-make process, so added the fixes from SG to FG acinclude.m4, to give it a try... using a scenario where OSG libraries are installed in $prefix/lib64 *** IT FAILED! *** Yes, it got through the FG ./configure --with-osg=$prefix ... but the Makefiles generated FAILED to add a path for the SG, and other libraries. They _DO_ have a path for OSG 'lib64' libraries. So the main link line (truncated) for fgfs was :- g++ -DPKGLIBDIR=\"/home/geoff/fg/fg8/install/fgfs/share/FlightGear\" \ -g -O2 -I/home/geoff/fg/fg8/install/simgear -D_REENTRANT \ -L/home/geoff/fg/fg8/install/OSG282/lib64 -o fgfs bootstrap.o lib
[Flightgear-devel] Handley-Page Victor K2 case sensitivity problem
Hi there, The panel on the Victor doesn't show (on Linux) due to a case sensitivity issue. Please apply attached patch to fix it. Cheers, Vik Index: Aircraft/victor/Models/Panel.xml === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/victor/Models/Panel.xml,v retrieving revision 1.1 diff -u -r1.1 Panel.xml --- Aircraft/victor/Models/Panel.xml 15 Oct 2009 11:01:26 - 1.1 +++ Aircraft/victor/Models/Panel.xml 15 Feb 2010 21:14:39 - @@ -5,7 +5,7 @@ RPM-1 - Aircraft/Victor/Models/Instruments/rpm-1.xml + Aircraft/victor/Models/Instruments/rpm-1.xml scale @@ -26,7 +26,7 @@ RPM-2 - Aircraft/Victor/Models/Instruments/rpm-2.xml + Aircraft/victor/Models/Instruments/rpm-2.xml scale @@ -47,7 +47,7 @@ RPM-3 - Aircraft/Victor/Models/Instruments/rpm-3.xml + Aircraft/victor/Models/Instruments/rpm-3.xml scale @@ -68,7 +68,7 @@ RPM-4 - Aircraft/Victor/Models/Instruments/rpm-4.xml + Aircraft/victor/Models/Instruments/rpm-4.xml scale @@ -89,7 +89,7 @@ Temp-1 - Aircraft/Victor/Models/Instruments/jpt-1.xml + Aircraft/victor/Models/Instruments/jpt-1.xml scale @@ -110,7 +110,7 @@ Temp-2 - Aircraft/Victor/Models/Instruments/jpt-2.xml + Aircraft/victor/Models/Instruments/jpt-2.xml scale @@ -131,7 +131,7 @@ Temp-3 - Aircraft/Victor/Models/Instruments/jpt-3.xml + Aircraft/victor/Models/Instruments/jpt-3.xml scale @@ -152,7 +152,7 @@ Temp-4 - Aircraft/Victor/Models/Instruments/jpt-4.xml + Aircraft/victor/Models/Instruments/jpt-4.xml scale @@ -173,7 +173,7 @@ OilPressure-1 - Aircraft/Victor/Models/Instruments/oil-1.xml + Aircraft/victor/Models/Instruments/oil-1.xml scale @@ -194,7 +194,7 @@ OilPressure-2 - Aircraft/Victor/Models/Instruments/oil-2.xml + Aircraft/victor/Models/Instruments/oil-2.xml scale @@ -215,7 +215,7 @@ OilPressure-3 - Aircraft/Victor/Models/Instruments/oil-3.xml + Aircraft/victor/Models/Instruments/oil-3.xml scale @@ -236,7 +236,7 @@ OilPressure-4 - Aircraft/Victor/Models/Instruments/oil-4.xml + Aircraft/victor/Models/Instruments/oil-4.xml scale @@ -257,7 +257,7 @@ Left ASI - Aircraft/Victor/Models/Instruments/asi.xml + Aircraft/victor/Models/Instruments/asi.xml 0.0 -0.56 @@ -267,7 +267,7 @@ Left Alt - Aircraft/Victor/Models/Instruments/altimeter.xml + Aircraft/victor/Models/Instruments/altimeter.xml 0.0 -0.34 @@ -277,7 +277,7 @@ Left HSI - Aircraft/Victor/Models/Instruments/hsi.xml + Aircraft/victor/Models/Instruments/hsi.xml 0.0 -0.64 @@ -287,7 +287,7 @@ Left AI - Aircraft/Victor/Models/Instruments/ai.xml + Aircraft/victor/Models/Instruments/ai.xml 0.0 -0.37 @@ -297,7 +297,7 @@ Right Alt - Aircraft/Victor/Models/Instruments/altimeter.xml + Aircraft/victor/Models/Instruments/altimeter.xml 0.0 0.65 @@ -307,7 +307,7 @@ Right ASI - Aircraft/Victor/Models/Instruments/asi.xml + Aircraft/victor/Models/Instruments/asi.xml 0.0 0.43 @@ -317,7 +317,7 @@ Right HSI - Aircraft/Victor/Models/Instruments/hsi.xml + Aircraft/victor/Models/Instruments/hsi.xml 0.0 0.64 Index: Aircraft/victor/Models/victor.xml === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/victor/Models/victor.xml,v retrieving revision 1.1 diff -u -r1.1 victor.xml --- Aircraft/victor/Models/victor.xml 15 Oct 2009 11:01:42 - 1.1 +++ Aircraft/victor/Models/victor.xml 15 Feb 2010 21:14:40 - @@ -19,7 +19,7 @@ -Aircraft/Victor/Models/Panel.xml +Aircraft/victor/Models/Panel.xml 2.65 0.0 Index: Aircraft/victor/Models/victor.xml.add === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/victor/Models/victor.xml.add,v retrieving revision 1.1 diff -u -r1.1 victor.xml.add --- Aircraft/victor/Models/victor.xml.add 15 Oct 2009 11:01:43 - 1.1 +++ Aircraft/victor/Models/victor.xml.add 15 Feb 2010 21:14:40 - @@ -1,5 +1,5 @@ -Aircraft/Victor/Models/Panel.xml +Aircraft/victor/Models/Panel.xml 2.65 0.0 -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] mpserver09
hi Daniel, I see relaying is active already :) had it in my config (mpserver12) Happy flying, Rob -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Shift key stuck once pressed
Hi all, (Please let me know if it would be more appropriate to report these issues at some bug tracker or the flightgear users list) I built the latest Flightgear version out of CVS and I'm using it with the data directory straight out of CVS as well. I have found a strange problem. When I load any model and then press one of the Shift keys, it gets 'stuck'. By this I mean that devices/status/keyboard/shift indicates 'true' even after I release the key, and all the lowercase keys (v for view, h for HUD, etc) stop functioning while uppercase keys (eg. H for HUD brightness) continue to work. And only the shift key does this, all the other modifiers (Ctrl, Alt, Super) appear to work correctly. No errors are logged on the console. Any ideas how to go about debugging this? Thanks in advance. Cheers, Vik -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Modifying OSG lib checks in FG configure.ac
On 02/15/2010 11:53 AM, Geoff McLane wrote:
> Just did a full SG cvs update, and this
> acinclude.m4 patch _BREAKS_ the SG build for me!
OK. It's a bug.
Thanks for testing.
Here's the patch. Please try again.
The reason for fussing with SG first is simple: this
is where Joe User is going to get into trouble. It
doesn't matter how good the FG configuration is if
Joe cannot get to that stage. And trust me, SG
will not build if it cannot find the OpenThreads
libraries, which are bundled in with OSG these days,
and located in lib64/ by default.
A lot of stuff I do makes more sense if you look
at it from the Joe User point of view.
I will fix up the FG side of things eventually.
commit 5764d1b7da5cb25947f6ada47aa45fe6b2272cec
Author: John Denker
Date: Mon Feb 15 14:50:29 2010 -0700
Fix sneaky bug: 'mylibdir' variable getting trampled.
diff --git a/acinclude.m4 b/acinclude.m4
index 889cbf4..0059bbf 100644
--- a/acinclude.m4
+++ b/acinclude.m4
@@ -113,14 +113,14 @@ for subexdir in $subexdirs ; do
dnl On 64-bit machines, if lib64/ exists and is not identical to lib/
dnl then it should be listed here, listed ahead of lib/.
mylibdir64="${exdir}/lib64${subexdir}"
-mylibdir="${exdir}/lib${subexdir}"
+mylibdir32="${exdir}/lib${subexdir}"
if test "x86_64" = $(uname -m) \
- -a ! ${mylibdir64} -ef ${mylibdir} ; then
+ -a ! ${mylibdir64} -ef ${mylibdir32} ; then
wi_EXTRA_LDIR($mylibdir64)
fi
-wi_EXTRA_LDIR($mylibdir)
+wi_EXTRA_LDIR($mylibdir32)
progdir="${exdir}/bin${subexdir}"
wi_EXTRA_PDIR($progdir)
--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] sub-option documentation : repeat
John Denker wrote: > The "repeat" sub-option would be even more useful if > it were more widely known. It is not mentioned in > --help --verbose and not mentioned in getstart.pdf. > > It would be nice if somebody would > a) At least mention README.IO in getstart.pdf and > also in --help --verbose. > > b) Also perhaps expand the discussion of --generic > in getstart.pdf to include the full range of > sub-options, perhaps by incorporating the relevant > passage from README.IO. Hi John, I'll have to plead ignorance here - I wasn't aware of the "repeat" option, and indeed haven't used the IO subsystem in a non-trivial way for a number of years. Keeping track of all the various features in FG is quite hard these days, though checking all the README files for useful information would probably be a good idea :). Given the size of getstart.pdf and the target readership, I think a simple reference to README.IO would be the most appropriate way forward. If you'd like to submit a patch to the manual, it would be very welcome. Otherwise I'll look at it when I get the chance. -Stuart -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Shift key stuck once pressed
On Mon, Feb 15, 2010 at 10:42 PM, Viktor Radnai wrote: > > I built the latest Flightgear version out of CVS and I'm using it with > the data directory straight out of CVS as well. How about OSG? What version do you have? -- Csaba/Jester -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Shift key stuck once pressed
Hi Csaba, It's version 2.8.2-1 that comes with Debian unstable. ii libopenscenegraph-dev 2.8.2-1 3D scenegraph development files ii libopenscenegraph56 2.8.2-1 low level graphics library for openscenegrap ii openscenegraph2.8.2-1 3D scenegraph binary files ii openscenegraph-doc2.8.2-1 3D scenegraph documentation Should I try 2.9.6 instead? Cheers, Vik Csaba Halász wrote: > On Mon, Feb 15, 2010 at 10:42 PM, Viktor Radnai > wrote: >> I built the latest Flightgear version out of CVS and I'm using it with >> the data directory straight out of CVS as well. > > How about OSG? What version do you have? > -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] ILS problem at EDDB
On 15 Feb 2010, at 09:12, James Turner wrote: >> Start at EDDB and tune nav radio to ils frequency 110.70 >> >> fgfs: ../../../src/Instrumentation/navradio.cxx:920: double >> FGNavRadio::localizerWidth(FGNavRecord*): Assertion `rwy' failed. > > Ack, my fault, I'll commit a fix against the crash later today. Fixed in CVS now, thanks for the report. Regards, James -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] ILS problem at EDDB
> Fixed in CVS now, thanks for the report. And thank you for the fix. :-) cheers -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Shift key stuck once pressed
On Mon, Feb 15, 2010 at 11:37 PM, Viktor Radnai wrote: > > It's version 2.8.2-1 that comes with Debian unstable. > > Should I try 2.9.6 instead? Yes. 2.8.2 reportedly also has the [ ] key bug. -- Csaba/Jester -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 503
On Monday 15 Feb 2010, Gene Buckle wrote: > On Sun, 14 Feb 2010, Alex Perry wrote: > > Pete, perhaps we need to create a separate queue for > > "flightgear-usability-bugs-that-gene-doesnt-care-about". > > I'll ignore the snark and point out that a wiki problem is not, > under any circumstances whatsoever a "flightgear usability > issue". Unless of course your particular copy of FlightGear > depends on the wiki in some magical fashion that prevents it from > running if the wiki is overloaded. > > g. The wiki tells you how to use FG and if you can't find that out then you can't use FG. Is that not a usability issue? LeeE -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 503
On Tue, 16 Feb 2010, leee wrote: > On Monday 15 Feb 2010, Gene Buckle wrote: >> On Sun, 14 Feb 2010, Alex Perry wrote: >>> Pete, perhaps we need to create a separate queue for >>> "flightgear-usability-bugs-that-gene-doesnt-care-about". >> >> I'll ignore the snark and point out that a wiki problem is not, >> under any circumstances whatsoever a "flightgear usability >> issue". Unless of course your particular copy of FlightGear >> depends on the wiki in some magical fashion that prevents it from >> running if the wiki is overloaded. >> >> g. > > The wiki tells you how to use FG and if you can't find that out then > you can't use FG. Is that not a usability issue? > Considering the volume of information available offline, no it doesn't. Regardless, fill up the bug database with whatever cruft tickles your panties at the moment. I'm done tilting at windmills. g. -- Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. http://www.simpits.org/geneb - The Me-109F/X Project ScarletDME - The red hot Data Management Environment A Multi-Value database for the masses, not the classes. http://www.scarletdme.org - Get it _today_! -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
