Jump to content

Choobe

Members
  • Posts

    142
  • Joined

  • Last visited

Everything posted by Choobe

  1. Thanks for the logs! Now we are finally able to reproduce and fix this issue! Glad to say the update is coming soon!
  2. Should be working with the next update.
  3. Thanks again, for the extra info! I think I am finally able to reproduce. A fix is being tested at the moment, will let you know soon!
  4. Thank you for the update! That looks promising, as I retried the offsets recently but couldn't reproduce the CTD. Will retry with new data soon!
  5. Please provide me with more data to reproduce. Last time I tried several times what Emanuel had but had no luck! So maybe your details would be helpful at last! So, if the CTD is recreatable, please describe your steps before that happens. Also include some files: *.flp flight route file, if was used; the files from related "Data" folder (e.g. "<Documents>\Aerosoft\Aerosoft A330 Professional\Data\") (make sure you have "Logging=1" in the related FMGS.ini); and please show me the Windows error report on this CTD. Thanks in advance!
  6. hi Jeff! I found you're using a bit outdated version of the EXE file. Please try the latest version attached, and overwrite the older file in "C:\Users\Jeff\Documents\Prepar3D v5 Add-ons\General\A3XX Connect Pro\" folder. And just in case, please take another attached archive with INI files and overwrite in "C:\Users\Jeff\Documents\Prepar3D v5 Add-ons\Aerosoft A318-A319 Pro V5\Data\" folder. No need of checking the Windows startup folder as you mention, just launch the EXE from the above given path ("C:\Users\Jeff\Documents\Prepar3D v5 Add-ons\General\A3XX Connect Pro\"). And for the purity of the experiment, 1st try the web page on the same PC where you run the P3D. Just click on the green IP address at the bottom right of the Connect app window, and it would open your webbrowser with the related page opened. Please make sure you're launching the app with admin rights; and the proper version is being used ("*_v5.exe" in "..\Prepar3D v5 Add-ons\.." for P3Dv5). And in case of the problem still persists, please zip and upload the "C:\Users\Jeff\Documents\Prepar3D v5 Add-ons\Aerosoft A318-A319 Pro V5\Data\" folder. Thanks. A3XXConnectPro_A318A319_V5.zip IniFiles.zip
  7. Thanks for reporting! I'll let the ND developer know.
  8. hi Jeff! Please clarify: are you using the P3D v4 or v5? I'm confused, because the forum refers to v4, but you mention paths with "v5". Besides, what is the exact filename and the version of the A3XXConnectPro_*.exe file you are launching? (For the file version you can right-click on the file, select Properties, and then Details.) Also could you show me the contents of the "\ProgramData\Lockheed Martin\Prepar3D v5\add-ons.cfg" file? Thanks in advance!
  9. Thanks Michel! It will be fixed with the next update.
  10. thanks for info. And please keep me informed on any news.
  11. Dear Tanatat, In addition to the logfiles, please also save a flight before this happens. And upload here. Thanks.
  12. Thanks for report! A fix will be available with the next update.
  13. Thanks for info and pictures! I have fixed my part, will be available soon.
  14. Thanks for reporting! So, do other modules work well in your end? No problems with a navdatabase, for instance?
  15. Guys, I think the EFB should work with your paths now. Please try the updated build, see the attachment. Just overwrite the old build located in "Panel_Fallback\WebSimGauge" folder of your specific aircraft. But in case of the problem persists, please close the sim and upload the "EFB_Ctrl.log" from the "Data" folder! Next: I wonder do other modules work well in your end? Does this problem takes place with EFB only? Thanks. EFB_Ctrl.dll
  16. Just to let you know, guys: this issue is not forgotten. It has a higher priority, so recently I made related changes in my side. And now we're waiting for another developer's input, it will take hopefully another few days.
  17. Thanks, will have a look! @mopperle Any idea what was the full user name in this case?
  18. 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 .
  19. 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.)
  20. 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.
  21. 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...