canuck21a

member
  • Content Count

    45
  • Joined

  • Last visited

Community Reputation

9 Neutral

About canuck21a

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

1578 profile views
  1. canuck21a

    A320 SID Test

    Yesterday I noticed that a new version of both the busses was available. I removed both from my test and regular systems and followed the prescribed methodology for re-install. Once I had updated Navigraph I decided to re-test the previous flight again. Using the provided A320 Lufthansa CFM I set up at a gate at EGKK. Once again the flight plan for cruise at FL070 was entered manually with one intermediate waypoint (WTZ) between the CLNX4X SID for 26L and TUSMU Transition for ILS29. After everything was set up and the systems were active I checked both the MCDU values and those shown on the ND which generally seem to display the constraint values. I placed these values in a table to make it easier to review: Those values in red show where the MCDU displayed things differently than the ND and the underlying constraint values. Perhaps these apparently contrary display values are simply part of the weird and wonderful Aerosoft Airbus logic? Now on to the actual flight............ Following the fully managed with copilot procedures the takeoff went without a hitch. At a suitable altitude and before the first waypoint AP was turned on. The MCDU and ND were watched closely to see if any strangeness happened. The aircraft passed KKW02 above 1500, KKE09 above 3200 and held at 4000 before KKE11. After KKE11 it climbed and maintained 5000 @ 250kias. After DET it climbed to 6000. At CLN it climbed to 7000 and held until TOD Descent and landing were normal. The SID profile was flown as expected and nothing strange (for me anyway) happened. It appears that the changes to the coding have corrected the previously encountered behaviour. Thanks for the fixes !
  2. canuck21a

    A320 SID Test

    Just dropped in to see if anything had changed. When something does I will re-run the test using the same procedures.
  3. canuck21a

    A320 SID Test

    Here is the updater screen that was checked before I started the test.: Are there any specific files that I might need to send to you to confirm if the update is as expected ?
  4. canuck21a

    A320 SID Test

    Hello, I reviewed the posts related to the flight management system failing to comply with published SID's. I too have been struggling with this using the new pro bus 318 & 320. A little info on my test setup: 1) i7-2600k 16GB RAM, OC 4.0 GHz, nVidia GTX970, Windows 10 Pro all the latest updates 2) P3Dv4.3 clean install with only a few ORBX addons; Global and LC. 3) Aerosoft A318/319 & A320/321 with all of the latest updates via the updater (A320/321 ver: 1.2.0.2) I set up a simple flight from EGKK to EGUN simply to test the MCDU and the flight. The departure was 26L using CLN4X like another user had with a single waypoint at cruise (FL070) and a transition to Rwy29 via TUSMU. I started the sim in turn-around mode and loaded the pax and cargo then closed the doors except the main. The main MCDU was used to enter the flight plan manually. The departure was reviewed using a commercial chart system and compared to the 1809 Navigraph proc for EGKK. Navigraph: NAVIGRAPH 1809 SID,CLN4X,26L,5 CF,KKW02,51.137656,-0.266325,0,DET,253.3,34.1,258.0,2.0,2,1500,0,1,220,0,0,1, CF,KKE09,51.195533,-0.206644,2,DET,258.2,31.0,78.0,3.0,2,3200,0,1,220,0,0,0, TF,KKE11,51.202697,-0.154894,0, ,0.0,0.0,0.0,0.0,3,4000,0,1,250,0,0,0, TF,KKE15,51.213975,-0.073089,0, ,0.0,0.0,0.0,0.0,0,0,0,1,250,0,0,0, TF,SUNAV,51.260250,0.194389,0, ,0.0,0.0,0.0,0.0,1,5000,0,1,250,0,0,0, TF,KKE42,51.227028,0.568528,0, ,0.0,0.0,0.0,0.0,1,5000,0,1,250,0,0,0, TF,DET,51.304003,0.597275,0, ,0.0,0.0,0.0,0.0,1,5000,0,1,250,0,0,0, TF,KKN52,51.385000,0.627611,0, ,0.0,0.0,0.0,0.0,1,6000,0,1,250,0,0,0, TF,DAGGA,51.821944,0.794167,0, ,0.0,0.0,0.0,0.0,1,6000,0,1,250,0,0,0, TF,CLN,51.848472,1.147589,0, ,0.0,0.0,0.0,0.0,1,6000,0,1,250,0,0,0, ************************************************************************************************************* COURSE TO FIX KKW02 +1500 @ 220 OVERFLY COURSE TO FIX KKE09 +3200 @ 220 FLYBY TRACK TO FIX KKE11 -4000 @ 250 FLYBY TRACK TO FIX KKE15 NOALT @ 250 FLYBY TRACK TO FIX SUNAV 5000 @ 250 FLYBY My interpretation of the SID TRACK TO FIX KKE42 5000 @ 250 FLYBY TRACK TO FIX DET 5000 @ 250 FLYBY TRACK TO FIX KKN52 6000 @ 250 FLYBY TRACK TO FIX DAGGA 6000 @ 250 FLYBY TRACK TO FIX CLN 6000 @ 250 FLYBY ************************************************************************************************************ SID (SimPlatesX Ultra) The details confirm that the first two waypoints can/should be above 1500 & 3200 while the third is limited (constrained) to 4000 feet It was interesting that there is no altitude for KKE15. Loading the MCDU flight plan: The plan was loaded using the dep/arr runways and stated STAR and Transition. The next image shows what the screens looked like right after loading (A), after modifying some waypoints to add constraints (B) and finally after the fuel prediction was activated. It can be seen that KKW02 shows an altitude that is clearly less than the required +1500 while KKE09 shows an altitude that conforms to the +3200 value. KKE11 displays the correct altitude and speed constraints. KKN52 is supposed to be 6000 but shows nothing so I entered it manually (B) CLN is supposed to be 6000 but it displays as 6100. The rest of the items appear to be correct. . . Now we turn to the A320 plan display to see what it shows: Viewing these all the constraints appear to be correct. Now looking at the DET plan versus display: Clearly it shows that one display is somehow wrong. After having set up the flight the full Checklist with copilot was started. The aircraft took off as expected and after reaching a suitable altitude the autopilot was turned on. The plan then proceed to climb immediately @220kn to the 4000 restriction. Once it passed KKE11 it decided to climb to cruise altitude blowing away all of the speed/altitude constraints; furthermore the flight plan changed all of the SID constraints to FL070. My past experience suggests that this aircraft now has a HAL9000 running in the background as it wants to do things that I or Navigraph do not want it to.
  5. canuck21a

    318/19 Crazy descend rates

    Hello, I decided to try your flight today using Ver 1100 A319 with the loadsheet similar to yours. My system is an older one i7-2600k 32GB 4.0GHzOC with a EVGA 970GTX P3Dv4.3 is a full install and there is little extra scenery. I use ORBX Global and NA/SA/EU Landclass. FPS were around 50 most of the time. [CoRte] ArptDep=LIPZ ArptArr=LIRN RwyDep=LIPZ04R RwyArr=LIRN4.Z RwyArrFINAL=ILS24.Z SID=CHI7V STAR=TEA1C APPR_Trans=POM1 Airway1=L612 Airway1FROM=CHI Airway1TO=ANC Airway2=M736 Airway2FROM=ANC Airway2TO=TEA Altitude was set to FL340 cruise. I used the full copilot checklist with 250 speed control turned on. After Descent checklist I set the final altitude to 2000. 15nm before TOD I engaged descent. Initial descent was 1000 fpm for some time after which it did its normal thing and started to descend more rapidly. I watched the descent rate and speed. The descent was about 2800 fpm @ 310knots for most of the descent At 12000 I engaged speed brakes to get the thing under better speed control. I left them on until the thrusters started to climb after which the speed brakes were off. The rest of the approach and landing were full auto with nothing strange happening.
  6. canuck21a

    Ignoring Constraints

    May I assume that this issue is not rectified in the latest update to 1100? I updated and tried the same setup again and the altitudes on the display changed like before when I clicked on the block fuel key.
  7. canuck21a

    Ignoring Constraints

    Not sure if further confirmation is require; however, I decided to test my clean sim/P3Dv4.3 to see if the issue prevailed. I started a flight at EHAM to EHGG. A flight plan had been made and saved earlier. Fuel was loaded but no further action taken; that is, no Fuel prediction actions in the init page 2. The image shows the FMC pages before fuel prediction was activated and after. Constraints for speed and altitude were added to the plan before the fule action was taken. After the fuel prediction was activated the altitude contraints disappeared. When the flight was tried the speed restriction were followed but the altitudes limits were not.
  8. canuck21a

    ILS Approach - Course Corrections

    Ok then, I just flew the same plan again but with no Active Sky or other external connections (ACARS, etc.) There were no deviations on approach. Perhaps, like another pilot mentioned, there is a potential influence being forced on the sim by either Active Sky or another add-on that perplex the flight system.
  9. canuck21a

    Exterior Lights during TAXI

    Hello, I have just completed my first flight after updating to the latest update 1.0.1.3. I used the Turn around state and full copilot. I did not make any premature setup actions but waited for the checklist to do so and I did not skip any CL items. I can report that at no time did the CL stop/hang and the flight completed without any apparent issues.
  10. canuck21a

    ILS Approach - Course Corrections

    Just got back to the flight sim word after a few days or real work (and golf) I decided to set up for a flight from London to Amsterdam (ORBX England and Netherlands True Earth). Active Sky was used (ver 6773). I used the SID/STARS/TRANS for the conditions that existed at the time. Approach was to 27. I checked the fps values (not average as I did not have that set up yet) at various phases during the flight On Ground EGLL: 26-30 Takeoff: 26-30 FL230: Tail: 45-75 InstrumentView: 35-50 VC: 35-60 Enroute: Tail: 70-105 InstrumentView: 60-80 VC: 65-100 Descent: VC 35-50 7000 ft over EHAM: 28-40 APP: 30-40 LOC: 35-40 (When set on) GS: 30-40 (When set on after GS indicator was close to the line) 5 miles out: 30-40 LOC/GS Active At ~3 miles the plane made a small course correction. At ~<1 mile the plane again made a slight adjustment System Specs GAMER (May 2017) Asus Maximus IX Hero i7-7700k 4.2 GHz (OC 4.5Ghz) Water Cooled 32 GB RAM 3000 Disks All SSD; C (system): 512GB M.2, E; 1TB (FSX/Steam), F: 1TB (P3D) Graphics: EVGA nVidia GTX 1080 OS: Windows 10 Pro 64 Controller: Saitek USB Yoke/Pedals Monitor: Acer CB280HK (UHD 4K2K) HDMI P3D Setup (Images from external site): Display: Lighting: Realism: Traffic: World:
  11. canuck21a

    Un-docked Options MCDU Sounds

    Thanks for the reply. I shall deal with it.
  12. canuck21a

    ILS Approach - Course Corrections

    I will try some Clear Weather flights to see if this happens.
  13. Hello, I have been using the Options and CAPT MCDU un-docked on a second monitor. I notice that if I change the focus from the main P3D screen to the options MCDU the copilot voices are blocked. I can only hear them if I then refocus on the main P3D screen. I have Windows 10 sound to not do anything in the communications settings. Is this to be expected? Any suggestions as to how to overcome this?
  14. Hello, On a few flights I have noticed that a mile or so before final whilst on a set ILS/GS approach the aircraft seems to do a dippity-do; that is, it seems to want to make a slight course correction with a bit of a wing dip back and forth. Is this expected ? I do not recall anything like this with the previous A318/319.
  15. canuck21a

    Exterior Lights during TAXI

    Thanks Rolf, Good to know that I have not lost my mind