Jump to content

herve

Members
  • Posts

    18
  • Joined

  • Last visited

Everything posted by herve

  1. thank you for the answer "With a working ADG" , that's why I said a minor detail :-)
  2. Hello Maybe the subject has been discussed, I did not find. It is a minor detail, but this plane is so detailed that it would add reality to the external inspection visit, the hatches of visits of the Challenger are practically all modeled on the fuselage except the hatch of the ADG, is it an oversight or a will due to a constraint? Thanks Hervé Sorry for my language, I use a translator.
  3. Hello Can be an answer here. extracted from "Challenger 605_650 Pro Line 21 Advanced Flight Management System (FMS) [Entertainment].pdf" RULES: The rules that follow are applicable to selection of a STAR and transition. • When a STAR is selected or changed, if the STAR is not associated with a previously selected approach or runway, the runway or approach selection on the ARRIVAL page is removed. • When a STAR is selected or changed, and the navigation database does not define the intended path to the waypoint and the waypoint is immediately preceded by a heading leg or a course leg that does not terminate at a fix, the FMS suppresses the waypoint display and removes the associated waypoint’s altitude. This issue can occur for departure, arrival, approach, and missed approach. For US RNAV operations, manually selecting and inserting individual, named fixes and altitude restrictions from the database will restore the waypoint display. • If a STAR is re-selected, and a leg of that STAR happens to be active, that leg stays in the flight plan as the active leg, and the legs of the new STAR, which is preceded by a DISCONTINUITY, follow the active leg. • When the selection of a STAR is changed, this removes the old STAR from the flight plan. The new STAR is inserted in place of the old STAR, unless a leg of the old STAR is active. In that case, the new STAR is inserted after the active waypoint. • If a previously selected runway is not associated with the newly selected STAR, the runway is removed from the flight plan. Bons vols Hervé
  4. Hi Thank you for your answers. @Pils , don't worry I know how to be patient but this question about the opening of dataref is more addressed to the professional team of Hot star than to the motivated volunteers... I'm glad to know that the cockpit tinkerers, of which I'm a part, have the same expectations as us Smartcopilot users. Birdy-dma is already very advanced in the creation of the config file for Samrtcopilot. We have done several test flights and to make the shared cockpit flight with this aircraft 99.9% operational we "only" need these few dataref. So please understand our expectation. Thank you Hervé
  5. hi a little feedback would be nice. 5, 6 writable dataref (HDG, ALT, BARO, COURSE, SPEED ...) and your beautiful plane is "smartcopilotable". This could interest some other pilots, your TBM900 has "only" 123875 downloads :-) https://sky4crew.com/download/hotstart-tbm900-1-08-version-1-0/ thank you Hervé
  6. Hi I didn't know the notions of part 91 and 135 (used in the USA among others). One more thing in my brain :-) To come back to Simbrief and the ETOPS Scenario block, I can do anything I want between 120 and 180 minutes. It's up to me, the head honcho of my company, to define my certification... or not Thank you Hervé
  7. Salut @robder Super, merci The video is is interesting for the implementation and exploitation of ETOPS data using the mcdu. Concerning the CL650 and the ETOPS certification to summarize and if I understood correctly : in private flight do what you want in the USA up to 179.99999 it's cool after that it's ETOPS certified in EU it's 120 ? :-) Hervé
  8. Hi I'm probably a buzzard :-) but I can't find any information on the ETOPS certification of the Challenger 650. Is it certified? What should we choose in flight duration on an engine in the Simbrief Scenario ETOPS block? Thanks Hervé
  9. +1 Me too !!!!
  10. Hello To disable the axis of speedbrakes and use buttons Herve "pilote d'essai" ;-)) I use translator ...... désolé
  11. hello; hope?? cordially Hervé
  12. thank you for the research I will wait :-)) Hervé
  13. bonjour; In futur time, ok for Linux ?? Hervé ( french man ) Ubuntu user
  14. Thank you I received the e-mail, the re-registration was validated Greetings Herve it is a translation via www.systranet.fr
  15. Hello; I sent a message since my account X-Aviation I re-registered myself with the service of the updates. To date, I did not receive any answer. How to make to obtain finally, the update of Corvalis 1.2… Greetings Herve Version Francaise Bonjour; J'ai envoyé un message depuis mon compte X-Aviation Je me suis réinscrit au service des mises à jour. A ce jour, je n'ai reçu aucune réponse . Comment faire pour obtenir enfin, la mise à jour du Corvalis 1.2 ... Salutations Hervé
  16. Merci, je vais le faire sur la page du Corvalis . Amicalement Hervé (google traduction) Thank you, I'll do it on the page Corvalis. Regards
  17. Hello; I think I understood the message; 1 - I unsubscribed by mistake Service Update Corval 2 - I can correct the error by contacting the support service of your site. This is correct? Cordially @pilotman22 Merci pour l'offre de traduction Hervé French texte : Bonjour; Je pense avoir compris le message; 1- je me suis désabonné par erreur du service de mise à jour du Corvalis 2- je peut corriger l'erreur en vous contactant par le service support de votre site. Cela est correct ? Cordialement Hervé
  18. Hello; After several unanswered http://www.x-aviation.com/catalog/contact_us.php sent here, I post here. I never received the link for the update to version 1.2 :-\ How? Looking forward to hearing from you. This is an automatic translation, sorry, I'm French. copy of the purchase: X-Aviation -------------------------------------------------- ---- Order Number: 2338 Detailed Invoice: https: / / www.x-aviation.com/catalog/account_history_info.php?order_id=2338 Date Ordered: Friday 23 July, 2010 Greetings Hervé
×
×
  • Create New...