canuck21a

members
  • Content Count

    63
  • Joined

  • Last visited

About canuck21a

  • Rank
    Flight Student - Airwork

Recent Profile Visitors

1656 profile views
  1. canuck21a

    Managed speed issues

    Just had an event today after many flights with no issues...... Operating System: Windows 10 Pro Ver 1803 Build 17134.472 Simulator version: P3D v4.4 (4.416.27077) Airbus version: Updater: 1.3.0.1 A320 1.2.3.1 Add-ons in use: FSUIPC5 (FS-Products ACARS), Navigraph 1902, ORBX SC/NC/NRM/PNW (Note: Clear Skies ASP4 is installed/available but not enabled on this flight) System specs: Asus Maximus IX Hero,i7-7700k CPU @4.2 GHz, 32GB Ram, EVGA GTX1080, SSD's. System build April 2017. All recent updates applied.  Description of the issue: Flight Plan Extended: YPPH N0120F360 KEELS5 MERIB T12 XMX G209 TKG CARL1A WIII During the Descent phase the PFD speed dropped to 190 although it should have been B280 according to the STAR. It almost looks like it decided to use the Approach speed. I also noticed that the speed select indicator on the PFD kept jumping up and back down as if it wanted to go up but was being told to keep down during this period. I changed to using the manual speed knob during the descent and all was well. I switched to managed speed when the speed was to be at 190. The rest of the flight was normal. Are you able to reproduce the issue? If so, what are the exact steps you are taking for this issue to happen? After at least 8 flights with no issues this happened. Additional information (route, weights, special area where the issue occurred etc.): I have attached the logs, flight plan and load sheet use for this flight all in one zip file. I could only grab a screen shot of the vc at the time. A320_Data_DRW_2019-Feb-19.zip
  2. canuck21a

    Managed speed issues

    Just read this..... Back in December I made several flights with the A320 using airways that crossed the BOI waypoint. I had speed control issues somewhere around that point as well. Wondering if there are potential Navigraph issues?
  3. canuck21a

    Managed speed issues

    Now getting back after my manually entered constraints. YSSYYMML01 64LOC ANKUB SBKWI KADOM A576 PKS Q94 CANTY ARBE2A Each of the first four departure waypoints were given different altitudes and speeds. AP was engaged before 64LOC. All speeds and altitudes were maintained. This is something that I had yet to see with the new bus. The ND markers also seemed to match the plan. I will now have a look at injecting weather to see if that has any effect.
  4. canuck21a

    Managed speed issues

    Hello again, I have now completed two more flights with the A320 United. The last flight was from Brisbane to Sydney at FL340 HUUG06 HUUGO H62 CORKY H12 BOREE BORE9P Rwy 19 to 16R Weather was CAVOK with no external weather engine. I used Navigraph 1902. I did use my multiplayer JoinFS (simconnect) and my ACARS (FSUIPC) with flight saves every 30 minutes. I had full logging turned on. The SID contained a speed restriction while the STAR had both BxxxxAxxxx and specific altitudes. It also had a speed restriction at one STAR waypoint. This seemed to have everything in it that had not worked in previous versions. In full managed mode for the entire flight every speed restriction was met as were all of the altitudes. It is hard to complain when everything seems to be working. My next flight will use manual restrictions for speed and altitude to see if there is a difference between Navigraph generated characteristics and manually entered ones. One thing that I continue to see is the MCDU showing an altitude that does not match the one that is being flown. Image attached showing two mcdu views for the same waypoint.
  5. canuck21a

    Managed speed issues

    Greetings, I have waited quietly in the wings in anticipation of the new "full" version. I removed both of the full installs (A318/319) & (A320.321). I also removed all folders in "My Documents" that had anything to do with Aerosoft. I then purged all remnants using CCleaner followed by a defrag. A reboot was completed. I then installed the new versions and rebooted. I then updated my Navigraph. I added no paints. Today I tried my first flight with the A319. A plan was created in Australia YPDNYPTN14 with SID LAKUP4 and a ILS-Y OM14 approach. The level was FL190. The departure had an altitude restriction A3000 and B5000 at different waypoints along with a 600 foot intersection turn after takeoff. A bit of a task. After take off the AP was turned on just before the A600 waypoint. The copilot and flight system worked flawlessly. I watched with hands off and the plane climbed to 5000 and stayed there until it passed the ALT restriction. Just after passing the plane started to climb to 10000. It levelled off a bit at 10000 and allowed the speed to reach 300 then began a feisty ascent to FL190. At TOD it started to descend and also reduced speed to ~280 (had to add some speed brakes here). After ILS Loc captured I still got the wing wave after a bit. Close to GS I enabled App. The plane flew in like a happy bird with no wing wave near the airport. So far so good....more to come later.
  6. canuck21a

    Managed speed issues

    I have just completed a return flight from CYVR to KDVT. The flight from KDVT to CYVR yesterday had no problems. On this occasion the speed problem occured. (Has happened on other flights but not all) Operating System: Windows 10 Pro Ver 1803 Build 17134.472 Simulator version: P3D v4.4 (4.416.27077) Airbus version: Updater: 1.2.2.0 A320 1.2.2.1 Add-ons in use: FSUIPC5 (FS-Products ACARS), Navigraph 1813, ORBX SC/NC/NRM/PNW (Note: Clear Skies ASP4 is installed/available but not enabled on this flight) System specs: Asus Maximus IX Hero,i7-7700k CPU @4.2 GHz, 32GB Ram, EVGA GTX1080, SSD's. System build April 2017. All recent updates applied. Description of the issue: After a normal take-off and climb to Cruise the sim decided to change the cruise speed to 222. This resulted in a loss of altitude and the need to disengage AP, change to manual speed. Once recovered AP speed ,NAV and ALT were re-established. Managed speed was never recovered. Upon final approach speed was engaged for landing and all check list actions by copilot worked without issue. Are you able to reproduce the issue? If so, what are the exact steps you are taking for this issue to happen? An attempt to save all logs and a special video was tried on a previous flight but no issues occurred. Today the flight was the reverse of the previous one but no video was captured and the speed issue occurred. Other flights along a similar route have also presented this issue Additional information (route, weights, special area where the issue occurred etc.): I have attached the logs, flight plan and load sheet use for this flight all in one zip file. I could only grab a screen shot of the vc at the time. a320troublefile1.zip
  7. canuck21a

    Speed Constraints in SID

    Thanks for the reply. I am using the latest build. I shall await the next update to see if things change.
  8. I had posted a query regarding setting a speed constraint in a SID last weekend but no replies have come to date. Perhaps I placed it in the wrong section?
  9. Hello, I decided to do some comparison testing to perhaps find where some strange things begin to happen. I have a single flight plan with a single loadsheet that was used for each of the successive flights. I am using the latest experimental build 1.2.2.0 and updater version 1.2.1.0 I used the standard American Airlines A319. I used the same options MCDU settings for each and proceeded with a full managed flight for each using copilot. Here are the raw details of the flight inputs: Loadsheet 132;3300.00;6211.73;84;0;20.8;0.8;39725;54113.00;5711.73;59781.40;58170.19; [CoRte] (KMIAKTPA01.flp) ArptDep=KMIA ArptArr=KTPA RwyDep=KMIA26L RwyArr=KTPA01L RwyArrFINAL=ILS01L SID=WINCO2 STAR= APPR_Trans= Waypoints in MCDU OHOFO BORLE MEAGN WINCO LAGOO SELMN Flight 1: Used the autogenerated values for speed/altitude; that is, I made no changes to the waypoints and their assigned values The flight proceeded on Autopilot without issue and all plan values seemed to complete as expected. Flight 2: Once again the autogenerated values were used save for one change. The OHOFO waypoint was changed to have an altitude constraint value of -5000. The flight proceeded on Autopilot, ascended to 5000 before OHOFO and once past that waypoint the aircraft climbed to cruise as expected. Speeds were also as expected <250@10000 Flight 3: Once again the autogenerated values were used save for two changes. The OHOFO waypoint was changed to have an altitude constraint value of -5000. The OHOFO waypoint was changed to have a speed constraint value of 200. The flight proceeded on Autopilot, ascended to 5000 @ 200 knots before OHOFO and once past that waypoint the aircraft began climbing to cruise as expected; however the speed stayed at 200 Should it not have changed back to not exceed 250 by itself ? The MCDU speed values at the next waypoint was 316 but I expected the aircraft to accelerate to 250 until it reached 10000. Am I supposed to do something different to get this thing to maintain expected climb and speed? ( I did press the speed button just in case it needed to be woken up but that made no difference)
  10. canuck21a

    P3D v4.4 & GSX 2

    Just a confirmation that the suggestions made by Hanse are correct. After deciding for no push-back I started the engines and the CL continued shortly after engine 1 was stabilised.
  11. canuck21a

    Transport Company Preview

    Thanks for the update. :) Looks like there might be fun for next Autumn (after golf season)
  12. canuck21a

    P3D v4.4 & GSX 2

    Thanks Rolf, I shall have a go a that on my next flight.
  13. I recently updated P3D v4.4 with a clean install followed by a clean install of all of the P3D v4.x buses. I updated all buses to the latest experimental build. Test flights showed no obvious issues. When I decided to try GSX 2 things seemed to go amiss. The issue I have is that I sometimes wish to proceed without pushback using the full copilot functions. Not using GSX this is not a problem as the checklist routine offers this as a standard option. I have attached an image that has several parts that sequence what I see. Essentially all goes well until I select the GSX option 4 in the GSX "Select pushback direction" screen. Then I get the "[GSX] Have a good trip" message followed by a screen with FOLLOW GSX INSTRUCTIONS that never goes away. I then have to disable the GSX pushback from the MCDU to get the checklist to continue. I am not sure if this is a bus problem or an FSDT problem. Also the FOLLOW GSX INSTRUCTIONS is blended into the P3D header rather than below the menu where I think it should be.
  14. canuck21a

    Transport Company Preview

    Anything new since early September ? Christmas is coming soon
  15. canuck21a

    GSX Automatic Door Handling

    I received a notification from FSDT that GSX2 has been updated with a new "Autopilot" feature that is supposed to handle many actions automatically. To what degree does this impact on the recent Aerosoft experimental update and GSX_Doors ? <quote> GSX Update GSX has been updated, adding a new feature that has been requested by our users: the Autopilot mode. In Autopilot mode, GSX can be set to perform all Boarding/Deboarding services automatically, without user intervention. See the "Assistance Services Auto Mode" option in the Simulation Settings. </quote>