Jump to content


  • entries
  • comments
  • views

Contributors to this blog

About this blog

Entries in this blog


Introducing Invernyx


Good Afternoon everyone!

As of May 25th, 2021, TFDi Corp is no longer the name of our parent company. As a result of this, we are now known as Invernyx, Inc. It is important to stress at this time that no changes to the running of the business are intended nor changes to our product offerings. Our registration numbers in Florida are remaining unchanged. This change is simply administrative, where we are taking on a new brand as we continue to grow and expand our presence. Both TFDi Design and JetStream Radio are remaining as their current name and no changes to these brands will be made.

We are taking all necessary steps to ensure that references to TFDi Corp are removed from our legal documents, agreements and websites, though the changes are expected to be rolled out slowly. Occasionally, you may notice references to TFDi Corp on our websites, and we encourage you to report these to us so that we can rectify these omissions.

Over the next few hours, our executive management team will be updating as many systems as possible to reference this change. We would also like to thank Daryl for his work on this new logo, our small team who provided feedback on our logos, and our team for their support as we transition to the next stage!

On behalf of the entire management team, we would like to thank you for joining us on this incredible journey from TFDi Corp to Invernyx, Inc. and for your continued support of our products and services.

Kind Regards,

Collin Biedenkapp and Joshua Riley
Invernyx, Inc. Executive Management Team



Live Development Q&A


We are hosting a live development Q&A session on 22nd of May, 2021 at 11:00EDT (08:00PDT/16:00 BST).

This Q&A and live stream event will be hosted via our public Discord stage channel and broadcasted via our Twitch. It will cover the TFDi Design MD-11, smartCARS 3, PACX, and touch on the TFDi Design 717.

Everyone is encouraged to come and chat with us, ask questions, and see what we've been up to.


A Year to Remember


Hello everyone,

To say 2020 was a unique year puts it lightly. There has been a lot of learning, growth, and struggle. We saw Microsoft Flight Simulator and Prepar3D v5 bring new opportunities and challenges to the table.

This year, our relationship with the community has strengthened through our forums, Discord, social media, and helpdesk. Our team has grown significantly and is ready to take on exciting new ventures as well as continue to deliver on promises we have already made. The PACX Early Access phase was completed, we announced the TFDi Design MD-11, and added two new simulators to the list of those we support (although, we still have things to polish up). We began our partnership with Orbx as our newest vendor. We also celebrated six years of TFDi Design with the community.

With the wind of these accomplishments in our sails, we step forward into a hopeful new year. We look forward to working with the community to continue to create and improve the products we have become known for. I, personally, look forward to spending another year with the fantastic, motivated team we have here and doing great things with them. Finally, we all look forward to hopefully reuniting with familiar faces at the upcoming events in 2021.

On behalf of all of us, I wish you all a fun, safe, healthy, and happy New Year.


6 years ago today, TFDi Design became an official registered company. Throughout this long period, the company has grown to where it is today, and from the administration team here, @turbofandude and I, we would like to thank everyone who has worked at TFDi Design, both past and present, for their motivation and abilities that helped grow the company.

One of our community members, @TheBoeing747, has been working with Collin and I over the past few weeks to help work on a celebratory house livery for the TFDi Design 717, and has also written a few words and asked our current staff members some questions about their time at TFDi Design.


After passing 6 years at TFDi Design, I sought out to ask the staff their opinions on their experience at TFDi Design, and what I received was an overwhelming amount of positive feedback. Here are some of the responses below.

Question 1: How do you like the team dynamic? Do you enjoy being a part of TFDi Design and working on various projects?

Fabio A: They are stupid talented, like ridiculously talented and I couldn't imagine working with any other team right now. We have a really good dynamic. I'd like to think that they know that and I get a lot of positive feedback for my work.

Ozzy H: I enjoy being surrounded by people who, for one, know what they're doing, and also have a passionate enthusiasm for what they do. This is definitely a big part of the team's structure, and it creates an environment where innovation can flourish. The amount of talent this team has acquired over the years is unbelievable.

Henry CI absolutely enjoy working at TFDi Design, without a doubt. The culture and way of doing things is just incredible, and there is really no other company like this.


Question 2: Q: Do you feel that TFDi Design is a good job to take to build experience and grow your talent? Can you elaborate what type of work is completed at TFDi Design?

Fabio A: This is the dream job. I have my day job, as mentioned, but I wouldn't trade TFDi Design for any other company.

Ozzy H: As a 3D modeler, I am always up for a new challenge to exercise my brain and continue refining my skills. This MD-11 project has been one of those satisfying challenges, and just about every technique I've ever learned has been implemented at least once. Everyone at TFDi Design has a high standard for quality, so the opportunities to apply all these nuggets of knowledge are virtually endless.

Henry C: For sure. This is where all of the experience gets built and put to good use. We always look for the best way to solve a problem and like what I am currently working on -- this kind of stuff builds on the knowledge and background of both a pilot and a programmer; this allows us to make sure we are creating the latest and greatest -- ground-breaking stuff that no other company has done before.


