Board index FlightGear Development Aircraft

New Aircraft: the Extra500

Questions and discussion about creating aircraft. Flight dynamics, 3d models, cockpits, systems, animation, textures.

Re: New Aircraft: the Extra500

Postby Hooray » Thu Jun 26, 2014 3:57 pm

don't know about others, but I am getting a ton of inexplicable access errors with latest SG/FG from git (it used to work a while ago), need to check on another computer (getting the correct splash screen etc, but it bails out shortly after initializing the scenery). But the nature of the errors suggests that it's something on the FG side, not the aircraft itself. Hopefully something local, and unrelated to the recent package/catalog updates ...

fgfs --aircraft-dir=/home/hooray/sources/extra500 --aircraft=extra500
Code: Select all

loadxml: reading '/home/hooray/sources/extra500/Models/Liveries/BlueWhite.xml' denied (unauthorized access)
Nasal runtime error: non-objects have no members
  at /home/hooray/sources/fgroot/Nasal/gui.nas, line 459
  called from: /home/hooray/sources/fgroot/Nasal/gui.nas, line 440
  called from: /home/hooray/sources/fgroot/Nasal/gui.nas, line 430
  called from: /home/hooray/sources/fgroot/Nasal/aircraft.nas, line 519
  called from: /home/hooray/sources/extra500/Nasal/liveries.nas, line 23
['parsexml(): reading '/home/hooray/sources/extra500/Models/instruments/IFDs/IFD_MapIcons.svg' denied (unauthorized access)', '/home/hooray/sources/fgroot/Nasal/canvas/svg.nas', 589]
MapIconCache.registerIcon(Icon_Test) fail
MapIconCache.registerIcon(Airport_0000) fail
MapIconCache.registerIcon(Airport_0100) fail
MapIconCache.registerIcon(Airport_0010) fail
MapIconCache.registerIcon(Airport_0110) fail
MapIconCache.registerIcon(Airport_0011) fail
MapIconCache.registerIcon(Airport_0111) fail
MapIconCache.registerIcon(Airport_1000) fail
MapIconCache.registerIcon(Airport_1100) fail
MapIconCache.registerIcon(Airport_1010) fail
MapIconCache.registerIcon(Airport_1110) fail
MapIconCache.registerIcon(Airport_1011) fail
MapIconCache.registerIcon(Airport_1111) fail
MapIconCache.registerIcon(Navaid_VOR) fail
MapIconCache.registerIcon(Navaid_DME) fail
MapIconCache.registerIcon(Navaid_Height) fail
MapIconCache.registerIcon(Navaid_Height2) fail
['parsexml(): reading '/home/hooray/sources/extra500/Models/instruments/IFDs/Keypad.svg' denied (unauthorized access)', '/home/hooray/sources/fgroot/Nasal/canvas/svg.nas', 589]
Nasal runtime error: non-objects have no members
  at /home/hooray/sources/extra500/Nasal/AvidyneEntegra9/base.class.nas, line 175
  called from: /home/hooray/sources/extra500/Nasal/AvidyneEntegra9/keypad.nas, line 28
  called from: /home/hooray/sources/extra500/Nasal/AvidyneEntegra9/keypad.nas, line 166
  called from: /home/hooray/sources/extra500/Nasal/AvidyneEntegra9/keypad.nas, line 710
  called from: /home/hooray/sources/extra500/Nasal/AvidyneEntegra9/keypad.nas, line 1304
['parsexml(): reading '/home/hooray/sources/extra500/Models/instruments/IFDs/IFD_Global.svg' denied (unauthorized access)', '/home/hooray/sources/fgroot/Nasal/canvas/svg.nas', 589]
Nasal runtime error: Invalid argument group (type != Group)
  at /home/hooray/sources/fgroot/Nasal/canvas/svg.nas, line 9
  called from: /home/hooray/sources/extra500/Nasal/AvidyneEntegra9/map/movingMap.nas, line 84
  called from: /home/hooray/sources/extra500/Nasal/AvidyneEntegra9/AvidyneIFD.nas, line 450
  called from: /home/hooray/sources/extra500/Nasal/AvidyneEntegra9/AvidyneIFD.nas, line 848
