Project FMC simplified for Project Airbus

fdd_fr
Posts: 1669
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 20 Oct 2017, 09:52

oh sorry. I missed A32x_system.xml file.

I fix the issue and post a fixed panel saturday or sunday.

wulfbindewald
Posts: 431
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 20 Oct 2017, 13:25

The red beacons are already working even w/o (!) the A32x_system.xml file.
If this file will be included in the A320_CFM folder, then there might be a double function for the red beacons. The beacon lights are pulsing and this will be visible inside the VC too.
This was not the case with the FORK version. Here all new lights were switchable and working w/o any neg. light effect inside the VC.
Please check.

EDIT: The culprit is the additional light in the aircraft.cfg in the [LIGHTS] section: The de-activation from "light.4=4,....." solved the pulsing light issue on my end.

fdd_fr
Posts: 1669
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 23 Oct 2017, 13:59

In panel that I post last week, VC light switch don't work because code about these switchs are in A32X_System.xml file. But lights switchs in the 2D panel works.

So I am preparing a new panel pack file, but I have some issues with the FBW protection that is in the A32X_System.xml file. When I set aircraft with a high bank, SEC1 is disconnected : ok.
but if you set more joystick input, you can overide the 30° bank limit
But when I recovery a right bank (0) , SEC1 switch flashes.

So for the moment, I disabled in the file the FBW protection and restored my old code in A320_FMS_Com.xml file. So I just added in my protection code a condition to work only in Direct Law.

Bjoern
Posts: 149
Joined: 16 Sep 2016, 18:07

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 23 Oct 2017, 15:56

The light switches on the 2D panel work without A32x_System.xml because I didn't modify it.

Flyer10
Posts: 128
Joined: 01 Jan 2017, 14:59

Re: Project FMC simplified for Project Airbus

Post by Flyer10 » 27 Oct 2017, 10:43

Is there any tick to get the VOR or ADF needles to work? I thought you just needed to use the switches under the range switch but this doesn't seem to work even though it shows the thin and fat arrows in the corner of the display.

Also, I think it would be a good idea if you can get the ILS switch for force the aircraft into approach mode.

wulfbindewald
Posts: 431
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 27 Oct 2017, 13:25

Flyer10 wrote:
27 Oct 2017, 10:43
Is there any tick to get the VOR or ADF needles to work? I thought you just needed to use the switches under the range switch but this doesn't seem to work even though it shows the thin and fat arrows in the corner of the display.
Have you switched the navigation controller in the EFIS to VOR or NAV? All ok on my end using A320 panel 2.0a.
EDIT: Now I could duplicate this issue with the FMC/flightplan activated. The needles work on ground, but not after take-off...they disappear. A Q for Francois.
Flyer10 wrote:
27 Oct 2017, 10:43
Also, I think it would be a good idea if you can get the ILS switch for force the aircraft into approach mode.
ILS capture mode to be activated with the APPR button in the FCU area (bottom right).

Flyer10
Posts: 128
Joined: 01 Jan 2017, 14:59

Re: Project FMC simplified for Project Airbus

Post by Flyer10 » 28 Oct 2017, 08:30

I was trying to see them in FMC mode, I would then change to Nav for a Vor approach once I was certain where I was. I am sure it used to work but cant remember when it stopped working.

When I said Approach mode, I meant the actual Airbus mode, say I have a diversion or need to return to the departing airport, there's no way to activate ILS, I think it would make sense for the ILS button to activate the approach mode (by that I mean the under 3000 feet AGL ready for landing mode) too at any point.

Edit, the A330 beta works fine so it's just a problem on the A32X.

moskito-x
Posts: 46
Joined: 29 Nov 2014, 19:58

Re: Project FMC simplified for Project Airbus

Post by moskito-x » 04 Nov 2017, 00:09

It's time.
FMC Airport Manager V 1.01 is ready for testing.

IMPORT (an FreenavDBgroup existing one)
- Error controll (yes there are some) ;)
- Change to match newer CHARTS ...
- etc.

EXPORT
- You want fo fly from an Airport with SID, but not available?
- Look at a CHART and choose the SID you like (of course weather/wind and direction. Of course, that should also be taken into account)
- create ONE SID or all and EXPORT and ready to use.
- Same for STAR's
-

All members of "Project FMC simplified for Project Airbus" can download the program and create their own SID and STARS, Appr. etc. per airport.
For a normal User, these are of course not official and only suitable for his/her own use.

