• Content Count

  • Joined

  • Last visited

Everything posted by turbofandude

  1. Perfect! I'll see about getting this amended.
  2. This should now be resolved. Please ensure the aircraft is up to date.
  3. We will get this resolved in time for Christmas flying.
  4. We've seen that particular bug happen once every so many months, then go away again. The crash on initial load, however, is new (and didn't happen to any one of the beta members, either). If you're experiencing that, PM me and we will get it fixed ASAP.
  5. I debugged the crash dumps and I was unable to trace them - they may have just been the regular "random" CTDs we all get. If you're able to recreate them reliably, please let me know.
  6. There are some limitations on usage of ILS/VOR together (that is one of them). Regarding removing an ILS, if the ILS is auto-tuned by the flight computer, it cannot be removed until it isn't needed. If it's manually added, deleting it will remove it.
  7. @orbmis I've figured it out. We actually removed the custom autorudder implementation, as it was deemed unnecessary (the default setting controls ours, now). That also resolves it adjusting the default autorudder setting.
  8. I found the issue. It's resolved in
  9. @Mistrfiksit Any idea? The only reference I have for this says the layout is this: # is the digit affected. Left Base: x#xx Left Top: #xxx Right Base: xx#x Right Top: xxx# Ours was wrong (even by the above), so I've corrected it to match.
  10. @kmax59 You should find it behaves far better in Does this appear correct? https://gyazo.com/d020254dea42cd61992279be93542e0f
  11. We put nearly in full time work, 5 days a week, for almost two years after the product was released. We also did not charge for the P3Dv4 version (which required work) or any of the work we've done since (it was a lot). So, although I understand your frustration, please keep that in mind. As big of a deal as this may seem to you, it is, overall, a smaller issue to resolve, technically, hence the slowness. We are also working on a decent size update (aimed for release this month), you can track its progress here: .I've added this to the list of items that must be fixed before can come out.
  12. @Slod My apologies for the silence. I've got this on my list of things to take care of in the upcoming week.
  13. This has been an ongoing discussion for a bit - our reference has provided inconclusive results. Traditionally, a "radial" is true, not magnetic, hence our code displaying it that way.
  14. Apologies for the late answer! This is resolved now and should behave as expected in the next version.
  15. The TrueGlass shader is somewhat hard to read, but one way you could do it would be to edit the v.p and/or v.t coordinates in the GS function. Although it's not the easiest solution, applying a transformation to the vertex data before triStream.append(v) call could rotate it. Here is a stack overflow post that explains it better: https://stackoverflow.com/questions/28124548/rotate-quad-made-in-geometry-shader
  16. We should be able to improve this now. There have been additions to the SDK for SLI related usage. We will review it more thoroughly in the upcoming days.
  17. Prince, First off, thank you for taking the time to investigate all possible support avenues. I do sincerely apologize for the delay, and to be quite honest, I don't know why or how your request sat for so long. I have personally reviewed and resolved your ticket. I've replied there as well with more information directly regarding the request for privacy. Thank you very much for your patience and support. If you ever need anything, feel free to message me here.
  18. I apologize for the delay here - I will review/fix this for the update.
  19. I'm glad we were able to get something sorted for you!
  20. @richcam427 It's currently on hold, but not dead.
  21. @jetfish Can you try setting your FPS limit to 60 in P3D to see if it improves? Also, are you using SLI graphics cards?
  22. @jetfish Ah! I've got this on the list - we'll have a pretty comprehensive post V1.1 patch at some point in the relatively near future, I'll do my best to throw this in there.
  23. Currently, these parameters aren't an option.
  24. We'll get this reviewed/looked into.