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

Emanuel Hagen

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Emanuel Hagen

  1. We would simply not know any way how a scenery could infuence the interiour lights of an aircraft. Also there are thousands of others who flew the PMDG 747 in and out of our Heathrow without reporting the issue. If it was an issue caused by our addon more users should see it. Therefore I'd rather suspect a tweak done to your simulator to take influence here. Tomato would be my first suspect.
  2. Hi, I'd not be aware how an airport could cause the dome light of the 747 to fail in certain angles. Tomato might seem like the more likely source here. Have you tried removing tomato to see if the same happens without it? This sounds like dynamic lighting indeed. It is unfortunatey not as dynamic as we'd like it to be as you can even see in your screenshot since it does not take any walls into account and simply lights everything up that faces the lightbulb. As long as most of the parts of your flightdeck are position "backwards" to the lamp they will not be lit.
  3. It works fine with a manual installation though if I remember that correctly from like a year ago. Correct me if I'm wrong.
  4. Hi Quentin, you'd have to find the texturefile containing the pilots texture and exchange the previous pilot with your picture. I believe in the 32bit version it was located in the Simobjects/Airplanes/AIrbus_Fallback (or similar) folder. That's the place you need to start looking.
  5. Hi Artox, soetwas wird normalerweise gemacht weil die Radien um die herumliegenden Parkpositionen sonst zu Überlappungen führen würden und damit AI Flugzeuge miteinander kollidieren würde. P3D kennt intern nur die Abfrage der Größe der Parkposition und stellt dann entsprechend Flugzeuge auf sie drauf. Wenn sich diese aber überlappen, würden die Flugzeuge kollidieren. Um das zu verhindern müsssen Entwickler dann manchmal zu solchen Tricks greifen und die Größe der Position verkleinern, damit es nicht zu Kollisionen kommt.
  6. Yes, they will work if installed correctly. See the guide in the respective subforum.
  7. Hi Jason, did you put the fuel in on the INIT B page?
  8. Derzeit gibt es kein Upgrade, als die P3Dv4 Editionen veröffentlicht wurden gab es für eine begrenzte Zeit einen Upgradepreis, dieser ist aber ausgelaufen, weshalb es jetzt nurnoch das Upgrade zum Vollpreis gibt.
  9. Hi Claus, ein offizielles deutsches PMDG Forum gibt es nicht. PMDG bietet nur englischen Support. Du kannst natürlich gerne in unserem Forum posten und wir helfen so gut es geht.
  10. The step by step guide explains TOGA LK, basically you pulled the nose up too fast (you should rotate about 2-2.5°/sek which equals one "line" on the ADI per second). Therefore you got too slow and to counteract it the Airbus applied full thrust and locked it. That's TOGA LK in easy words. The manual gives you more details.
  11. Kiesel, freedom of speech does not apply to privat company forums like ours. This forum is part of our marketing and while everyone is welcome to post here everyone will have to respect our rules in here. Your lawyer will (for quite a fee) tell you the same.
  12. Hi Mike, what is your FMA showing in such a situation? The FMA tells you what the Airbus is doing, not the position of the levers. If you for example overrotated and entered TOGA LK mode and the Airbus enters VS mode because you selected the new altitude to late, then you could have created a situation where you will slowly run towards the overspeed. The FMA will tell you exactly what's going on.
  13. The MCDU calculatest the angle resulting of the speed entered for descend using IDLE thrust, taking into account any restrictions in the F-PLN page. If you want to calculate your descend manually make sure to use a sensible distance. Using the direct distance you get from the PROG page is not always the best idea. What we do in my airline is to make modifications to the FPLN without executing/inserting them, that way the computer calculates predicted crossing altitudes. We then enter one of them as a hard altitude in the flightplan after erasing the temporary plan again. This way we get a good usable VNAV path from the FMC while maintaining the whole arrival routing in case ATC needs us to fly the whole procedure. While we descend down we periodically update those estimation based on new info from ATC, etc. Example: Arrival at Hamburg for an ILS23 via the NOLGO23 transition. Assuming there is not a lot of traffic expected at the estimated time of arrival I would enter a direct from DH611 to PISAS and a speed of 185 at PISAS. This gives me about what I expect to get lateron from ATC. The FMC will then predict new altitudes backwards on the arrival. Let's say it would predict NOLGO at FL80. I would then erase the modifications we have just done and afterwards enter NOLGA at FL080 which I then execute/insert. Now the VNAV will bring us down "on profile" for the expected shortcut while we still have the whole transition in the box in case we do not get the shortcut. This is just a general procedure which works at most airports and arrivals. Of course occasionally you will have to fly a longer track which means you'll use up some more fuel because you have been lower, but better you're too low than too high. If you still want to calculate it in your head I use this way: Altitude x 3 + 1NM for each 10kt IAS above 200 +/- 1NM per 10kt head/tailwind. This gets you down quite well. But here again, make sure to calculate with some sensible info. If you're coming in from the wrong side and have to fly around the airport there's no sense using the direct distance from the PROG page (or the FIX INFO page) as you will fly at least another 25NM.
  14. Hi, thanks for the report, I forwarded it to our sales team to be checked out.
  15. Der magnetische Nordpol wandert im Jahr um mehrere hundert Kilometer, damit ändert sich dei magnetic heading. Da die Runwayrichtung in Degrees Magnetic angegeben wird, ändert sich somit die Ausrichtung real langsam, meistens ein Grad alle paar Jahre. Nach vielen Jahren kann das sogar dazu führen, dass sich damit die Runwaynummer ändert, da der neue Runwayheading gerundet zur nächsten Nummer gehören würde (so geschehen zB 2010 in EDLD. Am besten schaut ihr für die aktuellsten Zahlen in die NavDataPro oder Navigraph charts, denn diese sind das aktuellste Material für die Flugsimulation. VATSIM updatet die Karten soweit ich weiß nicht monatlich, sondern nur wenn es größere Änderungen, wie SID Identifyer, etc. gibt. Hier sei allerdings angemerkt, dass diese Zahlen nichtmehr zwangsweise mit dem Simulator übereinstimmen müssen, da dieser nicht immer 100% tagesaktuell ist.
  16. Then you know best that a quick a dirty fix has nothing to do with giving your best
  17. Our aim with the A330 will, just like with the A320, be to simulate the aircraft from the pilots day to day life perspective.
  18. Edit: The new version should now be available to all of you. Please check your shopaccount for: (DD_EPKK-KRAKOW-X_V2_FSX_P3D_FSXSTEAM.exe - 12.11.2018 07:23:00 | 558 MB)
  19. Hi, we never had an automatic takeoff function implemented in any of the FSX versions, neither we have one now. Just like in the real Airbus the pilot will have to rotate himself.
  20. Only the data which is required by LIDO customers is included. In Turkey I doubt any major airport would be removed any time soon (it's still very usable as alternate, emergency diversion, etc.), but in other parts of the world some airports are not included. Santos Dumont is one of those if I'm not mistaken as in South America many airlines fly on Jepp data and those using LIDO are not using Santos Dumont.
  21. Hi Frank, it is available already:
  22. Hi John, sounds like you have a conflicting scenery installed. Anything from ORBX like FTX Vector or an AI traffic addon maybe? Try to disable their files for LGSK and see if that helps.
  23. Hi, 109.55 is the current frequency. We'll have to check with LIDO, it might just be a mistake in their chart. These things sometimes slip in occasionally, even with the best providers.
  • Create New...