loadxml: reading '/home/hooray/sources/extra500/Dialogs/autopilot.xml' denied (unauthorized access)
Nasal runtime error: Dialog class: XML dialog must have <name>
  at /home/hooray/sources/fgroot/Nasal/gui.nas, line 334
  called from: /home/hooray/sources/fgroot/Nasal/gui.nas, line 314
  called from: /home/hooray/sources/fgroot/Nasal/globals.nas, line 119
Nasal runtime error: container index not scalar
  at /home/hooray/sources/fgroot/Nasal/gui.nas, line 316
  called from: /home/hooray/sources/extra500/Nasal/dialogs.nas, line 26

Please don't send support requests by PM, instead post your questions on the forum so that all users can contribute and benefit
Thanks & all the best,
Hooray
Help write next month's newsletter !
pui2canvas | MapStructure | Canvas Development | Programming resources
Hooray
 
Posts: 11191
Joined: Tue Mar 25, 2008 8:40 am

Re: New Aircraft: the Extra500

Postby D-Leon » Thu Jun 26, 2014 4:17 pm

Hooray wrote in Thu Jun 26, 2014 3:57 pm:
fgfs --aircraft-dir=/home/hooray/sources/extra500 --aircraft=extra500

I use --aircraft-dir as a folder width aircrafts and not as the aircraft it self. If your folder structure looks like /home/hooray/sources/extra500, I would try --aircraft-dir=/home/hooray/sources --aircraft=extra500.
D-Leon
 
Posts: 28
Joined: Wed Oct 03, 2012 8:44 am
Callsign: D-Leon
OS: Linux

Re: New Aircraft: the Extra500

Postby Hooray » Thu Jun 26, 2014 4:22 pm

nope, but I am surprised that it works for you that way - I never ever used it like that before, need to check the code if that's supposed to work, because then something is clearly way off here. And like I said, a while ago, it did work like this. Will try some other "external" aircraft first.
Please don't send support requests by PM, instead post your questions on the forum so that all users can contribute and benefit
Thanks & all the best,
Hooray
Help write next month's newsletter !
pui2canvas | MapStructure | Canvas Development | Programming resources
Hooray
 
Posts: 11191
Joined: Tue Mar 25, 2008 8:40 am

Re: New Aircraft: the Extra500

Postby TheTom » Thu Jun 26, 2014 4:42 pm

Hooray wrote:fgfs --aircraft-dir=/home/hooray/sources/extra500 --aircraft=extra500

Works without a problem here...
TheTom
 
Posts: 321
Joined: Sun Oct 09, 2011 10:20 am

Re: New Aircraft: the Extra500

Postby Hooray » Thu Jun 26, 2014 4:47 pm

ok, thanks for checking - will empty the ccache then and rebuild the whole thing
Please don't send support requests by PM, instead post your questions on the forum so that all users can contribute and benefit
Thanks & all the best,
Hooray
Help write next month's newsletter !
pui2canvas | MapStructure | Canvas Development | Programming resources
Hooray
 
Posts: 11191
Joined: Tue Mar 25, 2008 8:40 am

Re: New Aircraft: the Extra500

Postby D-EKEW » Sat Dec 13, 2014 9:43 am

Yes, it is time for a new release for our Extra500: 1.2.0

This time the main improvement you can't see (from the cockpit), but the landing gear is upgraded in both model as movement. Check it out with an outside view or put the aircraft on Jacks (Ctrl+G) to retract on ground.

One of the big differences when you are flying behind your PC or flying for real is that you don't have any force feedback from your controls. Apart this feedback primarily gives an aircraft its 'feel' you also do not know where to trim to. As the Extra500 model actually calculates the elevator forces, it is now indicated if the pilot is pulling or pushing the yoke. Use your mouse wheel to trim the elevator force away or your virtual arms will get heavy...

There are some other small improvements and bug fixes as well:
* Aerodynamics: more realistic engine torque and slipstream effects
* Avionics: bug fixes and some minor usability improvements
* Autopilot: some logic and bug fixes
* Model: some interior fixes and improvements

Last but not least the Extra500 is now officially part of Flightgear which means it will ship with the upcoming 3.4 release.

Safe flight and (especially) landing!

