nazethc

Members
  • Content count

    59
  • Joined

  • Last visited

Community Reputation

38 Neutral

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    IVAO
  • Virtual Airlines
    Yes

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. nazethc

    FSL back at it again

    As for the folks looking for anything.....yup we are....they we're caught once, and lo and behold guess what....they we're caught again, and..... It happened with their shenanigans with Aerosoft, it happened with test.exe, it happened with cmdhost.exe, and way back when this certain developer was working on the MD-11 there was a piece of malware that destroyed paying customers FS installs. The company cut ties immediately after that happened. They even knew it was way over the line. Kudos to them! And on top of that, they get caught out there, and their response, Legal Action.......LOL! Coincidence? So yes, we are constantly looking. And are NOT surprised by the results. And we will keep looking.... Fool me once, shame on you; fool me twice, shame on me. Fool me four times.............
  2. nazethc

    FSL back at it again

    I also hope Avsim lets this thread stay up, as this is the second time FSLabs has been caught using "shady" anti-piracy methods.
  3. nazethc

    FSL back at it again

    This sums it up....well said Sir!
  4. nazethc

    FSL back at it again

    It might not be anything nefarious, but installing anything in the main windows directory is a big no-no....especially with no prior knowledge to the user. But it's FSLabs, no surprise at all. Go to /r/flightsim....they have all the info there, and it WONT be deleted.
  5. google Tomato Shade, better and free.
  6. nazethc

    P3D 4.1 CTD near Labrador

    And the one's with the errors have ORBX, Activesky...etc. We're the tests run by Umberto with a vanilla P3D? Or with a similar setup like most of us who have the error? Wasn't really specified in the post. And again, mesh, time zone why only westbound? Surely, if it was the case it would happen eastbound also, since the same files are loaded.
  7. nazethc

    P3D 4.1 CTD near Labrador

    And your conclusion will still be COUATL. But thanks for dismissing everyone else's findings.
  8. nazethc

    P3D 4.1 CTD near Labrador

    Never happened to me eastbound, I've flown eastbound through the same area from the west coast and never had a crash. @Eric yeah dunno why, but some other people in the thread also have to use the "kill" method.
  9. nazethc

    P3D 4.1 CTD near Labrador

    @ F737NG Lol I guess I have to take my own advice. @Eric I have tried the restart, and for me, it does not always work. For me killing couatl is the only option at this point. It's probably in the thread, but do you have Vector installed by any chance? @Boeing... with Eric's info we proved his hypothesis, for some restarting couatl works great, for others a kill in task manager works.
  10. nazethc

    P3D 4.1 CTD near Labrador

    So 20+ pages in, did you actually read any of it? It's COUATL, not time zone fixer which users in the thread have said is not the problem.
  11. nazethc

    P3D 4.1 CTD near Labrador

    That's the hit we have to take when no one wants to step up and fix the problem.
  12. nazethc

    P3D 4.1 CTD near Labrador

    You can use it at departure airport. But once you end it in task manager you will not have ground services at the arrival airport. It sucks, but better than a crash 8 hours into a flight.
  13. nazethc

    P3D 4.1 CTD near Labrador

    It is not a reset, so to speak. Before taking off, go into task manager and end couatl.exe. If you only restart couatl from p3d, you will crash.
  14. nazethc

    P3D 4.1 CTD near Labrador

    FSDT is one of the best payware companies out there. I own every one of their sceneries and GSX, the only problem I ever had was this couatl thing, but like I said, we cant say for sure that couatl is the sole cause of the crash. I was really speaking to the CRJ and Flight1 crap payware I wasted money on, in that last post. I should have made it clearer as it seemed i lumped everyone in together.
  15. nazethc

    P3D 4.1 CTD near Labrador

    Ain't that the truth! Too much work for simple fixes in most of that payware. But exorbitant pricing to mediocre/broken releases is just fine.