Jump to content

ois650

Members
  • Posts

    425
  • Joined

  • Last visited

  • Days Won

    23

Everything posted by ois650

  1. Hi, The airplane is AR capable. The requirements are dual FMS installation, dual GNSS with inertial positioning, dual PFD and NDs, dual Flight Directors, at least one Autopilot, dual Radio Altimeters and TAWS (which the 650 has of course). Re: SB list, standby on that one! Brgds, **Edit: I think I've misunderstood your post, I was referring to AR as in RNP AR approaches.**
  2. Hello, This is possible, click on the lower portion of the control column and it will sink down. Brgds
  3. Hi all, Have you adjusted your UI scaling in any way?
  4. Modifying the default data files will cause an error message on opening X-Plane 11, and will not allow the sim to run.
  5. Prior to shutdown, operate the engine at or near IDLE for a minimum of two minutes, to dissipate heat and stabilize internal operating temperatures. Taxi time at 70% N2 or below may be credited in the two minute cool-down period.
  6. I agree it would be nice and realistic, but X-Plane will throw an error message if you alter the in-built data. Hopefully in XP12 we'll be able to have two Navigraph databases at once.
  7. Depends how hard you land
  8. Check it out in sim. The gear and gear pins are exactly as they are in real life.
  9. Hello Rich, Thanks for taking the time to write this up. 1. With VFLC engaged and with VNAV PLAN SPD ACTIVE, the FMA VFLC Speed shows in Cyan (Blue). The FMA "VFLC" should be magenta. Anytime the FMC is generating the guidance cue, the label is magenta. Anytime the guidance is through manual control from the from flight guidance panel, the label is cyan. So with VFLC and VNAV PLAN SPD ACTIVE, VFLC should be magenta. If you move the SPEED knob, then you've taken manual control of the speed in VFLC and FMA annunciation changes to cyan. VNAV PLAN SPD is no longer active. You have re-activate it to get it go back into CDU and make VNAV PLAN SPD active again. BTW....in the CL300/350, we're not allowed to use VFLC when it is commanding a Mach speed (e.g., 0.78M). Bombardier found out that if the FMS suddenly drops the planned climb speed in Mach, it reverts to the minimum programable Mach speed of 0.50M. Things could get a little exciting if that happens climbing in VFLC and tracking 0.50M. 1. FMC commanded speeds of course should be magenta, and are (as far as I can recall). I'll do a quick flight soon to verify. If not, I'll file as a bug. Tested in VFLC, verified and filed (2538) Fixed in BETA build only 2. TEMP COMP is ON by default. TEMP COMP should be OFF by default in the FMS. That's Collins standard. In fact, TEMP COMP is not allowed in Collins FMSs that are not to the Fusion FMS level because TEMP COMP can cause dropping of the turn direction on a VA or CA leg in the FMS. The famous 10,000 approach deletion issue from several years ago. 2. On initial release TEMP COMP was on by default, it should be off now. Again, I'll verify this. Temp comp is off by default. Thanks for the heads up re: not allowed unless Fusion. 3. Climbing in VNAV and approaching a waypoint with an "at or below" constraint, the altitude alert sounds when 1000' below this constraint. The altitude alert tone sounds only in relation to the altitude set in the pre-selector window (cyan) using the ALT knob. It never sounds due approach or deviating from a VNAV altitude constraint (magenta). 3. Will verify and file if necessary. Could not replicate, will keep an eye on this one though. 4. I have an older FCOM for the CL605 (not CL650), and it says that the that the A/SKID IN TEST advisory message goes out after 6 seconds. Was this a change in the CL650? 4. I don't believe it was changed for the 650, will check this out. Verified and filed (2537) Fixed in BETA build only 5. LAMP TEST switch … Select 1 does not test lights only on BATT power. Select 2 does test all lights. It's a bit difficult to test using position 2 and then to look up to check the overhead. Some add-ons have a feature that if you select a switch with the mouse by holding the mouse button down, then slide off the switch, the switch stays in the selected position (when a momentary push or movement is what the switch supports) so that you can then move the mouse cursor to active another switch. Felis uses this with the B747 INS key entry when multiple key entries are required (e.g., pushing down the "9" and "7" simultaneously). Just a thought... 5. FCOM states LAMP TEST 1 & 2 behave identically with the only limitation being it can't be used when ATS is engaged. Re: difficulty holding down and checking lights, I will raise this with the developer and see if something can be figured out. Tested, can't find issue. 6. yesterday, I was having issues getting the checklist to advance and to speak yesterday. I could advance using the CCP's push button, but nothing else. No virtual co-pilot. Also, the joystick binding for checklist advance did not work. Could be one-time glitch... 6. Haven't experienced that behaviour before, glad it's worked for you since. 7. I have a Go-Flight MCP Pro. Using the GoFlight Interface Tool XP, I was able to bind all of the buttons and knobs on this device using the datarefs provided by HotStart. FIRST TIME EVER for an add-on! THANK YOU!!! However, the dataref for CL650/FCP/ap_eng was not working to cycle the AP engage switch. I was able to set a keyboard key to active this switch on the FCP, but I can't get it to control the FCP AP switch through GoFlight using the CL650/FCP/ap_eng. Is there something wrong with this dataref or binding? Am I using the correct one to active the AP switch on the FCP. 7. Will get the developer to check that out for you. Best regards,
  10. Hello, Please confirm you have done the following: 1. Set up your Navigraph Charts in User Settings, and Navigraph has authorised the CL650 to access charts. 2. You have selected "CHART" on the right side CCP Brgds
  11. Hello, We haven't had this issue with any other users. Would you mind uploading your log file here please? KR
  12. I meant clearing the calculated value in PERF
  13. Hello, Can you upload a screenshot of your PFD and MFD when this behaviour occurs? Thanks
  14. With further testing I was able to replicate this. Thanks for your report!
  15. The secondary database is the default X-Plane one. Unfortunately there is no way to update this. Yes this is indeed the case.
  16. Hello, If you join the Hot Start Discord server linked below some community members have been sharing resources. KR
  17. Hello, Passengers come (by default) with between 11kg and 19kg of bags. There is no way to input a time crossing restriction into the FMS-6200. You must manually adjust your speed to meet a restriction at your oceanic entry point. Brgds
  18. Once you select sensed fuel your in-flight total should remain accurate.
  19. Hi, Just to keep you updated, this is now fixed for the next release version. KR
  20. Hello, At this time there is no calculator available. The team has the numbers, just trying to figure out the best and most straightforward way to present these to the user. KR
  21. Hello, Unfortunately I was unable to replicate this behaviour. It's possible that it was previously a bug and it fixed in the latest beta version (and soon the next update). KR
  22. Hello, Can you confirm what airport this happened at? We will try and reproduce. KR
  23. Hello, This has been implemented for the next release version. KR
  24. Make sure you select CLB power before passing 15000ft, otherwise ATS will lose N1 target and disengage. This may be the issue?
  25. Hello, The menus behave as they do in the real ProLine 21 suite. KR
×
×
  • Create New...