• Content Count

  • Joined

  • Last visited

Everything posted by turbofandude

  1. Thank you for your support! Which simulator are you using? The hotkeys are finicky in full-screen.
  2. Thank you for the support! PACX will automatically detect cruise after you've levelled off. It takes some time (to avoid false positives while holding/slow climbing) but it should flip over to cruise after some time.
  3. We're using different technology than most of the others (with the exception of those that use our RealLight and TrueGlass) and we have different hurdles to overcome due to this. We're finding that the biggest issue in V5 is the immense VRAM consumption (and the color of displays/surfaces, but I believe we've got at least semi-fix for that). We've pushed everything down as much as possible and we're forced to simply recommend a reduction in settings now, which nobody wants to hear (understandably). Until this either becomes accepted or we have an updated sim that doesn't push back as hard as V5 does currently, we're going to be in "beta".
  4. In all honesty, it's because we don't believe the the experience is to the level required to be "production" (non-beta) at the moment. A lot of breaking changes occurred in the simulator and until we're able to either find a permanent, proper fix or at least identify and mitigate the issues, we want users coming into it to know it is not going to be the stable, polished experience you'll have in any other platform.
  5. Our intent is to support MSFS2020, assuming it is capable of supporting the product. Without more SDK information, we cannot make an informed, final statement on it.
  6. Assuming we're able to find real world reference for it, it will likely be on the radar.
  7. We will make our selection and roadmap for beta publicly known in advance, but we are way too to say anything definitive now. Thank you for the interest, however!
  8. Hello everyone, It's been a very busy few weeks! Over the last few weeks, we've released a moderately sized update for PACX (as it is nearly to version 1.0), we fixed a small snag in the TFDi Design 717's navigation display, and of course, have been hard at work on the TFDi Design MD-11. I've included some new renders and information from a few of the developers on the project. To start, I'll quote @Ricardo Ramos, the systems programmer for this project. @ozzman1997 has been doing some incredible work on the model as well. The exterior is nearing completion (still pending texturing, of course), but the cockpit has progressed immensely. Finally, I've been working on the FMC/MCDU (and its associated sensors, computers, and systems). I don't have a screenshot to show this time, as the majority of my work has been behind the scenes. That said, here are some key points of what's been added to the system recently: Triple, independent IRU simulations with simulated drift and realistic alignment behavior (for example, a fast align can be performed once the IRU has captured true north and has been previously aligned). The GNS systems are implemented and have the appropriate amount of sensors and information channels to integrate in a realistic way. The navigation database system has been optimized and brought into the MD-11 and is now being properly read by the FMC, including both primary and secondary databases. The next step is beginning to code flight planning and MCDU operations. Unlike our previous aircraft, we intend to simulate all (except maintenance/third-party software) features of the MCDU, such as wind entry and RTA. Of course, we're still early on, but progress so far bodes well. That's all for now and thanks for reading!
  9. Indeed, wind entry will be simulated.
  10. I found the issue causing this and have corrected it. An update will be out shortly.
  11. We are actually in the process of redoing the video and updating the product page to better describe the product. We agree that it does not have enough to understand it fully before purchase!
  12. If you copy the "LegacyRender" files in, does that work? (It's the same steps as this answer: https://support.tfdidesign.com/support/solutions/articles/62000104146-flickering-on-displays-lighting-or-trueglass-with-sli-enabled)
  13. What operating system are you on @atrailblazer?
  14. I don't see anything out of place. This sounds more like a hardware mapping issue.
  15. We will provide exact estimates when we have them and are prepared to share them.
  16. You cannot implement TrueGlass into a project without some access to the model, unfortunately.
  17. @tk92 Can you post the Documents\TFDi Design\717\Configuration.xml file here?
  18. The Navigraph FMS Data Manager should take care of it for you.
  19. This morning, we posted a (not so) cryptic tweet on our Twitter. The time has come for the announcement we mentioned. So, without further ado, I would like to announce the development of the TFDi Design MD-11. Before the questions come in, I will answer some of the important ones here. Project Status No, we cannot announce a release date. With that said, we are actually announcing this project a tad earlier than we originally expected. Although progress has been solid (and relatively quick), our intent was to show the aircraft off working in-sim as the first preview. We’re still a bit out from that (although, not TOO terribly far). We decided to do this today as recent announcements would have left the community wondering if there was going to be one in this market at all. We are happy to announce that we will be filling that gap. We have a larger team working on this aircraft than we had on the last, as well significantly more experience, which will allow us to develop it better and faster. We will, as always, keep the community up to date on development via our official social media and our Discord. Fidelity Our last aircraft, the TFDi Design 717, was a fantastic learning experience for us. We intend to build on that experience to create an even deeper, richer, and more realistic simulation on the MD-11. The similarities in the systems, as well as refined processes and technologies, will allow us to create something even the most experienced MD-11 crew and enthusiasts will enjoy. Simulation Support As of today, our intent is to natively support Prepar3D v4 and v5 at the time of release. It is a possibility that we will create a modified version of the product to support older simulation platforms (FSX, FSX:SE, Prepar3D v1-3), but we do not want to limit the potential of the product by designing it around dated standards. We have not yet made an official statement regarding Flight Simulator 2020. We will continue to monitor the development of this platform and will do our best to support it. We intend to develop this aircraft in a format that will allow cross-compatibility in a much more practical way. Want to get Involved? As some of you may remember, when we announced the TFDi Design 717, we also put out a call to all community members. This call was to help us by providing documents, videos, photos, sound clips, data, or even their personal experience and knowledge. It was thanks, largely, to this help from the community that we were able to deliver the level of accuracy that we did. Once again, we would like to put this call out. If you have any of the following, please do reach out to us to help us create the best product possible. Aircraft reference documents (FCOM, FCTM, etc.) Any aircraft photos (even of the most obscure items) Sound clips (such as aural warnings, unique flight deck sounds, etc.) Videos Engine data (such as EPR charts/tables, fuel flow data, etc.) Although we do already have a good amount of reference material, the more we have, the better we can do. We will, of course, continue to research and acquire our own reference material. Thank you, in advance, to anyone who is able to help! To submit information, please use this form. House Keeping TFDi Design 717 for Prepar3D v5 This is still in progress. We have the aircraft and its associated dependencies working in V5 and will be starting formal testing soon. We appreciate your continued patience. TrueGlass and RealLight for Prepar3D v5 To our commercial customers, we are working on this, as well. They are both operating in Prepar3D v5, but we are awaiting answers from Lockheed Martin to help us eliminate a few snags before we begin formal testing. If you are interested in testing the current iteration of the Prepar3D v5 versions, please reach out to your point of contact. PACX We are using the feedback we received from the community survey to develop and refine the product. We have some cool items in progress that should be ready for testing in the near future. Our intent is to wrap up a solid version 1.0 over the next 3 to 6 weeks and complete the Early Access phase of the product’s life. smartCARS 3.X This is something we have been alluding to for quite some time. We are working on a few potential directions we can take the development to create the best possible product for our customers and their pilots. There will be more announcements and development updates relating specifically to smartCARS 3.X as they become available. Closing Well, that about sums up our current status. We do intend to be more active in our Discord and on our social media regarding development updates for all products. A huge part of what makes us who we are, as a company, is our presence in the community and we intend to continue developing that relationship over the coming months. Thank you all for your support and for reading. We’re looking forward to embarking on this journey together!
  20. What does the event viewer log say?
  21. Andrea, Honestly this may be one of those issues that takes longer to debug than a reinstall does. I hate to recommend this, but we haven't seen this complaint in literally years (as far as I can tell) and I don't want to waste your time with guesses.
  22. That looks like either the simulator was running or an antivirus program was restricting the access to that file.
  23. That's definitely strange. This definitely sounds like a hardware mapping issue with FSUIPC.
  24. We're not actively working on this as we have almost zero real world reference for how it was done (in the displays, weight/balance, etc.). I have never seen an actual aircraft that had them.
  25. I'm not even sure that external would work - we simulate custom fuel burn rate (fuel reduced by burn rate times delta time) to get it more accurate.