Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

flyingfudge's Achievements


Apprentice (3/14)

  • Reacting Well Rare
  • First Post Rare
  • Collaborator Rare
  • Dedicated Rare
  • Conversation Starter Rare

Recent Badges



  1. @KirkR Your solution seems to work but I've found the easiest solution, especially if flying online, is instead of advancing the thrust levers to activate the ATS, instead press the ATS button on the glareshield panel. If it flashes and disconnects then press it a second time and it always activates with the second press. This method is an approved manual alternative to the automatic engagement when advancing the thrust levers.
  2. Route: LZIB/31 TOVKA1A TOVKA DCT LANUX DCT OKF DCT HDO M725 KOBUS P31 BUKIG DCT NUKRO NUK07R EDDB/07R I had a CDT when airborne selecting the RNP 07R approach in the FMS. I then used the situation auto-save but as soon as I selected the approach the sim crashed again. It even crashes if the RNP 07R approach is inserted on the ground before taxi. I tried it on the v1.7-beta 1 just out of interest and the same happened again. Attached 2 x Log.txt: Aircraft on ground in 1.6.1 & airborne in 1.7 Beta.(Log2) ( If the ILS 07R is selected it doesn't crash - maybe a Navigraph error?? ) Log.txt Log2.txt CL650_Log.txt CL650_Log2.txt
  3. Unfortunately I'm still getting the same problem. Hopefully it will be fixed in a future update.
  4. Make sure you've got a valid N1 value indicating on the EICAS. eg: Automated "in range checklist" doesn't always automatically do this for you. You have to insert the appropriate N1 thrust required for the go-around in the FMS "PERF" page. Without a valid N1 the ATS disconnects and will not reconnect until the N1 value is set. I'm pretty sure a similar situation can occur with the after takeoff automated checklist. I believe if it's delayed past 15,000 ft the ATS will lose the N1 target and disengage. ( after t/off checklist calls for transition to CLB thrust )
  5. @KirkR I did a short flight with a new airframe and the ATS worked as advertised. I then shut down the aircraft completely to cold & dark at destination. On the next flight the ATS again worked perfectly so it appears that the problem arises when the aircraft is left in a state other than cold & dark. It's not a deal breaker but I'm sure Toto & the team always strive for perfection so I'm sure it'll get fixed in the near future once they see our posts. I agree with you this is an amazing aircraft. I purchased it on day one & I honestly haven't flown anything else since.
  6. @KirkR I'm glad I saw your post as exactly the same has been happening to me for some time now. I thought it might be the X-Touch Mini that I use conflicting which is why I didn't post sooner about the problem. I'm using Windows10 so your MacOS Monterey is not a factor. I tend to leave the aircraft in a turnaround state with APU running and sometimes use the same position on reload and other times untick the "restore position" box and load into another airfield. I get the same result with both scenarios. Unlike yourself I generally don't advance the thrust levers but press the ATS button at the start of the take-off roll so thrust lever movement can be discounted as well. If I press the ATS button a second time it then stays engaged as demonstrated on your video. If I get a chance later today I'll try again with a new airframe and see what happens. It could be connected to the states being saved between flights but I'll report back here with the result.
  7. If you wanted to use RA minimums it should be set at 200 RA which is the figure in brackets ( height equivalent ) next to the 861ft DA on the approach plate. RA minimums are used for CAT II and CAT III approaches.
  8. Dunno about the CTD but the stuck nose door pin is a result of the hydraulics being energised and the compartment switch in the wrong position. If you select the nose door switch to the open position then you should be able to remove the pin. It's a failsafe system to avoid the doors being closed with someone in the wheel bay.
  9. I've had exactly the same problem. Surely the High Level Shutoff Valve should apply to the right wing and not the left? Or are we saying that the left tank was full originally but that it drained into the right tank after being parked on a slope? In that case, why is the right pump still showing "OP" when the tank is full?
  10. My last but one post above with a pic. of a clean wing is showing 0.4886. The picture above with ice depicted correctly is 0.8358 I presume these are the datarefs in question but if there are others how do I find them?
  11. No problem with it showing ice sometimes. I don't know what exactly the icing numbers mean but presumably they reflect the intensity of ice being experienced on the aircraft wing. Maybe it's just a bit of fine tuning needed to display ice on the wing at lower levels of sublimation. However there's something not quite right as in both these cases the aircraft was unable to get airborne and climb. In real life you have the benefit of touch but unfortunately unless it's depicted visually in a simulator it'll end up ruining your day!
  12. Don't know whether it's x-plane wrongly reporting ice or something to do with Toto's simulation of temp/humidity over the past 24 hours but the problem is that there's no visual ice on the wings. Having spent considerable time setting up the aircraft to find that it won't get airborne due to ice that cannot be evaluated visually on the walkaround completely ruins what is otherwise an amazing simulation of this aircraft. It's the same again at a different airfield (LFLB) with clear skies and a temperature of +8C. Are anyone else having similar problems or is something maybe affecting the icing datarefs on my system?
  13. https://forums.x-plane.org/index.php?/files/file/50510-popup-icing-display/
  14. Hi. Flight out of Dublin yesterday at appx. 15.00 local time. Outside air temp +10C & dew point +7C There was no visible ice on the top or underside of the wing and the CAS was clear but on take-off the aircraft fell out of the sky. I re-ran the saved situation a couple of times with the same result but then de-iced and it flew normally. A couple of questions. In that temperature scenario the likelihood of icing, especially of an accumulation that would prevent the aircraft from climbing is not realistic. Whether this is a shortfall of X-Plane's weather depiction or not, surely the presence of wing ice should be visually obvious on the aircraft regardless. I brought this up on Discord and someone kindly pointed me in the direction of a Lua script that interrogates X-Plane's icing datarefs and indeed it did show wing icing. This is not a criticism of this excellent aircraft addon but merely an observation. If the aircraft is detecting ice on the wing regardless of whether X-Plane is correct in it's assumption then surely the only way that can be reported to the sim pilot is in a visual representation which in this case it didn't. I understand that Toto has introduced many variables into icing such as overnight temperature, humidity and dew point etc. but in reality a 10C temperature in the middle of the afternoon on an aircraft that hasn't flown on that day would not have any significant ice and certainly not an accumulation of ice that would bring down an aircraft on take-off. I'm enjoying every minute of this remarkable aircraft creation by Toto, Goran and the team but would appreciate your thoughts on my comments.
  • Create New...