Eric
D-EKEW
 
Posts: 159
Joined: Mon Jan 10, 2011 8:22 pm
Callsign: D-EKEW, ELLX-TWR
Version: git
OS: Linux

Re: New Aircraft: the Extra500

Postby legoboyvdlp » Thu Dec 18, 2014 4:33 pm

ludomotico wrote in Thu Feb 20, 2014 4:49 pm:With only 4GB of RAM, I have experimented the "RAM vampire" behavior you were discussing not long ago: fgfs tends to use as much RAM as available, forcing other applications to swap. The simulator doesn't fail but when it closes, the rest of the system is completely KO for several minutes while swapping back to the RAM. Hence, I tested someone's advice: remove the *2 in the tilecache size and reduce the LOD. It worked like a charm: no more of that annoying swapping and only a bit of fog at the horizon. In addition, more or less at the same time I experimented a gain of 10-20FPS: the C172 used to fly @30FPS and now it runs @50-60FPS. This specific aircraft runs @30FPS on my machine. I don't know if it is related to the memory consumption or it is some update in the libraries/flightgear of the last week.


Just how would that be done, remove the 2* in the tilecache?
User avatar
legoboyvdlp
 
Posts: 5826
Joined: Sat Jul 26, 2014 1:28 am
Callsign: YV-LEGO
Version: 2018.3.1
OS: Windows 10 HP

Re: New Aircraft: the Extra500

Postby D-EKEW » Sat Jan 10, 2015 6:11 pm

Due to some bug fixes in the route manager for the upcoming 3.4 release, we had to...not sure how to call this...do some anti-bug fixes of our own. Therefore we released version 2.0.0 of the Extra500.
This release is for current Git users and of course for the 3.4 flightgear version when it arrives.

For users flying FG up to version 3.2, please use release 1.2.0. There is no back- or forward-compatibility!

Fly safe!

Eric
D-EKEW
 
Posts: 159
Joined: Mon Jan 10, 2011 8:22 pm
Callsign: D-EKEW, ELLX-TWR
Version: git
OS: Linux

Re: New Aircraft: the Extra500

Postby Hooray » Sat Jan 10, 2015 6:46 pm

D-EKEW wrote in Sat Jan 10, 2015 6:11 pm:Due to some bug fixes in the route manager for the upcoming 3.4 release, we had to...not sure how to call this...do some anti-bug fixes of our own.


This is a long-standing debate/issue - omega95 and others keep complaining about route-manager related changes, too.
Some aircraft developers went as far as re-implementing existing C++ functionality (AP + RM) completely in scripting space to isolate themselves from these kinds of API changes.

You know, the thing is, that we cannot expect FlightGear to evolve without also improving such components over time.

