Jump to content

Andras Field - Airport

All about the Andras Field Airport


87 topics in this forum

    • 11 replies
    • 3.9k views
    • 3 replies
    • 2.4k views
    • 19 replies
    • 4.9k views
  1. Appropriate Callsigns

    • 6 replies
    • 3.5k views
    • 2 replies
    • 2.7k views
    • 2 replies
    • 2.2k views
    • 2 replies
    • 2.1k views
  2. ATC Event 1 2

    • 30 replies
    • 5.6k views
  3. Flyin Wed 27th

    • 3 replies
    • 2.1k views
    • 11 replies
    • 3.1k views
  4. Themes for events

    • 0 replies
    • 1.6k views
    • 11 replies
    • 2.4k views
    • 21 replies
    • 3.4k views
    • 3 replies
    • 1.7k views
    • 21 replies
    • 3.8k views
  5. Event Ideas

    • 8 replies
    • 1.9k views
  6. Events Forum 1 2

    • 30 replies
    • 6k views
  7. FSWeekend

    • 1 reply
    • 1.6k views
  8. Ramp locations

    • 8 replies
    • 3.7k views
    • 4 replies
    • 1.4k views
    • 13 replies
    • 4.6k views
  9. Big Fly-In tomorrow!

    • 1 reply
    • 1.1k views
  10. Event Picture Page

    • 1 reply
    • 1.1k views
  11. Any fly-ins tomorrow?

    • 11 replies
    • 1.9k views
    • 2 replies
    • 3k views


  • Popular Topics

  • Latest Posts

    • Dear Mr KOK, When you say you are not responsible for "that", true you are not responsible for peoples systems or the differences to your tester's machines and those of the tens of thousands of customers who have not reported the problem.  BUT Your are responsible for the changes to the code in the updated version that have caused the problem.  The fact that only 12 have taken the time and trouble to report the problem to you is not evidence that the problem is more wide spread and more importantly your testers failed to pick this up and this could very well happen next time you do an update and every time thereafter.  Moreover we twelve paid you in good faith like all the other thousands and deserve to have a working product not to be dismissed because we are a tiny minority of your customer base.   Are you not even curious as to why changes you have made might have such tragic consequences for Us?  Would you not like to understand the impact the CRJ has on the main code to avoid making the same mistakes in the future?   Whereas you refuse to acknowledge the issues are with the CRJ code, you must accept that it is this very code that does not work in 100% of installations because of its interaction with the main code and the individual's PC.   Even if you will not accept fault with the code, you must accept that the attitude of you and Aerosoft to solve this even if for only 12 customers is sadly lacking.  Not you or any of your bug report team have even pointed us to the post by Hans Hartmann about how useful a dump file might be in resolving this and offering to help.  At the very least you should have done that, do you not agree. For the benefit of others with this issue even if it only for 11 people, here is the lin to the post.   Maybe Mr Kok, if you had sent that information to us, don't forget according to you, it would only be 12 communications, you would by now have had 12 dump files to analise and just think how good your organisation would look in resolving this issue and making that information available in the readme file for every future customer.   Finally may I offer these thoughts if you do feel inclined to revisit this issue. - The CRJ is quite different to all other aircraft from Asobo and all other 3rd parties. - The CRJ has a unique loading process, which on the first load takes a long time - The crashes that we are experiencing happen when we select the CRJ and it loads for the first time - The crash renders our systems unable to load again, until the CRJ folder is removed - The 'm' files never get created - The CRJ never flies   Even if you cannot recreate the problem it is self-evident that it is this initial running of the CRJ where the problem lies and whatever your software is doing as this time is the culprit for not playing nicely with the other parts of our system, when every other part of MSFS2020 and hundreds of other programs and applications are able to do so.  And you dare to suggest we wipe aqnd reinstall our entire systems simply because you cannot write your software well enough.   Frankly Sir that attitude is not acceptable.  
    • Prepar3D v5.2 was released few days ago.
    • Thanks Bernd. Confirmed bug and already fixed with rev. 26.   Have a nice weekend.
    • Hallo @TrippleJ,   zeige doch einmal die Ordnerstruktur des Patch-Ordners. Dann blickt man bessr durch.    
×
×
  • Create New...