Above does not apply to "FreenavDBgroup Airport developers", they know exactly what to do and what to look for.

Limit:
All recognized FreenavDBgroup Airport developers have no Limit.
All others are considered after the receipt of a PM to me.(In the order of receipt of request)
Currently: 10 "Project FMC simplified for Project Airbus" users per month.
This limit should suffice to check any questions and bugs.

The personal message (PM) should have following content

============================================================
Name :
Email address (download link will be sent to ) :
============================================================

The manual for "FMC Airport Manager V 1.01" is in a beginning state.
It is expanded daily.


Thomas

fdd_fr
Posts: 1669
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 05 Nov 2017, 07:01

Hello Mosquito,

Thank for this good news ! I send you a PM

New airports are online :

New airports :
CYXT - Terrace - Canada by Wulf Bindewald
DFFD - Ouagagoudou - Burkina Faso by Georges
KJAX - Jacksonville - USA (Florida) by Francois Dore
KJAX - Jacksonville - USA (Florida) by Francois Dore (version with current runway name for addon scenery updated)
LDPL - Pula - Croatia by Martien Van Rooten
LDRI - Rijeka - Croatia by Martien Van Rooten
LTAF - Adana - Turkey by Martien Van Rooten
LTBS - Dalaman - Turkey by Martien Van Rooten
LTCG - Trabzon - Turkey by Martien Van Rooten
LTFJ - Sabiha (Istamboul) - Turkey by Martien Van Rooten
TGPY - Saint-Georges - Grenada by Wulf Bindewald
TTCP - Scaborough - Tobago by Wulf Bindewald
TTPP - Port of Spain - Trinidad by Wulf Bindewald
YSSY - Sydney - Australia by Francois Dore


Updates :
KACV - Arcata - USA (california) by Wulf Bindewald
KBFL - Bakersfield - USA (California) by Wulf Bindewald
KBUR - Burbank - USA (California) by Wulf Bindewald
KFCA - Kalispell - USA (Montana) by Wulf Bindewald
KLGB - Long Beach - USA (California) by Wulf Bindewald
KONT - Ontario - USA (California) by Wulf Bindewald
KPSP - Palm Spring - USA (California) by Wulf Bindewald
KSNA - Santa Ana - USA (California) by Wulf Bindewald
PADQ - Kodiak - USA (Alaska) by Wulf Bindewald
PADQ - Kodiak - USA (Alaska) by Wulf Bindewald (version for FTX airport scenery)
PAEN - Kenai - USA (Alaska) by Wulf Bindewald
PAFA - Fairbanks - USA (Alaska) by Wulf Bindewald
PAHO - Homer - USA (Alaska) by Wulf Bindewald
PAHO - Homer - USA (Alaska) by Wulf Bindewald (version for FTX airport scenery)
PAKT - Ketchikan - USA (Alaska) by Wulf Bindewald
PAVD - Valdez Pioneer - USA (Alaska) by Wulf Bindewald
PAWG - Wrangell - USA (Alaska) by Wulf Bindewald
SKBG - Bucaramanga - Clombia by Carlos Maria Diaz


New AIRAC files :
FreenavAIRAC_11042017.BGL
XFMC_11042017.BGL

moskito-x
Posts: 46
Joined: 29 Nov 2014, 19:58

Re: Project FMC simplified for Project Airbus

Post by moskito-x » 05 Nov 2017, 08:24

Hello Francois,

Got no PM until now :(

Thomas

Edit : gotcha
Send you a PM back. Please read

Thomas

fdd_fr
Posts: 1669
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 05 Nov 2017, 15:41

ok, I answered ;)

I uploaded a new beta of the panel : PA A320 FD-FMC 2.0b

VC light switch fixed to work without bug with overhead 2D.
some change on ND approach readings and add some initialization code required by Bjoern's new variables.

A32x_system.xml file is not required now. Code has been dispatched in other gauges.

I have to work again on TCAS, because it seems that altitude selection doesn't work currently....

fdd_fr
Posts: 1669
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 05 Nov 2017, 16:02

oh there is a bug in case of rain. A wrong WAV file declaration....and your FSX may crash....

- go in the "\SimObjects\Airplanes\PA A32x_Common\"
- edit "A32x_Sounds.ini" file
- you must replace the line "Sound38=precip/c2prec1.wav,100" by this line "Sound38=./Sound/precip/c2prec1.wav,100"