I do agree that it would seem like a good idea to either introduce some kind of backward compatibility (e.g. a "rm-version" property for requesting a certain stable API that won't change in the future), or to expose these things to scripting space so that people can more easily work around such "improvements".

But overall, the people complaining about the degree of route manager related changes should keep in mind that related core development activities are a good thing in general.

There are many other components in SG/FG that are de-facto unmaintained - so it would be better to team up with other aircraft developers affected by this and get in touch with Zakalawe to suggest providing a version flag/property, so that you guys don't need to work around such improvements all the time.

Using a std::map<> it would be straightforward to maintain multiple versions of the route manager in parallel, even in C++ space - and as long as more functionality is exposed to scripting space, doing the same in Nasal is trivial, too.
Please don't send support requests by PM, instead post your questions on the forum so that all users can contribute and benefit
Thanks & all the best,
Hooray
Help write next month's newsletter !
pui2canvas | MapStructure | Canvas Development | Programming resources
Hooray
 
Posts: 11191
Joined: Tue Mar 25, 2008 8:40 am

Re: New Aircraft: the Extra500

Postby D-EKEW » Sat Jan 10, 2015 6:57 pm

Don't worry, we have no problem with maintaining our aircraft model!
Especially if it brings improvements to FG.

This was not meant as a complaint at all, just as a justification for our not-planned release and to explain to our users which Extra500 version to use for which FG version.
No more, no less!
D-EKEW
 
Posts: 159
Joined: Mon Jan 10, 2011 8:22 pm
Callsign: D-EKEW, ELLX-TWR
Version: git
OS: Linux

Re: New Aircraft: the Extra500

Postby D-EKEW » Sat May 02, 2015 4:41 pm

Dear fellow pilots,

A new stable version of the Extra500 is released: 2.1.0
Like the previous stable version it can only be used with FG 3.4 or later.

Changes include:

    * Autopilot: improved fail indication and flight director, fixes for broken functions, hot keys to enable modes
    * IFD: flightplan, map fuel reserve indication and obs course indication improved
    * ELT: improved and configurable msg
    * Electric system: more accurate model, External power indication (V+A)
    * Interior: door animation
    * Model: fixes, propeller, possibility to put aircraft on Jacks (CTRL G)
    * Engine: reworked oil pressure and TOT spool-down model

This version is available on FGaddon or checkout our gitlab repository:
https://gitlab.com/extra500/extra500/tree/release/2.1.0

Happy flying!
D-EKEW
 
Posts: 159
Joined: Mon Jan 10, 2011 8:22 pm
Callsign: D-EKEW, ELLX-TWR
Version: git
OS: Linux

Re: New Aircraft: the Extra500

Postby D-EKEW » Sun Jul 26, 2015 6:17 pm

Dear fellow flightgear pilots and developers,

As the release of Flightgear version 3.6 is approaching we are happy to report we bring out 2 versions of our Extra500 model.
The first is version 2.2.0, which has all the development of the last few months except that which is not compatible with 3.6. Version 3.0.0 adds those features and therefore should only be used with the upcoming flightgear release 3.6.

The following changes are only in available in 3.0.0:
* ALS: inside and outside (volumetric) shadow
* ALS: on windows: rain, ice and fog
* Cabin: fix for oxygen blackout on ground, de-icing and fogging
* IFD: PFD horizon, improved map data de-clutter
Download: version 3.0.0 for FG3.6.0

And these are for both versions:
* FMS: fix CDI indication (magnetic variation bug)
* IFD: fuel indication, map icons DME/NDB/TACAN
* Fuel: complete re-model fuel system (was nasal, now jsbsim)
* cabin: oxygen blackout
* Model: propeller, removed 'interference' mode; does not happen when looking at propeller in RL, only on TV
* Electric: improved battery model, some load fixes on purely resistive systems
* Autopilot: possibility to overpower the autopilot servos
* Environment: An optional weather model that uses the 20 closest METAR-s to produce smooth transitions of pressure, temperature, wind speed and direction etc.
* Sound: positioning, volume, angle and headset
* model performance: executing certain jsbsim code only when really used (I really really wished I knew this could be done before...)
Download: version 2.2.0 for FG3.4.0

Please visit our wiki page

Have fun and safe flying!
D-EKEW
 
Posts: 159
Joined: Mon Jan 10, 2011 8:22 pm
Callsign: D-EKEW, ELLX-TWR
Version: git
OS: Linux

Re: New Aircraft: the Extra500

Postby dg-505 » Sun Jul 26, 2015 8:59 pm

I wrote a short note for the July 2015 Newsletter and updated the german wiki page of the Extra500
It's not just a hobby. I'ts a passion: FLYING !!

DHC-6 Twin Otter development
User avatar
dg-505
 
Posts: 613
Joined: Mon Jun 02, 2014 2:36 pm
Location: Hessen, Germany
Version: next
OS: Ubuntu 16.04

Re: New Aircraft: the Extra500

Postby massima » Mon Jul 27, 2015 9:42 am

Great piece of news, i'll try you plane.
User avatar
massima
 
Posts: 208
Joined: Sat Jan 03, 2015 6:48 pm
Location: Italy
Callsign: M-AXX
Version: 2018.2.2
OS: debian testing

Re: New Aircraft: the Extra500

Postby wkitty42 » Mon Jul 27, 2015 3:28 pm

i just reported an issue for this craft in the gitlab issue tracker...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."
User avatar
wkitty42
 
Posts: 4755
Joined: Fri Feb 20, 2015 3:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 14.04.5

PreviousNext

Return to Aircraft

Who is online

Users browsing this forum: No registered users and 10 guests