Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by turbofandude

  1. Hello all, We will be posting official liveries today, and over the coming weeks, in our forums. Installation is manual currently. We will provide a guide for how to customize the aircraft settings on a per-livery basis soon. Official Liveries https://forums.tfdidesign.com/index.php?/files/category/13-official-liveries/ Bugs List and Reporting Please refer to the md11-bugs repository for the known issues and technical status of the project. The official progress page will receive updates, as well, but not as quickly as the bugs list. https://github.com/invernyx/md11-bugs Updates To update your aircraft, please run the TFDi Design MD-11 Updater program installed on your computer. More Up To Date Information We strongly encourage all Collector's Edition users to join our Discord via https://discord.gg/tfdidesign. We post much more regular development updates as well as more detailed information. You can verify yourself as a Collector's Edition owner in our Discord by linking your https://tfdidesign.com account to your Discord.
  2. 0.18.0-alpha (30 November 2023) [ADDED] Restriction and time display on ND in DATA mode [ADDED] TFDi Design house livery [ADDED] PROG page functionality [FIXED] Landing weight always showing in pounds on APPR page [FIXED] Digital/analog standby setting not saving [FIXED] Flight plan using block fuel, not UFOB [FIXED] EFOB not setting properly on certain legs [FIXED] PROF targeting altitude above cruise under some conditions [FIXED] Cruise altitude showing as "-99/-99..." on INIT page at times [FIXED] Visual reversal of ailerons [FIXED] RCWS attempting to control aircraft without valid data [FIXED] Resetting of speed/altitude predictions on departure runway/airport [FIXED] Inability to unmask FCP values in FMS-controlled modes [FIXED] Invalid airport elevation being entered as a PROF target [FIXED] Misuse of certain variables in flight plan calculations [FIXED] T/C and T/D predictions when they are adjacent [FIXED] Time prediction for FIX intercepts [FIXED] FMS SPD FCP edit behavior [FIXED] Pushing FMS SPD button not resetting FMS SPD mode to ECON [FIXED] Fuel valves defaulting to on in every scenario [FIXED] Invalid calculations on certain abstract waypoints [FIXED] Display of data around VECTOR or DISCONTINUITY on FPLN and DIR INTC page [FIXED] Missing dot in airplane symbol on ND [FIXED] Missing radar settings box on ND [FIXED] T/P waypoint not receiving valid ATO value [FIXED] NO LOC always showing in amber [FIXED] AFS speed selection not starting at FMS SPD correctly when editing [FIXED] CAWS altitude alerts occurring at wrong altitude [FIXED] Predictions of 0 or other incorrect values surrounding arrival [FIXED] Incorrect usage of distance field causing prediction issues [FIXED] Wildly inaccurate fuel predictions [FIXED] Prediction behavior surrounding discontinuities [FIXED] Cruise legs not getting an ETE [FIXED] ETE calculations [FIXED] T/C and T/D not having proper predictions [FIXED] DIR INTO and FPLN time display [CHANGED] Antiskid is now on by default [CHANGED] Panel states redone to fix issues with previous version 0.15.0-alpha (24 November 2023) [ADDED] SimBrief integration within the EFB [ADDED] Fix Data in FMS [ADDED] IRS alignment time option [ADDED] Working FIX INFO intercept/abeam behavior [ADDED] Captain and FO timer functionality [ADDED] Ability to disable hardware over-forcing the AP [FIXED] MAINT SD page having two pages [FIXED] Various timer/chrono related behaviors [FIXED] Early localizer capture (again) [FIXED] Analog standby altitude readouts [FIXED] Transponder can now be toggled between Mode A and C [FIXED] Annunciator light test no longer causes inaccurate conditions post test in the overhead [FIXED] Enroute timer using minute readouts after 60 minutes [FIXED] Aileron input being blocked after attempting to correct [FIXED] Gross weight on SD now updates with fuel burn [FIXED] T/D predictions overwriting the waypoint before T/C when T/C and T/D are adjacent [FIXED] Some engine indications appearing when EEC was unpowered [FIXED] Destination airport not having appropriate elevation data [FIXED] PPOS not being reset/removed by DIR TO [FIXED] Gross weight displaying too much accuracy on SD [FIXED] EFB not releasing keyboard and mouse input [FIXED] Starter cutting out at 60% N1 [FIXED] RCWS incorrectly limiting input during over-bank situations [FIXED] Various lights still remaining on after annunciator test [FIXED] WBS system displaying values when gear is not on the ground [FIXED] Gross weight not updating throughout flight (again) [FIXED] Cruise altitude change not triggering NAV/PROF prediction update [CHANGED] Start valves now close at 45% N1 instead of 60% N1 for GE engines [CHANGED] EFB no longer presents incorrect CG and ZFWCG 0.13.0-alpha (18 November 2023) [FIXED] Mach indicator displaying behind speed bugs [FIXED] Minimums knob not switching between BARO and RA [FIXED] Scratchpad resetting erroneously [FIXED] Incorrect visual behavior of upper and lower symbol for BETWEEN altitude restrictions [FIXED] Unreasonably low fuel consumption [FIXED] L0 alerts starting from top of column 3 on EAD [FIXED] Options being saved/set in panel states [FIXED] Spoilers not deploying at main gear spinup [FIXED] PFD incorrectly rounding dial-a-flap settings causing visual mismatch [FIXED] Inability to reset minimums [FIXED] Standby IAS indicator showing wrong airspeed [FIXED] GE, GR, and SE bugs not respecting mach equivalents [FIXED] Gross weight not updating throughout flight [FIXED] FCC not requiring power [FIXED] Autobrake EIS message causing master caution and appearing on EAD [FIXED] Unreasonably high IRU residual ground speed [FIXED] Automatic seatbelt and no smoking behavior not matching real world reference [FIXED] Overlapping text when entering 5 airways [FIXED] Various PFD visual items [FIXED] Display of "NO GS" text [FIXED] Localizer capturing outside of regional deviation [FIXED] ENG SD not displaying certain data correctly [FIXED] Landing weight display [CHANGED] Last state is now saved on a per-registration basis [CHANGED] Updated GDIPlus libraries to latest MSFS SDK version 0.12.0-alpha (14 November 2023) [ADDED] Transponder state, mode, traffic range, and ident code (not yet linked to online networks) [ADDED] G/A button function [FIXED] Jetways entering fuselage [FIXED] Crash during descent/approach with no upcoming legs [FIXED] Speed protection occurring too often and too early [FIXED] Fuel used and fuel flow values displaying in incorrect units [FIXED] Inability to load cargo on F models [FIXED] Reversed wind display [FIXED] Wind vector setting not properly adjusting to the setting [FIXED] Incorrect parsing of input on POS INIT [FIXED] Flight plan scroll resetting too often [FIXED] Airway leg lookup logic [FIXED] Airway insertion occurring at wrong location in flight plan [FIXED] V1 and VR causing flight plan recalculation [FIXED] Incorrect response from F-PLN page when erasing or inserting certain waypoints [FIXED] Crash when clicking past the end of the flight plan [FIXED] Approach names not showing up correctly under some conditions [FIXED] Freeze when advancing throttles with a flight plan [CHANGED] Revised speed protection logic
  3. Hello all, After 11 years of smartCARS, it is finally possible to track all flights, including your personal ones, with smartCARS Pro. smartCARS is an incredibly detailed, expandable flight tracking system. Previously, it was only for virtual airlines to provide to their pilots, but now it is for everyone. This means that every flight can now have: Extremely detailed flight review and playback, so you can see exactly what happened and how you handled it at every step of the flight Integrated SimBrief planning to make flight preparations faster and more seamless with less applications open Automatic, real-time flight backups, meaning you can restore your aircraft position after a simulator, or even PC, crash Cloud backups of all PIREPS across all smartCARS virtual airlines and Pro - your logbook is ironclad at all times Abnormal flight protection so that if you have to step away and something goes awry, you come back to a paused simulator waiting for your input And so much more Below are screenshots of some of these features in action on some of my own personal flights. We are really proud of what smartCARS has become and we're excited to share it with more pilots than ever. To learn more about smartCARS Pro, check out the product page here. For those of you who were already smartCARS Premium subscribers, thank you for your support and rest assured, your smartCARS Premium subscription and previous smartCARS Premium PIREPS have already been converted to Pro. That's all for now and thank you for reading.
  4. smartCARS Premium features are, as of now, present in smartCARS 3 and your benefits will carry over. We are working on migration steps to bring previous PIREPS forward, so your logbook keeps going.
  5. Firstly, we want to start this update by saying thank you to everyone that attended Flight Sim Expo and came to our booth to try the TFDi Design MD-11 and smartCARS 3. We saw so many faces who shared our enthusiasm in seeing a live demonstration of the aircraft and trying the brand-new version of smartCARS! The team has been working extremely hard since Flight Sim Expo, and we are here to show you some of the progress that we have made in the short time since we were on the show floor. TFDi Design MD-11 Visuals Since the version we demonstrated as Flight Sim Expo, the yokes and throttles have seen visual improvements, as well as other animations and parts throughout the cockpit. Engine Startup When we presented the MD-11 at Flight Sim Expo, we were still in the process of building the starters and ensuring that a full start could be achieved without any simulator assistance (such as Control+E). For the first time, we were able to completely start the aircraft from cold and dark and progress through to the take-off roll. Although a massive achievement, there is still progress to be made, as we still need to link up the engine starters to the APU and pneumatic demand. This requires the air system to be fully developed, which has been one of our main focuses. We will have more on the pneumatic system in our next update. Brakes and Gear We have also made progress on more of the displays and their surrounding systems. The “CONFIG” Secondary Display (SD) page has also been fully implemented, with a full simulation of the landing gear, the tires, and the brakes. The brakes behave realistically, including some pilot-induced failures. Hydraulic systems 1 and 3 each power one of two hydraulic pressure accumulators to provide backup brake pressure. When they have pressure, you have brakes: This backup system provides enough pressure to fully apply and release the brakes approximately 10 times. If they run out, the brakes no longer have pressure: If you have no brake pressure, your brakes will no longer provide any stopping power until the hydraulic pressure is restored. We have also simulated the brake temperature and brake overheat as well as tire pressure. This, in effect, means that if your brakes get too hot, they can melt a fuse that depressurizes the tire! With our custom autobrake system, we have ensured that the aircraft attempts to decelerate with the speed the real aircraft would: 6.5 feet/s2 for LOW, 9 feet/s2 for MED, and maximum braking force at MAX. This allows for a consistent and reliable stopping distance and a smoother ride for those onboard. The centre landing gear now responds to the CTR GEAR NORM/UP switch, meaning you can control the centre landing gear separately. Finally, the reverse thrust system has been implemented as well. This brings us one step closer to the flight ready state. Autoflight We are happy to report that the autoflight system is functional in MSFS! Nearly all standard modes are implemented and the aircraft is flying relatively well. Magenta line tracking code has begun but is not yet complete (though the code to generate and draw the magenta line is much further along). Along with these improvements comes improved LSAS functionality as well. When the controlls are released, the LSAS will attempt to hold the nose level (within its authority level); it will also help apply nose down force during landing to help with landing stability. Additionally, we implemented the single cue PFD layout as an option for those that wish to use it. We have also been working on becoming more transparent on the progress of the MD-11, so we created the TFDi Design MD-11 progress page, which breaks down the big items and shows you the total progress for our current focus phase. We are currently working towards a “flight-ready state”, and we are getting closer to it every day. We also post updates on our Discord before anywhere else, so make sure you join our Discord if you are interested in more updates. smartCARS 3 We are still working hard on smartCARS 3, and we have recently released a new update (0.12.1) which fixed a few major bugs and improved even further on the existing smartCARS Premium features! As we approach the end of the Premium roadmap, we are getting closer to a Release Candidate for smartCARS 3, which will mark a code freeze for the project until release! We want to note that there will also be some important changes to the API used by communities with the phpVMS 7 platform in the future to implement more natively with the platform. We do not yet have a timeline for when this rewrite will be ready to use, but it is a planned update. Finally, we will dive into the details of smartCARS Mobile after the smartCARS 3 desktop client completes testing. Conclusion As always, we want to say thank you to the community for their interest and support in our projects. We are excited to continue innovating and to see our customers enjoy the products we have been putting so much effort into over the last few years. If you are interested in supporting the TFDi Design MD-11 project, we have a presale opportunity available here that can save you $5 on the whole package and some download time on release day. If you would like to learn more about smartCARS 3, the product page contains more information and links to get started. Finally, thank you for reading and stay tuned for more!
  6. It will depend on which license you have, but the transition will be fair regardless.
  7. Edit (22MAY23): smartCARS 3 is now available for sale in open beta! To learn more, visit the product page. smartCARS has been at the core of TFDi Design's product lineup since 2012. As of a few weeks ago, smartCARS version 3 is officially in beta. This is a big moment for us and I want to take a few minutes to share some history and details about it. The Beginning smartCARS 1 was our first commercial application and although we have certainly outgrown it, we're proud of where we come from. It started, initially, as a bespoke application for colleagues we knew at the time. We changed how things were done (allowed multiple bids, added a real live-chat, etc.) and really tried to build a better user experience than what was available at the time. Below is the extremely old smartCARS 1 release video. We soon realized that smartCARS had the potential to be much more than a one-off contract. It seems we were right, because smartCARS became relatively popular in the virtual airline world not too long after. Enter smartCARS 2 smartCARS worked well for its intened purpose but it was obvious that we had a lot of headroom to expand. We wanted to allow more customization, add more detail to the logs, and give pilots a more rewarding experience. And so, we set out on smartCARS 2. We supercharged the code and user interface and created the next iteration of what was quickly becoming a staple of the virtual airline software world. The release trailer for smartCARS 2 is below. Fun fact: the music in the smartCARS 2 release trailer is actually a remix of one of my own songs. Further to the additions to the base application, we introduced smartCARS Premium. This is a pilot-based subscription that adds further features to user experience. This allowed us to create more specific and advanced features heavily geared toward the pilot, instead of the VA, as the pilot could also now be a customer. Premium included cloud flight backups that could survive even a complete PC shutoff, a mobile app that let you bring the flight with you, and some additional features (like dark mode) that weren't industry standard yet (at the time). The Quiet Years After smartCARS 2, we started focusing heavily on development of the TFDi Design 717. This took us quite some time, as did the application we followed it up with, PACX. With that said, we were still cooking up ideas for smartCARS. We collected user reports, our own ideas, and frequently discussed ways we could take smartCARS to the next level. As it soared to heights way beyond what we originally expected with over 1,000 licenses issued, we knew we had to follow up smartCARS 2 with something impressive. As we continued collecting ideas, one thing was clear: we had the core concept right but it was time to let others add to it as well. As a company, we have also focused heavily on efficiency and modularity. These concepts worked together as we designed a system that would allow others to add meaningful, important functionality at their discretion. Despite all of this interest and thought, it would somehow be many years until we broke ground on smartCARS 3. smartCARS 3 In 2020, we started on what would eventually become the smartCARS 3 that recently entered beta. We had some new team members to bring in new ideas, a fresh mindset for having had such a break, and a whole new world of technology to explore. We picked a web-based system (Electron) that would let us write simpler, platform-agnostic code. We developed frameworks and SDKs to allow plugins to add entirely new pages and features, or critical but invisible background functionaliy, to smartCARS. The unique thing about smartCARS 3 is that we wrote the flight tracking, chat, logbook, and flight center code using our own plugin API. This is significant because that means our plugin API really works. It will actually let community developers add meaningful content, whether specific and private to their VA, or something for the community to use. We took a great deal of care to improve the experience massively. A few highlights of these changes are: Single installation across all VAs without losing the customization (meaning you no longer had to install multiple copies of smartCARS for multiple VAs) Resizable, massively improved user interface Complete customization and extensibility via plugins and web APIs simBrief integration Overhauled map with ATC and online network support Massively improved and scriptable flight tracking (each VA can customize exactly what is logged and how) Overhauled chat experience that is more conducive to a friendly community message-board style conversation Improved PIREP viewer with real over-the-ground route plotting And too many minor but noticeable improvements to list Some images showing this are below. The idea for us is to make smartCARS 3 a platform, not simply another version of the program. We want to let others build and expand on the features they need without having to reinvent the wheel. We want to bring a compelling mobile experience and unbeatable Premium features (more on that another day) that'll serve the community for years to come. Conclusion smartCARS is near and dear to many of our hearts and we couldn't be prouder of where it's headed. Thank you for reading and thank you to the community for your feedback and support over the years. The wait is almost over; the smartCARS journey will continue.
  8. We're looking forward to diving deeper into it publicly VERY soon.
  9. Unfortunately, yes, they are sold out, but there will be plenty of MD-11s later this year!
  10. As I typically do each year, I'd like to take a moment to recap what 2022 was to us and what we're planning in 2023. In a sentence, 2022 was a head-down year. We did a lot of internal optimization, a lot of development, and a lot of strategic and team planning. We also did something we've never done; a presale. Although a bit controversial (we did expect that it might be), we remain humbled by the overwhelming support we received. This support confirms two things we already believed; that we are in front of a great community that we're proud to work with and that the TFDi Design MD-11 will be our largest product to date. This upcoming year is going to be a massive year for us and our community. We have smartCARS 3 rapidly approaching beta testing, the TFDi Design MD-11 is progressing nicely and overcoming obstacles quickly, and we have recruited a great team of voices for the upcoming PACX update. No matter what brings you to us, we will have something exciting for you this year. This means it is more important for us to stay present and communicative than ever before. This segues nicely into one of our focuses for 2023: continued and improved community presence. Our customer support satisfaction feedback last year says we did good helping and we're going to aim to make that great this year. We're working with our community and brand teams to find new, meaningful ways to share content with the world. We're working on optimizing internal policies and practices to make it easier for our developers to share their progress with you. All of these things mean we are continuing to find ways to foster the most open and interactive environment we can with our customers, fans, followers, and critics alike. From a technical standpoint, we are preparing to grow. We are working on infrastructure with higher reliability, better performance, a huge scalability. We're building on top of our modular and efficient approach to development to add expandability and scalability to our every day design language. Our technical leaders are discussing emerging technologies that will improve security and enable better system-wide performance. This means our community is going to see some of the most robust, customizable, and reliable software they have ever seen from us going forward. Thank you for reading and I know I speak for our entire team when I say thank you for your support. We are so excited to be entering into what is shaping up to be a huge year and we cannot wait to share the progress as it unfolds. As always, please do not hesitate to join our Discord, open a ticket, or comment or message us on social media. We look forward to seeing you all in the skies in 2023.
  11. Fall 2022 Development Update It has certainly been a while since our last update, but we were holding off making a post to add some highly anticipated features. In the background, we have made significant changes to our infrastructure to support the productivity of our developers and our supporting roles. With that being said, we would like to welcome @Ethanb_UK to his new role as Support Representative, and @lscott122 on his promotion to Community Manager. We look forward to seeing what both individuals can contribute to their new roles and how it will make a difference to our customers every day. We've got some exciting content to share today, so read on for more (yes, we know the videos are low resolution; this is to assist in viewing and uploading). PACX Although we periodically update PACX, it’s due for something new and exciting. @lscott122 and @Jishwaah have been working in the background preparing for the upcoming Voice Packs Expansion! The Voice Packs Expansion will add a whole slew of new voices (in both their native tongue and English) to further enhance the realism and localization of the PACX experience. With that said, we are pleased to confirm the following languages for the update: English (United Kingdom, English language only) Australian (English language only) Spanish German French Mandarin Japanese Portuguese Arabic As for the question that will inevitably get asked, we do not have an exact release date, but we are targeting a release during Q1 of 2023. We are now also hiring for voice actors to support PACX development by lending their voice and becoming virtual cabin crew! This role is open to anybody to apply, regardless of whether they have professional experience or are real-world cabin crew. If you are interested, or know somebody who is, and speak one of the languages above, get in touch today by submitting a short application at https://invernyx.com/apply. Successful applicants will be contacted to arrange an informal interview and to practice with the script before the official recording takes place. If you have any questions about the role, please reach out to Josh Riley via email at jriley[at]invernyx.com. smartCARS 3 We have been spending time working on smartCARS 3 behind the scenes. Finally, we are happy to present some solid shots (and a video) of some new features, as well as a more in-depth technical explanation. video.mp4 Although that doesn’t seem like a great deal of functionality, what is happening under the hood is quite significant. As we have mentioned before, smartCARS 3 is a platform, not simply an application. This platform allows developers (both third-party and first party) to add functionality at any time. What you are seeing above is this concept in practice. The flights page seen above is a plugin that we ship with smartCARS 3. That plugin manages your bid flights, will let you search and book a new one, and of course, will let you start a flight the way a smartCARS user expects. The difference is that if a virtual airline wanted to customize their booking experience (think dispatch system, etc.), they could simply create a plugin with our documented SDK that would entirely replace our booking system while still allowing users to benefit from the rest of the smartCARS experience. Plugins can add menu icons, provide background services, and interact with the rest of the application with the same level of access we are using to develop core functionality. This means that the days of having to develop or purchase a custom ACARS for a virtual airline are over. You can simply leverage smartCARS and customize it to suit the exact needs of your users. Above, we see the new “Virtual Airline Selector” experience. By default, partner virtual airlines will be displayed with their logo visible. A user can search for their virtual airline via that box and select the appropriate one. You will be able to link virtual airline accounts to your TFDi Design account to make restoring previously selected VAs easier. This new ease of use will not come at the expense of virtual airline customization, however. Virtual airlines will still be able to have custom icons, change colors, modify behavior, and give users shortcuts to launch directly to their instance of smartCARS. Under the hood, there is a plugin repository system, notification system, and inter-plugin communication system driving backend of smartCARS 3. With those features out of the way, you can expect to see significantly more visual progress as we approach the alpha testing/developer preview phase of the development lifecycle. MD-11 The highly anticipated TFDi Design MD-11 is progressing well and we are thrilled to announce that the aircraft should be released by the end of September, 2023. We are still leaving this to be very ambiguous, as we would like to allow some breathing room for any issues that may crop up. Since our last development update, we have welcomed another 3D modeler to the aircraft design team, with @arwasairl taking up the work on our newly modelled MD-11 cabin. The virtual cabin will allow you to move around the aircraft freely and get the experience of an airline passenger during your own simulator flights. Initial tests in P3D V5.2, the performance impact of the cabin was negligible. It will still be optimized before release, of course, and for those working on more performance constrained systems, we will provide an option to disable it entirely. Below are some in-sim screenshots of the cabin! Our cabin is based on the KLM 3-class configuration, so there may be some variances from cabin pictures you may have seen. We have continued work on the systems while the art team has been hard at work on the visual items. The autoflight system has quite a few of its more advanced features in-place. We are still tweaking exact numbers and performance, so we are not going to show it off in-flight just yet, but as of now, the following basic modes all work: Heading Hold Vertical Speed Hold Altitude Hold Level Change (Speed-On-Pitch) Speed Hold The important thing to note about those modes is that they are the foundation of the more complex modes. We have already worked heavily on the magenta line and navigation data usage (as you can see by the BAYPO9 SID displayed on the ND in the video). We have been really trying to capture the nuances of the autoflight system and it will vary from what you experienced in the 717, even if just slightly. One of the variances in the MD-11 is the pitch up guidance at 80 knots on the flight director (shown below). takeoff.mp4 We have also spent quite some time working on the stability assistance systems, the LSAS and RCWS systems. The LSAS is a complex system that assists in landing nose-down authority, speed protection, and pitch smoothing in-flight. We will post another video and/or dev update specifically detailing the ins and outs of the LSAS. We also have the (optional) roll control wheel steering (RCWS) feature. This assists horizontal stability by holding the roll wherever it was left by the pilot. It also will return the aircraft to a standard flight envelope if it is left outside of one (shown in the video below). rcws.mp4 Of course, there is the elephant in the room: Microsoft Flight Simulator (MSFS). We have been hard at work testing, optimizing, and refining our code and libraries to run in MSFS. Credit goes to Asobo for correcting a bug in the WASM compiler recently, so that has enabled us to progress further. Rest assured, although we're showing a lot of content in P3D or our standalone environment, nearly all of this progress translates directly to MSFS. We will have updates dedicated solely to MSFS progress over the next few months as we progress toward a fully flyable state. Community Discord has recently released a forum feature for channels, and this has prompted an internal discussion from some of our team about the future of the forums on the website and changing to a standalone blog for our development and news updates. A transitional period will then take place as we train our staff and moderators about how to manage the forum topics and how support will be given to customers who request it on Discord, and how downloads will be done. Our Discord has proven to be popular and active amongst our community. Please let us know your thoughts, as well – we want to ensure the best experience for our customers and followers as well as paving a more efficient path for our support staff to assist when needed. Closing As always, we greatly appreciate your support! As we end the quiet period of development on both the MD-11 and smartCARS 3, we are happy to start sharing more with everyone as we progress toward an exciting product line-up over the next year.
  12. It binds to any IP on the port specified, so port forwarding would 100% work (as far as I know).
  13. I've seen this report but I have yet to be able to recreate it. Can you open a ticket with us so we can try to do a one-on-one AnyDesk session?
  14. This is a very interesting idea. I don't know that we'll do this for the initial release, but a legitimate charter version of the plane does sound intriguing.
  15. We keep finding more and more variations the further in we get. We're going to try to do as many as we can get adequate reference for, so if you have any further details, please be sure to let us know so we can work them in!
  16. It isn't actually unusable according to the thousands of users not having a problem. That said, we've taken special care on the MD-11 to ensure it exceeds the 717's performance.
  17. I believe this was resolved in the latest beta - has it repeated at all since? It was caused by a passenger not having an assigned seat and it checking if they were sitting - that shouldn't be possible due to how seat assignments are generated. Can you give me some further details on how exactly you got it to crash? By this, I mean the exact aircraft and flight parameters you used to get it to crash.
  18. I'll take a look at this ASAP.
  19. We do have plans to integrate with GSX (as much as possible) as well as smartCARS for the ACARS up-link. It's possible that we'd introduce Simbrief as an alternative if you aren't using smartCARS. That said, yes, we're shooting for an immersive experience as well.
  20. I'll get this on our list - we may need to rebalance the likelihoods. I'm not sure if we'll implement this exactly in this format, but we can try to find a happy medium.
  21. I really like this idea. I've added this to our board to review ways we can implement something like this.
  22. There are indeed several sub-variants, but due to their popularity (or lack thereof) in some cases, we may not include them. The idea is something like this: if you only care about cargo, you can purchase just the cargo version for the base price. Then, if you decide you want passenger options later, you can add it on for a fraction of the base price. Inversely, if you decide you want passenger first and then cargo, it works the same way in reverse. The failures pack will be its own thing - we're going a la carte to make sure nobody is forced to purchase something they don't want or won't use.
  23. Is this something you can provide us more information on? I'll discuss it with the team at the next meeting.
  24. As we are preparing to end another year, I'd like to take a look back over what 2021 has been for us. This year was a year of learning and dedication for us. We got the opportunity to meet up face to face at FlightSimExpo for the first time since the pandemic began and it was a much-needed break from the every day routine we'd gotten used to. Spending time with each other and with the members of the community that were able to attend was definitely a highlight for me. This year, we also got the chance to grow our team, refine our processes, and set ourselves up to be the best that we can be. We've been hard at work developing and improving our products across the board in our most asynchronous and efficient manner yet. Armed with the largest and most efficient team we've had yet, we are prepared to make some impressive progress and have some exciting news for everyone who has been patiently waiting for the projects we've been working on. Finally, as always, we are honored to be a part of this community and to be in the position we're in. The support and appreciation we've received over the last year has been humbling and we plan on continuing to impress in 2022. We look forward to getting more hands-on with some of our development progress and participating in more community events, both in person and online, as the world continues to settle into its new normal. From all of us at TFDi Design, and Invernyx as a whole, we wish you a fun, safe, and happy, New Year.
  25. Opening We've been quiet while we've had our heads down recently, but it is time to show everybody what we've been doing! We have changed how we structure some of our development planning by splitting it into seasons. These seasons coincide with the traditional fiscal quarters and, for now, we plan on doing a major development update at least once per season with development streams and shorter updates in between. PACX We've been working slowly and steadily on improvements to PACX. Since the last time we talked about it, we've crushed a number of bugs and implemented a few requests from the community. Among these are items like improvements to record filtering, refinements and fixes for certain in-flight announcements, and general stability and performance improvements. We plan to start testing on this update relatively soon after the holidays to keep things fresh. One of the most requested items for PACX was additional voice packs and we intend to deliver. We've been working on the internal tools needed to create a thorough and immersive voice pack expansion remotely. This expansion will include a number of new voice packs in different languages and accents, as well as some changes to make the experience more realistic in those areas. The good news is that these tools are almost complete. We will soon be putting out a call for voice actors/actresses and/or flight attendants from around the globe to work with us in creating the new voice packs. smartCARS 3 The smartCARS 3 team has been working on some impressive items. The user interface is still very much a work in progress, so I will not be sharing any images here, but I will go into more technical detail about what's going on under the hood. smartCARS 3 is a platform as much as it is an application. We have created a plugin system that allows third party developers to have the same level of access to the core functionality that we are using to create it. This means that virtual airlines and communities can create a truly custom and personalized experience while still benefitting from the existing work done by others and by our team. For example, let's say a virtual airline created a completely custom booking and dispatching system that is totally incompatible with the way smartCARS handles it. This virtual airline could spend a few hours and create a new booking module that their pilots can install that works with their custom system. These pilots can still use smartCARS and benefit from the rest of the features without having to sacrifice the individuality and immersive experience that the virtual airline created. smartCARS 3 will be a huge improvement from the pilot's perspective as well. We've taken a huge number of requests over the years and we are implementing those as faithfully as possible. Little inefficiencies, such as the un-resizable window and auto-scrolling chat will become things of the past. The flight tracking and logging experience will be much more thorough and refined. The review of past flights will be much more detailed and useful, instead of simply seeing the PIREP text a second time. Even the smartCARS Premium features will become much more compelling and useful - allowing a greater amount of flexibility and dependability from your flying experience. When the user interface is ready, we will do a deep dive into the details of some of these new features and demonstrate all that it is capable of. In the meantime, just know that we have heard your requests and feedback and they are shaping the future of smartCARS. MD-11 The MD-11 has been making significant progress over the last several months as well. We can now officially announce that we have partnered with Turbine Sound Studios to create an immersive sound experience for the MD-11. More and more systems have been brought online in the last few months and functionality is getting more complex and realistic. Since the last development update, we've got the FADEC and engine computers implemented, the first part of the flight control systems and FCC working, improvements and additions to the electrical and hydraulic systems, and work has begun in the pneumatic system. The standby display is also now nearly complete, bringing another complex piece of electronics online in the cockpit. In the visual and artwork front, huge improvements have been made. The texturing of the cockpit has started, as well as the mapping and animation of the buttons and switches. It's worth noting that the cockpit seems VERY worn/dirty. This is an option - it's easier for us to create it at maximum wear and tear then reduce it than it is to go the other way. You will have the ability to select the level of wear and tear you'd like. The tools we've created to help develop and test the aircraft outside of the sim have also made getting it into the sim faster, so we expect to see a lot of functionality in the cockpit very soon. The cockpit isn't the only area getting attention, though. The exterior texturing and liveries are well underway. We have a pretty solid list of liveries we want to have available at launch and we're making good progress on them. As always, all of the images shown here are work-in-progress and not necessarily reflective of the final, refined product. If you see something that is out of place or not quite perfect, feel free to let us know, but it may be an issue we're already aware of and will fix at some point before release. We actively encourage participation via our Discord server. One final item that we've discussed on some of our streams but haven't officially stated yet is the price point. As of now, we anticipate the product being available as a base pack and two expansions. The base pack will either be the cargo or passenger version (your choice) and the other will be available for a small upgrade. We also plan on releasing a failures package that will include a full failures menu, operations-based failures and faults, and more. As of now, the base price is expected to be $89.99 USD. The expansion packages will be priced fairly with respect to scope and significance of the work required to create them. Closing Thank you for reading and if you haven't already, I posted our yearly review article here.
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.