Paul1966 0 Posted December 18, 2014 Share Posted December 18, 2014 Hi, today I installed A318, A319, A320, A320 Version1.21. Before I de-installed the previous Versions. All works fine. But with A321 the left MCDU don't work see screenshot. The MCDU is not initailized. No mouse-clicks are accepted. Please help. Link to comment Share on other sites More sharing options...
Paul1966 0 Posted December 18, 2014 Author Share Posted December 18, 2014 correction: I installed the A318, A319, A320 and A321 Version1.21 Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted December 19, 2014 Aerosoft Share Posted December 19, 2014 And it does work in the VC mode? Link to comment Share on other sites More sharing options...
Dazzlercee 0 Posted December 19, 2014 Share Posted December 19, 2014 Hi, today I installed A318, A319, A320, A320 Version1.21. Before I de-installed the previous Versions. All works fine. But with A321 the left MCDU don't work see screenshot. The MCDU is not initailized. No mouse-clicks are accepted. Please help. Hi, Did you move or resize the main P3D window at all? Regards, Daz Link to comment Share on other sites More sharing options...
Paul1966 0 Posted December 19, 2014 Author Share Posted December 19, 2014 The MCDU A318,A319,A320 (V1.21) works fine! Only the MCDU of A321 shows this initialization error even in VC mode, see pic below. Same error with V1.10 Link to comment Share on other sites More sharing options...
Paul1966 0 Posted December 19, 2014 Author Share Posted December 19, 2014 @Dazzlercee: this is fsx, not P3D. The MCDU accept no mouseclicks. Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted December 19, 2014 Aerosoft Share Posted December 19, 2014 We have never seen this error before and as the files are the same between the 4 versions it is very hard to understand why the problem is with one model. I would advise a clean install of all versions. Link to comment Share on other sites More sharing options...
Paul1966 0 Posted December 19, 2014 Author Share Posted December 19, 2014 tell me the exact(!) steps of a clean install. Link to comment Share on other sites More sharing options...
Paul1966 0 Posted December 19, 2014 Author Share Posted December 19, 2014 e.g. must I build a new fsx.cfg? Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted December 19, 2014 Aerosoft Share Posted December 19, 2014 tell me the exact(!) steps of a clean install. 1) remove the product using the Windows Software control panel (do not manually delete the program files)2) do a disk check (right click on the drive, select properties, select tools, select check now)3) reboot your computer4) log in with administrative rights5) disable the anti-virus software temporary6) install the product7) enable the anti-virus software8) defragment your disk (NOT if you are using a SSD) Link to comment Share on other sites More sharing options...
Paul1966 0 Posted December 19, 2014 Author Share Posted December 19, 2014 Hi folks! After a clean install I was able to re-produce the strange behavoir of the left MCDU (see above). It was NOT an Installation Problem (because the re-install doesn't solve the Problem), but I think a Caching Problem of the MCDU!!! Let me describe my fsx start configuration: I have stored a Default flight with aircraft A320 that I normally use at the beginning This fight will be auto-loaded after starting the fsx. But: When I choose after auto-load another airbus, e.g. the A321 to fly with (instead the Default A320), then the left MCDU is not initialized (see screenshots above). My workaorund:per each Airbus model I stored an own Default-Flight and use a small Batch script to Launch the fsx with the Airbus I want to use. Thats works! Changing between the Airbus models wihout terminating the fsx don't work, when you start with an Default Airbus!! Link to comment Share on other sites More sharing options...
EGS754 0 Posted December 19, 2014 Share Posted December 19, 2014 Hi, I have exactly the same problem. And it's not new in V1.21. It occured already in the first download in November, when I installed A320/321. Only if I start FSX with a saved standard-flight the left MCDU is working. Any time I change the Airbus (even on the fsx-start-screen): A0-0 and Engine UNKNOWN is shown in the left MCDU and it does not work at all. No way to initialize it. So I have to save an other standard-flight, then close FSX and restart it again. Link to comment Share on other sites More sharing options...
Don Lee 6 Posted December 21, 2014 Share Posted December 21, 2014 This seems to be posted long ago, someone stated that he couldn't continue using MCDU after he cut off engines for another flight. As long as it's not being fixed, you should not set it as a default flight in fsx to avoid this issue or use the right MCDU to load and refresh the aircrafts state. Link to comment Share on other sites More sharing options...
ipavlovi 0 Posted December 30, 2014 Share Posted December 30, 2014 I am encountering the same error with Airbus 318/319 from time to time. Left MCDU says that installed engines are UNKNOWN. Restarting FSX usually fix thee problem Link to comment Share on other sites More sharing options...
rovervr 0 Posted December 31, 2014 Share Posted December 31, 2014 I am getting the same error. Each time (no matter if a320/a321 iae/cfm) I reload the aircraft the mcdu reports "Eng unknown" When loading the first time the mcdu works like a charm. But if something is reset (i.e. the fsx loading bar appears) the mcdu is unusable. please fix [wenns euch bei der reproduzierung hilft, stehe ich auch für ne teamviewer session bereit] Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted December 31, 2014 Aerosoft Share Posted December 31, 2014 I am getting the same error. Each time (no matter if a320/a321 iae/cfm) I reload the aircraft the mcdu reports "Eng unknown" When loading the first time the mcdu works like a charm. But if something is reset (i.e. the fsx loading bar appears) the mcdu is unusable. please fix [wenns euch bei der reproduzierung hilft, stehe ich auch für ne teamviewer session bereit] We are unable to recreate this. What device you use to see the MCDU? Link to comment Share on other sites More sharing options...
rovervr 0 Posted January 1, 2015 Share Posted January 1, 2015 No external device. In the Virtual Cockpit or Left MCDU View. It doesn't matter. It seems the MCDU .dll cannot talk to the airplane process and initialization fails. The active NavData is displayed but the engine is not identified. Installing SimConnect does not affect anything. Link to comment Share on other sites More sharing options...
rovervr 0 Posted January 1, 2015 Share Posted January 1, 2015 Here's a youtube vid I made showing the problem: 1. I load an aerosoft A320 into FSX - the Left MCDU works without any flaws 2. I use FSiPanel to reload the aircraft. (Any other event that causes the fsx to show the progress bar will result in the same. It's not FSiPanels fault.) 3. The MCDU shows A0-0 - Engine Unknown and nothing is clickable 4. I change the aircraft to another aerosoft a321 5. MCDU is still not usable Link to comment Share on other sites More sharing options...
Deputy Sheriffs mopperle 4162 Posted January 1, 2015 Deputy Sheriffs Share Posted January 1, 2015 And what happens when you do not use Fsipanel? Link to comment Share on other sites More sharing options...
rovervr 0 Posted January 2, 2015 Share Posted January 2, 2015 I'm currently not able to reproduce this without FSiPanel. I experienced this error before installing fsipanel, though. What's currently happening is: * fsipanel relocates the aircraft * In this state the aircraft seems completely unintialized. In this state the left mcdu shows an unknown engine * If everything goes fine, fsipanel loads a custom user state into the right mcdu * after loading the user state an engine is displayed and the mcdu works In 20% of the cases the custom user state cannot be loaded into the right mcdu, because the right mcdu acft state page is completely grayed out. This (bug?) causes the complete initialization process to hang because no custom state can be loaded. Link to comment Share on other sites More sharing options...
Joshua Che. 1601 Posted January 2, 2015 Share Posted January 2, 2015 The aircraft needs to be unpaused to start intalization. Its a FSiPanel issue. Link to comment Share on other sites More sharing options...
up'n away 0 Posted January 13, 2015 Share Posted January 13, 2015 Hi there, is there any news in this issue? I experience the same trouble since today with all aircraft A31x and A32x. Only on the very first time I load a flight after a new start of FSX the ENG type is shown in MCDU I correctly. Whenever I change the aircraft thereafter "unknown" is shown in MCDU I. Sorry, but i don't know what FSiPanel is. My flight isn't paused when I change/load the aircraft. After a couple of trials to load different aircraft, the systems seem to have quit finally since in MCDU II "ACFT STATE" and Co. remains grayed out. Link to comment Share on other sites More sharing options...
up'n away 0 Posted January 15, 2015 Share Posted January 15, 2015 No idea, no support on this? With this behavior the AS Airbus family is almost useless since everytime I've to reload or change the aircraft, the complete FSX needs to be restarted. Edit: OK, I did some logging, maybe it helps you to find the cause. What i did: 1) Fresh start of FSX 2) Starting a flight with A318-114 CFM: -> ENG Type is shown in left MCDU -> copied FMGS.log to FMGS1...log 3) Stopped flight -> copied FMGS.log to FMGS2...log 4) Started again a flight with same aircraft: -> ENG type is not shown in left MCDU -> copied FMGS.log to FMGS3...log 5) Stopped flight -> copied FMGS.log to FMGS4...log I am unfortunately not allowed to upload log files FMGS1.log: [16/01/2015 00:15:33:895]: Start logging. [16/01/2015 00:15:33:895]: Gauge loaded: 2. [16/01/2015 00:15:33:895]: Info: 0, 0, size=0x0e0c0000. [16/01/2015 00:15:33:895]: Module version: 1, 2, 7, 4. Date/time: N/A. [16/01/2015 00:15:33:895]: [16/01/2015 00:15:33:895]: GDI+: EncoderClsid 4. [16/01/2015 00:15:33:895]: UpdateTh: POST_INSTALL=0x06e42240. [16/01/2015 00:15:33:895]: PIPE: The named pipe, \\.\pipe\FBW_DataExchange, is created. [16/01/2015 00:15:33:895]: PIPE[1]: Waiting for the client's connection... [16/01/2015 00:15:33:895]: UpdateTh started: 0x06e42240. [16/01/2015 00:15:33:920]: PIPE[1]: Connected to the client. [16/01/2015 00:15:33:920]: SetBuff: 6DFEAF0. [16/01/2015 00:15:52:426]: PIPE[1]: 1 packets in/out. [1486, 276, 0] [78,1, 0.0] FM= 0.00, 0.00. [16/01/2015 00:15:52:968]: [DMPw] ASC_AUTOSAVE_TRIGGER: vorheriger flug.fms. [16/01/2015 00:15:52:968]: [DMPw] Dump to vorheriger flug.fms started. [16/01/2015 00:15:52:968]: [DMPw] Wpts: 4. [16/01/2015 00:15:52:968]: [DMPw] 160 items written so far, last WPT: . [16/01/2015 00:15:52:968]: [DMPw] 227 items written so far, last WPT: . [16/01/2015 00:15:52:968]: [DMPw] 294 items written so far, last WPT: . [16/01/2015 00:15:52:968]: [DMPw] 361 items written so far, last WPT: . [16/01/2015 00:15:52:968]: [DMPw] CSTRALT: 0. [16/01/2015 00:15:52:968]: [DMPw] CSTRSPD: 0. [16/01/2015 00:15:52:968]: [DMPw] CSTRTME: 0. [16/01/2015 00:15:52:968]: [DMPw] Total 419 items written. [16/01/2015 00:16:03:992]: PIPE[1]: 501 packets in/out. [1060, 276, 0] [11,1,-0.0] FM= 0.00, 0.00. [16/01/2015 00:16:15:591]: PIPE[1]: 1001 packets in/out. [1060, 276, 0] [17,1,-0.0] FM= 0.00, 0.00. [16/01/2015 00:16:27:203]: PIPE[1]: 1501 packets in/out. [1060, 276, 0] [19,1, 0.0] FM= 0.00, 0.00. [16/01/2015 00:16:38:897]: PIPE[1]: 2001 packets in/out. [1060, 276, 0] [19,1, 0.0] FM= 0.00, 0.00. [16/01/2015 00:16:50:403]: PIPE[1]: 2501 packets in/out. [1060, 276, 0] [19,1, 0.0] FM= 0.00, 0.00. FMGS2.log: [16/01/2015 00:17:29:609]: Start logging. [16/01/2015 00:17:29:609]: Gauge loaded: 2. [16/01/2015 00:17:29:609]: Info: 0, 0, size=0x0e0c0000. [16/01/2015 00:17:29:609]: Module version: 1, 2, 7, 4. Date/time: N/A. [16/01/2015 00:17:29:609]: [16/01/2015 00:17:29:609]: GDI+: EncoderClsid 4. [16/01/2015 00:17:29:609]: UpdateTh: POST_INSTALL=0x4db52e28. [16/01/2015 00:17:29:610]: PIPE: The named pipe, \\.\pipe\FBW_DataExchange, is created. [16/01/2015 00:17:29:610]: PIPE[1]: Waiting for the client's connection... [16/01/2015 00:17:29:610]: UpdateTh started: 0x4db52e28. [16/01/2015 00:17:29:634]: PIPE[1]: Connected to the client. [16/01/2015 00:17:29:634]: SetBuff: 6DFE7D8. [16/01/2015 00:17:29:634]: PIPE[1]: Exiting, code: 1, 0x185C. FMGS3.log (actually the same as FMGS2.log!) [16/01/2015 00:17:29:609]: Start logging. [16/01/2015 00:17:29:609]: Gauge loaded: 2. [16/01/2015 00:17:29:609]: Info: 0, 0, size=0x0e0c0000. [16/01/2015 00:17:29:609]: Module version: 1, 2, 7, 4. Date/time: N/A. [16/01/2015 00:17:29:609]: [16/01/2015 00:17:29:609]: GDI+: EncoderClsid 4. [16/01/2015 00:17:29:609]: UpdateTh: POST_INSTALL=0x4db52e28. [16/01/2015 00:17:29:610]: PIPE: The named pipe, \\.\pipe\FBW_DataExchange, is created. [16/01/2015 00:17:29:610]: PIPE[1]: Waiting for the client's connection... [16/01/2015 00:17:29:610]: UpdateTh started: 0x4db52e28. [16/01/2015 00:17:29:634]: PIPE[1]: Connected to the client. [16/01/2015 00:17:29:634]: SetBuff: 6DFE7D8. [16/01/2015 00:17:29:634]: PIPE[1]: Exiting, code: 1, 0x185C. FMGS4.log [16/01/2015 00:20:15:000]: Start logging. [16/01/2015 00:20:15:000]: Gauge loaded: 2. [16/01/2015 00:20:15:000]: Info: 0, 0, size=0x0e0c0000. [16/01/2015 00:20:15:000]: Module version: 1, 2, 7, 4. Date/time: N/A. [16/01/2015 00:20:15:000]: [16/01/2015 00:20:15:000]: GDI+: EncoderClsid 4. [16/01/2015 00:20:15:000]: UpdateTh: POST_INSTALL=0x06eaa388. [16/01/2015 00:20:15:000]: PIPE: The named pipe, \\.\pipe\FBW_DataExchange, is created. [16/01/2015 00:20:15:000]: PIPE[1]: Waiting for the client's connection... [16/01/2015 00:20:15:000]: UpdateTh started: 0x06eaa388. [16/01/2015 00:20:15:025]: PIPE[1]: Connected to the client. [16/01/2015 00:20:15:025]: SetBuff: 6DFE5C8. [16/01/2015 00:20:15:025]: PIPE[1]: Exiting, code: 1, 0x32AC. Link to comment Share on other sites More sharing options...
up'n away 0 Posted January 17, 2015 Share Posted January 17, 2015 Since no one of the developers seem to be interested in finding a solution I did some investigation by myself. I figured out that the problem only exists unter my normal user account (with administrative rights). When using the admin account or my old Windows 7 installation everything is fine. When searching the registry I came up against an entry in the Users section regarding the Compatibilty Flags: [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers] "M:\\Program Files (x86)\\Microsoft Games\\Microsoft Flight Simulator X\\fsx.exe"="$~ RUNASADMIN IgnoreFreeLibrary<FMGS.DLL>" Obviously Windows 8.1 regards the FMGS.DLL as not compatible and hence added the enhancement "IgnoreFreeLibrary". As a consequence the FMGS.DLL won't be unloaded when ending a flight. I deleted the Ignore... entry and now the problem is solved (for the time being). The most interesting questing is, why Windows regarded the FMGS.DLL as not compatible and how long does it take until the entry is back... Link to comment Share on other sites More sharing options...
HAKL1958 1 Posted January 29, 2015 Share Posted January 29, 2015 Since no one of the developers seem to be interested in finding a solution I did some investigation by myself. I figured out that the problem only exists unter my normal user account (with administrative rights). When using the admin account or my old Windows 7 installation everything is fine. When searching the registry I came up against an entry in the Users section regarding the Compatibilty Flags: [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers] "M:\\Program Files (x86)\\Microsoft Games\\Microsoft Flight Simulator X\\fsx.exe"="$~ RUNASADMIN IgnoreFreeLibrary<FMGS.DLL>" Obviously Windows 8.1 regards the FMGS.DLL as not compatible and hence added the enhancement "IgnoreFreeLibrary". As a consequence the FMGS.DLL won't be unloaded when ending a flight. I deleted the Ignore... entry and now the problem is solved (for the time being). The most interesting questing is, why Windows regarded the FMGS.DLL as not compatible and how long does it take until the entry is back... Thanks for the tip. I have been searching for days. Works great. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.