Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 05/19/2019 in all areas

  1. 2 points
    I am jumping in as a neutral new customer of the plane. The bank angle problem is annoying and since it is fixed in the new update I do not understand why a hotfix can't be released. Most of the other stuff is working ok (engine temps are broken but we can survive without them). Also by the devs it was mentioned that the plane is actually an XP10 plane but ported to XP11. In the store site it isn't really clear that it is an XP10 plane. It says XP11 compatible and "X-Plane 11 Only" so I would expect that it works perfectly. It isn't like XP11 is something new. I do appreciate that the devs are still updating it though and what is clear is that a lot of love has gone into making the Saab. What I want to bring out is that there are reasons to be a bit disappointed after buying the plane, at least for now. Also communication is important and I wish that LES would give a bit more info than "we do not release dates" kinda answer. I understand that people get disappointed when a "deadline" is missed but a LevelDsim approach where you say little for years is also a bad way for communication. It just ends with frustration. Saab V2 has been announced for a long time but there has been no update at all so it will cause curiosity and frustration. Is there anything bad in just sharing a bit of planned upgrades and a loose percentage of how done it is. FlyJsim have a fantastic way of communication via their Discord where they livestream their update programming and 3d designing and so has HotStart (yes I know Goran is in there) so it would be nice to improve communication to loosen the tension. It is up to you if you choose to answer but please don't become defensive. I mean this meant as positive criticism since it is clear that you guys do care and love the plane and want us to have a great simulation experience. Regards, Manfred
  2. 2 points
    Hello All. This post will be locked as its only intended for public statement. While many people are aware of the IXEG Development status, many others will not and so this post is intended to provide clarifying information. For a while now, IXEG development has sat relatively idle. The reasons for this are multiple and have been stated in other forums; however, two significant factors contributing to that idleness have since wained and IXEG are looking at how to best move forward with IXEG updates again. There are two areas we are looking at for updates, 3D cabin/doors/animations and the FMS. Regarding the FMS, IXEG are looking at transitioning to the XP1100 Navdata format, which is derived from the ARINC 424 standard. Moving to this dataset format would yield increased accuracy in the representation of procedures and more practical data with which to improve LNAV / VNAV / performance caclulations. If it turns out that porting our code to the new XP1100 format is too cumbersome in the short term, then we will seek to patch what we have now and transition at a later time. The important thing is that IXEG are moving again to improve the FMS. Regarding the 3D, this will be a bit more of a undertaking. The development tools IXEG used for 3D development are nearly fully deprecated and there has been a major transition to newer tools and methods. This necessitates IXEG reconfigure our source material to the new formats and we have a LOT of 3D material to translate. This means that the 3D updates will be longer in coming than the FMS updates. Once the 3D is ported to the new tools though, any updates we implement thereafter would come much quicker, simliar to what was done shortly after our release for those that recall. We apologize for the idle time and appreciate all our customers and any patience you've exercised. We are sincerely committed to making the most immersive and accurate simulation of this aircraft as we can and will continue to push towards that goal, no matter where its end may be. -Tom Kyler
  3. 1 point
    Hi folks, I made a PDF document with all the Normal checklists from the official POH in only 2 pages, also I included some performance tables. I wanted to share it with the community. Let me know if I can improve it. Thanks for this great product! Cheers TBM-900 Condensed Checklist.pdf
  4. 1 point
    Hello All, This will serve as a formal forum announcement that we have released the version 4.8 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 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 4 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: New choices for cirrus, overcast, and cumulus cloud textures New user interface for choosing cloud textures; each cloud type now has its own configuration screen Fix appearance of precipitation in VR Suppress towering storm clouds above 40 degrees latitude (unless told to explicitly by an external injector) Fix cloud/terrain blending when using Real Weather Connector while only ground fog is present Fix fog / in-cloud effects in X-Plane 10 Improve accuracy of cloud altitudes Added backup weather download capabilities when using "always" mode in Real Weather Connector Fade time when cloud layers change increased to 30 seconds Fixed fog inside stratus clouds Fixed cloud shadows and other special effects in VR Fixed hard edges on solid & broken overcast clouds when viewed from above As always, thanks for purchasing from X-Aviation!
  5. 1 point
    I'm told X-Aviation is aware of the issue and working on it. Hang tight.
  6. 1 point
  7. 1 point
  8. 1 point
    +1 I opened a ticket couple hours ago... XP11.32 on macOSX Mojave here
  9. 1 point
    Same here. I will open a ticket as well...
  10. 1 point
    @Berraco I have the same problem. I opened a ticket this morning.
  11. 1 point
    Same here... and i don't have v4.7 of skymaxx any more. .
  12. 1 point
  13. 1 point
    @craighardy How much RAM do you have? When I had only 16GB in my computer I would sometimes get crashes with SMP from running out of RAM. Since upgrading to 32 I haven't had any issues. Note: It wasn't necessarily SMP causing the crash, it was usually at large add-on sceneries flying something like the FFa320, so SMP was just the straw that broke the camel's back.
  14. 1 point
    There are no plans to add a ferry tank to this version. The real thing never had it. It IS possible, though. With careful planning and favourable winds, it can be done from France to the US. In an 850, no less.
  15. 1 point
    I believe its something in FlywithLua! Working Fine! Thank You Sir!
  16. 1 point
    I'll look into it, this is the first time I've seen this.... 4.8 will have this fixed..
  17. 1 point
    And I'll have to defer to @JohnMAXX on the texture issue. We do have a whole new set of cirrus textures to choose from in the upcoming 4.8 update however, which will probably offer a solution for that.
  18. 1 point
    It's a good addition to the Daher videos. He goes into little details and explains things well. Hot starts, wet starts, etc. How to tell if you're battery's getting old (and how long it should last). How the start is different with a GPU. How long ITT can safely be in each of the 'red zones'. And more. Good stuff!
  19. 1 point
    We're working on it. Still a few things to take care of. All moveable parts in the cockpit have been re-animated with new datarefs. Some code still needs to be fixed. Have to run a few tests and check lighting. We're getting there.
  20. 1 point
    Hello all! I purchased the LES Saab 340A a couple weeks ago and have been having a wonderful time learning to fly it. That being said, it is undoubtedly the most complex aircraft I’ve ever flown, and as such, there are a few systems/procedures that I still don’t fully understand. I’m just going to list my questions below. What is the exact procedure for deactivating the CTOT? How does auto-corsen differ from auto-feather? Can reverse thrust be used to pull back from a gate? I can’t seem to get the plane to move this way, so I always do pushback. Is there a difference between using the tiller wheel or the rudders for nose-wheel steering? Is reverse thrust the only way to slow down upon landing? How does one go about calculating the center of gravity for a given flight? I’ve left it on default every time, and it’s been fine, but I can’t seem to find a formula. For example, the default KingAir C90 manual includes a procedure for calculating this value. What are the standard prop settings over each phase of flight? How do you find proper climb/decent power? As far as the last two questions, I’ve really been winging it with the power and condition lever settings. Would the charts provided with the plane be my best bet as far as finding the correct values? I just can’t ever seem to find the relevant chart, and the amount of information in them is, in general, overwhelming. I know that’s a lot, but I just have an itch to make sure I am getting the most out of this beautiful aircraft. Any feedback with any of these questions is so appreciated. Thank you all for your help, and happy flying! o7
  21. 1 point
    Lets see how we go 1) Turning it off after takeoff, slowly rotate the setting knob anti-clockwise, then turn off the switch. 2) The auto-coarsen on the A model doesn't actually feather the propeller, just moves it to a minimum drag position. Theoretically if the condition that triggered the auto-coarsen event was to relieve itself, such as a momentary power interruption, the prop will go back to its set position. In order to feather it, the engine failure memory items need to be completed, i.e. power lever flight idle, condition lever fuel off. It's only designed to buy the crew time to deal with it at a safer height, a V1 cut where the prop stays at full fine (max rpm) is lethal if not dealt with immediately. 3) Yes, but safety departments would hunt you down. Always done with the control off a tug, but it is possible providing you don't touch the brakes, the inertia will cause a tail strike. 4) The tiller is connected to the nose wheel, the rudder pedals is connected to just the rudder. Below about 80 kts you won't have enough aerodynamic power from the rudder to turn. 5) You can use brakes, but typically not until reverse has brought the speed below 40kts. So much as breath on the brake pedal above 40 kts with anti-skid inoperative and saab suggests you will blow the main tyres. 6) Don't know, LES version doesn't have that info that I know of, never really looked for it. 7) Max on the ground, take-off and landing, 1230 RPM climb, cruise, descent. 8) Don't know where they are listed in LES stuff, but XP11 engine model was changed not long ago and v1.5.1 has the old XP engine data so half a chance you'll hit temperature limits anyway. Power circa 60-70% Trq / ITT below 850 on the climb/cruise seems to work, Descent, whatever is required to stop the overspeed buzzer annoying the crap out of you....
  22. 1 point
    I'm too old for boxers now, I like my comfort too much lol.
  23. 1 point
    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
  24. 1 point
    When things calm down a little bit, I'll get around to finishing the XP11 version.
  25. 1 point

    Version 1.0.1

    211 downloads

    Official paint kit for the Hot Start TBM 900. Created by Goran Matovina and Cullen Chandler (Cessnarox).
×