• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSX Project completed: Airbus A320 with simplified FMC with real Vertical navigation management

VC is default A321 (just edited to activate PLN knob position). I havn't adjust longitudinal difference, because it seems that the location is ok or very close... maybe the placement of A321 VC is not right on the A321....(I checked with jetway view from the VC).

I did an adjustment only for the Project PA A330 (I believe that it was you that give me the solution with ModelConverterX)
 
Ah, now I remember. Yes we've had that conversation.

I've also done a quick side-by-side comparison of your included VC model with the external model and it does indeed seem to be at the correct longitudinal and vertical position for an A320!

For the default A321 external model, the VC is a bit too low, but otherwise also at the correct longitudinal location.
 
Obrigado, Francois!

I'll try to do a flight your A320 after I do a bit of research for suitable liveries for the 1980s.

I haven't read the manual yet, so you don't need to answer this if you don't want to.
Can the FMC use default FSX navdata or does it exclusively use your custom database?
 
vous remercier pour votre long effort durable! Je suis impatient de faire voler votre Airbus virtuelle à l'égard de ces belles systèmes que vous avez travaillé. En mon nom personnel, je tiens à vous dire merci pour une belle avions.

(sorry for the bad French, I've never been god at it...)
 
Hi Heretic,

Panel use the FSX GPS macro (Many thanks RPMC, for your workbook ! ) and FSX navaids database. A flight requires just to create a FSX IFR flight plan (.PLN), and the gauge will update the flight plan file with new waypoints, if you do a savegame (FMC data are stored in another file).

Our SID/STAR/Approach custom database adds only missing waypoints required for airports realised. these missing waypoints are compiled in a BGL file (that we call "FreenavAIRAC_mmddyyyy.BGL"). This file is updated each week, when I upload new airports on the freenavdbgroup website. http://freenavdbgroup.com/?page_id=228

Aircraft pack include 130 airports and the AIRAC file for these airports. It is easy to add missing waypoints for us, because a french guy gives me the whole navaids of the world, at the date of end 2014, in XML format. So we have just to do copy and paste for missing waypoints that we need.

Regards



F747Fly : Your french is better than my english :)
 
I'm installing the A320 at the moment and noticed that you've included default effects (fx_vclight.fx, fx_landing.fx, etc...) files in the download.
This is considered bad pactice, so if you're relying on modified default effects for the A320, please rename them (fx_vclight_320.fx or fx_landing_320.fx, etc...) to avoid overwriting any default files.


- Edit:

The aircraft.cfg requires the following add-on effects files:
Code: 
fx_beacon320pa
fx_contrail_320
fx_navgre320pa
fx_navred320pa
fx_PAland
fx_strobe2320pa

Regarding your (modified?) fx_vclight.fx, I've renamed it to "fx_vclight_FDD.fx" and adjusted the file name reference in the aircraft.cfg accordingly.


- Edit2:

The .mdl files also have attachpoints for fx_PAland2.fx. You probably did not include this .fx file because you've added the effects from fx_PAland.fx to the aircraft.cfg, right?
 
Last edited:
I added these FX files during beta test phase, because a tester had missing FX file on his computer. After I forgot to remove them of the pack that I prepared for AVSIM. A mistake ! I will remove them for the update pack !
Fx files are not modified.

You are right for fx_PAland2.fx. fx_PAland.fx is recommended by Project Airbus (they are Project Airbus files).
 
If you want to optimize the update pack any further, here is some more that can be done:

1. The cockpit model only requires
Code: 
A321_reflection.dds
Airbus_A321_*_C.dds
Airbus_A321_*_night_C.dds
so you can decrease download file size by only including these textures.

2. If the CFM model already has a "texture" folder with the shared cockpit textures, the IAE folder does not need to contain another "texture" folder with shared textures.
Simply make sure that the texture.cfg for any repaint of the IAE model reads:
Code: 
[fltsim]
fallback.1=..\..\PA A320FD-FMC_CFM\texture
The IAE model will then look for the VC textures in the CFM model's "texture" folder.

3. You can also put each repaint's lightmap textures into "texture".

4. Convert each paint to DXT5 .dds.

5. The VC model file (Airbus_A321_interior.mdl) can be located in a folder called "PA A320FD-FMC_CFM\model.cockpit" and be shared across all model variations by adapting the model.cfg.
CFM models:
Code: 
[models]
normal=A320_100_CFM/A320_200_CFM
interior=..\model.cockpit\Airbus_A321_interior

