Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content

Choobe

Deputy Sheriffs
  • Content Count

    124
  • Joined

  • Last visited

Community Reputation

25 Excellent

About Choobe

  • Rank
    Flight Student - Solo

Recent Profile Visitors

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

  1. hi! Does it still happen with the latest update? If so, please let me know how to reproduce the issue! Also please post the complete Windows error report, including not only the "Faulting module name", but also "Faulting offset" and so on. Thanks.
  2. hi! Are you able to recreate the issue? I can't, and the logs didn't help as the FMGS.log is missing in your archive. It would be created if you have the "Logging=1" in the "FMGS.ini". For now I only could find some problem in my code that could have a relation but not fully sure.
  3. I think I have a clue, just made related changes. Hopefully it won't happen again.
  4. hi guys, I still have no clue on the reason what causes this problem, and the logs contain nothing remarkable. Nobody knows how to recreate the issue? Okay, I'd appreciate if you at least give me the Windows error report after the CTD, like in the example below: Exception code: 0xc0000005Fault offset: 0x016c870fFaulting process id: 0x111cFaulting module path: MiscD2D.dll .
  5. Is anyone still having MCDU freezes with the last update? If so, please let me know in detail what were you doing before that (what kind of report being printed, was it PRINT ALL or just a single print, and so on), and please upload the FMGS.log file after you close the sim. (Make sure the logging is enabled in the FMGS.ini.)
  6. Yes please. Any such viewer, as mentioned above, would open a huge file immediately. Try to copy a portion of text at the beginning. If you can't, just a screenshot of the beginning would also work. Besides, don't forget about the LOG files please (make sure it's enabled).
  7. Thanks for reporting! I really wonder what was logged that much! Normally that file is around 1 Kb only, so probably something went really wrong. Any chance to know the contents of the beginning of the file? Many text viewers can open huge files instantly, without reading the entire contents to the memory. For instance, you can try internal viewers of file managers (press F3 to open), such as FAR or Total Commander. Also many standalone viewers, in case of need. Can you try some?
  8. Ok, I think I got it now. Made related changes. Please retry with the next update!
  9. hi Rich! Thanks for report! I found we're getting a wrong magnetic variation value for certain locations. Seems to be fixed now. Please retry with the next update (not sure on exact date).
  10. hi! That is a known bug from the sim weather, "You have to be close to a certain distance (app. 60 NM) to the destination / alternate airport". So please retry when you close enough. IIRC I got the WX coming when distance was around 90nm. Can't reproduce for now. Could you upload the "FMGS.log" please? (Make sure you have the "Logging=1" in the "FMGS.ini".)
  11. Hola! Thanks for report! What have you clicked just before it happened? If that was the PRINT ALL button, when that issue must be fixed already, will be available with the next update.
  12. Thanks for report! This one should be fixed with the next update!
  13. I think it's available in the latest update, you didn't try yet?
  14. Thanks for report! I'm going to make few changes here. Please retry with the next update.
  15. Guys, as I wrote in that closed topic, as soon as you get this please close the sim and then upload your logfiles: FMGS.log, and MiscD2D.log. (Make sure you have the "Logging=1" in "FMGS.ini".) Besides, those who still experience this issue, do you all have the V4.4? And do you all have it when printing weather, not other reports? I still can't reproduce, and still have no logfiles from you. Anyway, I made few changes that could fix the problem. Please retry with a next update! In case of the problem persists, please upload the logs and answer those questions. Thanks.
×
×
  • Create New...