Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 10/22/2019 in all areas

  1. So we have reached the "minimum" of what we need to put out an update. I want to make sure all understand the nature of this update. It is NOT a major fix of FMS stuff. This update has significance to us as developers, which will lead to significance for customers. From our perspective, its validation of our current toolchain, i.e. we can output code and flight model / 3D changes quickly with modern tools...being that the entire product has been generated from this new toolchain. From the customer perspective, it is mostly compatibility changes to the flight model given the changes in X-P
    31 points
  2. 29 points
  3. Hi everyone, starting today I will aim to make a video every week for your viewing pleasure...talking about IXEG development, flying our aircraft, showing you procedures, techniques and various other stuff. Stay tuned to this channel!
    28 points
  4. So this is a heads up that it might go quiet for a few weeks. Not because we're not working on it, we definitely are, but the conversion of sounds to FMOD is going to be a very intense task. We wrote our own sound engine before X-Plane adopted FMOD....and our system is quite versatile and very quick to add sounds in code, but its also based on OpenAL, which is going away in XPlane 12 IIRC. Now we could probably distribute an openAL DLL as a solution; however, that is probably asking for more trouble trying to play alongside X-Plane's FMOD sandbox....so we might as well tough-it-up and make
    27 points
  5. Hi all. This COVID thing has affected my employment and sent me in a different direction.....full time back on X-Plane! (note...I work on more than just the 737 though) We are working on the update every day as of late; however, we are still going to wait for some 11.50 stability before we release. In the meantime, we're cleaning up things we feel we can without putting the plane in the hangar with the major renovations like the FMS/holds/VNAV. We are back in the FMS code somewhat though and have made the coroutes loading more robust. We will be including that folder in our update so as
    25 points
  6. So we finally have something visual to show for the next update. With our 3D toolchain in place, we are able to make 3D updates reasonably quick... thoughit still takes time to add in the detail. This is a screenshot showing a typical mesh refinment before/after. Whereas when we started the 737 10 years ago, we had to be conscious of our polygon count, its not as bad as it was and X-Plane and modern hardware can suppport more detail. So as we move forward with our updates, we will be making these kinds of refinements around the airplane...moreso out of the cockpit than in, because the coc
    23 points
  7. So the following screenshot tells two stories. 1). We have almost completed the conversion of all 3D assets to to the new Toolchain. Two assets remain and I'll probably knock that out over the weekend. The second story....is that with the upgrading of our assets, we finally have a workflow between 3D and Substance Painter® for texturing....in this screenshot the glare shield has a bit of a texture to it, nothing major, but adds to the immersion that's so important to us. We'll be able to start sharpening up several 3D elements that are a bit low-res by todays standards. The roadmap aft
    23 points
  8. another update, for those who may not have seen discussions in other threads. As much as I've spoken about FMS work...that was mostly because all the other aspects of our project, the 3D, the sounds, etc....were bound up in deprecated technology and tools, making it VERY difficult to update things....whereas the FMS was just code work. This was not really a lack of foresight on our part regarding the 3D tools, but rather being so far ahead of the game way back when we started, we came up with our own solutions.....that were not quite compatible with the way X-Plane moved with regards to deve
    23 points
  9. Since the 1.3 update was released, we've been working to fix all the squawks that have been reported since the release. I want to extend my thanks to all who report items. While folks may wonder why we do or do not catch things, I can assure you the list is quite long of things we have to check constantly and I'm actually somewhat proud of the effort. Supporting VR and also integrating the mousewheel involved a little over 300 manipulators, each of which having anywhere between 3-9 parameters to enter/ check....easily over 2500 "fields" to look at when making these conversions, and that's j
    22 points
  10. Windmilling Fans added. This example shows direct headwind and tailwind for simplicity. The magnitude is obviously diminished off-axis with practical limits..and the rotation speed is asymptotic, so 100 kt winds doesn't create unrealistic rotation animations. Tail winds are less effective on fan rotation than headwinds, due to wind turbulence through the vanes that saps energy. Also, alignment with the wind vector has to be closer for tailwinds than headwinds to yield fan rotation. -tkyler
    22 points
  11. We squeezed in native AviTab support. What a great product! We definintely encourage you to get it and support the software author with a donation. If you have AviTab installed, you should see a new preference checkbox to enable AviTab. If you do not have AviTab installed, you won't see this preference option available. The video below shows the implementation, along with a bit of coroute usage. -tkyler
    22 points
  12. With modern tools, comes modern features.
    21 points
  13. So with the update relatively imminent, I thought I'd go over some things that are on my mind, because I expect many folks will have some expectations of things in this update that are not there and may naturally wonder just what we do and don't care about. Way back when, we had to be quite conscious of our poly count and texture size, and while that is still true to some degree,, machines can handle a lot more now than they could in our early planning stages. As we've gone through this update, some of the things we defintely want to improve, and which you can expect us to continue working t
    19 points
  14. we reworked the animations during replay so you actually have decent replays to watch/record your landings. We have too much custom stuff to replay the "cockpit" of course, but all the control surfaces replay as expected. The video shows the changes. The landing was pretty bad, but I had a cheap joystick in one hand and was monitoring a bunch of stuff at the same time. Oh ya....new winglet shapes too.
    19 points
  15. Conversion of all 3D to the new toolchain is complete and we have exported out all of the 737 objects from the new version of Blender. Jan and I will begin testing the functionality to see what I may have missed in the conversion as I had to hand-edit an enormous volume of elements to prep it for the conversion software. Next up is converting the sounds. The attached screenshot shows a "quickie adjustment" I made to test drive the 3D update process......about 15 minutes of fooling around in Blender to see how quick I could make an update to the 3D with the new toolchain. (I know, the cir
    19 points
  16. We have been very clear and forthcoming about our lack of updates and the reasonings behind, as well as stating the nature of this 1.3 update, so if you had high hopes, then you simply didn't come across our postings on the nature of the update before it was released...perhaps we should come up with more formal press release mechanism for IXEG....anyhow, whether or not any of us likes the situation or fallout thereof is irrelevant to the time still required to do the work. If given the choice to lament and say, "yea, its lacking, lets just stop working on it, or "keep going", I'll choose the
    17 points
  17. Hello all. I have not been able to get onto the FMOD sound conversions as of yet for personal reasons; however, things have transpired during the reorganization process such that we are now maintaining two development branches. A longer term branch which will use the new XP11 navdata I've written about above, with revised FMS and we'll also maintain a "now" branch which we'll use to make compatibility patches and small fixes as able until the major revision comes out. The 'now' branch is a combination of our current FMS code base, but with the new 3D development pipeline....and juxtaposing
    17 points
  18. We had a request to resize the 'mini EHSI', and also be able to toggle it on and off. That is now in for the next update.
    16 points
  19. Just so that no one can say I didn´t test 1.32 long enough...
    15 points
  20. Ok..another week gone by. 60 more hours of rewrite on the FMS route editing and guess what, we're still easily 95% of the way done Seriously, we are into the more hardcore route editing features now, the really fringe type of data entry patterns...changing your mind "mid transition" selection for example, or selecting a STAR, then approach, going to other pages, then coming back to select another STAR, then TRANS, then swap to a runway with an extension, then shortcut points, etc. Testing earlier in the week had us redesign some other algorithms and we figured we should just power thro
    15 points
  21. Doing some testing and shakedown flights to make sure all new features and fixes work as planned. So far things are going really good. ...at least for the passengers on MY aircraft .
    15 points
  22. Hello All, This will serve as a formal forum announcement that we have released the version 1.32 update for the Take Command! IXEG 737 Classic. All customers who have purchased the IXEG 737 Classic 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 the IXEG 737 Classic from today forward, your purchased download will already be updated to version 1.32 for you. It is for X-Plane 11. If you use X-Plane 10, you can still install an old version of the aircraft from the
    14 points
  23. Another weekly update. The rather rigorous testing of route editing over the last week had brough forth a few more issues, not unexpected during such a substantial rewrite though... but without a doubt, there are substantially less issues with route editing. Jan's last round of route testing, he was unable to get a gizmo crash when changing procedures aggressively and could swap any procedure at any time. Our goal here is for folks to not be scared of to push any buttons on the procedures page during descent / approach for fear of a gizmo crash, and be confident they'll get the route they
    14 points
  24. Captains, We are pleased to announce the Douglas DC-3 v2 is near release! This has been in development for the better part of a year and a half, and it will be a significant upgrade to the current DC-3 that LES has had on the market since 2012. In comparison, it will be multitudes more realistic in systems simulation that you have come to expect from Leading Edge Simulations, and further, the 3D modeling and texturing has huge upgrades as well. For those of you that have purchased v1, we will be extending a special upgrade discount to you and will announce the details of this soon.
    14 points
  25. Hello All, This will serve as a formal forum announcement that we have released the version 1.3 update for the Take Command! IXEG 737 Classic. All customers who have purchased the IXEG 737 Classic 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 the IXEG 737 Classic from today forward, your purchased download will already be updated to version 1.3 for you. It is for X-Plane 11. If you use X-Plane 10, you can still install an old version of the aircraft from the
    14 points
  26. Hello all. What started out as a 'quick bug fix" for our annoying gizmo '470' error has, over the last 80 hours in one week..... turned into a very significant rewrite of our route procedures editing code. I was hoping to have it done by this weekend, but we are not quite ready. We are easily 95% of the way though and will continue to push to get this rather significant FMS update out asap. Depending on the routes you enter, some may not notice much difference, but for others, the difference will be quite noticable with the "routes editing as expected". Of course there is no way we can t
    13 points
  27. Version 1.0.2

    370 downloads

    A black panel, throttle pedestal and older faded 70's brown leather seats. Great for those dirty dirty liveries Unzip the file. drag and drop the contents of the "objects" folder into you Torquesim BN-2 objects folder to replace the default for all or for specific liveries just place into the liveries "objects" folder. Viola
    12 points
  28. I apologize for this one, we are aware...so how did it end up this way? Well...... I reverse my scrollwheel direction for my 3D work in Blender and so it worked 'normally' on my end and I simply didn't catch it during the exports.....I understand I'm the exception here. For those interested in a workaround, until we send out a patch, you can 1). use the manips as previously or 2) reverse your mouse scrollwheel direction in the OS before running X-Plane. This is on our list. -tkyler
    12 points
  29. Sneak peak - new material for throttles:
    12 points
  30. Certainly once we get all the 3D assets converted to the new workflow, a cargo variant would not be terribly difficult. We'll put this on the wish list. -tkyler
    12 points
  31. I'm quite annoyed and disappointed frankly, on the small amount of users, that come here uninformed, rude and entitled to write sensational posts concerning the 733. The team has been very, very open from the beginning for the "shortcomings" of the model. As well as providing a target and intentions for upcoming releases and updates. You simply haven't read it. It's quite the shame for these people, to come to this forum to address our concerns with any issues the update might have brought about, or simply request and features that come every day... and to see these kinds of reactions and
    11 points
  32. This is a lengthy post, explaining our VNAV situation, or at the least, how we arrived where we are today, and where we're going from here. This is a tale of how being too ambitious and trying to be all things to all people bit us and our customers. In the beginning was nav data in XML format....whether other formats were avail in the beginning, I don't know, I only know this was my beginning because I inherited the FMS work and this was the dataset that landed on my plate. It was from Navigraph. The first thing I did when I started was to open up a few XML files to get the lay of t
    10 points
  33. Second one is up (sorry, forgot to post here):
    10 points
  34. + Vr config file + Custom particle effects
    10 points
  35. Good observations and everything noted! We will doublecheck and Tom can be lightning fast with these adjustments. We are down to the last 2 or three open issues for this next patch...and will finalize the "bugfix/improvement/additions" list in the next few days. I plan on flying the plane around for a few days before we launch it, but may take you guys along, showcasing the new stuff, in a little youtube video. Cheers, Jan
    10 points
  36. Kicking off a series of development updates, we will travel to the past, from when DC-3 was born to today, to understand the significance of this aircraft for the whole airline industry. Douglas Aircraft Company, after a TWA inquiry, started development of a new series of aircrafts, designated as Douglas Commercial (DC), the DC-1 in 1933, and DC-2 next year. Although DC-2 was successful, it was a bit narrow for what American Airlines wanted, which led to the development of one DST prototype. DST stands for Douglas Sleeper Transport! Yes beds in the airplane! Flew first time on December 17
    9 points
  37. so the 1.31 update has gone out, with the objective being to stabilize our "get back to where we left off with the new toolchain, but conformant to XPlane 11.5" update. Assuming we don't have really big show-stoppers, it is now time to start moving foward rather than just get stable. We have a few things we'll be working on simultaneosly from this point on. With an eye on X-Plane 12, we'll be working on swapping our sounds to the FMOD sound engine. This is a compatibility move, moreso than changing the way our sounds are played because we quite like our sounds. In addition, we'll be wor
    9 points
  38. Hi Enrique, please don´t take this as an excuse that our VNAV is not working very well - it should be and we have full intent on fixing it. But I flew the 737 for 10 years, another 6 years of 747-400 and too many years A320... it is a very rare circumstance that I have descended (or seen my FO/CPT use it) using VNAV. Most of the time your routing is not predetermined (vectors, shortcuts) or you are subject to ATC limitations (early/late descent, advised rates of descent). So for me (and many of my fellow pilots) VNAV is a gadget that serves very little practical purpose. I think VNAV
    9 points
  39. Version 1.0.0

    107 downloads

    Bush missions your thing? Look no further. Installation: Unzip contents into BN-2 liveries folder. N2119V - As seen in the video below.
    9 points
  40. After working with Ted from laminar to squash a few bugs in the 3D converter, we have it working and have successfully converted many objects over to the new Blender 3D workflow including some pretty complex ones as well. My hats off to Ted...this converter was a real lifeline for us. This was a very very big hurdle to clear. I expect to have all the objects converted before the weekend is out. This will effectively restore our 3D workflow and allow us to get back on the cabin / door work in the 3D department. We still have sounds to convert to FMOD and also our 2D GUI to rework to the ne
    9 points
  41. Version 2.3.0

    11,120 downloads

    P.180 Avanti II for X-Plane 11 - CURRENT VERSION: 2.3.0 (uploaded at: February 125th, 2020) If you want to support P.180 Avanti development, please donate here: PAYPAL v2.3.0 Main Features Compatible only with EXPERIMENTAL FLIGHT MODEL (11.40+), capable of flying up to M.67 at altitude. Terrain Radar operation via PFD/MFD buttons. Tablet for aircraft loading (engines must be off and the aircraft stationary), and access to AVITAB. Librain Support. See Change Log for more! If you don't have Gizmo already installed in your X-Plane copy, there
    8 points
  42. Hello All, This will serve as a formal forum announcement that we have released the version 1.1.12 update for the TBM 900. All customers who have purchased the TBM 900 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 the TBM 900 from today forward, your purchased download will already be updated to version 1.1.12 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
    8 points
  43. TorqueSim and X-Aviation are proud to announce the BN-2 Islander! Initially started independently of TorqueSim, the inclusion of this beautiful bird into the new TS development pipeline has allowed for rapid progress and the seamless integration of custom systems, as well as boosting the quality of the 3D models and textures significantly! This aircraft will feature a high quality model, PBR textures throughout, a full custom electrical system with working circuit breakers, support for the AFM G5 avionics on launch, and of course the fantastic roar of its O-540s w
    8 points
  44. Tweaked...speedbrake lever too
    7 points
  45. Hi everyone, thanks for the feedback and reports regarding our 1.33 update for the IXEG 737-300. Naturally some things slipped our quality control and some things we simply *** up . Rest assures, we are working on fixing those, for some there are already workarounds. I will post, update and maintain the list here for you - so if you encounter a problem, check it against this list and if it is already known, you can save yourself the time to post (unless you maybe have some further information for us!). Test button for leading edge devices on aft overhead panel does not wor
    7 points
  46. 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 re
    7 points
×
×
  • Create New...