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

PORTUGUES

O fórum para todos os nossos amigos Portugueses e Brasileiros, organizado por J.Pinto & Alejandro Diaz

94 topics in this forum

  1. Pinned topics
    • 20 replies
    • 15997 views
  2. Topics
    • 4 replies
    • 2359 views
    • 21 replies
    • 3139 views
  3. A318/A319

    • 2 replies
    • 1238 views
    • 0 replies
    • 1354 views
  4. A320-321 update

    • 9 replies
    • 4930 views
    • 2 replies
    • 1583 views
  5. acender displayer

    • 1 reply
    • 4857 views
    • 17 replies
    • 5307 views
    • 3 replies
    • 1351 views
    • 1 reply
    • 2862 views
    • 7 replies
    • 1400 views
    • 1 reply
    • 4363 views
  6. AFCAD de Lisboa

    • 1 reply
    • 4650 views
    • 1 reply
    • 1481 views
    • 0 replies
    • 1466 views
    • 1 reply
    • 1160 views
  7. airbus a 318/319 v121

    • 2 replies
    • 1448 views
    • 2 replies
    • 4942 views
    • 12 replies
    • 3313 views
    • 1 reply
    • 1382 views
  8. Airbus X Extended 1 2 3 4

    • 77 replies
    • 19762 views
    • 0 replies
    • 778 views
    • 5 replies
    • 1431 views
    • 2 replies
    • 2498 views
  • Posts

    • This was a real advice, as it solved the issue for the other user. He and you are the only 2 user having such a problem and this is clearly a sign that it is not a bug in the Airbus. Otherwise tons of other users would report this too. So there must be something else going wrong. May be something within your P3D environment is not standard and causes this issue.   I never had to use the mentioned batch file, but there are a lot of hints how to use it. But when talking about "generated files": P3D itself generates files in context with addons. And so for the Airbus. You find them under user/AppData/Roaming/Lockheed Martin/Prepar3D v4/Simobjects. There are several Airbus folders generated by P3D. When you now uninstall the Airbus, you can also manually delete these folders and reinstall the Bus again. Maybe this helps.
    • Hallo Hermann,   in Genua war ich schon nmal mit der149D. Die Piaggio Werke sind direkt am Platz und der freundliche Manager hat mit uns eine Tour durch die Halle gemacht. Wünsche dir eine angenehmen Flug.   Ciao, Rolf
    • Hm... "DeleteGeneratedFiles" is mean, that I have to reinstal/register all my addon sceneries? It that is, I rather say goodbay to the Bus. I wrote in my first post - solution provided by LecLightning56 is not satisfying me. Addon in 1.2.5.0 has a bug - default Raptor causes wrong behaviour of your addon (if I load F16 first - problem is absent). I didn't changed anything in my system / hardware /sim  except new version of AS Airbus Professional 64-bit. Can you give me any real advise?
    • ok Ill check this afternoon - so far since none of my other planes causes problems (Caronando D62 and Phenom P100 along with QW Ba46 and B787 plus FK27) I've neglected it though I miss the Twotter.
    • That's not very strange. I am pretty sure that our bus is the only aircraft on your system that is compiled with the very latest compilers. Those use different parts of standard OS calls. In any case, the issue is not in the add-on (otherwise all customers would see this) but in the OS files.
×
×
  • Create New...