If P3DV4 does not accept an Addon Scenery/Scenery folder, then you might define the Airac content like a further 3rd party scenery, with top prio.

Then you have to manually declare the XMLTools64.dll file in the dll.xml.

Have you tried to scroll the dim buttons in the VC from the PFD, ND, ECAM and lower display?
The overall VC and display brightness can be increased by switching the INT LT Dome light on the upper center panel.

Autom translation: Avez-vous essayé de faire défiler les boutons de réglage de la luminosité dans le VC à partir du PFD, du ND, de l'ECAM et de lower display?
La luminosité globale du VC et de l'écran peut être augmentée en allumant la lumière du INT LT Dome sur le panneau central supérieur.

Panel v2.10 - If your problem ONLY persists for the A320_CFM (all other A32x aircraft types are ok), then there is a workaround for the A320_CFM electrical bus problem as follows. Please open the [electrical] section in the A320_CFM aircraft.cfg and exchange the paramaters as follows:

Panel v2.10 - Si votre problème persiste UNIQUEMENT pour l'A320_CFM (tous les autres types d'avions A32x sont ok), alors il y a une solution pour le problème du bus électrique de l'A320_CFM comme suit. Veuillez ouvrir la section [electrical] dans le fichier aircraft.cfg de l'A320_CFM et échanger les paramètres comme suit :

  from.....
avionics_bus = 1, 14 , 17.0
avionics = 1, 9 , 17.0
gear_warning = 2, 2 , 17.0
starter1 = 2, 80 , 17.0
starter2 = 2, 80 , 17.0
standby_vacuum = 2, 5 , 17.0
fuel_transfer_pump = 2, 15 , 17.0

  to.....
avionics_bus = 0, 14 , 17.0
avionics = 0, 9 , 17.0
gear_warning = 0, 2 , 17.0
starter1 = 0, 31 , 17.0
starter2 = 0, 31 , 17.0
standby_vacuum = 0, 5 , 17.0
fuel_transfer_pump = 0, 15 , 17.0

You have to manually unswitch ATHR when "RETARD" in the sim.

Did You increase the TEXTURE_MAX_LOAD=1024 setting to 2048 or 4096 in the fsx.cfg [GRAPHICS] section too? I recommend to use the defined VC textures in 2048 and the setting  ...=2048 too, see my VC pic above. Higher settings tend to stutter in high density scenery area. IMO there is not a significant visual improvement between 2048 and 4096.

edit: I use FSX in DX10 with the fixer. No P3D experience.

Hi there,

information for users, who are using the current A32x panel 2.0 in a fresh FSX installation:

Please do not forget to install the ...fx files in the "Effects" folder, if not already done. Otherwise the beacon, strobe and nav lights are not visible outside.
You can find these ....fx files in a seperate Effects folder in any old FDD full panel package v1.55.

if you had no problems with the older panel version, then it is more likely that the new panel 2.0G is not installed properly.
So I propose to re-install the panel 2.0G at least for one aircraft type again.

7. Please delete the "PA A32x_Common" and "PA A320FD-FMC_CFM_2.0" folder in the FSX/SimObjects/Airplanes folder.

8. Copy and paste these 2 folders from the "A32x Family beta 2.0G.zip" into the FSX/SimObjects/Airplanes folder again. The ...zip folder is available in post #4749. Panel 2.0G Link:
http://freenavdbgroup.com/Temp/A32x%20Family%20beta%202.0G.zip

9. Please make sure, that no older PA panel versions are present in the Airplanes folder. Please delete any panel related CAB file in the FSX/Gauges folder (A318FD-FMC.CAB, A319FD-FMC.CAB, A320FD-FMC.CAB and A321FD-FMC.CAB), if not already done.

Bernard,
the FMC right column shows only U-waypoints and VORs. All AIRAC defined waypoints are missing.

4. Please unzip the downloded "FD_FMC airports pack V4 04072018.zip" and go into the "AIRAC" folder.

5. Copy and paste the 2 files "FreenavAIRAC_04072018.BGL" and "XFMC_04072018.BGL" into your FSX/Addon Scenery/scenery folder. These 2 files m.a. include all missing airport-relevant waypoints.
Now start FSX again, repeat your FMC loading and the test flight from LFBO to EDDF.

6. Caution: Only one set of these 2 bgl files, see (5.) should be installed into your FSX. Please delete older files after any further AIRAC update in the future. Otherwise there will be conflicting waypoint duplicates.

Bernard,
this is a known bug in the old popup MCDU (shift+7) from panel 2.0G (and older versions). There are 3 ways to go as a simple workaround:

a) Please repeat or change the proposed speed value again : 
     - mouse left click on the yellow frame
     - include the same or a changed speed value
     - mouse left click again on the yellow frame to save this value. The warning message should disappear.

b) Include all necessary entries as usual in each FMC window [TAKE-OFF],  [CLIMB]  and  [CRUISE] and ignore any warning message at first. Then go back and simply click through the 3 FMC windows again without changing any value. The warning message disappears, if all values are set within the required speed range.

c) Ignore any warning message..... 

Francois is aware of this hickup and hopefully he gets it sorted out.

Hi there,

the texture from the 2D popup MCDU is still under investigation. The three pics below show the evolution and improvement steps:

- pic 1: panel 2.0G with transparent popup MCDU at night.
- pic 2: panel 2.0G with the improvements as described in Francois´post #4863 "Vérifie aussi la valeur de color de [Window07] du panel.cfg".
- pic 3: under development and test.

André, have you tried my proposal #4889?

Thanks, André,

again....Could you please confirm, that in WIN10-64 the xmltools.dll is trusted in the [Trust] section within FSX.cfg?

I have recognized in your FSX root folder 2 xmltools.dll files...? Only 1 actual xmltools.dll file v2.0.0 or higher is necessary.

LoggerX.dll is not necessary as it is included in the xmltools.dll since v2.0.0. There will be a conflict if you have trusted LoggerX.dll as well, have a look into your [Trust] section in FSX.cfg. So my proposal is to delete the loggerX.dll file in the FSX folder (or at least to de-activate to e.g. loggerX.dll_off).
Don´t forget to delete the LoggerX.dll section in the dll.xml file as well. (dll.xml and FSX.cfg files reside in the same Microsoft/FSX folder).

Wulf