Board index FlightGear Development Aircraft

A320-family development

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

Re: A320-family development

Postby wkitty42 » Wed Aug 04, 2021 11:20 am

what are their file sizes and dates? most likely they are the same...

the reason for having two the same is because one can easily script a pull of "latest-nightly" and not have to edit the script when the name changes like you would if you were pulling "2020.4.0-nightly" when it changes to 2020.5.0 or 2021.1.0...
"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: 9146
Joined: Fri Feb 20, 2015 4:46 pm
Location: central NC, USA
Callsign: wk42
Version: git next
OS: Kubuntu 20.04

Re: A320-family development

Postby merspieler » Wed Aug 04, 2021 11:28 am

I've got no clue, what the difference is...

Dev branch is fine... there's the 3D branch containing the new exterior model.
Nia (you&, she/her)

Please use gender neutral terms when referring to a group of people!

Be the change you wish to see in the world, be an ally to all!

Join the official matrix space
merspieler
 
Posts: 2241
Joined: Thu Oct 26, 2017 11:43 am
Location: Wish to be in YBCS
Pronouns: you&, she/her
Callsign: you&, she/her
IRC name: merspieler
Version: next
OS: NixOS

Re: A320-family development

Postby PK-DNZ_107 » Wed Aug 04, 2021 11:32 am

wkitty42 wrote in Wed Aug 04, 2021 11:20 am:what are their file sizes and dates? most likely they are the same...

the reason for having two the same is because one can easily script a pull of "latest-nightly" and not have to edit the script when the name changes like you would if you were pulling "2020.4.0-nightly" when it changes to 2020.5.0 or 2021.1.0...

^^
they are the same size and dates. I decided to download the 2020.4.0 nightly versions.

merspieler wrote in Wed Aug 04, 2021 11:28 am:I've got no clue, what the difference is...

Dev branch is fine... there's the 3D branch containing the new exterior model.


I never tried the 3D branch, think I'm gonna give it a try. Thanks!
PK-DNZ_107
 
Posts: 88
Joined: Mon Aug 05, 2019 6:58 am

Re: A320-family development

Postby legoboyvdlp » Wed Aug 04, 2021 11:56 am

There is no difference at all in the files; I'm not sure why there are two.

As far the minimum FlightGear version you can use; I believe its currently 2019.2.0 with the dev branch. As far as branches; 3D is relatively stable -- none of the other branches are ready for use right now.

As far as I know the minimum version for 3D will be 2020.3 due to some engine features that are needed. @Octal450 can confirm that; I can't 100% remember.
and I don't recommend the nightly -- you can use it; but just as long as you know that it's incredibly unstable right now (due to a lot of work in progress on new features like HDR!)
User avatar
legoboyvdlp
 
Posts: 7981
Joined: Sat Jul 26, 2014 2:28 am
Location: Northern Ireland
Callsign: G-LEGO
Version: next
OS: Windows 10 HP

Re: A320-family development

Postby merspieler » Wed Aug 04, 2021 12:07 pm

I can't see why next would be unstable... runs pretty stable here right now... also HDR has absolutely no effect as it's a dedicated pipleline which is disabled by default.
Nia (you&, she/her)

Please use gender neutral terms when referring to a group of people!

Be the change you wish to see in the world, be an ally to all!

Join the official matrix space
merspieler
 
Posts: 2241
Joined: Thu Oct 26, 2017 11:43 am
Location: Wish to be in YBCS
Pronouns: you&, she/her
Callsign: you&, she/her
IRC name: merspieler
Version: next
OS: NixOS

Re: A320-family development

Postby legoboyvdlp » Wed Aug 04, 2021 12:42 pm

Well; here the Canvas displays only started working again recently; the compositeviewer is very unstable; and performance also appears to be somewhat degraded. I'm not taking responsibility for recommending people use the nightly. If they want to that's fine but I won't be recommending it when 2020.3 works excellently.
User avatar
legoboyvdlp
 
Posts: 7981
Joined: Sat Jul 26, 2014 2:28 am
Location: Northern Ireland
Callsign: G-LEGO
Version: next
OS: Windows 10 HP

Re: A320-family development

Postby cgdae » Wed Aug 04, 2021 12:59 pm

Can you give more information about CompositeViewer being unstable or performance being degraded?

There are certainly issues with some of the new functionality it provides, but i'm not currently aware of stability/performance problems.

Thanks,

- Jules
Last edited by Johan G on Wed Aug 04, 2021 3:46 pm, edited 1 time in total.
Reason: Please do not quote the entire preceding post.
cgdae
 
Posts: 117
Joined: Tue May 31, 2016 8:35 pm

Re: A320-family development