Sorry for this mistake....

wulfbindewald
Posts: 431
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 05 Nov 2017, 16:18

A320_2.0b:
Now rain sound works fine.
Several VC switches do not work on my end. They all automatically switch off again after trying to switch on.

Polus_WAW
Posts: 3
Joined: 08 Oct 2017, 18:40

Re: Project FMC simplified for Project Airbus

Post by Polus_WAW » 05 Nov 2017, 18:04

wulfbindewald wrote:
05 Nov 2017, 16:18
A320_2.0b:
Now rain sound works fine.
Several VC switches do not work on my end. They all automatically switch off again after trying to switch on.
APU can't turning on, ADIRS can't turning on, and automatically switch off after pushing. Can't fly.

Regards,
Polus

BTW, this is my first post here. Congrats to whole FD-FMC team, pretty good job!

fdd_fr
Posts: 1669
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 05 Nov 2017, 21:08

wulfbindewald wrote:
05 Nov 2017, 16:18
A320_2.0b:
Now rain sound works fine.
Several VC switches do not work on my end. They all automatically switch off again after trying to switch on.
Which switches ?

Do you use the panel.cfg file provided in the pack ? A32x_System.xml file must be disabled in the panel.cfg file
Last edited by fdd_fr on 05 Nov 2017, 21:39, edited 1 time in total.

fdd_fr
Posts: 1669
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 05 Nov 2017, 21:38

Check if you haven't the old A320FD-FMC.cab in the FSX gauges folder. If yes, move this file in the panel folder of the aircraft 1.60

wulfbindewald
Posts: 431
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 06 Nov 2017, 06:05

I am only using the new A320_2.0b folders set and installed both folders 1:1 into the Simobjects/Airplanes folder. The old A320FD-FMC.cab is deactivated in the FSX/Gauges folder.
Most switches are not working: ADIRS, APU, Cabin light and all external lights.

The file A32x_System.xml exists in the A320_CFM folder, but is not activated in the panel.cfg folder. Intended?
EDIT: The activation in the panel.cfg makes it worse. No soln.

fdd_fr
Posts: 1669
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 06 Nov 2017, 07:36

ok. I think that I found the issue. I have uploaded a wrong version.

This pack must fix the issue : http://freenavdbgroup.com/Temp/PA%20A32 ... 202.0b.zip

wulfbindewald
Posts: 431
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 06 Nov 2017, 07:47

Thanks, but the download requires a password.
EDIT: No password more nec. ok.

fdd_fr
Posts: 1669
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 06 Nov 2017, 08:17

link edited. The first link that I wrote was a FTP link. Now this is classic link. Sorry for the mistake

wulfbindewald
Posts: 431
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 06 Nov 2017, 08:36

Now the switches work as expected (similar to the 1.60 configuration). Thanks!
The "sound.CFM" folder is missing. Just copy the previous sound.CFM sound folder into the latest aircraft PA A320FD-FMC_CFM_2.0 folder again.

fdd_fr
Posts: 1669
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 06 Nov 2017, 08:50

yes, I have not provided the aircraft sound folder to avoid to get an heavy file ;)

wulfbindewald
Posts: 431
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 06 Nov 2017, 09:36

The VC light in the cockpit is pulsing during night if the landing lights or the Nav logo lights are switched on. My workaround is to deactivate the additional cockpit lights "light.4=4,....." in the aircraft.cfg [LIGHTS] section although this new dimmed lights.4 are well illuminating the OHPanel during night. I hope there is a better idea to solve this pulsing light issue. Anyone else with the same prob?

Polus_WAW
Posts: 3
Joined: 08 Oct 2017, 18:40

Re: Project FMC simplified for Project Airbus

Post by Polus_WAW » 06 Nov 2017, 14:14

wulfbindewald wrote:
06 Nov 2017, 09:36
The VC light in the cockpit is pulsing during night if the landing lights or the Nav logo lights are switched on. My workaround is to deactivate the additional cockpit lights "light.4=4,....." in the aircraft.cfg [LIGHTS] section although this new dimmed lights.4 are well illuminating the OHPanel during night. I hope there is a better idea to solve this pulsing light issue. Anyone else with the same prob?
I found temporary solution: when situation as above occurs, just turning the panel light off and on again will help :) it's really working on my installation.

Regards

wulfbindewald
Posts: 431
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 06 Nov 2017, 17:16

