Robbybobby 75 Posted February 17, 2013 Author Share Posted February 17, 2013 here is the report. the sim crash after 1-2 secs after i click to launch the AXConnect. Problem signature: Problem Event Name: BEX Application Name: fsx.exe Application Version: 10.0.61637.0 Are you really sure that you have FSX SP2 installed? On my system, fsx.exe has version 10.0.61472. Probably that is your problem? Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-461923 Share on other sites More sharing options...
swadeep 0 Posted February 17, 2013 Share Posted February 17, 2013 I installed SP1 and then the fsx acceleration pack which includes sp2...doesn't it? I am pretty sure I installed it..how can I check again? If not can I just install it....I mean would it affect fsx add ons in anyway? Thanks Swadeep Sent from my GT-N7100 using Tapatalk 2 Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-461926 Share on other sites More sharing options...
Robbybobby 75 Posted February 17, 2013 Author Share Posted February 17, 2013 I installed SP1 and then the fsx acceleration pack which includes sp2...doesn't it? I am pretty sure I installed it..how can I check again? If not can I just install it....I mean would it affect fsx add ons in anyway? Thanks Swadeep Sent from my GT-N7100 using Tapatalk 2 Correct, I just searched and found out that this is the version of the AccelPack. So, this should be fine. Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-461927 Share on other sites More sharing options...
Robbybobby 75 Posted February 17, 2013 Author Share Posted February 17, 2013 I installed SP1 and then the fsx acceleration pack which includes sp2...doesn't it? I am pretty sure I installed it..how can I check again? If not can I just install it....I mean would it affect fsx add ons in anyway? Thanks Swadeep Sent from my GT-N7100 using Tapatalk 2 Does the crash also occur with the original AXConnect or just with my mod? Could you also send me the fmgs.log and AirbusXConnectExtended.log? Make sure that you send them directly after the crash and before restarting a flight again, since they will be overwritten on each start. You can find the files in C:\Users\<username>\Documents\Aerosoft\AerosoftAirbusExtended Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-461928 Share on other sites More sharing options...
Jead 34 Posted February 17, 2013 Share Posted February 17, 2013 Hi By the way, I dont know if this is relevent, but crashes did happen even with the original file, but very very rarely and restarting the flight all is ok. I doubt your file is the issue as I can see from many other posts on different issues that not all pilots share the same issues, and in many cases, it happens randomly or very rarely. This beauty has a mind of its own, Jead Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-461987 Share on other sites More sharing options...
swadeep 0 Posted February 18, 2013 Share Posted February 18, 2013 It also happened with the original AXConnect and yes it happened randomly. I will try reproduce the crash this evening and send you the log. It's really weird. Aerosoft should really take a look at this. Thanks Swadeep Sent from my GT-N7100 using Tapatalk 2 Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-462048 Share on other sites More sharing options...
swadeep 0 Posted February 18, 2013 Share Posted February 18, 2013 here's the FMGS log.... [18/02/2013 17:17:31:933]: Start logging. [18/02/2013 17:17:31:933]: Gauge loaded: 2. [18/02/2013 17:17:31:933]: GetDLLInfo: 0, 0. [18/02/2013 17:17:31:933]: Module version: 1, 2, 0, 3. Date/time: N/A. [18/02/2013 17:17:31:933]: [18/02/2013 17:17:31:933]: GDI+: GdiplusStartup 0. EncoderClsid 4. [18/02/2013 17:17:31:933]: PIPE: The named pipe, \\.\pipe\MCDU_Input, is created. [18/02/2013 17:17:31:933]: PIPE[0]: Waiting for the client's connection... [18/02/2013 17:17:31:933]: PIPE: The named pipe, \\.\pipe\FBW_DataExchange, is created. [18/02/2013 17:17:31:933]: PIPE[1]: Waiting for the client's connection... [18/02/2013 17:17:31:966]: PIPE[1]: Connected to the client. [18/02/2013 17:18:14:765]: PIPE[1]: 1 packets in/out. [1603,79,0,333,1, 0.0]. [18/02/2013 17:18:34:781]: PIPE[1]: 501 packets in/out. [36,7,0,333,1, 0.0]. [18/02/2013 17:18:55:174]: PIPE[1]: 1001 packets in/out. [36,1,0,333,1, 0.0]. [18/02/2013 17:19:11:878]: PIPE[1]: 1501 packets in/out. [36,0,0,333,1, 0.0]. [18/02/2013 17:19:21:235]: PIPE[0]: Connected to the client. [18/02/2013 17:19:29:822]: PIPE[1]: 2001 packets in/out. [36,0,0,333,1, 0.0]. [18/02/2013 17:19:49:339]: PIPE[1]: 2501 packets in/out. [36,0,0,333,1, 0.0]. [18/02/2013 17:20:06:006]: PIPE[1]: 3001 packets in/out. [36,0,0,333,1, 0.0]. [18/02/2013 17:20:22:523]: PIPE[0]: Receives 2 bytes; Code: 21 [18/02/2013 17:20:25:069]: PIPE[1]: 3501 packets in/out. [36,0,0,333,1, 0.0]. [18/02/2013 17:20:30:142]: LNav mode: 0 off. [18/02/2013 17:20:30:142]: LNav mode: 0 off. [18/02/2013 17:20:32:413]: PIPE[0]: Receives 2 bytes; Code: 61 [18/02/2013 17:20:32:889]: PIPE[0]: Receives 2 bytes; Code: 57 [18/02/2013 17:20:33:108]: PIPE[0]: Receives 2 bytes; Code: 57 [18/02/2013 17:20:33:439]: PIPE[0]: Receives 2 bytes; Code: 57 [18/02/2013 17:20:36:596]: PIPE[0]: Receives 2 bytes; Code: 57 [18/02/2013 17:20:37:076]: PIPE[0]: Receives 2 bytes; Code: 38 [18/02/2013 17:20:37:804]: PIPE[0]: Receives 2 bytes; Code: 60 [18/02/2013 17:20:39:443]: PIPE[0]: Receives 2 bytes; Code: 68 [18/02/2013 17:20:41:747]: PIPE[1]: 4001 packets in/out. [36,0,0,333,1, 0.0]. [18/02/2013 17:20:42:761]: PIPE[0]: Receives 2 bytes; Code: 68 [18/02/2013 17:20:44:191]: PIPE[0]: Receives 2 bytes; Code: 68 [18/02/2013 17:20:44:725]: Error in GDI+: StoreImageFile 7, 32. [18/02/2013 17:20:45:520]: PIPE[0]: Receives 2 bytes; Code: 68 [18/02/2013 17:20:47:472]: PIPE[0]: Receives 2 bytes; Code: 57 [18/02/2013 17:20:48:609]: PIPE[0]: Receives 2 bytes; Code: 38 [18/02/2013 17:20:49:205]: PIPE[0]: Receives 2 bytes; Code: 60 [18/02/2013 17:20:50:713]: PIPE[0]: Receives 2 bytes; Code: 52 [18/02/2013 17:20:52:364]: PIPE[0]: Receives 2 bytes; Code: 49 [18/02/2013 17:20:52:574]: PIPE[0]: Receives 2 bytes; Code: 58 [18/02/2013 17:20:52:902]: PIPE[0]: Receives 2 bytes; Code: 6 [18/02/2013 17:20:52:958]: FP change: ARPT added, type: 3, [WSSS]. [18/02/2013 17:20:52:958]: FP change: ARPT added, type: 4, [VNKT]. [18/02/2013 17:20:52:968]: CSTRs: Checking the current WPT: []. [18/02/2013 17:20:52:968]: CSTRs: MCDU_WPT_ALTCSTR: 0,0,0. [18/02/2013 17:20:52:968]: CSTRs: MCDU_WPT_SPDCSTR: 0(0nm). [18/02/2013 17:20:52:968]: CSTRs: MCDU_WPT_ALTCSTR_COND: 0(0nm)|0(0nm)|0(0nm)|0(0nm)|0(0). [18/02/2013 17:20:52:968]: DEP/ARR: WSSS/VNKT. [18/02/2013 17:20:55:888]: PIPE[0]: Receives 2 bytes; Code: 0 [18/02/2013 17:20:55:888]: CoRte [WSSSVNKT01], exists: [1]. [18/02/2013 17:20:55:888]: CoRte [WSSSVNKT01] loading started. [18/02/2013 17:20:55:888]: Airway loaded: [VMR->B469->VPK]. [18/02/2013 17:20:55:951]: FP change: WPT added to #1, type: 1, [VMR] via [b469]. [18/02/2013 17:20:55:951]: CoRte loading Airway - new WPT [VMR, from 1 to 1] adding: OK. [18/02/2013 17:20:55:951]: CoRte loading Airway: [b469]/[1]; [VMR]/[VPK]. [18/02/2013 17:20:56:609]: FP change: WPT added to #2, type: 1, [bIKTA] via [b469]. [18/02/2013 17:20:56:614]: FP change: WPT added to #3, type: 1, [D90PU] via [b469]. [18/02/2013 17:20:56:619]: FP change: WPT added to #4, type: 1, [PADLI] via [b469]. [18/02/2013 17:20:56:625]: FP change: WPT added to #5, type: 1, [VPK] via [b469]. [18/02/2013 17:20:56:634]: CoRte loading Airway: OK. [18/02/2013 17:20:56:634]: Airway loaded: [VPK->M751->VKB]. [18/02/2013 17:20:56:634]: CoRte loading Airway: [M751]/[2]; [VPK]/[VKB]. [18/02/2013 17:20:57:108]: FP change: WPT added to #6, type: 1, [VKB] via [M751]. [18/02/2013 17:20:57:108]: CoRte loading Airway: OK. [18/02/2013 17:20:57:108]: Airway loaded: [VKB->M626->BGO]. [18/02/2013 17:20:57:108]: CoRte loading Airway: [M626]/[3]; [VKB]/[bGO]. [18/02/2013 17:20:57:823]: FP change: WPT added to #7, type: 1, [KADAX] via [M626]. [18/02/2013 17:20:57:840]: FP change: WPT added to #8, type: 1, [sUWAN] via [M626]. [18/02/2013 17:20:57:857]: FP change: WPT added to #9, type: 1, [sUPIN] via [M626]. [18/02/2013 17:20:57:874]: FP change: WPT added to #10, type: 1, [uPNEP] via [M626]. [18/02/2013 17:20:57:891]: FP change: WPT added to #11, type: 1, [MENEX] via [M626]. [18/02/2013 17:20:57:908]: FP change: WPT added to #12, type: 1, [EKAVO] via [M626]. [18/02/2013 17:20:57:924]: FP change: WPT added to #13, type: 1, [DALER] via [M626]. [18/02/2013 17:20:57:941]: FP change: WPT added to #14, type: 1, [DWI] via [M626]. [18/02/2013 17:20:57:957]: FP change: WPT added to #15, type: 1, [POXEM] via [M626]. [18/02/2013 17:20:57:974]: FP change: WPT added to #16, type: 1, [bGO] via [M626]. [18/02/2013 17:20:57:974]: CoRte loading Airway: OK. [18/02/2013 17:20:57:974]: Airway loaded: [bGO->G463->SMR]. [18/02/2013 17:20:57:974]: CoRte loading Airway: [G463]/[4]; [bGO]/[sMR]. [18/02/2013 17:20:58:586]: FP change: WPT added to #17, type: 1, [TMA02] via [G463]. [18/02/2013 17:20:58:594]: FP change: WPT added to #18, type: 1, [NIVOG] via [G463]. [18/02/2013 17:20:58:602]: FP change: WPT added to #19, type: 1, [AVLED] via [G463]. [18/02/2013 17:20:58:610]: FP change: WPT added to #20, type: 1, [TANAP] via [G463]. [18/02/2013 17:20:58:618]: FP change: WPT added to #21, type: 1, [CTG] via [G463]. [18/02/2013 17:20:58:626]: FP change: WPT added to #22, type: 1, [ONEKA] via [G463]. [18/02/2013 17:20:58:634]: FP change: WPT added to #23, type: 1, [75DAC] via [G463]. [18/02/2013 17:20:58:642]: FP change: WPT added to #24, type: 1, [ADMIL] via [G463]. [18/02/2013 17:20:58:650]: FP change: WPT added to #25, type: 1, [KANDI] via [G463]. [18/02/2013 17:20:58:658]: FP change: WPT added to #26, type: 1, [DAC] via [G463]. [18/02/2013 17:20:58:666]: FP change: WPT added to #27, type: 1, [OLPAS] via [G463]. [18/02/2013 17:20:58:674]: FP change: WPT added to #28, type: 1, [bATEL] via [G463]. [18/02/2013 17:20:58:682]: FP change: WPT added to #29, type: 1, [RAJ] via [G463]. [18/02/2013 17:20:58:690]: FP change: WPT added to #30, type: 1, [TEBID] via [G463]. [18/02/2013 17:20:58:698]: FP change: WPT added to #31, type: 1, [bIKIK] via [G463]. [18/02/2013 17:20:58:706]: FP change: WPT added to #32, type: 1, [MONDA] via [G463]. [18/02/2013 17:20:58:714]: FP change: WPT added to #33, type: 1, [uXAGA] via [G463]. [18/02/2013 17:20:58:722]: FP change: WPT added to #34, type: 1, [iPLAS] via [G463]. [18/02/2013 17:20:58:730]: FP change: WPT added to #35, type: 1, [GAURA] via [G463]. [18/02/2013 17:20:58:738]: FP change: WPT added to #36, type: 1, [ROMEO] via [G463]. [18/02/2013 17:20:58:746]: FP change: WPT added to #37, type: 1, [sMR] via [G463]. [18/02/2013 17:20:58:746]: CoRte loading Airway: OK. [18/02/2013 17:20:58:747]: CSTRs: Checking the current WPT: [VMR]. [18/02/2013 17:20:58:747]: CSTRs: MCDU_WPT_ALTCSTR: 0,0,0. [18/02/2013 17:20:58:747]: CSTRs: MCDU_WPT_SPDCSTR: 0(0nm). [18/02/2013 17:20:58:747]: CSTRs: MCDU_WPT_ALTCSTR_COND: 0(0nm)|0(0nm)|0(0nm)|0(0nm)|0(0). [18/02/2013 17:20:59:593]: PIPE[1]: 4501 packets in/out. [36,0,0,333,1, 0.0]. [18/02/2013 17:21:05:225]: PIPE[0]: Receives 2 bytes; Code: 31 [18/02/2013 17:21:05:446]: PIPE[0]: Receives 2 bytes; Code: 28 [18/02/2013 17:21:08:043]: PIPE[0]: Receives 2 bytes; Code: 29 [18/02/2013 17:21:08:231]: PIPE[0]: Receives 2 bytes; Code: 2 [18/02/2013 17:21:09:916]: PIPE[0]: Receives 2 bytes; Code: 28 [18/02/2013 17:21:10:516]: PIPE[0]: Receives 2 bytes; Code: 27 [18/02/2013 17:21:11:776]: PIPE[0]: Receives 2 bytes; Code: 4 [18/02/2013 17:21:11:776]: CostIndex: 10. [18/02/2013 17:21:13:394]: PIPE[0]: Receives 2 bytes; Code: 30 [18/02/2013 17:21:15:689]: PIPE[0]: Receives 2 bytes; Code: 31 [18/02/2013 17:21:16:147]: PIPE[0]: Receives 2 bytes; Code: 27 [18/02/2013 17:21:16:248]: PIPE[1]: 5001 packets in/out. [36,0,0,333,1, 0.0]. [18/02/2013 17:21:17:792]: PIPE[0]: Receives 2 bytes; Code: 5 [18/02/2013 17:21:17:792]: Defaulting ZFWCG: 25 pct. [18/02/2013 17:21:17:792]: Defaulting THS: 0.8 UP. [18/02/2013 17:21:17:792]: Defaulting ZFW: 56360.4 kg. [18/02/2013 17:21:18:398]: PIPE[0]: Receives 2 bytes; Code: 8 [18/02/2013 17:21:23:942]: PIPE[0]: Receives 2 bytes; Code: 18 [18/02/2013 17:21:26:664]: PIPE[0]: Receives 2 bytes; Code: 28 [18/02/2013 17:21:27:638]: PIPE[0]: Receives 2 bytes; Code: 36 [18/02/2013 17:21:29:920]: PIPE[0]: Receives 2 bytes; Code: 37 [18/02/2013 17:21:32:920]: PIPE[1]: 5501 packets in/out. [36,0,0,333,1, 0.0]. [18/02/2013 17:21:33:958]: PIPE[0]: Receives 2 bytes; Code: 27 [18/02/2013 17:21:35:864]: PIPE[0]: Receives 2 bytes; Code: 7 [18/02/2013 17:21:35:864]: Defaulting ZFWCG: 25 pct. [18/02/2013 17:21:35:864]: Defaulting THS: 0.8 UP. [18/02/2013 17:21:35:864]: Defaulting ZFW: 56360.4 kg. [18/02/2013 17:21:35:879]: Cruisealt: 34000. [18/02/2013 17:21:35:879]: LW estimated: 65207. [18/02/2013 17:21:35:879]: PredPrAppr: 9. [18/02/2013 17:21:35:879]: PredsPrAppr2: 13. [18/02/2013 17:21:35:879]: PredPrDes: 0. [18/02/2013 17:21:35:879]: CSTRs: Checking the current WPT: [VMR]. [18/02/2013 17:21:35:879]: CSTRs: MCDU_WPT_ALTCSTR: 0,0,0. [18/02/2013 17:21:35:879]: CSTRs: MCDU_WPT_SPDCSTR: 0(0nm). [18/02/2013 17:21:35:880]: CSTRs: MCDU_WPT_ALTCSTR_COND: 0(0nm)|0(0nm)|0(0nm)|0(0nm)|0(0). [18/02/2013 17:21:35:914]: PredTO, (dist: 1981). [18/02/2013 17:21:35:914]: PredClb2XML: 49, (dist: 1937; 1959). [18/02/2013 17:21:35:914]: PredClb: 2501, (dist: 1937; 1959). [18/02/2013 17:21:35:914]: PredCrz TOD: 8.66, 5895, 23. [18/02/2013 17:21:35:914]: PredCrz: 213, (dist: 95). [18/02/2013 17:21:35:915]: PredDes: 77 (total dist: 1985.58). [18/02/2013 17:21:35:915]: CSTRs: Checking the current WPT: [VMR]. [18/02/2013 17:21:35:915]: CSTRs: MCDU_WPT_ALTCSTR: 0,0,0. [18/02/2013 17:21:35:915]: CSTRs: MCDU_WPT_SPDCSTR: 0(0nm). [18/02/2013 17:21:35:915]: CSTRs: MCDU_WPT_ALTCSTR_COND: 0(0nm)|0(0nm)|0(0nm)|0(0nm)|0(0). [18/02/2013 17:21:40:310]: CSTRs: Checking the current WPT: [VMR]. [18/02/2013 17:21:40:310]: CSTRs: MCDU_WPT_ALTCSTR: 0,0,0. [18/02/2013 17:21:40:310]: CSTRs: MCDU_WPT_SPDCSTR: 0(0nm). [18/02/2013 17:21:40:310]: CSTRs: MCDU_WPT_ALTCSTR_COND: 0(0nm)|0(0nm)|0(0nm)|0(0nm)|0(0). [18/02/2013 17:21:49:615]: PIPE[1]: 6001 packets in/out. [36,0,0,333,1, 0.0]. [18/02/2013 17:21:55:967]: PredTO, (dist: 1981). [18/02/2013 17:21:55:967]: PredClb2XML: 102, (dist: 1869; 1959). [18/02/2013 17:21:55:967]: PredClb: 2501, (dist: 1869; 1959). [18/02/2013 17:21:55:967]: PredCrz TOD: 8.66, 5895, 23. [18/02/2013 17:21:55:967]: PredCrz: 200, (dist: 135). [18/02/2013 17:21:55:967]: PredDes: 105 (total dist: 1985.58). [18/02/2013 17:21:55:968]: CSTRs: Checking the current WPT: [VMR]. [18/02/2013 17:21:55:968]: CSTRs: MCDU_WPT_ALTCSTR: 0,0,0. [18/02/2013 17:21:55:968]: CSTRs: MCDU_WPT_SPDCSTR: 0(0nm). [18/02/2013 17:21:55:968]: CSTRs: MCDU_WPT_ALTCSTR_COND: 0(0nm)|0(0nm)|0(0nm)|0(0nm)|0(0). [18/02/2013 17:22:06:302]: PIPE[1]: 6501 packets in/out. [36,0,0,333,1, 0.0]. [18/02/2013 17:22:10:494]: FP change: All WPTs cleared. [18/02/2013 17:22:10:494]: Gauge unloaded. [18/02/2013 17:22:10:494]: End logging. I have noticed that if i just shut down the engines when flight is started and set parking brake and not do anything just yet except launch AXConnect then no CTD..weird. But have not done flight with it. I did the same this time with your MOD v1.3 and when i close FSX then the same error came up and above you can see the log. Thanks Swadeep Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-462095 Share on other sites More sharing options...
swadeep 0 Posted February 19, 2013 Share Posted February 19, 2013 hi...so any luck?? managed to find out what's the problem? thanks swadeep Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-462533 Share on other sites More sharing options...
Robbybobby 75 Posted February 20, 2013 Author Share Posted February 20, 2013 here's the FMGS I have noticed that if i just shut down the engines when flight is started and set parking brake and not do anything just yet except launch AXConnect then no CTD..weird. But have not done flight with it. I did the same this time with your MOD v1.3 and when i close FSX then the same error came up and above you can see the log. Thanks Swadeep I haven't been able to be at my FSX PC, yet. But it looks as if you we're able to press keys on the tablet MCDU and the FSX MCDU was reacting on those, right? A crash in the situation you described is not unusual. I too had problems when shutting down FSX with AXConnect still running. You should always start AXConnect after the flight has been loaded and shut it down before ending the flight. But you also mentioned that you had crashes when starting AXConnect. If you can reproduce that, the AirbusXConnectExtended.log file and fmgs.log file might help finding out more about it. Please also note that this crash probably needs to be fixed by Aerosoft as long as it already happened with the original version. Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-463054 Share on other sites More sharing options...
swadeep 0 Posted February 21, 2013 Share Posted February 21, 2013 Yes i think it's to be looked at from Aerosoft end. Anyway lately no CTD but a new problem has occurred which is stuttering as mentioned on other post. Every few seconds the sim will freeze for .5 seconds. I tried setting the HTML_INTERFACE = 0 as it solved problems for many other people but not for me. I have uninstalled the whole thing and reinstall it so i will try again tonight. This is really weird. It was working wonderfully and out of the blue all these problems start happening. Very annoying indeed. Thanks so much for your help though. Really appreciate it. Cheers Swadeep Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-463120 Share on other sites More sharing options...
Anthony99 49 Posted February 21, 2013 Share Posted February 21, 2013 Hello! I have an iPad mini will it work? If so how do I set it up? I don't have a clue how to set it up or what to do? someone please help! Thanks Anthony Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-463142 Share on other sites More sharing options...
Robbybobby 75 Posted February 21, 2013 Author Share Posted February 21, 2013 Hello! I have an iPad mini will it work? If so how do I set it up? I don't have a clue how to set it up or what to do? someone please help! Thanks Anthony That should work. Just use the original AirbusXConnectExtended application and follow the manual instructions. If you manage to establish a working network connection and key presses on the ipad MCDU are recognized, you can also try my mod to see if that improves performance for you. Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-463154 Share on other sites More sharing options...
Anthony99 49 Posted February 21, 2013 Share Posted February 21, 2013 That should work. Just use the original AirbusXConnectExtended application and follow the manual instructions. If you manage to establish a working network connection and key presses on the ipad MCDU are recognized, you can also try my mod to see if that improves performance for you. Hello Robby! Thanks for the quick reply! When i was reading the 'read me' i was confused how to do it. Do i need to install all of them? 1.1,1.2,1.3? Im really confused Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-463155 Share on other sites More sharing options...
Robbybobby 75 Posted February 21, 2013 Author Share Posted February 21, 2013 Hello Robby! Thanks for the quick reply! When i was reading the 'read me' i was confused how to do it. Do i need to install all of them? 1.1,1.2,1.3? Im really confused Before using the mod, please make sure that the original one is working. As long as you have connection problems with that one, the mod won't help. Once the original one is working, just use the latest version of the mod (1.3 as of today). Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-463163 Share on other sites More sharing options...
Anthony99 49 Posted February 21, 2013 Share Posted February 21, 2013 Before using the mod, please make sure that the original one is working. As long as you have connection problems with that one, the mod won't help. Once the original one is working, just use the latest version of the mod (1.3 as of today). Ill try this tomorrow morning because i have to go to sleep Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-463165 Share on other sites More sharing options...
crvchul 3 Posted February 21, 2013 Share Posted February 21, 2013 Working perfectly for me. (iPad Mini) Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-463175 Share on other sites More sharing options...
Anthony99 49 Posted February 21, 2013 Share Posted February 21, 2013 Working perfectly for me. (iPad Mini) ok thanks. If you dont mind can you please tell me how you did the setup. please? Thanks Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-463182 Share on other sites More sharing options...
Robbybobby 75 Posted February 22, 2013 Author Share Posted February 22, 2013 here is the report. the sim crash after 1-2 secs after i click to launch the AXConnect. Problem signature: Problem Event Name: BEX Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: FMGS.DLL_unloaded Fault Module Version: 0.0.0.0 Fault Module Timestamp: 5111921a Exception Offset: 17751401 Exception Code: c0000005 Exception Data: 00000008 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional Information 1: 7edd Additional Information 2: 7eddbe13fc3da61fbb560b04c5b5f7f0 Additional Information 3: 1a6a Additional Information 4: 1a6a2e8a8a8d44819de706cb2cfbb3ce Read our privacy statement online: http://go.microsoft....88&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt thanks swadeep I just had exactly the same error with FMGS.dll. It was happening just as I was pressing a key on the iPad. However, I was not very careful in starting things in the correct order, this time. And this has been known for some time now that this is very crucial. I actually did a reset of the flight after I had already started AXConnect - never do that. Always use this order: 1. Start the flight into Airbus X Extended 2. Only after flight is loaded and cockpit shows up, start AXConnectExtended 3. Shut down AXConnectExtended before you stop the flight If you need to restart AXConnectExtended during flight (sometimes it hangs), close it and wait AT LEAST 10 seconds before starting it again. Although the window is not visible any more, the process still runs for several seconds before it completely stops. Starting a second instance during that time messes things up. You can see that you were too fast if you see a crash dialog directly after starting AXConnect again. Just some tips for people out there. If I follow those, I don't have any problems. If I had access to the source code, I would like to fix those issues (they are already in the original AXConnect), but that is not possible for me right now. Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-463849 Share on other sites More sharing options...
Robbybobby 75 Posted February 22, 2013 Author Share Posted February 22, 2013 ok thanks. If you dont mind can you please tell me how you did the setup. please? Thanks Start AirbusX-ConnectExtended after you have started an Airbus X Extended flight in FSX. Then, you will see a green IP:Port adress in the window (e.g. 192.168.10.24:4040, your numbers will vary). Open your Safari browser on your iPad and type that into the browser address field. Then the MCDU should show up. If not, please report back. Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-463850 Share on other sites More sharing options...
Anthony99 49 Posted February 22, 2013 Share Posted February 22, 2013 Yes it showed Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-463907 Share on other sites More sharing options...
Robbybobby 75 Posted February 22, 2013 Author Share Posted February 22, 2013 Yes it showed Ok, great. If everything works as expected, you can use the original version. If it is responding slowly to your inputs, you can download my mod (latest version) and copy it into the same folder as the original AXconnect application (see the readme file for details). When you start my exe file instead of the original one, you might get better performance for key presses. Good luck! Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-463912 Share on other sites More sharing options...
Anthony99 49 Posted February 22, 2013 Share Posted February 22, 2013 It showed but nothing worked Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-463913 Share on other sites More sharing options...
Anthony99 49 Posted February 22, 2013 Share Posted February 22, 2013 Touching the mcdu on ipad nothing works Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-463914 Share on other sites More sharing options...
Robbybobby 75 Posted February 22, 2013 Author Share Posted February 22, 2013 Touching the mcdu on ipad nothing works Can you send your AirbusXConnectExtended.log? It is in c:\Users\<yourname>\Documents\Aerosoft\AerosoftAirbusExtended Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-463915 Share on other sites More sharing options...
Anthony99 49 Posted February 22, 2013 Share Posted February 22, 2013 It says i cant upload this kind of file Link to comment https://forum.aerosoft.com/index.php?/topic/64294-airbus-x-connect-extended-mod/page/3/#findComment-463919 Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.