IAE models:
Code: 
[models]
normal=A320_100_IAE/A320_200_IAE
interior=..\..\PA A320FD-FMC_CFM\model.cockpit\Airbus_A321_interior


Aircraft folder size before: 397 MB
Aircraft folder size after: 308 MB


Well, 100 MB are not much, but better than nothing at all.
 
Heretic, I think that you don't follow French Politician heroic life and work. :)

If I had the possibility to send an email to our dear Predient, Mr. Hollande, I will recommend you as Minister of Finance to manage our country budget, because you are the king of optimization, and our country is very bad with its 2200 billion € of debts! :twocents:

Heretic for President :)
 
Last edited:
Hahahaha, merci beaucoup François! Mais je ne suis pas sure si mon français est assez bien pour ménager des affaires financiers. ;)
 
Tweaked eyepoint:
Code: 
[Views]
eyepoint=48.22, -2.35, 4.36

Tweaked copilot camera definition (faster panning):
Code: 
[CameraDefinition.001]
Title = "Right Seat"
Guid = {8ff6c134-098d-409f-baec-caba3f683f98}
Origin = Virtual Cockpit
MomentumEffect = YES
SnapPbhAdjust = Swivel
SnapPbhReturn = False
PanPbhAdjust = Swivel
PanPbhReturn = False
Track = None
ShowAxis = YES
AllowZoom = TRUE
InitialZoom = .7
SmoothZoomTime = 2.0
ZoomPanScalar = 1.0
ShowWeather = Yes
XyzAdjust = TRUE
ShowLensFlare=FALSE
Category = Cockpit
PitchPanRate=30
HeadingPanRate=75
PanAcceleratorTime=0
InitialXyz=1.35, 0.0, 0.0
InitialPbh=8, 0, 0
 
I'm trying to fix up the models with ModelConverterX a bit, but they are a buggy mess, especially the lights.
So far, I've managed to set the lightmaps to "UserControlled", which means that you can control the window and vertical stabilizer lighting with the "panel lights" switch now.
I've also removed the satcom antennas from the IAE powered models (they can't be visibility controlled with "title= SATC", etc... on the FSX models anyway) and restored the satcom model for the A320-200 CFM.
The wing flex animation on the CFM models and the attached lights were removed because they couldn't be switched off.

Once I'm done (or given up), I'd send the models to you, so you can decide if you want them or not.
 
Last edited:
Waouh ! Many thanks Heretic !

Have you try the aircraft ? the VNAV behavior (about pitch control during takeoff, climb or descent) ? This is the main subject of this project.

Francois
 
I have to admit that I have not actually flown the aircraft yet because I got sidetracked.

If I ever get to fly it, you'll get feedback on the FMC's behaviour.
 
I've finally done a flight in the A320 and I have to say well done on the FMC and systems!
Without reading the manual, I could at least get the A320 up to cruise altitude with VNAV on a default flightplan. Had to read up on engaging the manged descent mode though, because I could not imagine that you need to press the altitude selector to initiate it. As I do not have the Freenav database installed, I could not do a STAR approach, so I landed manually.


One bug I've encountered is that the "50 ft" altitude callout kept playing after landing and only stopped after I set the altimeter to the current QNH.
Also, the "Minimums" callout made me jump out of my chair because of that alarmclock sound. :confused:

I could not resist and did a small modification to the displays so they don't disappear when they are switched off. Are you interested in implementing it into the next version?

The fuel pump sound is too loud for my taste, so I've lowered the maximum volume to 1300 (sound.cfg -> [Fuel_Pump] -> "maximum_volume=1300").
 
Thanks for your report heretic ! I am very interesting to see your turn off displays look improvement !
 
Bien sûr. It's nothing big, but it looks much better than no screens at all. I've attached the modified files. You can test them without having to delete or overwrite the .cab files. Simply put each folder into the respective "panel.[Engine version]" folder.

I also have new altitude callouts made from a video*, but I need to test their gauge logic** before I can upload them.

* From minute 1:05 :
** I've written a completely new logic.

- Edit:

I've found another minor issue. If the engines are running, the engine bleeds are on and the bleed air source is set to "engines", there is a double temperature readout on the "Bleed" ECAMS page.
 

Attachments

  • screens_off.png
    screens_off.png
    1.2 MB · Views: 961
  • Screens_Off.zip
    Screens_Off.zip
    268.7 KB · Views: 641
Last edited:
You must log in or register to reply here.
Back
Top