!! Windows 7 no longer supported !!

As Microsoft will stop supporting Windows 7 on Jan 20th we will be unable to test any of our
products on that platform. It may work, or it may not, but no guarantees from our side. 

Jump to content

lonewulf47

members
  • Content Count

    262
  • Joined

  • Last visited

Community Reputation

83 Excellent

About lonewulf47

  • Rank
    Gliderpilot

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. +1 I ask myself how many updates are required until you get this right. The grass RWY was closed already when your first version of LSGG was issued. A quick look to AIP Switzerland (yes, indeed, it DOES exist ) will prove that.
  2. My dear Refsmmat69 Let me put one thing straight: nobody is bashing Aerosoft being the worst company on earth. Talking about a product having 1000 features, I would like to tell you a short story. Imagine an Aircraft Designer presenting a wonderfully designed new aircraft, including all the trimmings and goodies every pilot and passenger would dream of. The only disadvantage would be that when it came to design the wings, the designer was lacking resources. He therefore decided to abstain from attaching wings to this wonderful aircraft, thinking that the absence of one single feature would not weight in too much against all the other available gimmicks and goodies. Now try to imagine in what numbers this fantastic aircraft would be sold ! And that's exactly what this thread is all about ! SimBrief has become one of the most used and most universal flight planning tools within a short time. Lacking support for such a tool has nothing to do with what you described with "every requester sees his request of course as the most important one". It is simply a fact that SimBrief as (I said it already) one of the most used flight planning tools is lacking support by NavDataPro. It does not need any reference to something " coming out from the children room upstairs" to understand that this lack of support reduces the low market share of NavDataPro even more. Ok, maybe in your world a market share for a product is the least important thing, but I doubt that this is the way a commercial company would and should think.
  3. If you take this out of the context it indeed may look like kind of a "honest answer". However if you consider the fact that this discussion is going on for more than two years and you still complain about limited resources, then it is definitely a bit doubtful - to say the least. TWO YEARS, not only a few days, but TWO YEARS ! If that does not ring a bell then I must admit that I'm obvioulsy missing a few things within the world of Flight Simulation... There's of course not much more that we as stupid members of the Simmer Community can do than to remind you every day of this important gap to be closed and pray for the day to come where Aerosoft can provide enough resouces to finally fulfill this task...
  4. Sorry, Mathijs, but this is not an acceptable answer. The subject ist not just arisig by now, it is now up for much more than one year, actually for two years already. If you have such "limited resources" that do not allow a solution for something that can be solved within one month, then I must ask myself whether you are in the position to really judge the importance of this whole matter. I'm afraid that you are not! We are talking about one of the most important support requests that has come up in the past months - not just a "spleeny idea" from a few Simmers. It would really be adviseable if you could convince your superiors to give this the importance it deserves !
  5. I am a NavDataPro subscriber from the first moment of its appearance on the market. However I noticed in several cases that NDP is extremely passive in expanding into new fields. I have furthermore never seen the resposible Project Manager to show up in this thread, although he was reminded of missing SimBrief Support more than a yea ago by me personally. I'm not sure what else needs to be done to wake up Aerosoft from its lethargy in that and other respects. The present situation could be a great oppoertunity to increase the rather low market share of NavDataPro in the Navigation Data business, it would however need some real efforts by the responsible people. From what I have learned in the past, I'm not sure what the real culprit is. Maybe people with closer relationship to Aerosoft and its Leaders could increase the intensity of direct wake-up calls ?
  6. Isn't that a somewhat simple answer for quite some time? Your Project Manager has been informed about the requirements long time ago even by me personally), but nothing has happened ever since. As SimBrief has become a widely accepted Planning Utility for the community, it cannot be that Aerosoft's NavDataPro is deliberately kept away from using it within SimBrief. I understand that this is a protective measure for Aerosoft's PFPX, but we are living in a world of diversification, aren't we?
  7. ... and maybe also simMarket? With the latest download from there I still get an error regarding a few SAM objects....
  8. Ebenso erstaunlich ist es, dass sich keiner der zuständigen Entwickler zu diesen Thema meldet ! Es sind immerhin alle 4 ILS-Approaches betroffen und das ist für einen Mega-Airport doch eher schwach ! Eine - noch so kleine - Randnotiz eines Entwicklers dazu wäre definitiv wünschenswert. Es kann ja nicht sein, dass dieser fatale Fehler einfach so unkommentiert bleibt, oder ?? Oskar
  9. Nicht nur auf der ILS 16 - siehe hier : http://forum.aerosoft.com/index.php?/topic/54233-mega-airport-zurich-x-falsche-ils-dme-readings/ Es ist einigermassen erstaunlich, dass sich noch keiner der Entwickler angesprochen fühlt. Es ist immerhin 80% der Radionavigation im Eimer... Oski
  10. Disregard this post here. I have opened it in the German Support Forum. Oskar
  11. Erstaunlicherweise ist es offensichtlich bis jetzt niemandem aufgefallen, dass alle vier ILS-DMEs falsche Distanzangaben liefern. Dies, weil die DME-Stationen fälschlicherweise bei allen vier ILS auf der Localizer-Antenne positioniert wurden, anstatt beim Glideslope-Sender. Dies ergibt je nach Runway Fehler zwischen 1.5 und 2NM. Da sollte ein Patch helfen können. Das DME jeder ILS von LSZH Zürich zeigt NULL am Touchdownpoint (0.2 NM nach dem Threshold). Nachstehend die Profile aller ILS-Anflüge in LSZH: RWY 14: RWY 16: RWY 28: RWY 34: Oskar
  12. Here is some additional information on that subject: See below the 4 profiles for the ILS 14, 16, 28 and 34: RWY 14: RWY 16: RWY 28: RWY 34: Regards Oskar
  13. Uhmm, yes Bruce, I'm definitely sure . LSZH Zurich is my home airport and I've done a few thousand IFR landings here and furthermore I'm working now for a company that produces route-manuals for airlines. I can tell you that all four ILS-DME's are reading ZERO at the touchdown-point (0.2 NM after THR). I have checked the AF2 files and they indeed show all four DME's at the LOC position. Yes, I'm definitely sure about that, don't worry Oskar
  14. Gentlemen, I wonder a bit that nobody has ever noticed a major shortcoming on this airport: ALL ILS-DME distances are WRONG as the DME's are placed at the localizer antenna instead onf the GP antenna. Therefore the DME distance at touchdown DOES NOT read ZERO as it should. All four ILS' are affected by this bug! I didn't check on other airports but I'm afraid that this bug is present on other airports too as it is a common misunderstanding. Oskar
×
×
  • Create New...