Leaderboard

Hello captains, I wanted to present you my Lua Script used as copilot in the 737. I wanted a very robust and simple solution, and so far the Lua script has proven to be reliable. While there is some limitations stated in the PDF manual I have written for you, it's a great help not to fly alone and have a very simple but efficient first officer ! All the best, and please let me speak about Speedy Copilot ! What it Speedy Copilot ? Speedy Copilot makes for you the steps normally done by the first officer and pilot monitoring, when you are pilot flying and captain of a Boeing 737. Speedy copilot is intended for the IXEG 737 (version 1.21 and above). It was tested and works with X-plane 11.20 and IXEG 1.21. It is not very realistic to do all the steps required in the procedures on your own. The Flight Crew Operating Manual makes a clear separation between actions from the left hand seat and the right hand seat. So we'd like to have the right hand actions (F/O, PM) done for us in reaction to the phase of flight and to left seat actions (CPT, PF). Several options exist to have a virtual copilot flying with you In X-Plane. But they might be technically complex, challenging to maintain, or require payware softwares. The intent was to provide a simple solution! We have made a transcript from the FCOM into a Lua script for the IXEG 737. We have made the transcription of the following procedures : Preflight procedure (triggered by the left hand side oxygen mask test) Before start (triggered by the beacon to ON) Before taxi (trigger by both engine generators to ON) Runway Entry procedure (including TCAS control, triggered by left outboard landing light) Take off run : gear and flaps retraction schedule (automatic trigger per rate and speed) Flight 100 and climbing items (automatic trigger per captain altitude) Flight 100 and descending items (automatic trigger per captain altitude) Approach, flaps extension schedule (automatic trigger per altitude and speed) Go around (reversion to Take Off procedure above) (automatic trigger at positive rate) After landing procedure (triggered by speedbrake down on ground) Apron entry (lights and doors) (triggered by runway turnoff lights OFF) Shutdown procedure until turn around state (beacon to OFF) The procedures are either manually triggered or automatically called. The Copilot is not calling the checklist. The copilot is doing the procedure. DOWNLOAD

Hello All, This will serve as a formal forum announcement that we have released the version 4.8.1 update for SkyMaxx Pro. All customers who have purchased SkyMaxx Pro v4 up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase SkyMaxx Pro v4 from today forward, your purchased download will already be updated to version 4.8.1 for you. What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php 2. Find your original SkyMaxx Pro v4 download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: What's New / Changed: Improved the appearance of cumulus congestus, cumulonimbus, and towering cumulus clouds (much less of a stacked / layered appearance to these clouds) As always, thanks for purchasing from X-Aviation!

Just to clarify again, you can set a decision altitude (height above mean sea level) in the Hotstart TBM, but you can't set a decision height (height above ground level). AFAIK the latter would be required for CAT II approaches, for which the TBM 900 is not certified anyway. So IRL it would add bit of safety but that's about it, in Sim it doesn't really matter.

Not sure if you made any headway with this issue but I took a look at the last log.txt file you posted in this thread and looked through it. It is quite possible that at the time of the crash, it may not be SMP that causes it directly, but rather indirectly. Since you have many other plug-ins running, they are all competing for processing during your flight, including SMP. The possibility that another plugin is processing at the time that SMP is wanting to refresh, that this could be causing your crash, which is evident with the last line of the log (the XPLM plugin, which I believe is the X-Plane Plugin Manager). With regards to plugins, no matter whether or not they are commonly used, the fact remains that not everyone will have the same results using them. Past historical discussions about users' systems vs. performance & stability benchmarks, indicate that since every user's system is different, coupled with the fact that we all have varying system configs for the OS and any other programs that may be running in the background, can have a deciding factor on crashes. One question that I didn't see asked was whether or not your system is overclocked, and if so, to what degree of overclock is in place as well as how stable the overclock is. I've been around the bend many times over the subject of overclocking cpus and gpus and I can tell you that not enough proper testing of overclocks can exhibit strange results. One easy way to check the stability of X-Plane, is to run a scenario and then hit CTRL+SHIFT+F on your keyboard, to get your cpu and gpu timings. Obviously the lower the number the better, but more importantly, compare the two and see which one is higher. Depending on which is higher, is dependent on your rendering settings. There are plenty of helpful tutorials out there to help decide which settings to adjust, but as a base. If I were in your shoes, I would visit the render settings, bring down some a notch and see if that might help.

The real TBM 900 has it, it's just not modelled. It would be a question for Toto or Goran if they may implement it with a future update. Anyway, it's not a big thing as baro minimums work too. The only downside is that it's Laminar default code which means we are limited to < 10000 ft. Not enough if you want to visit Aspen or Telluride.

FSGRW will always provide much better cloud representation when necessary compared to ASXP if SkyMaxx Pro is in use. This is because of a cooperation between the developers to add more features when the RWC+SMP+FSGRW combo is used.