Postby merspieler » Wed Aug 04, 2021 1:13 pm

For me CompositeViewer only breaks fg when I try to use it... as long as I keep my fingers away from it, I don't see any issues.
Nia (you&, she/her)

Please use gender neutral terms when referring to a group of people!

Be the change you wish to see in the world, be an ally to all!

Join the official matrix space
merspieler
 
Posts: 2241
Joined: Thu Oct 26, 2017 11:43 am
Location: Wish to be in YBCS
Pronouns: you&, she/her
Callsign: you&, she/her
IRC name: merspieler
Version: next
OS: NixOS

Re: A320-family development

Postby legoboyvdlp » Wed Aug 04, 2021 1:24 pm

cgdae wrote in Wed Aug 04, 2021 12:59 pm:Can you give more information about CompositeViewer being unstable or performance being degraded?

There are certainly issues with some of the new functionality it provides, but i'm not currently aware of stability/performance problems.

Thanks,

- Jules


I've mentioned those in the email -- but I've noticed that performance does seem to be somewhat lower after compiling flightgear again this week -- I haven't looked into it yet as I've been busy elsewhere -- sorry for being unclear; I wasn't blaming CompositeViewer but rather the nightly in general for the lower performance. :)
User avatar
legoboyvdlp
 
Posts: 7981
Joined: Sat Jul 26, 2014 2:28 am
Location: Northern Ireland
Callsign: G-LEGO
Version: next
OS: Windows 10 HP

Re: A320-family development

Postby cgdae » Wed Aug 04, 2021 2:34 pm

Ok, that's good to know about the performance, thanks.

However you said "the compositeviewer is very unstable" and don't think that is right. It's possible that i'm misinterpreting you but, for me, 'very unstable' means 'can make Flightgear crash'. To the best of my knowledge, CompositeViewer does not make Flightgear crash - otherwise we wouldn't have decided to make it the default on next.

I'm keen to get feedback on CompositeViewer. But as we all know, having Flightgear crash while one is using it is a real pain. There are legitimate reasons for avoiding next, but i wouldn't want people to avoid next for fear of CompositeViewer being known to make Flightgear crash when, as far as i know, this is not the case.

[The known issues with CompositeViewer in the flightgear-devel email concern the new 'extra view' windows incorrectly showing yellow highlighting and sometimes responding to mouse drags in the opposite direction from expected. Plus unnecessary diagnostics on the terminal output. I'm sure there will be others that we'll come across as people try it out.]

Thanks,

- Jules
Last edited by Johan G on Wed Aug 04, 2021 3:46 pm, edited 1 time in total.
Reason: Please do not quote the entire preceding post.
cgdae
 
Posts: 117
Joined: Tue May 31, 2016 8:35 pm

Re: A320-family development

Postby Octal450 » Wed Aug 04, 2021 3:56 pm

@Octal450 can confirm that


Correct. Hard floor at 2020.3.1, but any 2020.3.x will work all though always recommending the latest!

Kind Regards,
Josh
Skillset: JSBsim Flight Dynamics, Systems, Canvas, Autoflight/Control, Instrumentation, Animations
Aircraft: A320-family, MD-11, MD-80, Contribs in a few others

Octal450's GitHub|Launcher Catalog
|Airbus Dev Discord|Octal450 Hangar Dev Discord
User avatar
Octal450
 
Posts: 5583
Joined: Tue Oct 06, 2015 1:51 pm
Location: Huntsville, AL
Callsign: WTF411
Version: next
OS: Windows 11

Re: A320-family development

Postby remenary » Fri Aug 06, 2021 11:57 am

Hi Everyone!

New here. I have downloaded the latest FlightGear and A320 and trying to calibrate my Thrustmaster A320 throttle and am running into some issues.

With the aircraft loaded, I clicked File | Joystick Configuration.

From there I put some random (but independently verifiable) selections and accessed the configuration XML file:

Code ("C:/Users/username1/AppData/Roaming/flightgear.org/Input/Joysticks/TCA-Q-Eng-1&2.xml"): Select all
<?xml version="1.0"?>

