Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content

LuisVargas

members
  • Content Count

    108
  • Joined

  • Last visited

Everything posted by LuisVargas

  1. I'm away from home spending the holidays. I will return january 4th and I will test leaving runway at speed less than 30nm and only after msg LEAVE THE RUNWAY. I take this opportunity to wish you all a prosperous 2019. Thanks for your help, support and you were so patients with our doubts. Cheers!
  2. By the way, I am with Airbus Pro version 1.2.2.0, was flying with A319-132 IAE using NavDataPro as shown in the attached images.
  3. Flight made with an A319-IAE. I still have checklist problems at the SBSP airport that is 2631 feet above sea level. As shown in the jeppesen's chart SBSP is CAT1 then I entered with 2820 in the BARO (MCDU1) before activating the "DESCENT PREP CL: STARTS IN ...". After the "APPROACH CHECLIST" I confirmed the approach phase in MCDU1. During the final the PFD shows that SBSP is CAT3 (?). Is this a P3D v4.4 error? The "LANDING CHECKLIST" was executed, but when I landed and I leave the runway, neither the "AFTER LANDING CHECKLIST" nor the "PARKING CHECLIST" were executed. Upon stopping at the gate and activating the parking break I could heard a aural "HUNDRED ABOVE". Very strange.
  4. I made other flights and noticed that 'the issue' only happened once (the first time I saw it) and it is not happening anymore. It may have been some mistake of me. For me you can close this post. Thank you.
  5. As shown in the image mcdu1 at lower pedestal panel is not showing the speeds and altitudes constraints but the speeds and altitudes are show in the expanded mcdu (SHIFT+3).
  6. Ok, let's try again. I cann't update my Airbuses because ASUpdater is not doing nothing. Just a small initial movement in progress bar and it seems to be freezed. Is there a link to a newer version for ASUpdater? Thanks.
  7. Maybe it was the PC CLeaner PRO. I have noticed some minor issues after running it. I uninstalled my add-ons from P3D V4.3 (except Airbuses), did a full uninstall of P3D V4.3 and I did a fresh full install of P3D V4.4. Now I'm installing my add-ons back. I'll leave the Airbuses for the last and most probably when SP1 comes out. I am flying very little with them due to the problems with VNAV during descent. If I had problems to install the Airbuses, like registration, I will ask help here. Thank you.
  8. I need unistall Airbus Family Pro 64 bits to make a fresh install of Prepar3d v4.4. I can't unistall. What I do?
  9. But it is doing nothing. I already applied update 1.2.1.4 for my Airbuses.
  10. Airbuses updated to 1.2.1.4. Two issues encountered. 1st: Airbus A319-IAE do not follow with accuracy the flight patch from a SID and get lost as shown in the first screenshot where it shoud going to the waypoint INN. In the second screenshot the Airbus A321-IAE follow the SID flight patch with a almost very good accuracy and it's working for me. Please take the source codes from Airbus A321-IAE as base to review what is going on with flight patch of A319-IAE during a CLIMB being crawling a SID. A319-IAE lost flight patch. A321-IAE following the flight patch. 2nd: The vertical profile (DES) has problems with the altitude constraints in all Airbus models. My opinion is that descent vertical speed is not being adjusting accordlly to reach each waypoint at the programmed altitude. To work around this I change manually to selected mode the descent vertical speed until I can see if the level-off symbol at ND is near or at the waypoint/selected-altitude by ALT knob at FCU after that INITIATE DESCENT message at START DESCENT CHECKLIST. Thank you for some feedback.
  11. It's perfectly understandable, sir. No problems regarding the loss of saved flights. Thanks by your attention.
  12. After the update 1.2.1.4 all my Airbus saved flights lost information.
  13. Is there a more recent list? The one that is available is the first of July.
  14. My last contribution. I finally tested the A318-CFM. I had problems with the descent from start to finish. After activate de descent to 4000 feet the altitude dropped very fast and I almost collided with the hills below. I repeated the flight this time controlling the V / S and so went well until I captured the localizer and started the descent ramp on the G / S. This time the problem was the wrong reading of the altitude. A difference of 300 feet, because while it was at 500 "on the altimeter was sung 200". I did not hear the "MINIMUNS". I landed, applied the reverse til 60 KIAS, I take the reverse off and leaved the runway, but the message "LEAVE RUNWAY" not shown. Already towards the gates I heard "SEVENTY KNOTS" as if I were still in a situation of applying the reverses. The rest of the checklist (AFTER LANDING CL and PARKING CL) occurred normally. Okay, now I'm going to wait for SP1 to be released and I'll test all the models again. I love this Airbus and I will have a great pleasure in continuing contributing. Best regards and see you.
  15. Not all IAE. I did now a test with the A321-IAE and it did not have any problems during the flight. To my surprise, he, unlike the other A319 and A320, followed the SID's flight patch in the ND with absolute perfection... the better of them, except A318 with which I have not yet flown.
  16. Ok, I Will stay in stand by until the next patch. Best regards.
  17. I forgot to say that A320-IAE also has another problem that I have not found in the others. During takeoff and climb executing the SID It did not got follow the flight patch in Navigation Display with accuracy and got lost. I had to enter with a 'DIR TO' to the waypoint BRENO. Here are the files with the saved position before NERAS (20nm before "APPROACH CL STARTS IN 4.7 NM...) when I was at 4000 feet and 250 KIAS. A320-IAE-NERAS.wx A320-IAE-NERAS.fxml a320-iae-neras.fms a320-iae-neras.asc A320-IAE-NERAS.abx
  18. All of the five flights I have salved in a two distincts points to be able to back to them and repeat the remainder of the flight. A point after the message "DESCENT PREP CL" and another more close to destination and before the message "APPROACH CL STARTS IN...". I come back to this second one with A320-IAE BRITISH AIRWAYS and I continued the flight. My speed should be with 250 KIAS (speed at saved flight) instead I am at 228 KIAS. No problem. I entered in the final (G/S) with 198 KIAS but the speed increased to 202 KIAS as in the original flight (see attached screenshot). I applyed spoilers and the speed went to line bellow 200 KIAS but when I take the spoilers off the speed increased to 202 KIAS again. This time I selected 195 KIAS in the speed button at FCU. I was at 1700 feet and the FLAPS2 had not yet been automatic launched so I did this manually, the speed dropped and FLAPS3 happened automaticaly as FLAPS FULL and all remainder of the flight occurred without problems. As exposed above (again I beg your pardon for my english) I really feel a problem with A320-IAE in what concerns the G/S speed profile and FLAPS management at the final of a landing. Best regards.
  19. I'm still investigating the original problem, but during the tests I found the problem described below. I did five flights using the route LOWILFMN01 with aids of the checklist/copilot. Three of them with success. In the fourth I had a issue because flaps 2 was not applied automatically and I already was at 1700 feet in the final ramp to runway 04l. I have observed that the speed increase from 198 KIAS to 202 KIAS and maybe this can my have been the origin of the problem because flaps 2 must be applied with speed below 200 KIAS, isn't? So I manually set to flaps 2 (the bus complained because of speed!) and only after is that I heard "GEAR DOWN" and the speed begun to drop. From this point to the end (landing) everything went good. I repeated all the flight and again the same thing has been occured, that is, I had to manually dropped flaps to 2 and again the remainder of the flight run well. The aircrafts used with success in the first three flights were A319-IAE GERMANWINGS, A319-CFM AIRBERLIN and A320-CFM AER LINGUS. In the last two flights were I had problems I flew with A320-IAE BRITISH AIRWAYS. So I think that A320-IAE has an issue with controlling speed at approach descent.
  20. Please, left this post in stand by until I have more informations to confirm if I have ou not a issue. Thanks.
  21. I made flight LOWILFMN01 and everything worked fine. I saved the flight when I passed by NERAS to have a point to return and practice GO AROUND and alternative routes. I returned later to the saved flight and continued it. The speed was 230 kts. When the call out "APPROACH CL: STARTS IN 4.7 MILES ..." appeared, I pressed the '1' and the approach cl was sung. After the call out "FLIGHT ATTENDANTS PREPARE FOR LANDING." I activated in the MCDU the approach phase, FLAPS 1 was deployed automatically but the speed dropped to 200 kts and not 170 kts as I suppose it should have been. I waited for a while and I entered in the grand final. Then, manually, I changed the speed to 170 kts. Upon hearing "LOCALIZE ALIVE", I pressed the APPR button on the FCU and passed the ROSE to LS. I was stabilized at 170 kts and then I commanded the speed for managed. The speed began to rise to 200 kts. I changed again to 170 kts. At 2000" of altitude the FLAPS 2 and speed had not yet dropped, so I manually applied FLAPS 2 and then I heard "GEAR DOWN" and only then did the speed begin to drop. From then on, FLAPS 3 and FLAPS FULL were automatic deployed and the remainder of the flight went smoothly. I ask for help or instructions. Thanks. LOWI-LFMN-NERAS.wx LOWI-LFMN-NERAS.abx LOWI-LFMN-NERAS.fxml lowi-lfmn-neras.fms lowi-lfmn-neras.asc
  22. I made flight LOWILFMN01 and everything worked fine. I saved the flight when I passed by NERAS to have a point to return and practice GO AROUND and alternative routes. I returned later to the saved flight and continued it. The speed was 230 kts. When the call out "APPROACH CL: STARTS IN 4.7 MILES ..." appeared, I pressed the '1' and the approach cl was sung. After the call out "FLIGHT ATTENDANTS PREPARE FOR LANDING." I activated in the MCDU the approach phase, FLAPS 1 was deployed automatically but the speed dropped to 200 kts and not 170 kts as I suppose it should have been. I waited for a while and I entered in the grand final. Then, manually, I changed the speed to 170 kts. Upon hearing "LOCALIZE ALIVE", I pressed the APPR button on the FCU and passed the ROSE to LS. I was stabilized at 170 kts and then I commanded the speed for managed. The speed began to rise to 200 kts. I changed again to 170 kts. At 2000" of altitude the FLAPS 2 and speed had not yet dropped, so I manually applied FLAPS 2 and then I heard "GEAR DOWN" and only then did the speed begin to drop. From then on, FLAPS 3 and FLAPS FULL were automatic deployed and the remainder of the flight went smoothly. I ask for help or instructions. Thanks.
×
×
  • Create New...