• Content Count

  • Joined

  • Last visited

Everything posted by turbofandude

  1. There is no wait anymore - you can reset it on your own to avoid having to wait for us. https://tfdidesign.com/index.php/knowledgebase/53/How-to-reset-activations-on-717.html
  2. It did not ever get added, no. It is still on our proverbial list of items we know are missing, but it is not slated for the next update, no.
  3. Also, to further Josh's point; we don't even necessarily know what portion of the model would require reworking. There are SO many textures, materials, and surfaces in the file and there's no guarantee that a redone model wouldn't have the same problem. We will not be redoing the model to attempt to fix a problem we have a workaround for in the knowledgebase. Edit: This KB article https://tfdidesign.com/index.php/knowledgebase/44/Simulator-Crashing-When-Changing-Views.html and this forum topic https://forums.tfdidesign.com/index.php?/topic/3754-view-switch-crash/ both describe workarounds. If you haven't completed a full flight in a year, it's because you haven't looked at the solutions we've provided.
  4. It hasn't yet, but it will be for the 1.0 update (which we are currently working on).
  5. I am working on getting some remote support sessions setup to try this again. It isn't the bug we initially believed it was.
  6. Is this possibly the view-switch related crash? If so, there are articles/posts that may help you in our knowledgebase/forums.
  7. This is them: TFDi_Design_717_Fx.zip
  8. You'll want to map events, not variable control - i.e. make pressing your switch trigger the button press event. Most of our code is built with that idea in mind.
  9. Are any of you seeing the bulb illuminated like my screenshot? If not, there's something wrong.
  10. We've never been able to isolate one setting, addon, etc. that re-created it. It's comforting to know they're on it.
  11. Hmm. I suppose that's possible I suppose. I see it like this in my sim: They're definitely not the brightest, but they are indeed on/visible.
  12. We will be natively supporting the new phpVMS (and newer PHP versions) with smartCARS 3.
  13. They confirmed it is on the list but they haven't had time to work on it yet (per the latest email from them).
  14. It is indeed part of the AIRAC. It should be read from your arrival airport (if I remember correctly).
  15. I'm checking with them now to see if there has been any further progress.
  16. None of our reference actually states that the transition altitude is editable. It's an easy fix if it is, but that's why it's locked now.
  17. If the problem was in the code, I'd agree. The issue they found is a bug in an texture-related operation, which is more difficult for us to work around.
  18. Folks, As we are approaching the end of the year, I wanted to give an update on the status of the project and the plans going forward. Right now, there are 15 open items on the list for us. These vary in complexity and importance, but overall, they're focused on smoothing out the user experience and polishing the product as we approach version 1.0. The list includes items like: More flight comment types More passenger interaction options The cabin lights dimmed announcement Fixed/improved integration for certain third party aircraft (NGXu, Quality Wings 787) Serious improvements and refinements to sound volume, timing, and splicing There are already several changes listed on the change log here that aren't on that list. Once version 1.0 is out, we will be able to look at corporate, military, and general aviation support. We've had some requests but interest has been mixed, so we will working with the community to determine the best plan. Thank you all for your support and feedback and have a great New Year!
  19. This is not an intended behavior, more a side-effect of the UI kit we used. I remember reviewing this recently and did not find any code that explicitly sets it. Future versions (smartCARS 3.X) will not have that issue.
  20. The project is still actively maintained, but it is not under active development. We periodically fix things or add minor improvements as time goes on. Do you have any particular requests? I make no promises with ACARS/CPDLC functionality - it's something we'd like to see, but time/technical limits may not give us an easy path forward.
  21. smartCARS 2.X has been around for a while. Part of our hesitation in adding major things is because we're focusing new development efforts on smartCARS 3. The code is not the same standard in smartCARS 2 as in our recent projects and it has become harder to maintain. It's not because we don't care - we have a massive list of improvements, additions, and fixes to add to smartCARS 3.X.
  22. It is extremely unlikely that smartCARS is causing this. smartCARS reads from FSUIPC but does not write unless it is to disable slew mode or restore from a backup. Otherwise, it only reads.
  23. Ernesto, Sorry for the delay! How are you trying to integrate it? We can provide a kit to do so.
  24. We've had a hard time figuring out exactly what the issue is. I've seen that the lights are a dim, but they're "working" in that they appear when they should. Can anyone having the issue send some screenshots of what they're seeing so we can try to identify it?