Project FMC simplified for Project Airbus

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

Re: Project FMC simplified for Project Airbus

Post by moskito-x » 16 Mar 2018, 22:32

Bjoern wrote:
16 Mar 2018, 18:22
Posting a list of changes from the old version along with the request for testers would be useful.
Hello Bjoern,

the update information is communicated to the "FMC Airport Manager" users with the respective version.
Forum members who do not use "FMC Airport Manager" : The update information are neither useful nor helpful.

At the moment with
Version 1.0.1

Developed for "FreenavDB Airport" producers.
To help without laborious work on Excel .csv files.

But now ? There are already created .csv files created with Excel ....
I had to enable an import.

That was my mistake.

When importing the various airports, there was a crash after another.
To protect the program I had to catch all sorts of wrong values.
That sounds easier than it is.

Considering what people can do wrong, to edit manually the approximately 7650 commas and values in a file!!
If only I had the import not done.
I would have spared myself a lot of time and trouble.

and now : 60% of program code is only to protect the program from crash.
With import of Airports that are NOT created by "FMC Airport Manager"


At the moment with version 1.0.1
=======================================
Statistics :

- Three years development.
- source code
1.146.175 Letters
/ 1500 --> (standard letters per book page)
= 764,11 Pages
/ 325 --> (standard pages per book)
= 2,35 Books a 325 pages
=======================================

- Control of existing airports.
- Create new airports with many help tools in the application.
- and more

Only users with "FMC V.1.0.1" experience.
Those who can handle the app correct, will get access to the version 1.2.0.

That should protect me the developer from countless "How To : this and that".
There are users who find it easy to find their way around a complex program without reading the manual.
These users are always asking how is this or that.
A friendly call : Please read the manual there it is described.
Answer : I have no time to read the manual. :(

If users use the program with the recommended steps.
Then questions are not a problem! Contrary these are welcome! :)
There is always something to be improved.

Version 1.2 (ready for public release > 6 month)

- a Database
- Visual map of Airports with all waypoints that are present within a radius of 100 nm.
- Drag and drop waypoints to a new position ( If old position not match new charts)
- Typing an existing waypoint name - and the Lat / Lon setting are inserted to all waypoints with same name(in ALL .csv files) automatically.
- and many more

Version 1.3 (ready for public release > 12 month)
- import Navigraph AIRAC
- and many more

Thomas
Last edited by moskito-x on 16 Mar 2018, 23:00, edited 1 time in total.

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

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 16 Mar 2018, 22:56

So the change from the previous to the current version is mainly bugfixes?

I would give the Airport Manager a try to correct at least TXL (which has a bug in a SID or STAR), but the process of applying for each new updated version and running the risk of not being picked because there are no more slots available for the month is simply too inconvenient for me.

If the current version runs well enough, why not simply post it for everyone to download with a disclaimer that stupid questions will not be answered and users must read the manual before using it?
Or lock the program with a password, which is hidden in the manual to make people read it.

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

Re: Project FMC simplified for Project Airbus

Post by moskito-x » 17 Mar 2018, 02:02

Bjoern wrote:
16 Mar 2018, 22:56
So the change from the previous to the current version is mainly bugfixes?
10% are bugfixes for "FMC Airport Manager" 90% are for the already existing created Airports.
Never expected such a sign at such a place.

To check the values ​​of an airport over and over again and all at once makes the program terribly slow and difficult to handle.
To make it fast and not to notice a delay it is divided into different sectors.

These are then executed when the right time for deeper checking is available.

- "OPEN" (SID STAR APPROACH): 40% of the error control.
- "Line Test": 35% of the error control.
- "Manual Maintenance" 25% of the error control.

If an error can not be assigned exactly, the "Manual Maintenance" is called.

There, an attempt is made to alert the user to detected errors and offered "Try to solve" buttons.

As I said it is easier to visually display wrong values.
An experienced user will soon know what's wrong and change it.
An inexperienced user who has never worked with excel on the .csv files is overwhelmed.

