\
data/Aircraft/bf109 \
data/Aircraft/bo105 \
data/Aircraft/c172 \
data/Aircraft/c172p \
IMHO we should not include the two c310 and replace them with
1. SenecaII (great twin with lots of documentation)
2. de Havilland Beaver - Floats (shows
On Fri, Feb 17, 2012 at 2:37 PM, Stuart Buchanan wrote:
I'm currently writing a script to generate the aircraft download page
that will include ratings, so users will be able to see the ratings of
aircraft _before_ they download them.
Hopefully I'll get it finished this evening in time
and
paint myself into a corner I can't get out of.) :-)
I sense that there have been a substantial number of updates to individual
aircraft that are only going into the master branch and aren't getting
cherry picked into the 2.8.0 release branch. Perhaps this is intentional
or I'm misunderstanding
On Fri, 17 Feb 2012 19:49:34 +, Stuart wrote in message
cap3ntytjoav9wecmued6fkfczjhrpfqsodmfim3ftmtthcm...@mail.gmail.com:
On Fri, Feb 17, 2012 at 2:37 PM, Stuart Buchanan wrote:
I'm currently writing a script to generate the aircraft download
page that will include ratings, so users
-on to the base
package. Or something like that.
I'm currently writing a script to generate the aircraft download page
that will include ratings, so users will be able to see the ratings of
aircraft _before_ they download them.
Hopefully I'll get it finished this evening in time for the weekend release
/dhc2/white.png
on lines 1303, 1740, 3615, 5310 and 7174, which will cause file accesses
to drive D.
I also checked other aircraft files from git repo, and found other three
files include the path to D:/Git_New:
Aircraft/Buccaneer/Models/buccaneer.ac
Aircraft/Buccaneer/Models/flap.ac
Aircraft
files need to be modified to fix this problem:
- admin/make-aircraft-pkgs.pl
- admin/make-aircraft-html.pl
- data/Aircraft/787/787-set.xml
But I don't know which file should be modified.
I hope someone can correct this issue and comit to CVS.
One more thing that I want to request is to include ATC
Hi All,
The rating system
(http://wiki.flightgear.org/Formalizing_Aircraft_Status) has now been
in place for some time, and a number of aircraft are rated.
Additionally Fred B. has added rating information to FGRun, which is excellent.
A question for Curt - would it be possible to include
) and IAR80 (53.8 meg) all
have very big aircraft directories and are highly developed although
I don't think that any of the authors consider them to be complete
yet.Using --min- status=production should include the IAR80 in
it's list but not the p51d- jsbsim (which has a status of early
Hi all!
Calling something a major release is not just a matter of what's possible,
but also what's done.
There's a lot possible with Rembrandt, but 99% of our aircraft don't use it.
And lots of aircraft look ugly with Rembrandt
(non-translucent windows and fake shadows mostly). I just
version of FG? ;o)
Everything is here so anyone can see _how_ the
buggy ones fail, and try fix them.
So if there is a release they will be add to the
Download page, am I right?
..if somebody puts it there, yes. ;o)
I expected a far smaller number of
aircraft in developement
,
has this changed?
I used
fgfs --show-aircraft --min-status=production
which did not work. So as a test I tried
fgfs --min-status=production --show-aircraft
and that worked and it produced a list of 15 production aircraft. This did
not include the IAR80 perhaps because it sets
represent a compromise in quality
or
capabilities. This will be particular apparent when people do the inevitable
comparison with MSFS and X-Plane, which include a wider selection of aircraft
with the initial install.
3) New users often want to fly a military jet or commercial jet ASAP, despite
When I built OSG (from the latest SVN ) using Cmake I did not include
tiff
libraries. The net result was a similar error message to yours when I
tried
to use a tiff texture file. Also all my panels were white.
I replaced the tiff file with a png equivalent (as used by many FG
aircraft
/jeep/jeep-yasim.xml
/var/cvs/FlightGear-0.9/data/Aircraft/jeep/jeep.jpg
initial release
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2007-08-28_10:31:56 (dfaber)
/var/cvs/FlightGear-0.9/data/Aircraft/jeep/Models/Jeep.xml
/var/cvs/FlightGear-0.9/data/Aircraft/jeep/Models
On Thu, Jun 7, 2012 at 5:04 PM, Gijs de Rooy wrote:
Hi all!
Calling something a major release is not just a matter of what's possible,
but also what's done.
There's a lot possible with Rembrandt, but 99% of our aircraft don't use it.
And lots of aircraft look ugly with Rembrandt
(non
(JST)
Hi all,
As you may know, 787 aircraft has been disappeared from official
aircraft download page.
cf.
http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg21552.html
To include the 787 on download page at the next release timing, I'll
send a simple patch for 787
Rembrandt
in the release, but not mentioning it (explicitly) in
the changelog/press-release; and thus versioning it 2.8.0.
Anders presented that as an easter egg. Xiii likes easter eggs :-)
That'll keep the expectations low, and allow aircraft developers to
spend some months (till the next release
it.
There's still plenty of time before the release...
I didn't think it harsh myself , but from my point of view , I'd
rather not waste time on something I can't see or use... I get about 5
fps and a brilliant green terrain , with a duplicate black aircraft ,
not shadow , right beside the main aircraft.
I
- A6M2 (Zero)
Suggested by Melchior, for ease of operations use. I think this is a good
point. The release will be the first FlightGear hands-on experience for many
people and we want to make sure that that first experience is as positive as
possible by providing aircraft that have reasonably easy
a major new feature, and is appropriate to bump the major
version number up for. it also allows us to side-step the issue
of the a future 2.10.0 release. :)
Also, release numbers are cheap, and X-Plane, MSFS are already
on version 10, so we've got some space to catch up :)
2) Which aircraft do we
, 06 Jan 2010 00:18:03 +0900 (JST)
Hi all,
As you may know, 787 aircraft has been disappeared from official
aircraft download page.
cf.
http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg21552.html
To include the 787 on download page at the next release timing
repository - now is the time!
Two questions have to be discussed and answered until the release
branches get created on July, 17th:
1) What's the version number of the new release?
a) 2.8.0
b) 3.0.0
2) Which aircraft do we ship in the base package?
a) just the c172
b) same as before
c
is the time!
Two questions have to be discussed and answered until the release
branches get created on July, 17th:
1) What's the version number of the new release?
a) 2.8.0
b) 3.0.0
2) Which aircraft do we ship in the base package?
a) just the c172
b) same as before
c
to
help see
what the majority really wants, as with some of the replies
in this
thread I cannot tell what some people believe should be
done about
these aircraft.
First this is not what the majority of USERS wants- that's what the majority of
DEVELOPER's and release managers wants
Thanks for all the replies,
summing all up, I end up with the following:
The summer release will become v2.8.0. Rembrandt is included but
disabled by default and announced as an experimental but cool new feature.
We keep the current selection of base package aircraft for 2.8.0.
We keep last
While I'm at it. :-)
With each release we include a selection of representative aircraft that
highlight FlightGear's capabilities. Inclusion criteria include: Completeness,
variability across categories, realism, suitability for demo flights (think of
aerotowing, AI/Multiplayer refueling
It's as good a selection as any and I would go with this, but ISTR a
decision in the context of the last, abortive, release to include only the
default aircraft. If this is the case, I would be more than happy to go back
to the principle of a small selection that shows off FG's capabilities
/now/ (actually, already merged locally, just
testing before I push) since getting the API into this release is useful, and
the changes are strictly opt-in - no chance of breakage for aircraft that don't
use the canvas.
James
all,
As you may know, 787 aircraft has been disappeared from official
aircraft download page.
cf.
http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg21552.html
To include the 787 on download page at the next release timing, I'll
send a simple patch for 787
including a single aircraft implies that the simulator is
only really designed for that aircraft, and any other aircraft may
represent a compromise in quality or capabilities. This will be
particular apparent when people do the inevitable comparison with
MSFS and X-Plane, which include a wider
Hi everybody,
today is June, 17th and this marks our feature freeze for the sources of
SimGear, FlightGear and FGDATA. Within FGDATA, only aircraft not being
part of the base package are not part of the feature freeze. Maintainers
for those aircraft are kindly requested to carefully check
based on who bothered to self-rate, not based on what is
good
I think if we intended to include these ratings on the download page,
developers would be very keen on rating their aircraft. After all, we
create them to share with the community, and this will help encourage
people to try different
On Sunday 05 October 2008 10:13:54 Durk Talsma wrote:
While I'm at it. :-)
With each release we include a selection of representative aircraft that
highlight FlightGear's capabilities. Inclusion criteria include:
Completeness, variability across categories, realism, suitability for demo
, but well you know how I always say one sentence too many and
paint myself into a corner I can't get out of.) :-)
I sense that there have been a substantial number of updates to individual
aircraft that are only going into the master branch and aren't getting
cherry picked into the 2.8.0 release
Heiko Schulz wrote:
Martin wrote:
Durk Talsma wrote:
So, with these criteria in mind, what would be your
current top 10 of
aircraft?
I'd be very happy to see Heiko's overhauled C172
model included in the
release. The outer hull is waaay better than the old one,
yet
Seconly, do we want to maintain our current aircraft selection, or do we
want to include a (partially) updated selection from our git repository, or
-alternatively- do we want to strip the entire selection down to just single
aircraft, and make the others downloadable from our main website
Seconly, do we want to maintain our current aircraft selection, or do we want
to include a (partially) updated selection from our git repository, or
-alternatively- do we want to strip the entire selection down to just single
aircraft, and make the others downloadable from our main
the
release plan
in the wiki, then Yes. I think it strikes the right
balance to allow aircraft
developers some time to work with the stable binaries.
-Stuart
--
Live Security Virtual Conference
Exclusive live event
Hi all,
As you may know, 787 aircraft has been disappeared from official
aircraft download page.
cf.
http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg21552.html
To include the 787 on download page at the next release timing, I'll
send a simple patch for 787-set.xml
it, but it seemed to have no effect.
Jon
C:\cygwin\home\jon\flightgearFlightGear\projects\VC90\Win32\Release\fgfs
--fg-root=c:\cygwin\home\jon\flightgear\fgdata
Processing command line arguments
using aircraft-dir
for:c:/cygwin/home/jon/flightgear/fgdata/Aircraft/c172p/splash.png
Warning: Could
.
We can but try. Certainly this seems to have a bit more momentum behind it
than previous attempts, based on the feedback here and on IRC.
If enough people rate their aircraft and we can use it to provide a better
download page for the upcoming release, it will succeed.
Let's hope - some
Sounds good , I hope someday to be able to see the results .
My list of aircraft is:
dhc2
dhc6
777 , though there are a number of other commiters now , but dont
think this will affect anything
a6m2
dc6-b
Sikorsky-76C
R22
b1900d
Citation-Bravo
Citation-II
Citation-X
Aerostar-700
P47
I should
suggestion.
Firstly populate fgdata with a bare minimum of aircraft . A starting point
is those packed in the regular release.
Secondly include within flightgear/fgdata a database of other aircraft.
This database should be searchable by keyword(s). Fgrun and similar programs
will also need
Durk Talsma wrote:
While I'm at it. :-)
With each release we include a selection of representative aircraft that
highlight FlightGear's capabilities. Inclusion criteria include:
Completeness,
variability across categories, realism, suitability for demo flights (think
of
aerotowing, AI
On dimanche 05 octobre 2008, Durk Talsma wrote:
While I'm at it. :-)
With each release we include a selection of representative aircraft that
highlight FlightGear's capabilities. Inclusion criteria include:
Completeness, variability across categories, realism, suitability for demo
flights
contributors who
are committing major aircraft changes _after_ the freeze do expect
the respective aircraft not to apply for getting included in the
release package.
Given that they should be self contained and shouldn't affect any
other part of the sim, [...]
Quite often aircraft changes _do_
Hello,
Two questions have to be discussed and answered until the release
branches get created on July, 17th:
1) What's the version number of the new release?
a) 2.8.0
b) 3.0.0
Keep it consistent: 2.8.0
My reasons:
-Rembrandt is still experimental and Fred's To-Do-list is still big. I
package, and a
carrier ready aircraft (these are two very prominent new AI features in
this release that we want to showcase). So, how about replacing the f16
with the Ligntning (for AAR scenarios)?
j3cub
A few people have a suggested dropping the cub, but given its various
qualities, I'd like
version contains many exciting new features, enhancements and
bugfixes. Major improvements from v2.4.0 include reduced AI aircraft
load times, easier graphics tuning, more sophisticated AI aircraft and
improved usability.
Founded in 1997, FlightGear is developed by a worldwide group of
volunteers
The FlightGear development team is happy to announce the v2.6.0
release of FlightGear, the free, open-source flight simulator. This
new version contains many exciting new features, enhancements and
bugfixes. Major improvements from v2.4.0 include reduced AI aircraft
load times, easier
proper lights are more
involved.
If I was being harsh I'd suggest that the aircraft maintainers
should man up and do it.
There's still plenty of time before the release...
I didn't think it harsh myself , but from my point of view , I'd
rather not waste time on something I can't see
On Sun, 2012-07-01 at 14:20 +0200, ThorstenB wrote:
Am 01.07.2012 14:04, schrieb Gijs de Rooy:
Before the next release , maybe it would be a good idea to disable
those 'panel' outlines , which show up when you press 'C' to view
hotspots.
IIRC the bug is not in the displaying
.
Anyway, I think it's a great plane, both in terms of the FDM and the visuals.
Otherwise I'd like to see either the IAR-80 or the P-51D. There was also some
work on the DHC6 - that's also a really popular plane - we might include that.
3) Should we keep last year's commit policy for aircraft
suggested replacing this aircraft. So I guess we
keep it.
Yes, it is very detailed and nice aircraft IMO.
bf109 - A6M2 (Zero)
Suggested by Melchior, for ease of operations use. I think this is a good
point. The release will be the first FlightGear hands-on experience for many
) What's the version number of the new release?
a) 2.8.0
b) 3.0.0
2) Which aircraft do we ship in the base package?
a) just the c172
b) same as before
c) [name your preferred aircraft]
3) Should we keep last year's commit policy for aircraft during the
feature
to use Flightgear and their favourite planes nevertheless.
Converting aircraft to Rembrandt will still mean that they work
perfectly well with non-Rembrandt.
Making an aircraft Rembrandt-compatible just involves marking
transparent surfaces as such, and has no effect on the non-Rembrandt
systems
Curt (love you too), in compliance with our release plan, only bug fixes can be
cherry picked into the release branch, now that we've past July 17. This is to
make sure that we don't end up having countless of non-functioning/buggy
aircraft on the download page. New features and completely
complete
jetliner. I like
to follow that suggestion.
A-10
As far as I can see, nobody suggested replacing this
aircraft. So I guess we
keep it.
bf109 - A6M2 (Zero)
Suggested by Melchior, for ease of operations use. I think
this is a good
point. The release
like
to follow that suggestion.
A-10
As far as I can see, nobody suggested replacing this aircraft. So I guess
we
keep it.
bf109 - A6M2 (Zero)
Suggested by Melchior, for ease of operations use. I think this is a good
point. The release will be the first FlightGear hands-on experience
see, nobody suggested replacing this aircraft. So I guess
we
keep it.
bf109 - A6M2 (Zero)
Suggested by Melchior, for ease of operations use. I think this is a good
point. The release will be the first FlightGear hands-on experience for
many
people and we want to make sure
@lists.sourceforge.net
Sent: Sunday, October 5, 2008 4:13:54 AM
Subject: [Flightgear-devel] Call for aircraft nominations
While I'm at it. :-)
With each release we include a selection of representative aircraft that
highlight FlightGear's capabilities. Inclusion criteria include: Completeness,
variability
; there are probably people with much
better ideas/knowledge on this list :)
Seconly, do we want to maintain our current aircraft selection, or do we want
to include a (partially) updated selection
from our git repository
What exactly is the current aircraft selection? We did welcome some extremely
nice
more logical to me,
but none of my aircraft include proper nav lights yet so I don't know much
about these.. :)
/Anders
--
---
Anders Gidenstam
mail: anders(at)gidenstam.org
WWW: http://www.gidenstam.org/FlightGear/JSBSim-LTA
The FlightGear development team is happy to announce the v2.6.0
release of FlightGear, the free, open-source flight simulator. This
new version contains many exciting new features, enhancements and
bugfixes. Major improvements from v2.4.0 include reduced AI aircraft
load times, easier
Am 01.07.2012 05:52, schrieb syd adams:
Before the next release , maybe it would be a good idea to disable
those 'panel' outlines , which show up when you press 'C' to view
hotspots.
I don't think this was intentional. The outlines aren't even properly
aligned on any aircraft I checked - so
-functioning/buggy aircraft on the download page. New features and
completely new aircraft should not end up in the release branch.
See: http://wiki.flightgear.org/Release_plan
Understood, but it seems (and I could be mistaken) like a lot of small bug
fixes and rembrandt compatibility updates
model
- there are no points awarded for the accuracy or the fidelity of the 3d
model. E.G there is at least one model with afterburners modelled where
none existed.
I've updated the external model to include the world Accurate for ratings
3-5.
Of course, we're trusting that aircraft
aircraft.
And finally - the points system could award a high status to a poor model -
there are no points awarded for the accuracy or the fidelity of the 3d
model. E.G there is at least one model with afterburners modelled where none
existed.
I've updated the external model to include the world
On Sat, 02 Jun 2012 21:36:17 +0200, Torsten wrote in message
4fca6b31.3090...@t3r.de:
Hi,
in just a bit more than two weeks from now we reach June, 17th,
marking the first milestone for the release of next FlightGear
version: the feature freeze period.
If you have some great
to divide aircraft into categories. The obvious ones include
military, light aircraft, civil transport, helicopters, spaceships,
comic-book etc. This should be quite flexible. The ability to add
categories should be available. Some aircraft will belong in more than one
category, so a cross
Hi Durk,
Durk Talsma wrote:
FWIW, I would like to build a minimum base package this time, which only
consists of one aircraft, no AI, and a minimal set of shared models. AI and
other aircraft can be released as a separate ADDON packages, or via CVS.
Likewise, shared models are now
. But bugfixes should only affect the third
version number then, i.e. a bugfix for the 2.0 stable should be 2.0.1. It
sill makes sense to move to 2.2.0 now - stable release versions should be
even.
Seconly, do we want to maintain our current aircraft selection, or do
we want to include a (partially) updated
I'm at it. :-) With each release we include a
selection of representative aircraft that highlight FlightGear's
capabilities. Inclusion criteria include: Completeness, variability across
categories, realism, suitability for demo flights (think of aerotowing,
AI/Multiplayer refueling
. This
new version contains many exciting new features, enhancements and
bugfixes. Major improvements from v2.4.0 include reduced AI aircraft
load times, easier graphics tuning, more sophisticated AI aircraft and
improved usability.
Founded in 1997, FlightGear is developed by a worldwide group of
volunteers
Durk Talsma wrote:
While I'm at it. :-)
With each release we include a selection of representative aircraft that
highlight FlightGear's capabilities. Inclusion criteria include:
Completeness,
variability across categories, realism, suitability for demo flights (think
of
aerotowing
Am Sonntag, den 05.10.2008, 10:13 +0200 schrieb Durk Talsma:
While I'm at it. :-)
With each release we include a selection of representative aircraft that
highlight FlightGear's capabilities. Inclusion criteria include:
Completeness,
variability across categories, realism, suitability
available shader
technology, FlightGear’s graphical quality has been substantially improved,
compared to the previous release. Assorted highlights of this version include:
new shader based water textures, capturing the sun’s reflection, three
dimensional city block textures, more realistic
to contribute.
Full text below.
-Stuart
The FlightGear development team is happy to announce the v2.6.0
release of FlightGear, the free, open-source flight simulator. This
new version contains many exciting new features, enhancements and
bugfixes. Major improvements from v2.4.0 include reduced AI aircraft
a preliminary v2.8 aircarft download page created (
http://www.flightgear.org/download/aircraft-v2-8/) but Gijs is working on
an improved aircraft download page that should be ready in time for the
release.
Curt.
--
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http
definition , i asked some weeks
ago, why the group name is not taken within OSG
I never got any answer :(
So the best would be, to avoid to include it in the AI _demo of that next
stable release, it can remain as a Geometry model.
--
Gérard
http://pagesperso-orange.fr/GRTux/
J'ai
it througt csv).
2) which aircraft to include ?
[...]
Cheers
Francesco
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
it througt csv).
2) which aircraft to include ?
[...]
Cheers
Francesco
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network
system like that (i.e. the next series could
be 2.2.0 for stable, and 2.3.0. for development).
Seconly, do we want to maintain our current aircraft selection, or do we want
to include a (partially) updated selection from our git repository, or
-alternatively- do we want to strip the entire
Am 17.06.2012 21:14, schrieb Torsten Dreyer:
today is June, 17th and this marks our feature freeze for the sources of
SimGear, FlightGear and FGDATA. Within FGDATA, only aircraft not being
part of the base package are not part of the feature freeze. Maintainers
for those aircraft are kindly
for the release announcement. i.e.:
The FlightGear development team is happy to announce the v2.10 release
of FlightGear, the free, open-source flight simulator. This new
version contains many exciting new features, enhancements and
bugfixes. Highlights in this release include improved usability,
better
== ANNOUNCEMENT + SUMMARY ===
FlightGear 2.0.0. reflects the maturation of the OpenSceneGraph port that
started with the previous 1.9.0 release. In addition to many internal code
improvements, FlightGear 2.0.0. marks the introduction of many new
exciting improvements in the graphics and sound
.:
== ANNOUNCEMENT + SUMMARY ===
FlightGear 2.0.0. reflects the maturation of the
OpenSceneGraph port that started with the previous 1.9.0
release. In addition to many internal code improvements,
FlightGear 2.0.0. marks the introduction of many new
exciting improvements in the graphics
,
Durk
== ANNOUNCEMENT + SUMMARY ===
FlightGear 2.0.0. reflects the maturation of the OpenSceneGraph port that
started with the previous 1.9.0 release. In addition to many internal code
improvements, FlightGear 2.0.0. marks the introduction of many new
exciting improvements
behavior of existing features.
Highlights of this new version include:
Sound
* Complete Overhaul of the Sound Code
* doppler effects
* distance attenuation
* 3D positional sound sources
* assignment of sound sources to external objects (i.e. AI controlled
aircraft)
* User
for the property to
be sent over MP.
If most aircraft use bool for nav lights it is probably a
good idea to
change the type in multiplaymgr.cxx. (Bool does sound more
logical to me,
but none of my aircraft include proper nav lights yet so I
don't know much
about these.. :)
Yes, I
Am 17.06.2012 21:14, schrieb Torsten Dreyer:
today is June, 17th and this marks our feature freeze for the sources of
SimGear, FlightGear and FGDATA. Within FGDATA, only aircraft not being
part of the base package are not part of the feature freeze. Maintainers
for those aircraft are kindly
as improved
usability of key features, and improved behavior of exsisting features.
Highlights of this new version include: Dramatic new 3D clouds,
dramatic lighting conditions, improved support for custom scenery, and many
many new and detailed aircraft models.
Sound
* Complete overhaul
there.
These are not only core features but also new/updated aircraft, scenery
improvements, usability changes - whatever made FlightGear better since
the last release.
The changelog is often copied by online media and might help to attract
new user, so please help creating a persuasive advertising
--- Durk Talsma wrote:
To follow up on this: It seems like the initial testing round went pretty
well, with mostly minor problems being reported, and many of them being fixed
already. I'm hoping to roll up the tar files for the release itself this
weekend.
Is this just the final tarballs
- John Denker a écrit :
2) which aircraft to include ?
That's a different question. I can't help with that.
in data : cvs up -Pd -r V2_0_0B
in source : make data-tar
Or wait the release: official data and source tarballs will be released.
-Fred
--
Frédéric Bouvier
http
Am 20.07.2012 11:10, schrieb Anders Gidenstam:
Given that there is some risk that the behaviour of carefully tuned flight
models change I'd suggest we only update 2.9.0 and do not update 2.8.0 as
it is late in its release cycle.
Valid point. Can someone with more insight into the patch
(Jon
to have
a own flightgear data distribution, missing huge updates from the last couple
of years probably. On the other hand some terrasynced scenery data will be out
of data sync probably for some months with the change, but I guess this is the
part which can be updated out of core release cycles
, with doors missing, rotor blades all in one
spot etc. It would be nice to have some property to key on and just
present a low-LOD version of a plane when it is being viewed as a remote
mp aircraft.
I hoped that the bo105 will look correct with the current release?
The network packets include
airplane
config, the best we can do is exit gracefully.
--
Csaba/Jester
The C310 is one of the aircraft that - in the JSBSim cvs repository - is
used for extensive testing of JSBSim operation. There is a need for an
autopilot for the aircraft to be able to fly out the tests. The autopilot
file
1 - 100 of 182 matches
Mail list logo
