Jump to content


Popular Content

Showing content with the highest reputation since 10/13/2019 in Posts

  1. 3 points
    So its been a while, time for another update. There was a pause after the rush of FMS work mentioned above. During this pause, I have finished up my NASA obligations...and demobilized from Houston back to San Antonio, where I live, and some much needed stability to my schedule. Last week, I dug back into the FMS code and started coding up the route editing features using the new XP1100 dataset. This is the backbone of the FMS future with regards to performance.....for VNAV calculations, performance progress and also holds. Its one of those things that I wanted to be real sure I was ready to dig into before doing so. This route editing coding will go on for a bit......'route editing' involves building the route data that the FMS will use during lnav and vnav tracking and so is critical to be flexible and correct. It is my belief that if carefully done now, the FMS will be functional and stable for many years to come, which is the most important thing. -TomK
  2. 2 points
    This is an update on the situation to say that we have converted some of our products/installers to utilize the new security protocols Apple requires for OS X Catalina, as well as 64-bit installers. As of this writing, some of our most popular products have been converted and uploaded to our servers. These products that will now work in Catalina are: TBM 900 IXEG 737 Saab 340A Dubai/OMDB TerraMaxx SkyMaxx Pro v4 Pocket Rocket Gate to the Great Lakes: Custer Gate to the Great Lakes: Fox Islands Work continues on updating further products, and we will likely send out a mass newsletter once every product is complete.
  3. 2 points
    Just a short note to say that this problem came back, I guess due to an X-Plane update. To solve it, the option in planemaker is no longer called "nosewheel spring force", it's now called "right and left brake power to help with steering (middle top)", set it to zero. Not sure if Jan needs to update there download version to reflect this? I don't know if I have broken anything by using planemaker 11.36, but I don't know another way. Cheers Iain
  4. 2 points
    I found a small gap to push another update for Avanti. A few things I have on works for sometime now. 1. Flight Model With the latest updates, the FM has left behind, with some weird behavior, specially in the high speed region, where propellers were accelerated well above the 2000 RPM limit, when cruising close and higher than M.60. Now this is fixed and you can happily fly up to the Mach limit (M.67) with no problems. Also The propeller control now is very accurate. You can reduce the RPM for cruise easily down to minimum of 1800 RPM. 2. Terrain Radar In cooperation with DrGluck, the terrain radar will be added, in a way close to how operates in the real aircraft. The terrain button in each display (PFD, MFD) will cycle through weather radar, terrain radar, and off. You can have the terrain radar On PFD, MFD, and on both. But if you select the weather radar in any display, the weather radar has priority over the terrain, and will be displayed instead of the terrain. Going off weather radar, will restore previous status. 3. Tablet I added a huge tablet (the size of a "Pro" model!) where you can add passengers and fuel, as well have full access to Avitab. But there is a catch! You can add passenger and fuel while engines are running! So take care to do it before start any of the engines! At the end I would like to ask you if you want to show your appreciation and support this project, please donate here: Paypal Thanks a lot for your support, and enjoy the Avanti... In the next few days will be available to you!
  5. 2 points
    Hello again. I'd like to give another update. During our investigation into updating our NavData to the XP1100 format, it became apparent that this must be the way to go for long-term future compatibility and more reliable route calculations, including holds, but would require a significant rewrite of the FMS base architecture to do so. So over the last 4 weeks, we have done exactly that. We now have the beginnings of a 2nd FMS running in parallel with... but independently of.... our original FMS. We are running 'newFMS' on CDU1 and 'oldFMS' on CDU2. We will NOT be simulating dual FMCs though. This old/new arrangement only exists so we can compare the new with the old while developing the new. It is much like building a new bridge alongside an old bridge...and when the new one is ready, we will remove the old. Much of the challenges we have faced with regards to drawing routes / vnav have been related to the limited nature of the navData format we have used since we began the project. Moving to a format which have been designed expressly for "navigation processing" will go a long way towards easing our algorithm development. The image below shows the two CDUs, both on the "IDENT" page, but clearly displaying differing data as they use differing algorithms/databases....and for those curious, the pilot CDU displays 'odd' formatting simply because we were testing our new display drawing code. We are very excited moving to this new XP1100 format. We have, in 4 weeks, accomplished what took us over 24 months to accomplish originally. Of course we have the benefit of experience, but the elegance and efficiency of the new navData format and architecture allow us to focus on the FMS functionality by orders of magnitude more than before. With the new infrastructure complete, we will begin working on the route editing. The current navData set only supports about 8 different waypoint types. Arcs are not supported, as is common in today's RNAV procedures, but the new format contains all path/terminator types typical in today's procedures. As usual, we thank you for any patience you have managed to muster as we work to improve the IXEG 733. P.S. Jan and myself will be at Flight Sim Expo in Orlando, FL/USA in a few weeks if anyone wants to talk shop. -Tom Kyler
  6. 1 point
    Great! Going to try that! Thank you very much
  7. 1 point
    Ok. Solved my problem. My Saitek throttle had some screwy button assignments. Appears to be working ok now.
  8. 1 point
    You can file bugs here: http://dev.x-plane.com/support/bugreport.html Be aware that a non-centered range ring might not be a bug per se. In the real G1000 the ring also includes wind information and I think that is also modelled in the xplane G1000. Definitively a bug it is when the ring is totally misplaced.
  9. 1 point
    The "why" I don't know, but just to explain what I meant with "off": 1. It shows a false range. -> That is something Toto has been working on, so it's a TBM "bug" and will have to be fixed by Hotstart. 2. The ring sometimes does not center correctly. -> That seems to be a Laminar bug, but I have no idea if they are working on a fix. If you can reproduce it best would be to file a bug report with Laminar.
  10. 1 point
    Very possible that Laminar fixed it in 11.40. I believe they were made aware of it.
  11. 1 point
    Been busy the last 6 months, new job means more free time so IXEG is getting dusted off and flown again, still loving this little Tin Mouse!
  12. 1 point
    as always, thank you very much for your answers, so I can learn more about the plane, greetings Jan
  13. 1 point
    Thanks for all the input and help from your side. I'll try to keep all this in mind. My last flight was successful, VNAV and LNAV worked fine, although I now tend to deselect VNAV on reaching top of climb.
  14. 1 point
    The scenery errors can be ignored. As long as it doesn't crash, you're fine.
  15. 1 point
    Dangerous Airport Crazy Landings! Happy Friday all! This is a great scenery to have fun with, and yes it exists! Enjoy! https://www.youtube.com/watch?v=biwlMwlnO8k
  16. 1 point
    Solved it was due to RealView plugin
  17. 1 point
    Yes! Ive seen their both the master warning and caution annunciator switches which is perfect for the TBM.. not the cheapest though. DE-ICE panel now ready too
  18. 1 point
  19. 1 point
    Those are virtually useless in the real aircraft. Wink
  20. 1 point
  21. 1 point
    The function to turn it on or off is not modelled in the Laminar G1000. You will see the ring appear by default, but you will also find it is way off and not accurate in most cases.
  22. 1 point
    Lets just hope that it remains true to the real thing.. instead of minimizing the swerve for the simmers getting happy.
  23. 1 point
    Hi Mirlo, I"m doing a bit of "multi-threading" at the moment, bouncing around between the Moo, the IXEG and NASA work. That being said, I need some access to an MU2 to move forward with some more 3D and a owner about 1.5 hrs away have invited me to come see his, but I've been a bit busy preparing for SpX16 launch, which is in 2 weeks. Things get VERY hectic in the 6-8 weeks preceding a launch. BUT.....the good part.....I have NO more space missions on the calendar for 2019....and will be making arrnagments to meet this MU2 owner asap and get what I need and will then continue on with this guy. It hasn't all been on pause though, duing my coding efforts for the IXEG, I have written a great deal of code that will also go in to the MU2, to bring it to a point of "serious systems simulation" like the IXEG. I have been working on that nearly every day in the evenings....so we're moving right along and I am definitely ready for this SpaceX mission to end so I can really dig into this thing. TomK
  24. 1 point
    Hot Start TBM 900 Paint Kit View File Official paint kit for the Hot Start TBM 900. Created by Goran Matovina and Cullen Chandler (Cessnarox). Submitter Goran_M Submitted 10/23/2018 Category General Aviation Livery For http://www.x-aviation.com/catalog/product_reviews_info.php/take-command-hotstart-tbm-900-pri-158?reviews_id=837 X-Plane Version(s) X-Plane 11  
  25. 1 point