The simplest possibility is to say. Here is something wrong I just do not know what.
- is it a comma in the wrong place?
- there are too many or too few commas in the waypoint data.
- is it a wrong value in the wrong data field
- is it because a missing comma before the data. Now all the data have moved forward one data field.
- the whole waypoint with all its data is just a remnant of a waypoint data that has no consecutive number. (just forgot to assign a number.

It can not help a user to inform with "Wrong value at position "LATITUDE"should be a numeric value like 123.123456"
Now the user change the value to "123.123456" but the "ICAO name of the waypoint" (due the missing comma is now overwritten) with "123.123456"

hundreds of possibilities.
This is not a chess program that finds the greatest likelihood and then serves the solution on the silver tray.

I tried to do something like this.
In some exceptions was cases ...
In doing so, the airport data was destroyed more than it was to be improved.

So I had to let this kind of help out to the user.
Because there was no guarantee for a success to improve.

Always remember. A change in the data in one place can easily have an impact on a completely different position.

A comma seperated .csv file is a Database.
In real life: normal databases are no longer opened with a hint.
- Database corupted!

Without pointing out where the errors are.

This is done for a simple reason.
No database server can decide.
- when writing to the hard disk a sector error arose.
- The hard disk has invalid sectors or more worst case is damaged.
- the database has been changed by an unwanted program.
- etc.

Therefore, simply the database is declared as invalid and ready.
Should the user take care of a restore from a backup.

This can not do my program just like that.
The user is disappointed and expects help.
So I offer the user a solution he should decide for himself what is wrong.
This is visually much easier to do than for a software code.

It offers the waypoints line by line to visually let the user decide what is missing or wrong.

Here's a riddle for you.

Look at next picture where is the mistake.
Hint: look at the column STATUS the line with the most content (also !! are in) is the right line.
What is wrong.
(normally you would select that line and the Hint to the mistake is shown.)
(But it's only a picture. So no click at the picture can help) ;)

Image

Bjoern wrote:
16 Mar 2018, 22:56
I would give the Airport Manager a try to correct at least TXL (which has a bug in a SID or STAR),
but the process of applying for each new updated version and running the risk of not being picked because there are no more slots available for the month is simply too inconvenient for me.
I can not know in advance how high the interest in "FMC Airport Manager" is.
If you read my last post correctly, there are no more restrictions.
That does not mean that will not come again when the rush becomes too big.
But all accepted users have no restrictions and also not in the future.

Register once and you're done.

More users, more questions, more time, etc.
At the moment I have almost no time to program. because
- help me here and help me there
- the manual must be completed urgently.
changes and new functions have to be added.
- newly discovered Airport mistakes must be treated.
- etc
Bjoern wrote:
16 Mar 2018, 22:56
If the current version runs well enough, why not simply post it for everyone to download with a disclaimer that stupid questions will not be answered and users must read the manual before using it?
When I do that, I have no control over my development at all.
Everyone downloads it and does what it wants with it.

Hundreds of unknown people ask for help or shower me with spam.

To protect my program, I had to pay 500, - euro.
To a company for professional software protection.
Of course I do not say what protection it is.
That would only make it easier for pirates to crack it.

Some download it just to disassemble the program and make a new design about building some new features and then selling it as their own program.
Many useful features in my program
This can be used well in other FSX applications.

and users must read the manual before using it?
And how can I control that.
A user claims he has read it three times and still does not understand it.
With specific questions, I can see that he has not read it yet.
But how can I prove that, he does not say the truth. He is lying!
Bjoern wrote:
16 Mar 2018, 22:56
Or lock the program with a password, which is hidden in the manual to make people read it.
After all, development would only be as easy as some people imagine.

Clever people open the manual read a page and close it again.
How should I control something like that.
Is this additional effort worth the reason.

Thank you for reading

Thomas

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

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 17 Mar 2018, 16:08

moskito-x wrote:
17 Mar 2018, 02:02

Look at next picture where is the mistake.
Hint: look at the column STATUS the line with the most content (also !! are in) is the right line.
What is wrong.
(normally you would select that line and the Hint to the mistake is shown.)
(But it's only a picture. So no click at the picture can help) ;)
The "O" should be a "zero".

I can not know in advance how high the interest in "FMC Airport Manager" is.
If you read my last post correctly, there are no more restrictions.
That does not mean that will not come again when the rush becomes too big.
But all accepted users have no restrictions and also not in the future.
You're right. I've overlooked that.
When I do that, I have no control over my development at all.
Everyone downloads it and does what it wants with it.

Hundreds of unknown people ask for help or shower me with spam.
I do it like this: No e-mail address, no support via private messages, show people the threads they may use for support. And that's it.
To protect my program, I had to pay 500, - euro.
To a company for professional software protection.
Of course I do not say what protection it is.
That would only make it easier for pirates to crack it.
Why would you need copy protection for a freeware program that's only intended for a very specific purpose?

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

Re: Project FMC simplified for Project Airbus

Post by moskito-x » 17 Mar 2018, 17:53

Bjoern wrote:
17 Mar 2018, 16:08
The "O" should be a "zero".
I'm impressed.
That's right.
Not so easy to find and can be quickly overlooked.
Bjoern wrote:
17 Mar 2018, 16:08
I do it like this: No e-mail address, no support via private messages, show people the threads they may use for support. And that's it.
You do it your way and I do it my way,
Bjoern wrote:
17 Mar 2018, 16:08
Why would you need copy protection for a freeware program that's only intended for a very specific purpose?
The reason for that is easy for me to understand.

I am already working on the 1.2.0 version.
In order not always to switch between the versions 1.0.1 and 1.2.0 I work only on the 1.2.0 version.

My experiences have taught me ...
- if bugs are found.
- new features are incorporated.
- improvements in the program process are to be coded.
- new errors in the existing airports are known.

Then I always have to make these changes in both versions.
There can be quickly forgotten a line.
A different code treatment can not be completely ruled out.
In short, both basic codes are always diverging more and more.
Difficult to manage and keep track of.

That's why I always work on just one version.
All new features and improvements are always the same.
With a compiler call v1 the v2 functions will not be reachable.
So it is in the v.1.0.1 version everything in ... which is also present in v1.2.0. Just not available and not visible.

With a compiler call v2, I can just start where I left off yesterday.

But it has a disadvantage.

It already happened to me that I have provided the v1 users with a version that was compiled with v2.
They have wondered what v1 already can do and so many new features. 8-)

OK shit happens :D

cheers
Thomas

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

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 25 Mar 2018, 17:43

Hello guys,

Sorry for the delay, but I have found a little time this weekend to work on project. So I prepared a pack, with all A32x family updated with Bjoern's VC and nexw feature.

As I began Bjoern, many files are now placed in the "PA A32x_Common" folder:
- VC textures with 1024, 2048 or 4096 choice (orange or white night)
- Engines sounds (3 choices)
- Virtual Cokpit

FD-FMC gauges are now common to all aircraft in this folder. Easy now to update !
Only 3 gauges are specific per aircraft (4 for A321). With this new organisation, Panel can be merged very easily with a new aircraft (A330....)

I am uploading the pack.


What's new on the panel :
I havn't yet completed the LEG and RTE page of MCDU, but I added a security when you want delete a waypoint of the flight plan in these page : If waypoint is in the SID, STAR or Approach, you cannot delete it, because that would occur problem in the FMC. In the RTE page, you have the information about if waypoint is in the SID, STAR or Approach.
With previous version, when you selected a waypoint in the LEGS page, that change the active waypoint in the flight plan : fixed.
Now, Flaps and slats Minimum speed retractation (symbol on PFD and value in MCDU) are dynamic according weight.
Please note that these speed are minimum speed that you MAY retract flaps or slats. Not MUST !

Now HOLD key of the MCDU works to engage an holding pattern.

I fixed some bugs.

I must completed altitude and speed information in the LEGS page....Ok until cruise but false at this time for descent....

Zip file takes 400 Mo !

Links to download : http://freenavdbgroup.com/Temp/A32x%20F ... %202.0.zip

Dll's are not provided; This pack works only if you already use a FD-FMC aircraft (Xmltools.dll must be installed).
I joined one livrery by aircraft type
I added "2.0" at each aircraft folder name. You can keep your old aircraft version if you want. This pack can be added as new aircrafts. Not necessary to delete old gauges in FSX folder.

If you add your own livreries, copy the "texture.cfg" file located in texture folder of this pack in your new texture folder.
You can edit this file to change VC texture color and resolution (change 2048 by 4096 in the line for example...)
please, note that "sound" must be

In the ZIP file, you have a folder FD_FMC with a file : "Config_A32xFD-FMC".
Copy this file in your FSX\FD_FMC folder.

You can configure aircrafts at startup by editing this file with following option :
ColdAndDark,1 <--- set to 0 if you don't want cold and dark state at startup
AutoReset,1 <-- set to 0 if you want disable the autoreset gauge which reloead panel if flight plan chage detection
mbar,1 <-- set to 0 if you want atmospheric pressure in InHg by default
WeightPounds,0 <-- default weight unit 0=weights in kg 1=weights in lbs
Meters,0 <-- 0=feet 1=meters
BlackBox,0 <-- for developers to activate a blackbox gauge


It remains a problem ; There is Night texture issue for the MCDU and I havn't found a solution ....please, can you help me Bjoern ;)

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

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 25 Mar 2018, 17:53

fdd_fr wrote:
25 Mar 2018, 17:43
It remains a problem ; There is Night texture issue for the MCDU and I havn't found a solution ....please, can you help me Bjoern ;)
What problem?

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

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 26 Mar 2018, 07:22

When I turn on the cabin light, MCDU texture disappear. It become black

Panel light off: all is ok
Image

Panel light on : MCDU lost its texture (same thing for 2D gauge:
Image

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

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 26 Mar 2018, 07:32

2 missing files in the pack; I am really sorry. This is 2 bitmaps for IAE ECAMS.

You can download them with following links :

http://freenavdbgroup.com/Temp/ECAM1_MAIN_IAE.bmp
http://freenavdbgroup.com/Temp/IAE_off.bmp


Copy these 2 files in the "\A32x Family FD-FMC 2.0\SimObjects\Airplanes\PA A32x_Common\A32x_MainPanel\" folder

I prepare and upload a new pack....

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

Re: Project FMC simplified for Project Airbus

Post by Flyer10 » 26 Mar 2018, 08:58

I have just loaded V2 up, it looks great. Finally I can see the PFD with landing lights on in P3Dv4. The AP still works for me just fine.

Everything looks correct so far with the exception of two things, keyboard or fsuipc commands for lights don't work, they flip on for a fraction of a second and then turn off. I used the 4096 textures and it looks a bit wrong around the AP button as there's 2 sets of buttons there. I will try the 2048 textures and see if they are ok.

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

Re: Project FMC simplified for Project Airbus

Post by Flyer10 » 26 Mar 2018, 10:18

I finished my first flight, overall, amazing job!
-The N1 take off limit stopped the red line take offs even at max flex.
-The Nav worked perfectly, has the climb and descent coding been worked on? Everything seems to be so much better, even the slow down at 10000 feet.
-new engine sounds are great
-I figured out the lights problem, you changed to lvars which I can use so not a problem. The textures were user error.

now the problems
-I changed, the climb from 85% to 87%, when I typed in 8, the wrong value error came up but didn't disappear when I entered the 7 and pressed the button.
-Int LT off turns off all the displays, the on setting doesn't seems to light up the cockpit.
-The backup instruments seem very, very bright. Any chance they could be turned down a bit or linked to an ecam brightness switch?
-No ADF or VOR pointers on the MFD
-No vref on airports not in the database.

I couldn't find the altitude to switch to approach mode, it would be nice if the user could do that at any time by pressing "select APPR" in the new FMC.
I think I will using the v2 release as my FD planes now.

Also, is there a 64 bit version of the 2 gauges in the common folder?

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

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 26 Mar 2018, 10:50

I checked 3 VC light criteria for all aircraft with quite different results.

VC doomlight function / ECAM dim light does not work / Overall cockpit light during night (doomlight unswitched) much too bright .
"ok"= works fine
"-" does not function

A318: ok / ok / ok
A319_CFM: - / ok / -
A319_IAE: ok / - / -
A320_CFM: ok / ok / ok
A320_IAE: ok / - / -
A321_CFM: - / ok / ok
A321_IAE: - / ok / -

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

Re: Project FMC simplified for Project Airbus

Post by Flyer10 » 26 Mar 2018, 12:01

Hmmm, I flew the A318 and the cockpit was dark apart from when the taxi or landing lights were on, the white lights shining down were ok.
So are you saying the A318 cockpit lights up from the cabin lights and also the ecams work even with the Int lights switch to off?

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

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 26 Mar 2018, 13:15

Flyer10 wrote:
26 Mar 2018, 12:01
Hmmm, I flew the A318 and the cockpit was dark apart from when the taxi or landing lights were on, the white lights shining down were ok.
So are you saying the A318 cockpit lights up from the cabin lights and also the ecams work even with the Int lights switch to off?

A318: The OVHD INTEG LT must be switched on during night and the VC looks fine as expected, otherwise the VC is nearly dark. The DOME LT can be switched on too and there is a slight additional lighting within the cockpit (it could be a bit more, but this is q of taste). The illumination/ brightness from all 4 glass panels (MFD,ND,ECAM, below ECAM) look fine and can be dimmed individually.

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

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 26 Mar 2018, 14:41

fdd_fr wrote:
26 Mar 2018, 07:22
When I turn on the cabin light, MCDU texture disappear. It become black

Panel light off: all is ok
...

Panel light on : MCDU lost its texture (same thing for 2D gauge:
...
Check the visibility conditions for the illuminated bitmaps in the A32x_FMC_Dummy.xml.

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

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 26 Mar 2018, 14:43

Flyer10 wrote:
26 Mar 2018, 08:58
Everything looks correct so far with the exception of two things, keyboard or fsuipc commands for lights don't work, they flip on for a fraction of a second and then turn off.
That's because they use custom gauge code which ultimately controls the FSX/P3D internal lights. Use the VC controls.

- E: Ah, you already found out.

Flyer10 wrote:
26 Mar 2018, 10:18
Also, is there a 64 bit version of the 2 gauges in the common folder?
Haven't we discussed this before?

https://douglassdawson.ca/
-> XML sound gauge -> Rename A32x_Sounds.gau -> Overwrite
-> XML Config gauge -> Rename A32x_XML_Config.gau -> Overwrite

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

Re: Project FMC simplified for Project Airbus

Post by Flyer10 » 26 Mar 2018, 15:19

wulfbindewald wrote:
26 Mar 2018, 13:15

A318: The OVHD INTEG LT must be switched on during night and the VC looks fine as expected, otherwise the VC is nearly dark. The DOME LT can be switched on too and there is a slight additional lighting within the cockpit (it could be a bit more, but this is q of taste). The illumination/ brightness from all 4 glass panels (MFD,ND,ECAM, below ECAM) look fine and can be dimmed individually.
I had the displays set to 50%, that's why they switched off because they were so dark. Turning them up to 100% brings them back.

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

Re: Project FMC simplified for Project Airbus

Post by Flyer10 » 26 Mar 2018, 15:22

Bjoern wrote:
26 Mar 2018, 14:43

Haven't we discussed this before?

https://douglassdawson.ca/
-> XML sound gauge -> Rename A32x_Sounds.gau -> Overwrite
-> XML Config gauge -> Rename A32x_XML_Config.gau -> Overwrite
Yes we did but the sounds gauge is a huge 648kb while the DD one is 175kb so I assumed it was a different gauge. I matched up the other one fine because they were the same size.

I didn't remove the post as I thought it would be something else considering it's 4 times the size of the one one the DD site.

Another bug, slowing at the 10000 feet point worked once and then I blew through it 3 times without any attempt to slow down or pitch up to adhere to the 250kn restriction. Everything I have posted is about the A318, I will try the A321 CFM tomorrow.

Coki, if you are around, you asked what you could do with textures. The whole new cockpit looks great with the exception of the 5 buttons above the map range selector. Everything else is pin sharp.

I can confirm Wulfs findings on the A319 and A321 CFM, also, in the A321FCM, switching off the cockpit light (even though it doesn't work) really does switch of the displays, even at 100%.

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

Re: Project FMC simplified for Project Airbus

Post by Flyer10 » 26 Mar 2018, 15:57

Sorry for the new post but I am fixing the lights.
For the A321, overwrite these lines.
light.8=10, 47.00, -1.00, 3.00, fx_vclighth // VC Day Lighting eclairage jour
light.9=4, 48.00, 0.00, 5.00, fx_vclighth // eclairage nuit Cockpit
For the A318
light.8= 10, 45.90, -1.00, 5.50, fx_vclighth , // eclairage de jour du VC Par Fdd
light.9= 4, 46.90, 0.00, 1.00, fx_vclighth , // Night pilot cabin lighting by Francois dore

These should give you a dim light with the middle click and a pretty bright light with the upper selection. The former good for flying and the latter good for pre flight.

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

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 26 Mar 2018, 17:04

yes, sorry, I forgot to edit the dome and pilots's night light with the Bjoern's VC location. Currznt values were to old VC.

Copy the 2 lines about VC day lighting and night lighting of the from the aircraft.cfg where that's works fine in all other aircraft.cfg files

Example, if as said wulf that's ok for A320 CFm, 2 lines are :
light.4=4, 44.50, 0.00, 3.00, fx_vclight , //cokpit Night ligthing
light.7=10, 47.25, -1.00, 2.90, fx_vclight , // VC day lighting

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

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 26 Mar 2018, 17:18

Bjoern wrote:
26 Mar 2018, 14:41
fdd_fr wrote:
26 Mar 2018, 07:22
When I turn on the cabin light, MCDU texture disappear. It become black

Panel light off: all is ok
...

Panel light on : MCDU lost its texture (same thing for 2D gauge:
...
Check the visibility conditions for the illuminated bitmaps in the A32x_FMC_Dummy.xml.
I tried to add <Bright>True</Bright> in bitmap bacground declaration : no effect
I duplicated the background bitmap by adding a "night" suffix (A32x_FMC_Dummy_night.bmp) ....no effects.

Sorry I don't understand what's happens.

information : I renamed A32x_FMC_Dummy.xml in A32x_MCDU.xml in this panel.

When you will have a little time to check this issue...not urgent. :)

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

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 26 Mar 2018, 17:51

The favourized VC internal light definition can now be generally adopted to all 7 Aircraft versions, because the VC is fully standardized for all versions and located in one position (independent of the aircraft length). No need to vary, but all VC internal lights will be looking the same in all aircraft.

In addition I adopted my favourite "eyepoint = 45.5,-1.74, 3.8" definition from the A320_CFM to all 7 aircrafts too.

To Flyer10: Your VC light approach for the A321 looks fine, a good alternative. Please be aware that there are 2 different effect files "fx_vclight" and "fx_vclighth". Both work fine but need quite different "virtual" light positions/coordinates as shown above.

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

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 26 Mar 2018, 19:32

Flyer10 wrote:
26 Mar 2018, 15:22
Yes we did but the sounds gauge is a huge 648kb while the DD one is 175kb so I assumed it was a different gauge. I matched up the other one fine because they were the same size.

I didn't remove the post as I thought it would be something else considering it's 4 times the size of the one one the DD site.
That's probably because the developer left some debug code in. It doesn't alter the functionality, but it's there.
Coki, if you are around, you asked what you could do with textures. The whole new cockpit looks great with the exception of the 5 buttons above the map range selector. Everything else is pin sharp.
Those buttons have nothing to do with the VC textures as they are basically gauges.


fdd_fr wrote:
26 Mar 2018, 17:04
yes, sorry, I forgot to edit the dome and pilots's night light with the Bjoern's VC location. Currznt values were to old VC.

Copy the 2 lines about VC day lighting and night lighting of the from the aircraft.cfg where that's works fine in all other aircraft.cfg files

Example, if as said wulf that's ok for A320 CFm, 2 lines are :
light.4=4, 44.50, 0.00, 3.00, fx_vclight , //cokpit Night ligthing
light.7=10, 47.25, -1.00, 2.90, fx_vclight , // VC day lighting
If you want, you can try to move the cockpit to the positions appropriate to the A318, 319 and 321. The new ModelConverterX releases do not seem to have the clickspot bug anymore.
fdd_fr wrote:
26 Mar 2018, 17:18
I tried to add <Bright>True</Bright> in bitmap bacground declaration : no effect
I duplicated the background bitmap by adding a "night" suffix (A32x_FMC_Dummy_night.bmp) ....no effects.

Sorry I don't understand what's happens.

information : I renamed A32x_FMC_Dummy.xml in A32x_MCDU.xml in this panel.

When you will have a little time to check this issue...not urgent. :)
The visibility conditions are in line 650 and 658, e.g.

Code: Select all

<Visibility>(A:LIGHT PANEL, bool) (A:TIME OF DAY, enum) 1 != and (A:TITLE, string) 'PNL_LT_ORANGE' sstr 1 &lt; and</Visibility>
1. Panel light switch must be on
2. Time of day must not be "day"
3. For the orange MCDU, the "title=" line of the [fltsim.x] entry in the aircraft.cfg must contain "PNL_LT_ORANGE" (no quotation marks), otherwise the white one will be displayed.

I don't have any motivation for the Airbus at the moment, so I can't do any real bug fixing work.

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

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 27 Mar 2018, 20:33

All 3 IAE versions have the same ECAM problem: not dimmeable, the checklist click spots (in the botton left) do not work properly.

Prosdocimo
Posts: 250
Joined: 10 Oct 2014, 12:05

Re: Project FMC simplified for Project Airbus

Post by Prosdocimo » 29 Mar 2018, 17:46

fdd_fr wrote:
25 Mar 2018, 17:43
Hello guys,

Sorry for the delay, but I have found a little time this weekend to work on project. So I prepared a pack, with all A32x family updated with Bjoern's VC and nexw feature.

As I began Bjoern, many files are now placed in the "PA A32x_Common" folder:
- VC textures with 1024, 2048 or 4096 choice (orange or white night)
- Engines sounds (3 choices)
- Virtual Cokpit

FD-FMC gauges are now common to all aircraft in this folder. Easy now to update !
Only 3 gauges are specific per aircraft (4 for A321). With this new organisation, Panel can be merged very easily with a new aircraft (A330....)

I am uploading the pack.


What's new on the panel :
I havn't yet completed the LEG and RTE page of MCDU, but I added a security when you want delete a waypoint of the flight plan in these page : If waypoint is in the SID, STAR or Approach, you cannot delete it, because that would occur problem in the FMC. In the RTE page, you have the information about if waypoint is in the SID, STAR or Approach.
With previous version, when you selected a waypoint in the LEGS page, that change the active waypoint in the flight plan : fixed.
Now, Flaps and slats Minimum speed retractation (symbol on PFD and value in MCDU) are dynamic according weight.
Please note that these speed are minimum speed that you MAY retract flaps or slats. Not MUST !

Now HOLD key of the MCDU works to engage an holding pattern.

I fixed some bugs.

I must completed altitude and speed information in the LEGS page....Ok until cruise but false at this time for descent....

Zip file takes 400 Mo !

Links to download : http://freenavdbgroup.com/Temp/A32x%20F ... %202.0.zip

Dll's are not provided; This pack works only if you already use a FD-FMC aircraft (Xmltools.dll must be installed).
I joined one livrery by aircraft type
I added "2.0" at each aircraft folder name. You can keep your old aircraft version if you want. This pack can be added as new aircrafts. Not necessary to delete old gauges in FSX folder.

If you add your own livreries, copy the "texture.cfg" file located in texture folder of this pack in your new texture folder.
You can edit this file to change VC texture color and resolution (change 2048 by 4096 in the line for example...)
please, note that "sound" must be

In the ZIP file, you have a folder FD_FMC with a file : "Config_A32xFD-FMC".
Copy this file in your FSX\FD_FMC folder.

You can configure aircrafts at startup by editing this file with following option :
ColdAndDark,1 <--- set to 0 if you don't want cold and dark state at startup
AutoReset,1 <-- set to 0 if you want disable the autoreset gauge which reloead panel if flight plan chage detection
mbar,1 <-- set to 0 if you want atmospheric pressure in InHg by default
WeightPounds,0 <-- default weight unit 0=weights in kg 1=weights in lbs
Meters,0 <-- 0=feet 1=meters
BlackBox,0 <-- for developers to activate a blackbox gauge


It remains a problem ; There is Night texture issue for the MCDU and I havn't found a solution ....please, can you help me Bjoern ;)
Hi thank you! Does it include Bjoern latest modifications?

Prosdocimo
Posts: 250
Joined: 10 Oct 2014, 12:05

Re: Project FMC simplified for Project Airbus

Post by Prosdocimo » 29 Mar 2018, 20:33

fdd_fr wrote:
26 Mar 2018, 07:22
When I turn on the cabin light, MCDU texture disappear. It become black

Panel light off: all is ok
Image

Panel light on : MCDU lost its texture (same thing for 2D gauge:
Image
Hi I found that if you remove the black color to the bimap (add aplha channel to the black color, in A32x_FMC_dummy_white.bmp file), you get it right.. The issue is that the popup FMC window becames transparent! But if you know how to add a background color to this popup, you may fix it

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

Re: Project FMC simplified for Project Airbus

Post by Flyer10 » 30 Mar 2018, 08:31

Prosdocimo wrote:
29 Mar 2018, 17:46

Hi thank you! Does it include Bjoern latest modifications?
Yes, from what I can tell it looks 100% like Bjoerns VC but uses the FD autopilot which means you can use hardware or buttons to control it.

Prosdocimo
Posts: 250
Joined: 10 Oct 2014, 12:05

Re: Project FMC simplified for Project Airbus

Post by Prosdocimo » 30 Mar 2018, 16:53

Hi Flyer10, not properly the latest.
In François v2.0, the file Airbus_A320_Int_Mod.mdl is dated 04/06/2017 (in PA320common/model.cockpit. In my previous airbus installation it was 19/11/2017 so more recent. There were several changes

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

Re: Project FMC simplified for Project Airbus

Post by Flyer10 » 31 Mar 2018, 09:41

I don't doubt that but I can't tell ant difference in the VC although the AP control is quite clearly different.

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

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 31 Mar 2018, 10:13

The Airbus_A320_Int_Mod.mdl dated 19/11/2017 includes e.g. the remodelled engine start switches with a double-click-security and the remaining light switches on the OHP. All the additional features only work properly with an updated system related xml (Bjoern provided the system related files in Nov. too). I hope that Francois integrates this addon in a further A32x release.

The overall A32x data path structure is already "prepared" for this next step....

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

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 01 Apr 2018, 17:15

Sorry for VC model error.

Current gauges works with the 19/11/2017 VC except Seatbel and No smoking switch.

I have updated and fixed Overhead gauge and A32x Common gauge and I will upload in few minutes with lastest VC.

Prosdocimo, I don't know how to work with alpha channel on bitmap. Have you found a solution to black texture ?

I don't know if I am alone to have this texture problem or if you have it so....

Someone get the texture ?

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

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 01 Apr 2018, 17:27

Gauge bitmaps are not in 32 bit format and therefor do not support alpha channels. If their image properties are set to "Transparent=True" in the gauge (which I think is default), then pure black (RGB 0,0,0) is drawn as transparent.

Fliptod
Posts: 33
Joined: 20 May 2013, 21:36

Re: Project FMC simplified for Project Airbus

Post by Fliptod » 01 Apr 2018, 19:42

Is anyone else having the same problem that the radio stack doesn't come on?

Prosdocimo
Posts: 250
Joined: 10 Oct 2014, 12:05

Re: Project FMC simplified for Project Airbus

Post by Prosdocimo » 01 Apr 2018, 21:09

fdd_fr wrote:
01 Apr 2018, 17:15
Sorry for VC model error.

Current gauges works with the 19/11/2017 VC except Seatbel and No smoking switch.
R
I have updated and fixed Overhead gauge and A32x Common gauge and I will upload in few minutes with lastest VC.

Prosdocimo, I don't know how to work with alpha channel on bitmap. Have you found a solution to black texture ?

I don't know if I am alone to have this texture problem or if you have it so....

Someone get the texture ?
I opened A32x_FMC_dummy_white.bmp with Gimp. I transformed the black in transparent (alpha) and then i overwrote the file. In this way the MCDU texture is fine on the pedestal at night. But popup texture is transparent. Thus I opened panel.cfg and modified Window07 with background=10,20,30. Is not the fix.. but at least popup is not transparent! I can give you the modified bmp

Prosdocimo
Posts: 250
Joined: 10 Oct 2014, 12:05

Re: Project FMC simplified for Project Airbus

Post by Prosdocimo » 02 Apr 2018, 06:55

Fliptod wrote:
01 Apr 2018, 19:42
Is anyone else having the same problem that the radio stack doesn't come on?
Hi, me too. But i set "avionics on/off" by choosing a keyboard key, and in this way it comes on. I don't know where is the avionics switch in the VC. On the radio panel there is also a small switch to make working the autopilot

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

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 02 Apr 2018, 09:53

Hi Prosdocimo,

Thanks for your help and solution. Yes, I would like to get your bmp file.

About readio stack panel and Avionics switch, I am checking.....

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

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 02 Apr 2018, 11:50

As long as François has implemented the november version of A32x_RMP_ACP.xml into the latest beta, the FSX avionics switch is controlled by the Radio Management Panel master switch.

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

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 03 Apr 2018, 08:21

ok, I uploaded panel gauge update :http://freenavdbgroup.com/Temp/PA%20A32x_Common.zip

- Fix Avionics problem (avionics is now on when you turn on battery or do a CTRL+E startup)
- Last Bjoern's VC provided with gauges fixed to overhead

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

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 03 Apr 2018, 09:39

Bjoerns last Airbus_A320_Int_Mod.mdl dated 19/11/2017 to be included and activated in the "model.cockpit" folder at first, but...
the engines can not be started although the engine starter is correctly engaged (double click) and the Cockpit int lights at night do not work although switchable.

Prosdocimo
Posts: 250
Joined: 10 Oct 2014, 12:05

Re: Project FMC simplified for Project Airbus

Post by Prosdocimo » 03 Apr 2018, 13:47

Bjoern changed the start procedures in this way:

"Engine startup is revised. Changes from François procedure:
- You can't start both engines at the same time (bleed air constraints)
- "Crank" mode on the engine mode selector is now operational (engage starter without igniting)
- Fuel cross feed is only required when starting, say, the left engine with the right fuel pump running, not during normal operation (removed the corresponding ECAMS checklist items)
- Autostart is still possible"

I don't know if this may help you Wulf

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

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald » 03 Apr 2018, 14:27

Thanks, Prosdocimo. Unfortunately I am unable to start one engine even switched to crank and fuel cross feed open (Ctrl-E works to start engines sequenced). The light prob persists.

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

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 03 Apr 2018, 19:07

Engine management is contained within A32X_System.xml, dated November 19th, 2017.

Engine start requires bleed air and fuel pressure.

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

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 08 Apr 2018, 05:49

Hello guys
Unfortunatly, I will be available tout post new airport tomorrow only. Sorry for thé delay.,

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

Re: Project FMC simplified for Project Airbus

Post by fdd_fr » 09 Apr 2018, 17:26

Prosdocimo has fixed VC night texture to solve the transparent issue when panel light is on.

You can download them here : http://freenavdbgroup.com/Temp/FMC_Night_texture.zip

Copy and replace this 2 files in "\A32x_Common\A32xFD-FMC\" folder

Edit panel CFG of each aircraft and in [Window07] section add this line :
BACKGROUND_COLOR=10,20,30

now, texture is ok in VC. I remains the issue only with the 2D gauges.

Many thanks to Prosdicimo ! ;)


So, other thing, if someone can explain to me what is the "crank" mode to start engine ?

Prosdocimo
Posts: 250
Joined: 10 Oct 2014, 12:05

Re: Project FMC simplified for Project Airbus

Post by Prosdocimo » 09 Apr 2018, 19:57

Hi François thank you.
There is still a small issue about the MCDU popup tat night. There is too much contrast and thus the characters are a little difficult to read. I don't know how to fix it, maybe reducing contrast or bightness? I'll try next

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

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 10 Apr 2018, 16:40

fdd_fr wrote:
09 Apr 2018, 17:26
So, other thing, if someone can explain to me what is the "crank" mode to start engine ?
Block igniters and then run the starter. Useful for clearing vapors or pools of fluids from the engine or preinjecting some fuel.

See here: https://www.metabunk.org/attachments/do ... pdf.16733/

SimonKelly
Posts: 7
Joined: 14 Apr 2018, 21:38

Re: Project FMC simplified for Project Airbus

Post by SimonKelly » 14 Apr 2018, 21:42

Don't exactly know where else to put this but I edited the cockpit textures based on CokiBH's so the flap indicator now has positions 1, 1+F, 2, 3, and Full, and I couldn't find any way of contacting him but I'd like to share them. I know it's a small thing but I like being able to check the flap handle and know for certain where the flaps are. If anyone can put me in contact with the FreeNav team or Coki, I'll send them across? Also free to work on any more texturing if I can lend a hand?

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

Re: Project FMC simplified for Project Airbus

Post by Flyer10 » 15 Apr 2018, 07:44

Those textures would be wrong, 1 and 1+F are the same detent and the computer decides when to use each one.

" In addition to the slats, the flaps will also extend to 1 when…

Anytime on the ground.
If we’re planning a departure, we want our flaps out, not just the slats. Airbus logic knows this and the flaps will extend too.
Anytime we’re retracting from flaps "greater than" 1, the flaps will stay at 1 until we move them to "O" position.
Sequentially this makes sense when retracting. We wouldn’t want them to go from flaps 2 to up, losing our lift, until we're ready

When won't we get flaps 1 when we select the 1 position?
When airborne and we go from a clean wing to flaps 1 selection we only get the slats. Flaps will not come out until we select flaps 2 position.

When flying this plane everyone knows that Flaps 1 on arrival doesn’t really do a whole lot for slowing their plane. Do they know why? I'm not sure how many remember that we don't even have flaps when we select 1."

Image

SimonKelly
Posts: 7
Joined: 14 Apr 2018, 21:38

Re: Project FMC simplified for Project Airbus

Post by SimonKelly » 16 Apr 2018, 12:46

While that's true, the current aircraft doesn't simulate that, and 1 and 1+F use different detents, If and when it gets simulated, the textures as they are would work, but for the mean time, they don't.

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

Re: Project FMC simplified for Project Airbus

Post by Bjoern » 16 Apr 2018, 22:18

Unless François changed something, the 1+F auto logic is in, with a bit of a bug in that the flaps will auto-retract to 1 when accelerating past 100 KIAS.

Post Reply

Who is online

Users browsing this forum: No registered users and 17 guests