Polus_WAW wrote:
06 Nov 2017, 14:14
wulfbindewald wrote:
06 Nov 2017, 09:36
The VC light in the cockpit is pulsing during night if the landing lights or the Nav logo lights are switched on. My workaround is to deactivate the additional cockpit lights "light.4=4,....." in the aircraft.cfg [LIGHTS] section although this new dimmed lights.4 are well illuminating the OHPanel during night. I hope there is a better idea to solve this pulsing light issue. Anyone else with the same prob?
I found temporary solution: when situation as above occurs, just turning the panel light off and on again will help :) it's really working on my installation.
Yes, but then no other light relating switch to be toggled. Otherwise the panel light off and on procedure begins again...a temporary solution.

Bjoern
Posts: 149
Joined: 16 Sep 2016, 18:07

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 11 Nov 2017, 02:09

Here's a fork of v2.0B.


Changes:

- All shared elements outsourced to "PA A32x_Common". This includes the VC model, shared textures, all panel files and documentation
- V2.0B changes implemented into v1.60 for, including the IAE ECAMS
- Installation procedure updated for P3Dv4 users
- Some other changes that I've probably made after the latest release (5th/10th of June 2017)


Download:
https://drive.google.com/file/d/0B6K_xi ... sp=sharing


Read the readme, especially the chapter dealing with carrying over repaints!
You'll need to modify some lines of the [fltsim.x] entries (see the template at the top of every aircraft.cfg) and use new texture.cfg files (from "PA A32x_Common\texture.VC_Orange" or "PA A32x_Common\texture.VC_White").



This is the folder structure I prefer for the project since it completely separates the aircraft from the cockpit and all panel elements and drastically cuts down on duplication (minus 50 MB download size, minus 75 MB installed size compared to the v1.60 fork). The only difference between the IAE and CFM models is the ECAMS gauge anyway.
I also reverted lighting system control to A32x_Systems.xml since I want to keep my contributions as separate as possible from François' to facilitate updating for me (and maybe him).

Testing was only done on the ground so far and I'll try to squeeze in a flight tomorrow to see if there's any ill effects or bugs.

fdd_fr
Posts: 1669
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 11 Nov 2017, 10:18

hello,

I have an issue. Sometimes, during a flight, I loose all clickspot area in the VC. Can you tell me if someone has a same issue ?

wulfbindewald
Posts: 431
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 11 Nov 2017, 11:07

Yes, but only if the distance between eyepoint and switch is too big. Try to reduce the distance....

Bjoern
Posts: 149
Joined: 16 Sep 2016, 18:07

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 11 Nov 2017, 12:58

This may happen during dawn or dusk when the panel lights are off or when the eyepoint is too close to the headrest so that the camera is behind the closest polygon.

fdd_fr
Posts: 1669
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 11 Nov 2017, 13:37

thanks ! I change eyepoint and it seems now ok. :)

wulfbindewald
Posts: 431
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 11 Nov 2017, 21:04

Q to Bjoern, is it posible to locate the VC model location x,y,z coordinates in a simple but seperate data file, so that all 4 Airbus A318/319/321 VC positions within each aircraft can be defined easily in each aircraft folder. I think the correct VC location within the aircraft is essential to avoid significant misplacement when you are looking out of the VC e.g. definition similar to coordinate definitions in the intelliscene.cfg.

Bjoern
Posts: 149
Joined: 16 Sep 2016, 18:07

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 12 Nov 2017, 03:15

After the reorganization, I'm doing a bit of minor cosmetical work on the model. One of the things I'm fixing is the display brightness, which was reportedly too low during the day. After outsourcing the displays to a material with slightly different properties, they present themselves like this during the day. Hope that's better.

Image


wulfbindewald wrote:
11 Nov 2017, 21:04
Q to Bjoern, is it posible to locate the VC model location x,y,z coordinates in a simple but seperate data file, so that all 4 Airbus A318/319/321 VC positions within each aircraft can be defined easily in each aircraft folder. I think the correct VC location within the aircraft is essential to avoid significant misplacement when you are looking out of the VC e.g. definition similar to coordinate definitions in the intelliscene.cfg.
No, not possible at all. The only way to alter the physical location without the source file is moving the model with ModelConverterX, at the risk of losing clickspots or other bugs.

