Jump to content

turbofandude

Administrator
  • Posts

    2,503
  • Joined

  • Last visited

Everything posted by turbofandude

  1. I'll add this to our backlog and get it looked at - strange indeed!
  2. The strange part is that all of those airports are coded as "RU", meaning it should be selecting those names. Is this recreatable?
  3. My apologies for the late response! Thank you for the offer! I do believe we have some of this information in digital form now, so I wouldn't want you to go through the trouble of sending it just for it to sit. That said, that is an awesome piece of aviation history now.
  4. Can confirm this was a bug and it is now fixed in my build. We (somehow) had a hardcoded constant gross weight, so it wasn't respecting the actual flight parameters. Now:
  5. I don't believe we ever said it would be 4.5 only. It will support both v4 and v5.
  6. I just took a quick look through the code and we do indeed use 145 as a placeholder if the approach speed isn't valid. I'm not sure why it's being forced to it currently, though. If you manually edit the speed, does the FMS speed reflect it?
  7. 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.
  8. turbofandude

    Landing Data?

    We track landing as the last vertical speed before the on-ground condition becomes true.
  9. That's awesome! If you need any other vars/events, please do let us know!
  10. This is included in PACX by default now.
  11. Just to further add to this - we aren't ruling it out as a possibility. We are focusing on the core functionality and development at the moment. We are writing the majority of our code in a very platform agnostic way and will make every effort to reach as many as platforms as possible when the time comes. Only time will tell what is possible as these platforms develop.
  12. The best way is to trigger the event associated with it - that'll give you the sound and the associated function more than the variable will.
  13. If they have changed/added additional variables, it may be something we can fix now.
  14. We just recently had an issue with Orbx Central not installing all RealLight textures, as well. I figure this may be related (as our distribution of the textures does indeed have the _n textures included). I've let them know and asked for their insight. Thank you for the help figuring it out @NBFlightSim
  15. 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.
  16. PACX does not directly modify the volume of the microphone. This is likely other software causing this.
  17. This is something we can look into in the future but would require significant changes to the way we handle flights. I have put it on the suggestions board.
  18. You can hide it by right clicking the PACX icon in the tray to hide it. That said, we could make this an option, in the future.
  19. Thank you for the support! We will keep everyone updates as things progress.
  20. Regarding the new plane, there are quite a few of us who work on different areas, so the existence of the MD-11 does not mean no further work will come to anything else. As far as the issue at hand - we have rewritten a good chunk of the TrueGlass and RealLight rendering backend from scratch AFTER the initial V5 version initially came out. That was to address the VRAM consumption (which, for the most part, it did). Now we're grasping at straws trying to isolate the cause of the DXGI DEVICE REMOVED/HUNG issue. That's the only other main thing holding it back and we were hoping 5.1 would alleviate it somewhat (it evidently has not). We've also periodically sent out updated DLLs to test various fixes via Discord but they not yet proven successful, hence a lack of an update. Also, please keep in mind the 717 has been out for several years and can be installed into 6 different simulators - P3Dv5 being the sixth. We are not going to forget about it, but we also have to balance moving the company forward with maintaining existing software. This is why you see the priorities change, at times. As we're finding that the passive approach (waiting for the simulator to iron itself out) is not working, we will begin taking a more active approach again very shortly.
  21. There is currently a working beta. If TrueGlass causes issues, disable it temporarily. We have been working on it on and off for months, going back and forth with testers, monitoring feedback, and working with LM to try to isolate the problem. We're not "abandoning" it and we've made it clear we will support it, but the problems are proving more complex than we originally anticipated.
  22. Could you open a ticket with our support team? We can get an AnyDesk session with you so we can take a direct look. That may be easier.
  23. Are you receiving any error messages or similar? Or is it simply not working?
  24. They are compatible but we are currently experiencing more instability than we're comfortable with for a non-beta release. We're hoping future versions of P3Dv5 will bring us a more stable base to work from and we can then continue refining/fixing our pieces of the puzzle.
×
×
  • 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.