<PropertyList>
<name type="string">TCA Q-Eng 1&amp;2</name>
<axis>
<desc type="string">Throttle Engine 0</desc>
<binding>
<command type="string">property-scale</command>
<property type="string">/controls/engines/engine[0]/throttle</property>
<factor type="double">-1</factor>
<offset type="double">0</offset>
<power type="double">1</power>
</binding>
</axis>
<axis n="1">
<desc type="string">Throttle Engine 1</desc>
<binding>
<command type="string">property-scale</command>
<property type="string">/controls/engines/engine[1]/throttle</property>
<factor type="double">-1</factor>
<offset type="double">0</offset>
<power type="double">1</power>
</binding>
</axis>
<button>
<desc type="string">Aileron Trim Left</desc>
<binding>
<command type="string">nasal</command>
<script type="string">controls.aileronTrim(-1);</script>
</binding>
<repeatable type="double">1</repeatable>
</button>
<button n="1">
<desc type="string">Aileron Trim Right</desc>
<binding>
<command type="string">nasal</command>
<script type="string">controls.aileronTrim(1);</script>
</binding>
<repeatable type="double">1</repeatable>
</button>
<button n="2">
<desc type="string">Weapon previous</desc>
<binding>
<command type="string">property-adjust</command>
<property type="string">/controls/armament/weapon-selected</property>
<step type="string">-1</step>
</binding>
</button>
<button n="3">
<desc type="string">Target next</desc>
<binding>
<command type="string">property-adjust</command>
<property type="string">/controls/armament/target-selected</property>
<step type="string">1</step>
</binding>
</button>
<button n="6">
<desc type="string">Propeller Coarse</desc>
<binding>
<command type="string">nasal</command>
<script type="string">controls.adjPropeller(-1);</script>
</binding>
<repeatable type="double">1</repeatable>
</button>
<button n="7">
<desc type="string">Mixture Rich</desc>
<binding>
<command type="string">nasal</command>
<script type="string">controls.adjMixture(1);</script>
</binding>
<repeatable type="double">1</repeatable>
</button>
<button n="8">
<desc type="string">Azimuth left</desc>
<binding>
<command type="string">property-adjust</command>
<property type="string">/controls/radar/azimuth-deg</property>
<step type="string">-5</step>
</binding>
</button>
<button n="9">
<desc type="string">View Up</desc>
<binding>
<command type="string">property-adjust</command>
<property type="string">/sim/current-view/goal-pitch-offset-deg</property>
<step type="string">20.0</step>
</binding>
</button>
<button n="10">
<desc type="string">View Left</desc>
<binding>
<command type="string">property-adjust</command>
<property type="string">/sim/current-view/goal-heading-offset-deg</property>
<step type="string">30.0</step>
</binding>
</button>
<button n="11">
<desc type="string">Elevation up</desc>
<binding>
<command type="string">property-adjust</command>
<property type="string">/controls/radar/elevation-deg</property>
<step type="string">5</step>
</binding>
</button>
<button n="12">
<desc type="string">Azimuth right</desc>
<binding>
<command type="string">property-adjust</command>
<property type="string">/controls/radar/azimuth-deg</property>
<step type="string">5</step>
</binding>
</button>
<button n="13">
<desc type="string">View Down</desc>
<binding>
<command type="string">property-adjust</command>
<property type="string">/sim/current-view/goal-pitch-offset-deg</property>
<step type="string">-20.0</step>
</binding>
</button>
<button n="14">
<desc type="string">View Right</desc>
<binding>
<command type="string">property-adjust</command>
<property type="string">/sim/current-view/goal-heading-offset-deg</property>
<step type="string">-30.0</step>
</binding>
</button>
<button n="15">
<desc type="string">Elevation down</desc>
<binding>
<command type="string">property-adjust</command>
<property type="string">/controls/radar/elevation-deg</property>
<step type="string">-5</step>
</binding>
</button>
</PropertyList>


The device inputs with their corresponding (random) selections are:
Throttle Left: (axis) Throttle Engine 0 (input 0.48 @ idle)
Throttle Right (axis 1) Throttle Engine 1 (input 0.46 @ idle)
Dent CLB Left: (button 10) View Left (input 0.01)
Dent CLB RIght: (button 14) View Right (input 0.00)
Dent FLX/MCT Left: (button 9) View Up (input -0.48)
Dent FLX/MCT Right: (button 13) View Down (input -0.49)
Dent TOGA Left: (button 8) Azimuth Left (input -1.00)
Dent TOGA Right: (button 12) Azimuth Right (input -1.00)
Reverser Left: (button 11) Elevation Up (1.00 @ full reverse)
Reverser Right: (button 15) Elevation Down (1.00 @ full reverse)
A/THR Disconnect Left: (button) Aileron Trim Left
A/THR Disconnect Right: (button 1) Aileron Trim Right
Eng Master Left: (button 2) Weapon Previous
Eng Master Right: (button 3) Target Next
CRANK: (button 6) Propeller Coarse
IGN/START:: (button 7) Mixture Rich

Naturally I want to assign them to the relevant A320 modes. I tried to see if there was some hints in the source and looked within the code and found this:

Code (D:/FlightGear 2020.3/data/Aircraft/A320-family/Nasal/Systems/FADEC/engines-common.nas): Select all
# Engine thrust commands
var doIdleThrust = func {
# Idle does not respect selected engines, because it is used to respond
# to "Retard" and both engines must be idle for spoilers to deploy
pts.Controls.Engines.Engine.throttle[0].setValue(0.0);
pts.Controls.Engines.Engine.throttle[1].setValue(0.0);
}

var doCLThrust = func {
if (pts.Sim.Input.Selected.engine[0].getBoolValue()) {
pts.Controls.Engines.Engine.throttle[0].setValue(0.63);
}
if (pts.Sim.Input.Selected.engine[1].getBoolValue()) {
pts.Controls.Engines.Engine.throttle[1].setValue(0.63);
}
}

var doMCTThrust = func {
if (pts.Sim.Input.Selected.engine[0].getBoolValue()) {
pts.Controls.Engines.Engine.throttle[0].setValue(0.80);
}
if (pts.Sim.Input.Selected.engine[1].getBoolValue()) {
pts.Controls.Engines.Engine.throttle[1].setValue(0.80);
}
}

var doTOGAThrust = func {
if (pts.Sim.Input.Selected.engine[0].getBoolValue()) {
pts.Controls.Engines.Engine.throttle[0].setValue(1.00);
}
if (pts.Sim.Input.Selected.engine[1].getBoolValue()) {
pts.Controls.Engines.Engine.throttle[1].setValue(1.00);
}
}


But at this point I think I'd do more damage than good. I notice that the thrust in the code varies between 0 (IDLE) to 1 (TOGA), where as the throttle seems to vary between 0.5 (IDLE) to -1.00 (TOGA).

Please note, the device doesn't have a Reverser IDLE dent. The closest I can to reverse IDLE is an input value between 0.7-0.8, or the device will through design click to thrust IDLE.

Any help will be greatly appreciated!

Many thanks,

remenary
remenary
 
Posts: 3
Joined: Fri Aug 06, 2021 11:30 am

Re: A320-family development

Postby merspieler » Fri Aug 06, 2021 2:15 pm

Hey, welcome to the forum.

For now, I think the following forum post will help you with your configuration: viewtopic.php?p=384761#p384761

On a feature branch (3D) we've got already stuff for adjusting the detends in place... so things will get much better, once that gets merged.
Nia (you&, she/her)

Please use gender neutral terms when referring to a group of people!

Be the change you wish to see in the world, be an ally to all!

Join the official matrix space
merspieler
 
Posts: 2241
Joined: Thu Oct 26, 2017 11:43 am
Location: Wish to be in YBCS
Pronouns: you&, she/her
Callsign: you&, she/her
IRC name: merspieler
Version: next
OS: NixOS

Re: A320-family development

Postby Octal450 » Fri Aug 06, 2021 4:14 pm

Hi @remenary

On the 3D branch, I have built in throttle detent adjustments into my new FADECs.

The props are in /systems/acconfig/options/fadec/ and to save them, just change any setting in ACCONFIG then change it back if you wish, ACCONFIG will automatically save all settings.

there are -t meaning "top of the detent" like idle-t, toga-t, and -b meaning "bottom of the detent" like toga-b. You can set these as you wish. You can see the current throttle in /controls/engines/engine[0]/throttle.

I will make a NICE UI for all of this soon that will allow easily setting these detents.

Kind Regards,
Josh
Skillset: JSBsim Flight Dynamics, Systems, Canvas, Autoflight/Control, Instrumentation, Animations
Aircraft: A320-family, MD-11, MD-80, Contribs in a few others

Octal450's GitHub|Launcher Catalog
|Airbus Dev Discord|Octal450 Hangar Dev Discord
User avatar
Octal450
 
Posts: 5583
Joined: Tue Oct 06, 2015 1:51 pm
Location: Huntsville, AL
Callsign: WTF411
Version: next
OS: Windows 11

Re: A320-family development

Postby remenary » Sat Aug 07, 2021 6:11 pm

Thanks for the replies!

@merspieler I checked out the other forum post - it works almost perfectly, and will continue the discussion about the throttle over there.

@Octal450 the 3D branch looks very promising - I'm no stranger to configuring text files, but a little new to FlightGear, could you give an example/explanation how to change the *-t and *-b settings? (or where I can find out) For example, for my Thrustmaster A320 throttle:
TOGA: -1.00
FLX/MCT: -0.5
CLB: 0
IDLE: 0.5
FULL REV: 1.00
All values +-0.05 ish.

Thanks again!

remenary
remenary
 
Posts: 3
Joined: Fri Aug 06, 2021 11:30 am

PreviousNext

Return to Aircraft

Who is online

Users browsing this forum: No registered users and 19 guests