I can check how moving the entire cockpit in 3ds Max fits into my workflow and at least deliver .mdl files for the entire A320 family with every release, but I can't really hunt for bugs in FS each and every time since I only want to focus on the A320.

Flyer10
Posts: 128
Joined: 01 Jan 2017, 14:59

Re: Project FMC simplified for Project Airbus

Post by Flyer10 » 12 Nov 2017, 11:31

Bjoern, can you tell me how you change the display brightness please? Is it via xml or is it hard coded into the model?
Gauge brightness in P3Dv4 is a real problem and can often lead to unreadable displays, especially in the Ruth aircraft which seem almost like CRTs with a searchlight powering them.

If you can edit a cockpit, maybe a wall behind the cockpit could stop this happening?

Bjoern
Posts: 149
Joined: 16 Sep 2016, 18:07

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 12 Nov 2017, 11:51

Come on, the display brightness selectors aren't that hard to find.

fdd_fr
Posts: 1669
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 12 Nov 2017, 12:32

I confirm, It is possible only to move forward with modelconverterX (and when you move forward, you move up also)

If you move backward, mouse clickspot stop working.

wulfbindewald
Posts: 431
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 12 Nov 2017, 14:25

FORK A320 V2.0B : Two Issues found so far:

1. Immediate CTD because of missing A320_FlapLever_mod.wav sound file in the "PA A32x_Common/Sounds" folder.
a) Simply delete in the "A32x_Sounds.ini" file the line "Sound40=A320_flaplever_mod.wav" and "Lvar40=A32x_FlapLever_Sound".
I consider that a previous sound.CFM data set will be pasted as usual into the aircraft folder.
All necessary sound files are included in this sound.CFM folder.
or b) Copy and paste into the "PA A32x_Common/Sounds" folder an existing "A320_flaplever.wav" file
(to be found in the sound.CFM folder) and rename it to "Sound40=A320_flaplever_mod.wav".
or c) May be Bjoern provides the next time this magic wav.file.

2. I can not set the flaps with the joystick. Though the flaps can be moved with the mouse (clickspot lever),
but not as usual with the joystick controller.
Both throttles work fine with the joystick.
I crosschecked again with the previous A320 CFM version, where everything works fine.

Flyer10
Posts: 128
Joined: 01 Jan 2017, 14:59

Re: Project FMC simplified for Project Airbus

Post by Flyer10 » 12 Nov 2017, 14:32

Bjoern wrote:
12 Nov 2017, 11:51
Come on, the display brightness selectors aren't that hard to find.
They do nothing to solve the problem, the landing lights shining into the cockpit mean everything is mega bright, add in HDR and its unreadable no matter what settings are used. You won't see it unless you have P3Dv4.

Re the above post, not being able to use a joystick axis for flaps is a pretty big issue.

Bjoern
Posts: 149
Joined: 16 Sep 2016, 18:07

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 12 Nov 2017, 14:59

wulfbindewald wrote:
12 Nov 2017, 14:25
1. Immediate CTD because of missing A320_FlapLever_mod.wav sound file in the "PA A32x_Common/Sounds" folder.
a) Simply delete in the "A32x_Sounds.ini" file the line "Sound40=A320_flaplever_mod.wav" and "Lvar40=A32x_FlapLever_Sound".
I consider that a previous sound.CFM data set will be pasted as usual into the aircraft folder.
All necessary sound files are included in this sound.CFM folder.
or b) Copy and paste into the "PA A32x_Common/Sounds" folder an existing "A320_flaplever.wav" file
(to be found in the sound.CFM folder) and rename it to "Sound40=A320_flaplever_mod.wav".
or c) May be Bjoern provides the next time this magic wav.file.
Known bug and yes, the file will be included in the next upload.
2. I can not set the flaps with the joystick. Though the flaps can be moved with the mouse (clickspot lever),
but not as usual with the joystick controller.
Both throttles work fine with the joystick.
I crosschecked again with the previous A320 CFM version, where everything works fine.
The flap system is custom to prepare implementation of the automatic extension and retraction sequence for the 1/1+F configuration.
Only the standard events like "flaps_up", "flaps_down", "flaps_decr" and "flaps_incr" are implemented via XMLEvents, which covers the default F5 to F8 keys and any controller buttons.

Not sure how masking axis is supposed to work, to be honest.


Flyer10 wrote:
12 Nov 2017, 14:32
They do nothing to solve the problem, the landing lights shining into the cockpit mean everything is mega bright, add in HDR and its unreadable no matter what settings are used. You won't see it unless you have P3Dv4.
No P3Dv4 here. Have you tried the model without HDR?

