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

admins
  • Content Count

    9641
  • Joined

  • Last visited

  • Days Won

    96

Everything posted by Emanuel Hagen

  1. Do you get any returns (indications on the display) when switching the radar to MAP mode with the aircraft in flight?
  2. Does the MAP mode of the radar work when you are in flight?
  3. Take a look at what SkyForce indicates at the top of the program. It tells you the status of the different options, like weather engine, live synch, etc.
  4. Together with the SkyForce internal weather engine or default weather with just the SkyForce live cloud injection?
  5. I've tried just SkyForce, SkyForce with ASP4 and SkyForce with FSGRW. All went without problem. I understand you are using only SkyForce, right?
  6. Can you recreate this on several flights or was this just a one off situation? I never had problems with our WXR and SkyForce.
  7. And you are sure you actually have rain in your simulator? Keep in mind the radar can only show reflections from rain. If there is no rain there are no returns, regardless of how dramatic a cloud may look.
  8. Hi, I can confirm, our weather radar works with any weather addon. As long as the weather is present in your sim you can be sure you will see it on our radar. Are you sure you turned the brightness of the WX display overlay up? Your WXR settings look correct, so the only real reason here could be that you did not turn the display brightness up. If you encounter this issue again please take a screenshot of the brightness selectors, too.
  9. Let me explain it for you: Looking at the screenshots you can see the aircraft has no vertical mode. So it pitches anywhere. Then take a look at the speed trend vector. The situation you see in the screenshots is a situation where the aircraft trades speed for altitude. The speed trend vector shows around -15kt in the next 10 seconds which is a significant reduction in speed. And that is why he gets the 8000fpm. If he had a vertical mode engaged the aircraft would not do that. It would fly at a constant speed and therefore lower the nose to stop the speed from bleeding off. The rate of climb would then be significantly lower than in the pictures. I can only guesstimate here, but I'd say at least 3000fpm to 4000fpm less. And the then resulting 4000-5000fpm could be as expected for an A319.
  10. Captains, we see a large number of you encountering issues because of incorrect use of the automation. We recommend all of you to take some time and review the golden rules of flying an Airbus. http://www.smartcockpit.com/docs/Golden_Rules.pdf Particularly rule number 5: Know your guidance at all times! Many of you encounter issues with strange climb or descend behavior. In many of these cases these are because of incorrect modes (or in fact no modes selected at all!). Does your Airbus climb at 8000fpm only to reach stall speed? Why does it do so? Is CLB or OP CLB engaged at all? We know there are still some issues in the code which can cause such behaviour, this thread is not meant to deny any bugs. In fact those issues are being looked at. This thread is meant as a reminder for you that you are still in command of the aircraft. Lots of the issues we see reported here could have been prevented by correct piloting technique as advised in the manuals though. Always know your FMA. It is the only way how the aircraft communicates with you. Be able to predict your FMA. What will it show you next? Does it actually do what you expect it to do? In many threads we read comments like "but I set my thrust levers to CL" or "my MCP (call it FCU for starters ) shows the correct lights". That's fine, but what does the FMA say? If you have your thrust levers in CL, but you over-rotated and are now stuck in TOGA LK mode, then it is foreseeable that you will overspeed when you level off (okay, in real life your engines would melt before reaching cruise level.. but we already took this burden off your shoulders). All of you, next time you encounter an "issue" with the Autopilot not doing what you expect it to do: Take a look at the FMA and ask yourself: Is it showing the correct modes? Will those modes which are presently indicated get me where I want to get? If the answer to either of the two question is mmmwah, maybe (in other words: no), then take action. Make the aircraft do what it should do! (And in the meantime Robert will work hard to make it work the way it should for those 30% of you who actually do everything correctly and stil experience issues)
  11. Once Lockheed adds a feature which actually enables you to correct working sunshades which actually have an effect on the light inside the flightdeck (such as shining a yellowish cast over the panels) you can be absolutely sure we will look into this again! Simply pulling up the shades, but without any visual effects, does not seem worth it.
  12. For most people it works fine, it seems Dave is the only one who had this problem during testing. For those who actually have this, does vPilot show you that you have tuned the correct frequency? What happens if you use vPIlots text command to enter a frequency (.com1 122.800 for UNICOM for example), does it work then?
  13. That's normal, VATSIM does not model the frequencies correctly. The whole flightsim world uses the .25kHz spacing, so correct frequencies would be 120.500, 120.525, 120.550 and 120.575. This is all P3D supports. VATSIM simply cuts off the last digit and makes it a zero, even though it would be a five. Nonetheless, all pilot clients are programed to correct for this, so if you tune 120.575 in your aircraft the correct VATSIM frequency of 120.570 will be tuned by your pilot client.
  14. You would normally not set the parking brake on the runway, in fact in my airline that is a big no go which could even fail you a check. When stopping however it is SOP to set the parking brake on the runway.
  15. Hello Lennart, please send us a ticket to support@aerosoft.com and include as many details as you can. Our team in the offices will sort the issue out for you there.
  16. Hi, are you using EZDOK camera? I have seen some issues with EZDOK which can show this kind of behaviour if EZDOK is not updated properly for your simulator version. Check the EZDOK forum for details on this kind of problems if you indeed have EZDOK.
  17. Hi, I can't recreate this on my setup, any EFIS panel switching has no effect here for me. NAV mode constantly follows the route, regardles of the EFIS panel switching as long as proper modes are selected on the FCU and displayed on the FMA. What do your FMAs show in such a situation and could you send us a few screenshots?
  18. Thank you for the report, I forwarded it to the developers to check out. Could very well be a bug.
  19. It works fine over here when in the air, did you maybe select an ECAM page which might overwrite the camera?
  20. Hi, the second picture is okay, while the V speeds, among others, are based on the runway conditions, the Flap retraction speed is based on the manouvering speeds. So what you see there is correct and realistic. For the first picture please tell us your flight plan and the weather conditions during your flight. Also tell us which arrival you used there and if you did any manual changes to it.
  21. Please try it on the tutorial once, we have seen many cases where customers said they proceeded exactly as per the tutorial, but then missed some steps.
  22. If the constraint is not even shown in the F-PLN page then it is no surprise the Airbus does not follow it. Make sure it is in the F-PLN page, otherwise it can't be followed. If it is missing from your AIRAC you have to add it manually.
  23. Make sure CLB is armed before takeoff. This can be accomplished by pushing the ALT knob. If the mode does still not engage after takeoff you might have to press the knob again to engage it. The theory is this one: Whenever the mode is not what you think it should be, or what suits the phase of flight: Change it. That's your responsibility as a pilot. (though of course the correct mode should still engage automatically... that will be looked at).
  24. Hello Frafty, usually you should not need to press the knob again, but of course it depends on which FMA's are currently active. Do you still recall what the FMA was in your situation?
  25. Hi Miles, what was your gross weight and what were the ambient conditions in this situation? Could we also get some screenshots of such situations?
×
×
  • Create New...