Jump to content

canuck21a

Members
  • Posts

    86
  • Joined

  • Last visited

Everything posted by canuck21a

  1. I have both Steam and Store versions of MSFS. I have the free Paderborn installed. It is shown as not installed. (Also no other item in Community folder shows as installed. I have the CRJ also installed and it is listed as not installed. Both are in the Community folder. I moved them to a safe place and restarted MSFS. No items listed. Shut down sim, put them back and restarted. Listed as not installed. Removed from Community folder. Re-installed CRJ using installer. Started MSFS but still listed as not installed. Asobo messed something up again, it appears.
  2. I have noticed a potential issue with the options for sound setting for the new A330. Unlike the new A318-A321 the sound volume for Checklist PM cannot be changed from 80%. I was also informed by a friend that purchased the new A330 that he is encountering the same odd behaviour.
  3. Just dropped in to advise that 1.0.0.6 continues to present the co-pilot's inability to go past trim set UP1.6. I am now trained to slap him and do the rest myself.
  4. I have now set up a new flight, checked various values and took some pictures. First I set up the fuelplanner: After starting P3D v4.5 HF2 I set up the aircraft (Installed version: 1.0.0.5 No updates available for this product!) in the Turn-Around State. Getting ready to proceed with MCDU work I usually begin with Loading the Aircraft: After completing the initial phases with my copilot active it was time to get pushed back, start and set up the control surfaces: The copilot was busy spinning the trim wheel but seemed to get tired and stop at 1.6 UP. Note that the GWCG value displays as 29.5 The nagging helper kept asking me to fix it, so I did and eventually the Checklist continued: After that all went well so I checked the load sheet one more time just before take-off. I saw a value that confused me: So my issue with automatic trim setting continues.
  5. I will check what Secondator asked on my next flight. What Hanse has said: "If you are using the CL as well as the Copilot then this will automatically be done e.g. checking and setting......." is the issue that I am having as the CL/Copilot was not completing the full adjustment to 0.8UP. It was stopping around 1.5UP. I shall see if this continues on my next flight.
  6. I am using A330 1.0.0.5. I normally start with Turn-Around state. The fuel planner is used. I load the info from MCDU and can see that the trim value for the flight is UP0.8. When the checklist runs and it is time to adjust trim the co-pilot begins to trim down but stops around 1.5 UP. I have to manually complete the adjustment. This has happened on two successive flights. Am I alone with this behaviour? Note that I do not click on the Adj CoG Reset button. Should I be ding that each time I use the fuel planner? Maybe it makes a difference?
  7. Thank you, That has helped. I still do not know what the other two values of '84' and'0' relate to but they seem to be constants as is apparently the DOW. On that basis I can now leave you alone on this topic.
  8. Thank you for the reply. I have reviewed what you suggested; however, there continue to be fields that are not clear to me. Perhaps the are calculated fields but it would make my efforts at documenting values presented much easier if I knew what they are supposed to represent. The ones in question are those marked with '?' in the text file.
  9. Hello, I was wondering if the powers that be would be kind enough to provide the header details for the present A330 fuel planner output file? Data output= 240;15000.00;22441.68;84;0;35.6;0.6;127326;162486.00;21941.68;184356.01;172324.78; PAX;CARGO;?;?;?, etc. Thanks for any help given..; and.. Happy New year !
  10. Hi, Although I was not an original poster to this I can add my experience from the last two days. Prior to yesterday I had no issues with the co-pilot nor the checklist. 1. I was departing Thule Greenland and I believe that I was following the steps correctly. I was asked to taxi to 10+. I did so but nothing happened at 10+ or above. There were some issues with pushback with the plane deciding to taxi as I was not asked to put on the parking brake. I stopped and started again but no joy. 2. I restarted P3D and the flight from the turn-around state. I then completed the push-back (no GSX active) and was eventually given the go-ahead to taxi. Once again nothing happened after 10+ knots. II managed to fumble my way through the 2600+ nm flight without crashing the thing. 3. Today I started a new flight in NZAA to NZCH with GSX active. All of the checklist items worked and there were no surprises. Well, there were some new items displayed that I do not see with the A320 but things seemed to work. The fact that I was given the go to taxi (checklist) suggested that the triggers were all lined up but something was not working in Greenland (it was 9:00AM and well below 0 Celcius but still dark)
  11. As a temporary quick fix I renamed the new planner with a different extension and used my backup copy of the planner exe for the A318-A321. I can now resume using the planner for my A318-A321 flights as it now shows the expected values. Of course I cannot use this exe for the new A333 but that is ok by me for now as I can manually swap the planner executable when required.
  12. Hello, I tried removing the xml but the values did not change. I reported this yesterday and the reply from Masterhawk was: We changed the fuelplaner Logic for the A330. There are now new config files for the A32S series. Have to check if they are already released. Else it will happen with next update.
  13. After installing the new Bus I seem to no longer have balance values presented for the previous aircraft although the A333 does present these values. Is this to be expected?
  14. 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
  15. 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?
  16. 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.
  17. 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.
  18. 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.
  19. 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
  20. I have recently re-loaded the FSX Beaver and used my existing files to upgrade the install to version 320. I am trying to see if there are any further updates since Version 320. Many thanks, Darryl Wightman
×
×
  • Create New...