I can try to exclude all VC materials from being rendered with light bloom, but this won't solve any simulator limitations regarding other light sources like landing lights.

fdd_fr
Posts: 1669
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 12 Nov 2017, 15:17

Hello Bjoern,

Testing your last package.

I think that we cannot work at the same time on the same gauges, because that occurs confusion and work lostand maintenance will be very hard in the future.....
I think that it will be better to dispatch work....

Some remarks :
- I have some issues with the FBW protection : SEC1 turn off at each input on my stick : is it normal ?
- When bank is >30°, aircraft stop : ok, but if you release and push again, you can overide the 30° easily.
- SEC1 command is inverted if you don't use FBW (Direct law) and occurs issues. I propose to you to use your protection only when FBW is full activated (NORMAL LAW). I have an existing variable that can be used :
(L:Law,enum) :
0 = commands disabled
1 = Normal Law : FBW full active
2 = Direct Law : Classic command like an Boeing

I propose to set your protection with FBW full active and let my old protection when Direct Law is used.


You have removed all the init code to get a cold and dark state when start up the flight. May be have you a reason ?
You have removed the auto reset when a new flight plan is loaded. As some users load their flight plan after loaded the aircraft, without auto reset function, they will be a big issue when they landing (wrong airport altitude in the FMC data...). I don't understand why you removed this function.


About folder organization :
I agree that this new organization avoid many duplicate files and I am ok to keep it. So, I am afraid that some users will be lost or will have difficulties to install aircraft or to do updates, because elements are not in classic place.
So for me, I am ok but I think that it will be interesting to get advices of this topic followers.

I haven't yet the time to test other new functions (Traffic gauge). I will do it in during the week.

But the most important AMHO is a better communication between us and dispatch work for a better efficiancy.


Thanks !


Francois

Bjoern
Posts: 149
Joined: 16 Sep 2016, 18:07

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 12 Nov 2017, 15:47

fdd_fr wrote:
12 Nov 2017, 15:17
Hello Bjoern,

Testing your last package.

I think that we cannot work at the same time on the same gauges, because that occurs confusion and work lostand maintenance will be very hard in the future.....
I think that it will be better to dispatch work....
Well, just tell me what you're working on and I'll try to find a way around.

Generally, I'd like to focus on the aircraft systems.
- I have some issues with the FBW protection : SEC1 turn off at each input on my stick : is it normal ?
Yes. The switch on the overhead will have to be masked in future versions.
- When bank is >30°, aircraft stop : ok, but if you release and push again, you can overide the 30° easily.
Control device input runs at frame rate, the gauge running the FBW fix runs at 18 Hz, so it's possible to override the bank protection. Not much I can do about it.
- SEC1 command is inverted if you don't use FBW (Direct law) and occurs issues. I propose to you to use your protection only when FBW is full activated (NORMAL LAW). I have a existing variable that can be use :
(L:Law,enum) :
0 = commands disabled
1 = Normal Law : FBW full active
2 = Direct Law : Classic command like an Boeing

I propose to set your protection with FBW full active and let my old protection when Direct Law is used.
Ideally, there'd be a better solution for the FBW. All that's actually needed is a way to decrease the required controller input.

I've also toyed with the idea of writing a PID controller for the pitch and roll axis and disable the default FBW logic altogether. But the refresh rate limit of 2D gauges would not make this a smooth solution.
You have removed all the init code to get a cold and dark state when start up the flight. May be have you a reason ?
I don't like to have to reset everything every time I load the aircraft. Hence XMLConfig (or, in the next version, a Logger script, coordinated with your FMS load/save script to avoid interference).
As written some time ago, I want to integrate an aircraft manager panel at one point, with buttons for loading, saving and resetting the plane to cold and dark.
You have removed the auto reset when a new flight plan is loaded. As some users load their flight plan after loaded the aircraft, without auto reset function, they will be a big issue when they landing (wrong airport altitude in the FMC data...). I don't understand why you removed this function.
Because it reset the aircraft right upon touchdown during a flight for me. So it had to go.

Normally, loading a new flight plan in FSX' flight planner and setting up the FMS should not interfere with the other aircraft systems in any way. After all, real crews don't shut down the entire aircraft during short turnarounds at the destination either, but just plug a new flight plan into the FMS while retaining APU/GPU power and other things.

