A320 FMGS beta 30

[AirFan]

Hi Daniele,

Thanks for your reply. Meanwhile I've figured it out and I've really read your post when you released the last soundset In fact, when you posted it you mentioned that this set only covers some new sounds... anyways, I really do like it and its quality.
I hope you will get all the other missing sounds as well. That would mean I could stop bothering my lazy contact in a full flight simulator center of an airline

What I still dont understand is the APU part. You have spilt it into 3 files. Ok... but I cant hear it running, stopping or starting?
and... what I also noticed: The "regular" cockpit environment sounds are always on. You always hear the avionic fans even the aircraft power is turned off. any idea?

Really nice job...
Regards,
Rob

[immaging]

Hi Rob,

Let me explain ..... the three rows of the APU were included in the sound folder for future implementation of the module sound.exe (I hope JL consider it ).
in FS2004 is not 'can implement the sounds APU.
In FSX this is possible, but I'm having problems dealing with the three sounds with offsets. In fact fsx only manages an offset (APU run). I hope to resolve the problem over the next few days.
With regard to the ambient sounds in the cabin, I think it is possible to enable / disable this through the electrical bus.
I'll let you know.

Cheers

Daniele

[stefangr]

Hi,

as I still had problems with B28 as updated version, I have installed it with the complete installer (B28.3) from scratch now. The following problems still occur:

1. I first start the starter.exe on the server which is working fine. Then I start it on the client PC. At that moment I am getting 2 error messages on the server from Widefmgsserver: "System Error. Code 1400. Invalid Window handle" or "System Error. Code 1410. Class already defined" (translated these messages as the appear in German). After I close down the error messages, the system seems to be working ok.

2. On both NDs the traffic is displayed with values such as +337 or +255.

Thanks
Stefan

[Leonidas]

Hi,
as I still had problems with B28 as updated version, I have installed it with the complete installer (B28.3) from scratch now. The following problems still occur:
1. I first start the starter.exe on the server which is working fine. Then I start it on the client PC. At that moment I am getting 2 error messages on the server from Widefmgsserver: "System Error. Code 1400. Invalid Window handle" or "System Error. Code 1410. Class already defined" (translated these messages as the appear in German). After I close down the error messages, the system seems to be working ok.
2. On both NDs the traffic is displayed with values such as +337 or +255.
Thanks
Stefan

I confirm both of them to me too

[mardar]

I confirm both of them to me too

Hello, same problem for me as well - But after closing the two windows everything runs without problems.

I just have another issue, I have started to connect several panels thru the OC Cards, and all is running well, I´m just facing the problem that the AUTOBRAKE switches & LED´s are not working - They are working without problems thru the SIOC monitor, and as well the switch inputs are shown within the hardware connect module. It just looks like FMGS is not recognizing it... As mentioned, all other switches (BRAKE FAN, A/SKID, TERR ON ND) are working without problem. Any hint would be appreciated, as I´m runnig out of ideas where to look for...

Thanks & best regards

Dennis

[jeehell]

Dennis, this is probably a bug in my software, I need to check that.

Best regards,
JL

[AirFan]

Hi,

I can also confirm the 2 bugs described by Stefan in post #313. I also noticed that the light test on the OVHD does not cover the landing gear indicator lights.

Regards,
Rob

[AirFan]

Sorry, I just forgot a question: JL, which data is considered to show CATII or CATIII on PDF FMA during autoland? I am not sure why but all my landings are displayed as CATII even the earthnav file says its a CATIII runway.

[jeehell]

Rob, the navdata is not a criteria for CAT1,2,3 display on the FMA. The FMA displays aircraft capability, and not runway capability, meaning the pilot is responsible to check the runway/ILS is OK for CATI,II,III operations.

So to have CAT3 displayed on the FMA you need:
-At least two ADIRUs ON and aligned (3 ADIRUs for CAT3 DUAL)
-AP is engaged (both APs for CAT3 DUAL)
-ATHR engaged
-AC essential bus supplied by either GEN1 or GEN2

JL

[AirFan]

Thanks for explaining... Hm? That makes it even more strange. Even with all your listed issues it still shows CATII on the FMA. Any idea?