Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/17/2020 in all areas

  1. 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 developer tools. WELL.....thanks to Ted Greene of Laminar.....he has coded up a "converter" between the old toolchain we used and the 'toolchain of today'. Only in the last week did we work out some critical bugs that allowed us to begin converting all our assets into the modern workflow supported by Laminar. We are currently in the process of converting all our work to this new toolchain and have converted some of the most complex aspects of it already...so we do not anticpate much resistance converting the rest of the work. This converter by Laminar is a huge lifeline of sorts and will allow us to again respond quickly to bugs and manage updates once we establish a new baseline with these tools. -TomK
    7 points
  2. http://forums.x-pilot.com/files/file/1081-p180-avanti-ii/ Enjoy the sexyest airplane.
    1 point
  3. Is it possible for the devs to confirm the issue? I am trying to find what I am doing wrong without success... And just to say. Aside from that, I love the bird. Been flying it a lot and reading the manuals. Just having trouble with this one...
    1 point
  4. We have confirmed the issue with Laminar. They are aware of the issue now and chasing it down. This issue should resolve itself with a future update from XP. -tkyler
    1 point
  5. 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 new look. The FMS work will resume once all the 3D conversions are done. It is unfortunate that all this infrastructure doesn't have anything visual to show for it but I can assure you, its quite significant for IXEG ability to get back on track with improving things. -tkyler
    1 point
  6. No, that is a bug 100%. I am getting it every single flight. The G1000 is showing correct amount of fuel in the SYSTEM-FUEL page, but the FPL calculations are not using that figure.
    1 point
  7. Hello, that’s exactly what I did, bought a HDMI splitter , so both PFD units are run by the same HDMI output. Basically just two copies of the same PFD. (In a way it doesn’t matter since In the TBM you can only use one PFD, not independent ) here are a few photos or my current setup, Bare in mind I’m still long way away from finishing , some panels still require bolting on properly , etc. thank you for your feedback.
    1 point
  8. 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
    1 point
×
×
  • Create New...