About folder organization :
I agree that this new organization avoid many duplicate files and I am ok to keep it. So, I am afraid that some users will be lost or will have difficulties to install aircraft or to do updates, because elements are not in classic place.
So for me, I am ok but I think that it will be interesting to get advices of this topic followers.
It will make things even easier when installing other models like the A319, 321 or 318 alongside since you won't need a gauge package for each and every aircraft.
Distribution can be on a pack+add-on basis, with the "common" folder being the base pack and at least one aircraft being the minimum requirement to use the aircraft.
I haven't yet the time to test other new functions (Traffic gauge). I will do it in during the week.
According to DougDawson at FSDev, there'll be a 64bit traffic radar gauge soon, so P3D users can also use the TCAS.
But the most important AMHO is a better communication between us and dispatch work for a better efficiancy.
Oui.

fdd_fr
Posts: 1669
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 12 Nov 2017, 16:06

Auto reset is because FMC get many data when you launch the flight and keep values (many GPS function requires multiple gauge cycle so I get them in one time at the beginning to avoid to run "heavy" code during all the flight with no reason. And also, FSX keep in cache many data between 2 flights and I had many issues in the beginning of the project,

This is the reason why if you do a second flight, or if you load a new flight plan after launch the flight, there will be issues with FMC data.

So, I propose to use FMC_Path.ini as a configuration file with following things (may be extanded to other function...)

AutoReset=0 or 1
Cold&Dark=0 or 1

User will can choose how his aircraft begin....

What do you think about ?
Last edited by fdd_fr on 12 Nov 2017, 16:09, edited 1 time in total.

wulfbindewald
Posts: 431
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 12 Nov 2017, 16:07

Bjoern wrote:
12 Nov 2017, 14:59
2. I can not set the flaps with the joystick. Though the flaps can be moved with the mouse (clickspot lever),
but not as usual with the joystick controller.
Both throttles work fine with the joystick.
I crosschecked again with the previous A320 CFM version, where everything works fine.
The flap system is custom to prepare implementation of the automatic extension and retraction sequence for the 1/1+F configuration.
Only the standard events like "flaps_up", "flaps_down", "flaps_decr" and "flaps_incr" are implemented via XMLEvents, which covers the default F5 to F8 keys and any controller buttons.

Not sure how masking axis is supposed to work, to be honest.
As stated above the axis controlled flap control worked fine in all previous versions. Now it doesn´t.
There is an axis entry in the Joystick controller/Standard.XML which might be missing to be assigned?
<Axis>
<AxName>ZAxis</AxName>
<Index>2</Index>
<AxEvent>AXIS_FLAPS_SET</AxEvent>
<AxScale>-127</AxScale>
<AxNull>1</AxNull>
</Axis>

Bjoern
Posts: 149
Joined: 16 Sep 2016, 18:07

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 12 Nov 2017, 16:23

As I've said, the flap system is custom and therefor, axis control is currently not possible.

wulfbindewald
Posts: 431
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 12 Nov 2017, 16:33

Bjoern wrote:
12 Nov 2017, 16:23
As I've said, the flap system is custom and therefor, axis control is currently not possible.
I hope this can be solved soon, otherwise a development step backwards. Is this solveable by Francois´panel definition?

Flyer10
Posts: 128
Joined: 01 Jan 2017, 14:59

Re: Project FMC simplified for Project Airbus

Post by Flyer10 » 12 Nov 2017, 16:43

Bjoern, here's what I was referring too, I appreciate it's hard to know what's going on when you don't have the sim. The grey speedtape, VSI etc is impossible to read with landing lights on. Is there a brightness switch on the normal FMC cockpit apart from the Int Lt on the overhead panel?

Image

François, that is the A330 beta and there's a weird double ghosting effect on the lettering at night with the A32x cockpit.

Bjoern
Posts: 149
Joined: 16 Sep 2016, 18:07

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 12 Nov 2017, 17:09

wulfbindewald wrote:
12 Nov 2017, 16:33
I hope this can be solved soon, otherwise a development step backwards. Is this solveable by Francois´panel definition?
No guarantees. It's basically a realism vs compatibility issue. Take your pick.
Flyer10 wrote:
12 Nov 2017, 16:43
Bjoern, here's what I was referring too, I appreciate it's hard to know what's going on when you don't have the sim. The grey speedtape, VSI etc is impossible to read with landing lights on. Is there a brightness switch on the normal FMC cockpit apart from the Int Lt on the overhead panel?
And without bloom?

Bjoern
Posts: 149
Joined: 16 Sep 2016, 18:07

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 12 Nov 2017, 18:51

fdd_fr wrote:
12 Nov 2017, 16:06
Auto reset is because FMC get many data when you launch the flight and keep values (many GPS function requires multiple gauge cycle so I get them in one time at the beginning to avoid to run "heavy" code during all the flight with no reason. And also, FSX keep in cache many data between 2 flights and I had many issues in the beginning of the project,

This is the reason why if you do a second flight, or if you load a new flight plan after launch the flight, there will be issues with FMC data.

So, I propose to use FMC_Path.ini as a configuration file with following things (may be extanded to other function...)

AutoReset=0 or 1
Cold&Dark=0 or 1

User will can choose how his aircraft begin....

What do you think about ?
Good idea, at least until I can outsource aircraft state management to a configuration panel.

Or what about a "reset FMC" button in the FMC window?



By the way:

Do the A318, A19 and A320 require different values for some variables in the FMC compared to the A320 (e.g. for VNAV calculation)?

If yes, what about an auto-detection algorithm that will determine the current type of A32x and assign the appropriate values to the e.g. VNAV related variables?
This can be implemented pretty easily by reading the empty weight of the aircraft from the aircraft.cfg ((A:EMPTY WEIGHT,pounds)). So for a range of 90000 to 95000 lbs, the FMC knows that the current aircraft is an A320, while for anything more than 95000 lbs, it's an A321, for a range of 88000 to 90000 lbs, it's an A319 and with less than 90000 lbs an A318.
This would eliminate the need to have three different FMC gauge files for each A32x model and make development and updating easier.

I'm using this algorithm to auto-configure the payload manager for another aircraft and it works really well.


In other news, I managed to improve my FBW fix a bit by cutting down the stick/yoke movement delay to the bare minimum. Letting go of the stick will now make the default FBW logic capture the target pitch and bank better.

I'll take a look at your direct law code and see what I can do with it.

Flyer10
Posts: 128
Joined: 01 Jan 2017, 14:59

Re: Project FMC simplified for Project Airbus

Post by Flyer10 » 12 Nov 2017, 22:19

Bjoern wrote:
12 Nov 2017, 17:09

And without bloom?
Still unreadable, even some payware suffer from it. Its turned down to about 15-20% on that screenshot.
Its because v4 has dynamic light which lights up everything, other planes landing lights even light up your cockpit.

Bjoern
Posts: 149
Joined: 16 Sep 2016, 18:07

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 12 Nov 2017, 23:04

Spent the last few hours fighting with the bloody FBW system and bank and pitch protections. Elaborate attempts at a solution didn't yield a usable result, so in the end, XMLTools will simply block any attempts to bank or pitch the aircraft beyond (user definable) limits. No aileron axis control, no joystick axis blocking, no K: var spam for the elevators or ailerons.
You will get some ugly minor shuddering when hitting a limit, but that's due to the 18 Hz refresh limit of 2D gauges and I can't do anything about it. Made provision to disable the blocking once the stick is moved in the opposite direction.

Time to do more relevant stuff.

Flyer10 wrote:
12 Nov 2017, 22:19
Still unreadable, even some payware suffer from it. Its turned down to about 15-20% on that screenshot.
Its because v4 has dynamic light which lights up everything, other planes landing lights even light up your cockpit.
Just googled the landing light issue and it's model related. Angling the attachpoint of the light source downward is supposed to fix this, but you'll at least need ModelConverterX to do this and do it yourself. Decide if the dynamic lights are really worth the trouble. I can't help you here.

wulfbindewald
Posts: 431
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 13 Nov 2017, 08:08

Bjoern wrote:
12 Nov 2017, 17:09
wulfbindewald wrote:
12 Nov 2017, 16:33
I hope this can be solved soon, otherwise a development step backwards. Is this solveable by Francois´panel definition?
No guarantees. It's basically a realism vs compatibility issue. Take your pick.
Thanks in advance. It is always good, if the sim user can choose his favourite control tool between mouse, keyboard or joystick.
Below a pic, how I "managed" flap settings on my desk with all FDD panel and older fork versions.
Image

Post Reply

Who is online

Users browsing this forum: No registered users and 12 guests