Question 3: Is software development your main line of work, or do you have an alternative career?

Fabio A: It's a passion at the moment, while I wish it could be my full time job, it can't be right now. My dream has always been Google :P 

Ozzy H: Developing flight simulator content was actually just a hobby of mine until I gained the necessary skills and experience to venture into the commercial landscape. For a living, I am a full-time mechanical engineer in the field of heavy equipment design for mining applications. It's what I went to school for, and I do enjoy being a part of a machine design team as well as getting my hands dirty every once in a while. I've always had a creative side though, and while it occasionally shows itself in the engineering profession, doing artwork for flight simulator serves as more of a creative outlet for me. Personally, I enjoy the balance that I get by doing both.

Henry C: This is the dream job. I have my day job, as mentioned, but I wouldn't trade TFDi Design for any other company. 

Without further ado, @TheBoeing747 has also painted us the 6th Anniversary livery for the TFDi Design 717 which we hope to see flying in the virtual skies soon! Please make sure you submit your photos on our Discord, or in this forum post:

To get your hands on the Official livery, you can download it from here:

Once again, thank you for your continued support, and we look forward to bringing the MD-11 to market!

smartCARS 2.0 has been released! The official release trailer is below.

Starting today, virtual airlines around the world will begin migrating to smartCARS 2. We’ve thoroughly enjoyed getting to create a flight tracker/pilot client that exceeds expectations and allows us to deliver more than ever before. We’ve listened to feedback, suggestions, and complaints alike and implemented the best of them into what we hope to grow into a powerful application experience. In addition, we’ve implemented smartCARS Premium – a new system that allows us to offer extended features to all smartCARS pilots (per their desire, of course). More information on that is available via the product page (links at the end).
As of now, we have the release and development of smartCARS 2 planned in three phases. I’ve detailed them below:
Phase 1: Initial rollout. Starting today, we’ll be getting virtual airlines converted from smartCARS 1.X to 2.0 and getting any initial bugs squashed. Phase 2: Immediately following the holidays, we’ll be working with translators and our team to offer a unified, localized experience for users of many different languages. We’ll also be finishing the smartCARS mobile apps during this phase. Phase 3: Approximately 90 days from now, we’ll begin phasing out smartCARS 1.X and removing legacy files and support from our servers. An official change log from smartCARS 1.47 to smartCARS version 2 is available here http://tfdidesign.com/forums/index.php?/topic/571-change-log/.
Starting with smartCARS 2, you can purchase a smartCARS license for either a $69.99 up-front fee, or for $5.83 for 12 months. The smartCARS product page is available at https://tfdidesign.com/?p=smartcars2.
smartCARS Premium is available for $3.99 per month for the pilot. The virtual airline does not purchase Premium. The smartCARS Premium product page is available at https://tfdidesign.com/?p=smartcarspremium.
The Future
As always, an initial release is never the end for us. This is a community platform and now that it’s in full view of the community, we have so many things we look forward to adding to smartCARS and smartCARS Premium (such as a fuel planner… except, it’ll be better than expected). We look forward to hearing community feedback and continuing to impress with the smartCARS platform.
It has been about four months since we announced the 717 project, and it’s time for us to let you know what’s been happening. While we were working on smartCARS, progress was being made on the 717. As of now, we have an animated 717 external model ready for exporting to Flight Simulator. This means that texturing will begin shortly, and you will start to see in-sim screenshots. Below are our second, and likely last set of 3DS renders of the 717 before you start in-sim previews.
Now, we have some things to tell everyone.
We are expecting a completed external model, including animations and textures in early 2013. We will, at that point, begin showing in-sim videos and more screenshots than before. We have begun collecting the resources for the sound package, and but we have no estimate on completion. We have purchased manuals and resources needed for the systems. This means that we will begin the instrument programming soon. We are going to follow through on our concept of an initial ‘lite’ release, followed by the full release later on. I’m leaving this unlocked for now, so feel free respond. Thank you for reading, and we hope you’re enjoying your weekend!
As we bring another year to a close, it’s time to review what 2019 was for us and our community.
In 2019, we made changes to our infrastructure, policies, development standards, and organization that made us stronger, more efficient, and more capable. We started growing a team of great people who are proud to be with us and excited to pave the ground forward with us.
We released PACX and have worked with the community to refine it. We helped JetStream Radio get their new website and streaming system up and running. We proudly attended Flight Sim Expo in June and participated in the first two-day Flight Sim Show event in Cosford in October.
We’ve made breakthroughs in some important areas. We finally have a light at the end of the tunnel for the infamous view-switch crash. We are closer to overcoming technical limitations that have held us back in the past. We even started our next aircraft (no, we can’t tell you what it is yet).
We are now combining the best of the business experience we’ve gained with the community and product-oriented mindset that made us who we are. We’re looking forward to bringing you the next iteration of smartCARS, pushing PACX out of Early Access, and continuing to develop the products our community and partners have come to know us for.
As we move forward, we are going to continue to grow, optimize, and reach toward the dreams we were founded on. Thank you to our community, friends, and followers for their patience and support. The fantastic feedback and knowledge you provide help us better ourselves and enjoy what we do. On behalf of the entire TFDi Corp family, I want to wish everyone a great, fun, and safe New Year.
As we prepare to wrap up 2017, I wanted to take a second to say a few things to the community.
Over the last year, we had one of the most stressful, but rewarding, development cycles we’ve ever had. There’s no doubt that when the 717 released at the end of 2016, we still had a lot of work to do; a lot more than we realized. The amount of support and patience the community has given us is humbling. In my opinion, we’ve learned more from the initial missteps, than we would have from a perfect launch. We got an opportunity to learn first hand, what not to do, as much as we learned what to do.
The Community Opt-in Beta has given us insights into how our product is used. As well, it has shown us the problems users encounter that we never see, and has helped us identify such a wide range of inefficiencies or problems in the system that will help us pave the way for future products. In the years we’ve been in this market, the Community Opt-in Beta was, by far, the most effective testing method we’ve had. Although our intent wasn’t to launch into a beta, that style of testing method is likely to be part of future products – before the official “final” launch, of course.
Launching TrueGlass and RealLight, technologies that the community, as a whole, was excited to hear about, was a fantastic experience. We had looked forward to making them possible for years, and to finally have done so, is motivating and exciting.
With that said, I know I speak for all of us in saying that the future looks brighter and more exciting now than it ever has. We’re looking forward to the official major update to the 717 early on in 2018. We also have two other projects we’re getting ready to put into full-time development (which we have held off on to make sure the 717 was where it needed to be). One of these will come as a surprise, and one of them will come as exciting news to those waiting for it. We have a bigger, more refined team now and a much more optimized workflow – this will no doubt be reflected in future products.
If you’ve met any of us, at events throughout the year or online, you’ll know that the one thing we all did our best to do was to be honest, transparent, and responsive, both internally and externally. As we continue to grow, there are no plans for that to change.
From all of us at TFDi Design, thank you for the lessons and the opportunities this year, and we’re looking forward to exceeding expectations in the coming year. Have a safe, fun, and Happy New Year.
Public Update Released (
To say it’s been a long road for everyone would be an understatement. We’ve been busy for the last 6 months getting this aircraft to where the community had expected it to be back in December. There were a great number of areas that we realized were lacking, so we spent the first half of this year working on enhancing the aircraft with those of you who opted into the Community Beta. As of update, these improvements are now available to the public. With your help, we’ve been able to bring the aircraft to a point that we’re happy to put our name on it. A full list of the changes that have been made can be found here.
The team would like to thank all who participated and gave feedback during the Community Opt-in Beta.
If you are having issues with the new version, please submit bugs and suggestions here.
If you are having issues with activation, please open a ticket with us here.
Immediate Future
We can hear the question already, “Where’s the paint kit?” Well, we’re working on finishing up the changes to the exterior of the aircraft as fast as possible. Once these are completed, we can release the paint kit to you. We believe this to be a short-term goal to get finished, not something that is on the back burner.
We are also working on getting the aircraft ready for Prepar3D v4. This is something we are also hoping to have available to you soon. We are dealing with a couple CTDs and adding support for new technologies that are available to us in this sim. This is also a short-term goal for us.
Going forward, there will still be ongoing updates, but once these two final short term goals have been completed, some of our focus will be moved to future projects that we are excited to tell you about in due time.
If you are going to be attending FlightSimCon in Connecticut (June 10-11), we would like to see you! Please stop by and say hello at booths 207 and 208. Most of our team will be there and happy to answer questions.
It is with great excitement, pride, and some nerves, that we announce the release of the TFDi Design 717. It is now available for purchase here.
We started this journey four years ago. Throughout those years, we’ve made many friends, worked with developers, pilots, testers, dedicated simmers, and combinations of all four. We’ve learned more than we had ever anticipated and it has been an incredible journey. As I hinted at yesterday, we are now beginning a new journey with our customers and supporters. We have taken great pride in giving the community that supports and purchases our products a voice. We’ve taken pride in, despite the circumstances, staying humble and part of the community.
On that note, we want to take the opportunity to work with you on the 717 from here forward. There are plenty of areas we’d like to improve and features left to add, and there are things we can’t do alone. We want to hear your thoughts and feelings on the product – new features, fixes, and more are possible quickly and easily and we have every intention of delivering them. We want to make the 717 a product like no other, beyond simply correctly modeling the aircraft.
We look forward to hearing from you and continuing to expand and improve the product you’ve waited so long for. On behalf of myself, Brandon Filer, Joshua Mendoza, Martyn Becker, and Brandon Olivo to the developers, testers, pilots, and enthusiasts that have helped us along the way, thank you.
See you in the skies.
Yes, you read the title correctly. After an extremely long journey of over four years, we have set a target beta date that we’re ready to announce. Before I jump right in, I’d like to cover a few important topics.
What will “beta” be for this product?
This will not be a several month beta process. We have been in what our community manager, Josh,  has called a “progressive alpha” for just shy of a year. What this means is that many of the systems on the airplane have already been tested relatively thoroughly. They’ve been reviewed by pilots, checked against documents, and tested via aircraft sharing by testing team members and developers alike. The result of this is that our systems are no longer “bleeding edge”. Beta will be aimed primarily at finding and fixing “showstoppers”, meaning crashes, memory issues, or major system malfunctions.

How will post-release updates work?
No matter how much we prepare, test, and consider, finding EVERYTHING before release is impossible. We’re aware of this and we’re prepared to respond accordingly. Our addon manager will have the ability to deliver updates to the product efficiently (by that, we mean without remembering passwords, re-downloading the entire aircraft, or reactivating). Our intent is to consider the aircraft in active development immediately following its release. Problems will be corrected quickly and we will do everything we can to stay ahead of reported issues.

What should you expect from here?
We will post another article before release detailing exactly what to expect on launch day, details regarding our activation system, and preparations we’ve made to ensure the best possible service on day 1. Any questions or concerns expressed before then will be handled via that article.

When will the 717’s beta start?
Thank you for actually reading what I had to say. As of now, our target beta date is December 10th, 2016. At this point, it is time for the testers we’ve confirmed over time to contact us, as we stated you would be told. You must include a reference to your confirmation of acceptance to the beta team in your correspondence. We are not accepting new testers at this time.
We’re almost there folks. Stay tuned for more information in the coming weeks. We’re still on track for release this year. When we have a firm date, we’ll be sure to let everyone know.
You can discuss this article on the TFDi Design Forums by clicking here.

TFDi Design will be holding an Ask Me Anything on June 14th, 10 PM GMT (6 PM EDT/3 PM PDT) at the flight simulator subreddit, /r/flightsim. An AMA is an opportunity for the community to ask questions and receive answers to most of them. While we are going to try to answer as many questions as possible, we will not be announcing a release date (other than that it will be in 2016). We look forward to seeing you all there!
TFDi Design is happy to announce we will be doing a live stream of the 717’s first public flight on June 9th, 2016 at 10 PM GMT (3 PM PDT/6 PM EDT). You will be able to tune into our stream at twitch.tv/tfdidesign to watch and chat with us! We will be flying the aircraft from startup to shutdown.
This will be the first time that the community will get to see the full scale of the 717 project, not just screenshots or highlight videos. The stream will provide you the opportunity to directly inform the team of your feedback and input to help improve the plane. It will also allow us to answer community questions about the plane and the development process.
The 717 is a unique plane in real life and we feel that we have captured its personality quite well in the simulator. We look forward to sharing how far we have come and we’re excited to hear what you, the community, have to say about it.
Our first post under our new brand will be a fun one. Today, we’ll go into more detail about where we’re at on the FMS and navigational equipment.
MCDU and Flight Management System

Yes, the keyboard has been disabled while we’re still working on the FMS. There are three main pieces – navigation, performance, and miscellaneous (everything not covered by the first two). We’ve made solid progress in fractions of the time it traditionally takes, which is music to all of our ears. As of now, the flight planning and navigation portion of the flight computer is mostly complete. Basic planning such as departure airport and arrival airport are already complete, and terminal procedures (SIDs fully, STARs partially), airways, and direct legs are functional. We’ll be cleaning up a few areas of concern and implementing the last of the features on that front.
I’m sure you’re wondering how we’ve made such progress without an in-sim keyboard. We build all of our technology in a notoriously modular fashion – this means we are able to plug and play components in a matter of minutes. For those of you with coding background, our modularity extends to the point that installing the electrical system, for example, consisted of adding a call to “execute_electrical_system();” to our main system function. Once installed, it reads from the rest of the aircraft’s systems and populates them with information about the electrical system. What this means for the 717 is that, when more complete, we’ll install our extensible and configurable “FlightManagementSystem” module to the aircraft and hook it up to the screen. Until then, we’re developing it in a sandbox project where testing and changes are infinitely easier (this is part of how we optimized the process).
Navigation Data
We had intended to use Aerosoft’s NavDataPro for our navigation data source. Since that decision was originally made, we were finally able to get in touch with Navigraph (the fault was ours – we had reached out to them via the wrong venue and our message got lost). Since then, they’ve been equally as supportive and friendly as Aerosoft. Additionally, Navigraph has provided us with a navigation data format that has worked very well with our FMS platform and that has made development more efficient. Our plan is to work with Aerosoft to unify the formats, but we can’t officially confirm whether or not we’ll be able to support NavDataPro.
Recently, we have been researching inertial navigation systems (IRSs) and the Global Navigation Satellite System (GNSS). These two concepts play major roles in providing the 717 its navigation and gyroscopic (pitch, bank, heading, etc.) information. We’re working on creating an IRS that will drift, over time, if not updated by other systems and a GNSS unit that reports realistically accurate positions. As well, we’re working on isolating both on and off-side air data and inertial reference units to bring function to the gusset panel. We have mapped out and begun coding modular IRS and GNSS systems to install into the 717 – that, and its implications, will fit nicely into our next article. The displays are prepared to accept IRS input, however, and our air data computer sensor simulation will integrate nicely.

The Immediate Future
We’ll be posting more soon, as there are other developments happening that we haven’t covered in this article (hint, there isn’t an INOP sticker on DU2 and DU4 anymore), but we wanted to leave off on this. We’ve confirmed that this is the year of the 717 – it will be released in 2016. When, exactly, we can’t confirm, of course, but it’s safe to say that the majority of the hurdles that were mystifying our date estimates, such as the autopilot, FMS, and some of our unnamed but exciting features, have all progressed better than expected. We’re at a very good place.
It’s been awhile since our last major update on the 717, but we’re back with some exciting progress.

First and foremost, we’ve officially announced our cooperation with Turbine Sound Studios for the internal/external sounds. The 717 will ship with their soundpack specially fitted into our aircraft (at no additional charge to the customer, of course). This, paired with our realistic cockpit ambience and mechanical sounds (fans, avionics, switches/handles, etc.) will be quite an experience.
Note: the cockpit sounds heard in our last video (“717 Flight Controls Overview”) are not final and may be improved as development continues.
Since our last post, we’ve implemented three important pieces of the 717’s systems – the primary flight display, electronic instrument system (EIS) alert system, and display unit reconfiguration system. Without further ado, here is our primary flight display:

We’ve gotten the majority of its function and visual effects complete. The captain’s and copilot’s displays are completely independent – including separate minimums callouts, giving us a very robust foundation for the more complex display options. The next major step, display-wise, will be implementing the navigation displays (activating the last currently inoperable main displays).
EIS Alerts
One of the most complex pieces of the 717’s EIS is the alert system – it displays logically arranged messages on the engine and alert display (EAD) and the respective system display (SD). Here’s a screenshot showing this – in the first screenshot, the aircraft is running properly on APU power with all transfer buses automatic.

In the second screenshot, I’ve turned the left transfer bus to open (preventing power flow), which has isolated the left AC bus, causing the following alerts:

As well, you can see that the “ELEC” cue switch has become illuminated on the pedestal. Pressing this switch, as this point, will acknowledge the new electrical warning messages and move them entirely to the electrical SD and extinguish the light.
Display Reconfiguration
The other new system we’ve implemented is the automatic switching of displays. When a display unit is turned off (or is off due to insufficient power), the system will reconfigure which displays appear on which physical screen. This can be seen in the following screenshot set. In the first shot, all displays are turned on.

In the next shot, I’ve turned off display units 4 and 5, causing the system to move the SD to display unit 2, instead of 4.

The Near Future
I won’t be including any new cockpit screenshots here, as we’re not quite ready to show it off yet. That said, Brandon Filer (our resident graphic/texture guru), has been hard at work crafting some considerable visual refinements for the cockpit. It is very likely that our next major post will be chock full of nice new things to see.
We’re moving closer to considerable project milestones and have also been slowly preparing our internal infrastructure for the inevitable testing period over the last few months. Of course, we don’t give release estimates until they’re sure enough for us to bet on, but we are moving along quite a lot, especially in some areas you can’t see just yet (FMS/AFS, etc.).
Wrap up
That’s all for now and we’re looking forward to bringing this aircraft into the sky.
TFDi Design is proud to announce the release of the smartCARS Virtual Flight Tracking Software, making it available to virtual airlines for purchase. smartCARS is a state of the art Aircraft Communications Addressing and Reporting System (ACARS) developed for Microsoft Flight Simulator X and Lockheed Martin Prepar3D. smartCARS was designed with an easy-to-use and extensible user interface.
Benefits for Pilots
Fluid, dynamic user interface High speed connectivity Straight forward and informative flight information Detailed flight log Multi-bid support In-app route search and bid management GPWS callout system (with two different callout types) Flight attendent announcements Chat with the whole smartCARS community, or just your airline Automatic login Extensive options Benefits for Virtual Airlines
Web License Management (not available for the November 4th release) Cloud-based pilot chat (driven by the smartCARS™ Cloud_x64 System) Automatic updating (web script and pilot clients automatically update) Extensive logging options (not available in November 4th release) Customized login screen (your logo and airline name) For more information, visit the official smartCARS product page.
The journey begins here!
TFDi Design is proud to announce the TFDi Design 717 project!
We are working hard on the new 717 project, and it is farther along than expected.
Why the 717?
The 717 is a very fun airplane to fly, and is different than any other aircraft. It has a unique design, both externally and internally, and will be a pleasure to design and fly. The flight simulation community was in desperate need of a quality 717, and we feel we can fulfill that need.
How far along is it?
The 717 is currently about 20% of the way completed. Currently the external model is mostly completed, and the flight dynamics are mostly complete as well. We are in the process of texturing the external model and collecting resources for the virtual cockpit. We are planning a rapid development cycle for this project, and plan to push it as fast as we can without sacrificing quality.
As always, TFDi does NOT make any projections on release dates, as they are subject to enormous change. We will keep everyone updated, and the best place to stay up to date is right here!
Want to contribute?
TFDi needs resources and information from real pilots and crew, and we would love any help any of our fans could give us. If you or someone you know can help, please email us at admin@tfdidesign.com!
On behalf of the whole team here at TFDi Design, we are proud to announce the release of Passenger and Crew Experience, dubbed PACX.
After several years of hard work and several members of the team pulling together, we can finally share with you the result of our dedication and allow you to finally use our product. Throughout this time, we have worked tireless hours, made great friends and recorded over 1000 individual sound files and it has been yet another amazing journey made by our team.
With that being said, our product is not completely finished. This is because we appreciate community feedback and intend to roll our product out as “Early Access” so we can continue to build and develop PACX over time and to continue to build on what our beta team has told us. This means that we want to hear from you. We want to hear your thoughts on our product to allow us to build new features, release fixes and deliver on what you want.
On initial release, you will be able to communicate with the cabin, whether that be by completing a pre-flight announcement, dealing with drunk passengers or resolving an in-flight passenger emergency. PACX takes your simulation journey to the next level, by providing you with an in-depth insight into flying an aircraft full of holidaymakers or business travelers in the rows behind you.
At this moment in time, we would like to thank all our developers, testers, pilots and experts along the way and look forward to speaking with you in the coming weeks to help shape PACX into the program that will provide a higher level of flight simulation.
Find out more about PACX and get your copy today at https://pacx.online.
Over the last year, thanks to an immense amount of help from the Community Opt-in Beta, we have added, fixed, or changed over 400 different items in the TFDi Design 717 and Addon Manager. It has become largely a new product. With that said, we are approaching version 1.1, which marks the main, public release of the aircraft that we were initially aiming for last December. When we release the update, we will post another article detailing the significant changes.
The Plan
So, that said, we have a few changes we wanted to explain to everyone and make our plan clear. As of version 1.1, you can expect the following:
Development effort toward the aircraft will be reduced, though several new features and bug fixes will still occur Information, announcements, etc. for other/future products may occur We will move all posts before version 1.1 to a sub-forum to clean out the main aircraft forums The latest (at the time of the 1.1 release) Community Opt-in Beta version and Prepar3D v4 will become public The Community Opt-in Beta will still be used to test fixes and new features What will 1.1 Contain?
When we release version 1.1, we will post information detailing specific new features, note-worthy fixes, and significant changes to the aircraft. For users catching up who are not part of the Community Opt-in Beta, you will notice changes like the following:
Numerous new MCDU features Innumerable systems additions, improvements, and fixes Major changes to the tablet Countless new Addon Manager features Considerable stability improvements Various CTD fixes Prepar3D v4 support TrueGlass and RealLight (for Prepar3D v4) Significant FADEC and engine improvements Performance improvements And MANY, MANY smaller changes For a complete list of what has changed in the Community Opt-in Beta, please see the changelog here.
Version 1.1 will also contain the following (that are not currently in the Community Opt-in Beta versions):
Exterior texture overhaul and a proper paint kit (this will break existing repaints) Overhauled fan blade appearance and added blurred variants for engine running/high RPM scenarios Wholly rewritten documentation (full systems and FMS guides) Cabin lighting The WING/NACL light in P3Dv4 (this will be released to the Community Opt-in Beta soon, but I listed it here for sanity) Various external model details and fixes The Future After 1.1
We have promised several features and had intended for them to be in version 1.1. That said, as we’ve discovered, the current Community Opt-in Beta version,, is proving to be one the most stable and thorough versions yet. That, combined with the fact that we do not want to hold out on delivering the massive amount of other improvements to the aircraft from customers, led us to delay those features. We want to ensure that a stable, complete version of the plane is available to all customers while we take time to correctly implement and test these new features.
With that in mind, we will continue working on and testing, and at some point in the foreseeable future, add the following features:
HOLD ALTN F-PLN Level-off arrows while changing altitudes Official compatibility with specific GoFlight hardware (more details to come) We do have intentions of adding several other options/features. However, I don’t want to officially promise them as we do not know what the future will hold just yet. We’re aware that the delay of some of these things may frustrate or disappoint some users, so I’d like to take a minute to explain entirely, from our side, our reasoning beyond the obvious.
Last year, as we prepared for release (still blissfully unaware of how far we still had to go), we all strapped in and worked weeks of 16 hour days. During that 6 week sprint, three of us put in, combined, nearly 2000 hours of work. Although I am, to this day, impressed with the level of commitment and dedication my team showed, we felt the effects of that up until around Flight Sim Con 2017. It affected our drive, the enjoyment we took in our work, in some cases, the quality of work, and it contributed largely to the tunnel vision that led us to release the aircraft in the state we did. I made a promise to never do that to my team again, and I wanted to ensure that we all, our fans, customers, and us alike, can enjoy the holiday season this year with our families. So, this, combined with the fact that we have a version of the aircraft we know everyone will enjoy and that the remaining features will require more time and testing, we decided that this was the best route to take for everyone.
Although we will not announce the exact date of this update, it is getting VERY close. We all sincerely appreciate your patience and enthusiasm and look forward to seeing you all fly what our vision for this aircraft was. Also, to add some media to the wall of text above, here is a preview at cruising altitude with the WING/NACL light on in Prepar3D V4:

It has been a long month since launch and the feedback from the community has helped us improve the product quite a bit just in the last month. Some of you have been keeping an eye on the changelog and have noticed quite a big update on the horizon. While we would love to roll it out immediately, we are going to take a different approach to this next update. We are introducing the community opt-in beta that will allow you to receive the latest beta version of and subsequent updates.
How can I participate?
If you wish to help us test before we roll it out to everyone, you can go to the Client Area and select the “My Products/Services” tab. Click on “View Available Addons” tab on the left sidebar of the webpage, click on “Click here to view & order”, and select TFDi Design 717 Community Opt-In Beta (we suggest that you select the PayPal payment option, it will skip payment information since it is free). This will allow you gain access to the COB and from there you can open the addon manager and it should automatically update to the latest version of the COB. Please note: You will need to own the 717 before seeing the COB option.
This build will introduce many features people have been asking for as well as many fixes and new tools for us to help you. The first feature I’d like to introduce is the addition of pop-up display unit and MCDU 2D panels. Here is a photo that Collin posted to the forums.

We also are adding the ability for you to hide the yoke if you wish. This was another popular feature request from many of you and will be available in the update. Here is a GIF of that feature:
  00:04 00:07 A Better Platform for the Future
With this newest update, we are introducing new tools for us to help you solve your problems. We are hoping that these tools will allow us to gain a better understanding of certain crashes that are very difficult to impossible to recreate. This will allow us to begin pushing updates that solve some of the edge-case CTDs that some of you are suffering from. We look forward to getting many of you back in the air so we can start focusing on adding more features in future updates!
First, let me start off by saying this has been an incredible journey. We made a commitment that 2016 would be the year of the 717, and so it shall be. Before I announce the all important date and time, there’s something I’d like to share.
The release for us isn’t the end of the journey. It is a start, in a way. We believe the product we’re going to release will be thorough and enjoyable. That said, like any other product, especially the first release, it will not be perfect. We have developed technology to deliver updates that are smaller, quicker, and easier than they are for any comparable product. There are many things we intend to expand and improve in time. These updates will be provided frequently and free of charge to all customers, naturally, potentially excluding something like support for a new simulator platform or an entirely new expansion to the product.
We are ready to begin the second half of this journey, and at 6:00PM Eastern (2300z) on December 22nd, you will be too.
I’ll leave off with a few pictures of the aircraft at night, as we haven’t shown that off much yet.
TFDi Design is pleased to announce the opening of its official forums. The forums will provide users a place where they can ask questions and receive community assisted support for official products. Additionally, users can discuss the latest topics in the world of flight simulation, and even share their screenshots and videos.
This additional gateway into the community will also provide us a new method of collecting user feedback for the 717. As well, it will let us share more frequent progress updates, including media (screenshots and videos) exclusive to the forums.
The TFDi Design Forums can be accessed by visiting forums.tfdidesign.com, or by clicking the “Forums” tab in the navigation bar of the TFDi Design website.
EDIT: Congrats to the winner, DaneFlats! We are looking forward to seeing your streams of the 717!
Want the chance to win a free copy of the TFDi Design 717? A giveaway will be held during the First Public Flight Live Stream on June 9.
How to Enter
Tune into the TFDi Design 717 First Public Flight Live Stream on June 9 at 10 PM GMT (more details here). Type the specified command (to be announced during the stream) into the chat on the TFDi Design Twitch channel during the stream. Remain tuned into the live stream until the winner is announced. Details
Only one (1) winner will be randomly selected to receive the free copy. Only one entry per user is allowed. Users with multiple entries will be disqualified. This ensures a fair opportunity for everyone. A coupon to redeem the free copy will be made available to the winner when the 717 launches later in 2016. A Twitch account is required to enter the giveaway. Good luck to everyone! We look forward to sharing our progress on the 717 next week.
It’s been a little while since our last update, but we return bearing news. Since our last update, we’ve made progress in four major areas.
Navigation Display (ND)
In our last pictures, the second and fifth displays were still off. This is no longer the case. Although it’s not complete yet, we now have the navigation display present and functional with wind indication and even a radar of some sort (hint hint). Here’s the ND without air data input:

Here it is with everything set up:

We will focus almost exclusively on the ND when the time is right, so don’t worry if it looks a little barren now.
Engines And Engine and Alert Display (EAD)
We’ve got the pneumatic system started now (visible by the non-zero manifold pressure and temperatures on the system displays), which was the last component required to implement the engine starters. This, of course, urged us to progress the EAD enough to display what the engines are doing. Here it is with the engines started:

Note: the “AC/PRESS INOP” warning is there as a reminder to the internal team that the pneumatic system isn’t complete yet. We’ve been working closely with our flight dynamics expert to get engine timing and numbers right. We’ll create a video showing the engine starter system once we’ve got all of the indications and modes working properly and the sounds are fully in place.
Flight Management System
One of the reasons we’ve been very quiet is our recent devotion to the FMS. It has progressed in leaps and bounds since we lasted posted about it. It now properly supports SIDs, STARs, airways, and is in the process of getting the remainder of its flight planning capabilities implemented. A little more cleanup and it’ll be time to move on to performance. As discussed, the FMS won’t be seen functioning in the VC until it’s nearly complete, so do not be alarmed by its absence.
The (Near) Future
We’ve very close to several large internal milestones. Once these are hit, the next phase of development (no, not beta just yet) and subsequently, how we’ll be presenting information about the aircraft’s progress, will begin. That said, some of the things to look forward to in our next progress update include the rest of the pneumatic system, the annunciators, some major visual improvements to various cockpit components, and the first pass at the autopilot (meaning heading, altitude, speed, N1, and vertical speed modes).
A modern and inviting brand is important in the era of social media and technology. As all of us here at TFDi Design continue to push the limits of flight simulation with both smartCARS and the 717, we figured it would be a good time to finally give our public appearance a new beginning.
The Colors
The first step at creating a fresh look for TFDi Design was to create a color combination that was inviting while still sticking to a red. After careful tweaking of RGB values, we decided on a deep red and dark gray (and white if/when needed).

The Logo
Next, we had to come up with a logo that the entire staff was happy with and that we thought the community would like. From the beginning of the design process, we knew that we wanted to maintain some form of a ‘swirl’ as a sort of tribute to the original icon that has been with the company since its inception.
After some rough concept work in Photoshop, we came up with the design below.

This was nice, but it didn’t quite cut it for us. After some more trial and error, we found that creating a circle and cutting the above shape out of the circle left us with a rather interesting design.

The staff was sold. The basic shape of this icon was very much liked by all members of the team. With the design decided, we created a vector version of the icon that is more symmetrical than the concept/mock-up.
Now that we had a clean/vector version of the final icon, we added text and began trying different color combinations before we finally decided on the final version of the logo shown below.

The Website
With the new color scheme and logo ready, we set to work designing and coding a brand new website. Our previous website, although it did its job, was definitely beginning to show its age. From the outside, it was clunky, more difficult to navigate than we’d like, and not laid out in a way that fit where we want to take the company. We started the process by upgrading our content management/billing system to the latest version and repairing the current outstanding issues.
Then we began the front end work. The design started by us scrapping the previous design we tried and building on similar ideas (much like we did for smartCARS 2 – which also ended up being for the better). Once we knew what we wanted to do, we started coding it.
Mobile Centricity
Today’s society is becoming more mobile powered than ever before and it was about time we responded. We reached into the mobile software world with smartCARS Mobile and it was only fitting that our web technology joined it. We designed every page to maintain the adaptive/responsive experience it needed to be not only viewable, but enticing and productive, on a mobile device. We modified templates of the content management system itself, as well as adapted its responsive elements into third party modules we’ve implemented.
We ensured that breadcrumbs are accurate and present where applicable, menus react to device size to showcase content, and that graphics are effective and immersive across all viewing experiences. Careful consideration was given to color choice, content location, interactive effects, and responsive adaptations.
Revisited Logic
We re-evaluated our core principles relating to how our content is laid out to create a more user-friendly experience. Menus aren’t as deep, links are more logical, and navigation is far more intuitive. We’ll be working on improving our knowledgebase content over the coming weeks, as well, to offer a more robust and helpful library.
Upward and Onward
This is not just a new website for us. It’s us taking the next step toward sculpting TFDi and demonstrating our growth as developers, business managers, and community members. Our logo’s colors represent our ideals – the red is the passion, the fun, and the creativity that fuels our work. The black represents the business, logic, traditions, and guidelines that we follow and set that keep us traveling in the best possible direction. The shape of our logo, the swirl, which was originally loosely based on the appearance of the center of a jet engine (with the cone painted white), is still present, representing our commitment to our roots and morals.
We’re confident that we’ll be able to continue to not only meet, but exceed both our expectations and our customers’ expectations as we continue to progress. We all look forward to the year of the 717 and beyond.
  • 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.