These days, I compile FlightGear 1.9 source code with MSVC2005, I found the
project files
in folder "projects\VC8" have some bugs. Some source file are not included into
project files,
and some old source link files are not be removed. So if use these project
files to complie FlightGear 1.9
wil
On Sat, 2009-01-10 at 00:33 +0100, Csaba Halász wrote:
> On Sat, Jan 10, 2009 at 12:10 AM, Alasdair Campbell
> wrote:
> > I find that I am unable to load any file (fails the
> > sanity check in data/nasal/io.nas (even as root)) The enclosed temporary
> > patch, removing the check resolves the pr
On Sat, Jan 10, 2009 at 12:10 AM, Alasdair Campbell
wrote:
> I find that I am unable to load any file (fails the
> sanity check in data/nasal/io.nas (even as root)) The enclosed temporary
> patch, removing the check resolves the problem for me.
Rather than removing the security check, you might c
Alasdair Campbell a écrit :
> In eager anticipation of James Turners' proposed improvements to the
> Route Manager/GPS code, I have been playing around some and noted that
> that the route manager dialog contains a "Load List" option. If I try to
> use this option, I find that I am unable to load a
On Fri, Jan 9, 2009 at 11:46 PM, John Denker wrote:
>
> Is there any reason why simgear/io/sg_socket.cxx could not return
> a more informative error message, one that included sys_errlist[errno]?
Yeah. The reason is, this code is in plib and that doesn't provide a
portable way to get the error me
In eager anticipation of James Turners' proposed improvements to the
Route Manager/GPS code, I have been playing around some and noted that
that the route manager dialog contains a "Load List" option. If I try to
use this option, I find that I am unable to load any file (fails the
sanity check in d
On 01/09/2009 02:53 PM, Csaba Halász wrote:
> This usually means that port 5500 is already in use.
Is there any reason why simgear/io/sg_socket.cxx could not return
a more informative error message, one that included sys_errlist[errno]?
That would be better for users. They wouldn't have to gues
On Fri, Jan 9, 2009 at 3:53 PM, Csaba Halász wrote:
> On Fri, Jan 9, 2009 at 6:30 PM, John Miller wrote:
> >
> >--generic=socket,in,10,,5500,udp,FGWriter1
> >--fdm=null
> >
> > Every time I run the programs with these parameters, FG crashes and I get
> > back the following messages from th
On Fri, Jan 9, 2009 at 6:30 PM, John Miller wrote:
>
>--generic=socket,in,10,,5500,udp,FGWriter1
>--fdm=null
>
> Every time I run the programs with these parameters, FG crashes and I get
> back the following messages from the log
>Error: bind() failed in make_server_socket()
This usua
Tim Moore wrote:
> Can we all live with a default near plane value of .25?
I don't think so, the C172 cockpit frame looks quite strange with 0.25,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--
On Fri, 9 Jan 2009, Tim Moore wrote:
> Can we all live with a default near plane value of .25? I'll check that
> in tonight. In the meantime, you can set the property on the command
> line.
No, 0.25 is too much for my Submarine Scout (and most likely for the
bubble sextant instrument too, thou
Hello,
I am working to make FlightGear communicate the LabView on a OS X platform.
I have the
Currently, I have succeeded in getting FG to send anything I want to
LabView, using FG protocols and udp reciever I built in LabView. This is the
command-line segment I have been using to send data from
On vendredi 09 janvier 2009, Tim Moore wrote:
> Frederic Bouvier wrote:
> > - "gerard robin" a écrit :
> >> On vendredi 09 janvier 2009, Torsten Dreyer wrote:
> Hello,
>
> What happen now with the Cockpit view
> Getting now the cockpit cutted
> >>>
> >>> That's the near clip
Frederic Bouvier wrote:
> - "gerard robin" a écrit :
>
>> On vendredi 09 janvier 2009, Torsten Dreyer wrote:
Hello,
What happen now with the Cockpit view
Getting now the cockpit cutted
>>> That's the near clipping pane,
>>> you might want to add
>>>
>>>
>>>
>
- "gerard robin" a écrit :
> On vendredi 09 janvier 2009, Torsten Dreyer wrote:
> > > Hello,
> > >
> > > What happen now with the Cockpit view
> > > Getting now the cockpit cutted
> >
> > That's the near clipping pane,
> > you might want to add
> >
> >
> >
> > 0.1
> >
Brian Schack wrote:
> I've noticed that with AI traffic turned on, there is a constant
> setting and resetting of the time accessed by
> globals->get_time_params()
This sounds like a misplaced leading slash in a property for AI models
to me.
Erik
--
On vendredi 09 janvier 2009, gerard robin wrote:
> On vendredi 09 janvier 2009, Torsten Dreyer wrote:
> >
> > That's the near clipping pane,
> > you might want to add
> >
> >
> >
> > 0.1
> >
> >
> >
> >
> > in your model-set.xml
> >
> > Torsten
> >
> >
> > To
Hi,
On Jan 9, 2009, at 11:38 PM, Torsten Dreyer wrote:
>> Hello,
>>
>> What happen now with the Cockpit view
>> Getting now the cockpit cutted
> That's the near clipping pane,
> you might want to add
>
>
>
>0.1
>
>
>
>
> in your model-set.xml
It works on fg/cvs,
On vendredi 09 janvier 2009, Torsten Dreyer wrote:
> > Hello,
> >
> > What happen now with the Cockpit view
> > Getting now the cockpit cutted
>
> That's the near clipping pane,
> you might want to add
>
>
>
> 0.1
>
>
>
>
> in your model-set.xml
>
> Torsten
>
>
> "Ron" == Ron Jensen writes:
>> 81:: Consider the case where FlightGear is run with the
>> --disable-ai-models command line option.
>>
>> It appears that some of the ai-related code continues to
>> run. You can easily verify by turning on log-level=info, in
>> which
> Hello,
>
> What happen now with the Cockpit view
> Getting now the cockpit cutted
That's the near clipping pane,
you might want to add
0.1
in your model-set.xml
Torsten
>
> In addition to it , i have never seen, clouds so well displayed in
> reality, look
gerard robin wrote:
> Hello,
>
> What happen now with the Cockpit view
> Getting now the cockpit cutted
>
> Here two snapshots:
>
> the first one is done with an older fg CVS version ( 17-12-2008) still
> running on my system
> http://pagesperso-orange.fr/GRTux/Before-was-right.jpg
>
> the secon
Hello,
What happen now with the Cockpit view
Getting now the cockpit cutted
Here two snapshots:
the first one is done with an older fg CVS version ( 17-12-2008) still
running on my system
http://pagesperso-orange.fr/GRTux/Before-was-right.jpg
the second one done with the last CVS version (
On vendredi 09 janvier 2009, James Turner wrote:
> On 9 Jan 2009, at 13:18, gerard robin wrote:
> > get same kind of crash here with gdb:
> >
> > [Thread debugging using libthread_db enabled]
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x0088c7c9 in
> > FGAirport::getIt
On 9 Jan 2009, at 13:18, gerard robin wrote:
> get same kind of crash here with gdb:
>
> [Thread debugging using libthread_db enabled]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0088c7c9 in
> FGAirport::getIteratorForRunwayIdent(std::string const&)
> const ()
> Current
> On 9 Jan 2009, at 11:17, James Turner wrote:
> > If anyone else is seeing this (or isn't, with a clean, up-to-date
> > tree), that'd be very helpful information, since I'm not.
>
> Never mind, I can reproduce this locally on my (Vmware) ubuntu, so
> it's something Linux-y, not a build issue.
>
>
On vendredi 09 janvier 2009, James Turner wrote:
> On 9 Jan 2009, at 11:17, James Turner wrote:
> > If anyone else is seeing this (or isn't, with a clean, up-to-date
> > tree), that'd be very helpful information, since I'm not.
>
> Never mind, I can reproduce this locally on my (Vmware) ubuntu, so
> It's not clear to me if this as a clean build (in the code sense) -
> you say fresh autogen.sh and configure, but that doesn't necessarily
> imply existing object files get rebuilt (or does it?)
Oh sorry - forgot to mention that I also executed "make clean"
>
> If anyone else is seeing this (or
On 9 Jan 2009, at 11:17, James Turner wrote:
> If anyone else is seeing this (or isn't, with a clean, up-to-date
> tree), that'd be very helpful information, since I'm not.
Never mind, I can reproduce this locally on my (Vmware) ubuntu, so
it's something Linux-y, not a build issue.
Will commi
> If anyone else is seeing this (or isn't, with a clean, up-to-date
> tree), that'd be very helpful information, since I'm not.
I did some digging with the following result:
The code crashes when calling apt->getRunwayByIdent for airport OAKB and
runway 29 for the OAKB 29 CAT II ILS.
With some d
One more trace,
with log-level=debug, the last thing I see is:
Splash screen progress reading aircraft list
Splash screen progress reading airport & navigation data
Loading Airport Database ...
Data file version = 810
End of file reached
[FINISHED LOADING]
Loading Navaid Databases
localizer:IITL,
On vendredi 09 janvier 2009, Craig Benbow wrote:
> gerard robin wrote:
> > On vendredi 09 janvier 2009, gerard robin wrote:
> >> Hello,
> >>
> >> Arrgh, i never had any problem with OpenAl before , coming back to the
> >> computer i am trying to build FG CVS , i get the following error with
> >>
* KOCH Mate -- Thursday 08 January 2009:
> - I can't completely disable the scrollbar (even if I set the width of
> it to zero, the scrollbar is still visible, and it is also without any
> text in the box)
PLIB only hides the scrollbar in the but not the widget
at the moment. This will probably
On 9 Jan 2009, at 10:42, Torsten Dreyer wrote:
> with cvs as of today, I receive a segfault shortly after starting
> fgfs;
> No command line args, no .fgfsrc, no .fgfs directory, standard
> preferences.xml
> fresh autogen.sh and configure
Almost certainly my fault - do you known when you las
Hi,
with cvs as of today, I receive a segfault shortly after starting fgfs;
No command line args, no .fgfsrc, no .fgfs directory, standard preferences.xml
fresh autogen.sh and configure
Here is a backtrace
Program received signal SIGSEGV, Segmentation fault.
FGAirport::getIteratorForRunwayIdent
> In that distrib/installation (OpenSUSE 11.1 64bit)
> openal , openal-32bit , openal-devel, freealut, freealut-devel
> are installed correctly.
>
> Is there anything new within FG that i have missed ?
Building FlightGear on my suse x86_64-11.1 is no sweat - maybe config.log has
a hint what's wro
36 matches
Mail list logo
