C-like in many ways. Probably the biggest barrier for most people is
going to be getting their development system setup properly so they can
compile their new code additions or changes.
I sort of disagree here. Setting up a development system is not a big deal
(even I managed to do it, so
* Torsten Dreyer -- Thursday 25 October 2007:
To make things easier for developers, can we think of a plug-in
system for callbacks so a potential developer write a library
that is linked in dynamically by the flightgear core?
No.
That would mean to add and maintain plug-in loader code for all
Sent: 25 October 2007 14:10
To: flightgear-devel@lists.sourceforge.net
Subject: Re: [Flightgear-devel] FlightGear/Plib periodic stutter notes
* Torsten Dreyer -- Thursday 25 October 2007:
To make things easier for developers, can we think of a
plug-in system
for callbacks so a
Would it be possible to change the default position for the j3cub to
sitting in the front seat instead of the back seat? That would make
the instruments (especially the compass) actually readable. Maybe have
a second -set file for back seat drivers?
--
Hans Fugal
Why not ad a second view, from where you can fly the
aircraft? Better than two -set.xml-files...
HHS
--- Hans Fugal [EMAIL PROTECTED] schrieb:
Would it be possible to change the default position
for the j3cub to
sitting in the front seat instead of the back seat?
That would make
the
Ah, I didn't realize you started there for weight/balance reasons. I
thought it was just someone's preference. Definitely don't change it
then. That mouse trick is nice.
I wonder if it is really that hard to see the compass in the real
plane. Maybe so, but combined with the small size and the
On 25/10/2007, Hans Fugal [EMAIL PROTECTED] wrote:
I wonder if it is really that hard to see the compass in the real
plane. Maybe so, but combined with the small size and the various
reasons why it's hard to make out the magnetic compass in FG even at
regular size I have to think maybe it's
I just tried this (plib version) and get this error
Nasal runtime error: No such member: getValue
at ./fgd/Nasal/view.nas, line 95
called from: /input/keyboard/key[86]/binding, line 1
And a useless view. Replacing the original view (without n=100) works fine.
On 10/24/07, Jon Stockill
Since I came back to FlightGear a few weeks ago, I've flown the J3 Cub
mainly with the mouse (for short breaks from work), so I hadn't
noticed how badly out of trim the plane has been flying. I've just
checked in changes to fix the (non-adjustable) rudder and aileron trim
to get rid of the strong
Thanks! You mention the nonadjustable rudder and aileron trim - is
that nonadjustable in theory only or does flightgear also enforce
this? If not, can it be made to? It wasn't clear from the j3cub.xml
file.
On 10/25/07, David Megginson [EMAIL PROTECTED] wrote:
Since I came back to FlightGear a
On 25/10/2007, Hans Fugal [EMAIL PROTECTED] wrote:
Thanks! You mention the nonadjustable rudder and aileron trim - is
that nonadjustable in theory only or does flightgear also enforce
this? If not, can it be made to? It wasn't clear from the j3cub.xml
file.
You can adjust it in flight if you
Hello,
Me, Aeortro and maybe some ohthers noticed a problem
with fgfs.
With the builts from 10/24/2007 and 10/05/2007 in both
branches OSG and plib FGFS shut down while intializing
subsystems. There are no error messages in the shell
and no on the win32 eventmanager...
Does anyone else have
Hi Heiko
On Thursday 25 October 2007 20:20, Heiko Schulz wrote:
Hello,
Me, Aeortro and maybe some ohthers noticed a problem
with fgfs.
With the builts from 10/24/2007 and 10/05/2007 in both
branches OSG and plib FGFS shut down while intializing
subsystems. There are no error messages in
Hi Durk,
Yes, I used the windows version. I checked the data -
always matching. I checked this first.
On the version 10/05/2007 it was like an old car -
sometimes it started, sometimes not or after several
trying.
Note, that is was even mentioned on a fedora system:
Hi Durk,
Yes, I used the windows version. I checked the data -
always matching. I checked this first.
On the version 10/05/2007 it was like an old car -
sometimes it started, sometimes not or after several
trying.
Note, that is was even mentioned on a fedora system:
* Durk Talsma -- Thursday 25 October 2007:
With the interval timing bug solved, we could consider opening up the
discussion for a new release again.
Yes, it's really *high* time. But what's with the plib release?
I would have liked to make fgfs depend on 1.8.5. This fixes a
bug with font
On Thursday 25 October 2007 19:44:54 Melchior FRANZ wrote:
Yes, it's really *high* time. But what's with the plib release?
I would have liked to make fgfs depend on 1.8.5. This fixes a
bug with font colors in list widgets (property browser!) and
other stuff.
Wouldn't it be a bit excessive to
* AJ MacLeod -- Thursday 25 October 2007:
Wouldn't it be a bit excessive to make fgfs DEPEND on 1.8.5,
No. It's statically linked, and 99 percent of the users use
compiled binaries (number made up). The 1 percent can be
asked to download the latest stable release. The broken
version 1.8.4 makes
On Thursday 25 October 2007 20:44, Melchior FRANZ wrote:
* Durk Talsma -- Thursday 25 October 2007:
With the interval timing bug solved, we could consider opening up the
discussion for a new release again.
Yes, it's really *high* time. But what's with the plib release?
I would have liked
* Durk Talsma -- Thursday 25 October 2007:
Probably the best course of action is to send a friendly reminder
to the plib list, and if it doesn't happen again, stick to plan B.
Yes, but I won't do that. I did it on 2007/04/02, and the question
remained unanswered. The last posting before that
On 10/25/07, David Megginson [EMAIL PROTECTED] wrote:
On 25/10/2007, Hans Fugal [EMAIL PROTECTED] wrote:
Thanks! You mention the nonadjustable rudder and aileron trim - is
that nonadjustable in theory only or does flightgear also enforce
this? If not, can it be made to? It wasn't clear
Heiko Schulz
Sent: 25 October 2007 19:21
To: FGFS Developers Mail List
Subject: [Flightgear-devel] Unknown failure while
Initializing subsystems onwin32 and Fedora 7 x86_64
Hello,
Me, Aeortro and maybe some ohthers noticed a problem
with fgfs.
With the builts from 10/24/2007 and
On 25/10/2007, Hans Fugal [EMAIL PROTECTED] wrote:
You can adjust it in flight if you bind some keys to the trim
properties, but it would be pretty unrealistic -- I doubt that any J3
Cub has ever had rudder or aileron trim.
Or have a joystick.
Actually, the J3 does use a stick instead of
On 10/25/07, Vivian Meazza [EMAIL PROTECTED] wrote:
Heiko Schulz
Sent: 25 October 2007 19:21
To: FGFS Developers Mail List
Subject: [Flightgear-devel] Unknown failure while
Initializing subsystems onwin32 and Fedora 7 x86_64
Hello,
Me, Aeortro and maybe some ohthers noticed a
Hi,
I'm not sure but I'm think the problem is maybe in
WinCVS. Today I noticed that the CH47 was not quite
uploaded. The ac.model was missing though Syd had
uploaded 3h before
Maybe I have to try the TortoiseCVS...
HHS
--- Thomas [EMAIL PROTECTED] schrieb:
On 10/25/07, Vivian Meazza
On Tuesday 23 October 2007 11:57, Tobias Nielsen wrote:
Okay, here is one gigantic file dump...
Be awere that i have added a few extra lines of debug since i wanted
to try to locate the problem. But i assume that you will be able to
see your way out of it..
On Friday 26 October 2007 00:01, Heiko Schulz wrote:
Hi,
I'm not sure but I'm think the problem is maybe in
WinCVS. Today I noticed that the CH47 was not quite
uploaded. The ac.model was missing though Syd had
uploaded 3h before
Maybe I have to try the TortoiseCVS...
Could be well
27 matches
Mail list logo
