Jump to content

SierraDelta

members
  • Content Count

    50
  • Joined

  • Last visited

Community Reputation

4 Neutral

About SierraDelta

  • Rank
    Flight Student - Airwork

Recent Profile Visitors

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

  1. The TRK toggle button didn't work for me until after turning the Layer button off. After that - no problem, and I can now have both TRK and Layer(s) displayed. I used cut'n'paste from https://pilotweb.nas.faa.gov/common/nat.html exactly like I always did with v1.xx
  2. No, you're right, those are the spot winds at the time, sorry.
  3. Not correct. Here is the EDDF part of the current_wx_snapshot.txt file from earlier today. After the first set of double semicolons the TAF from 091200 to 101800 is included: EDDF::EDDF 091150Z 23017G27KT 9999 -SHRA FEW015 SCT021TCU BKN028 09/04 Q1001 TEMPO SHRA::EDDF 091100Z 0912/1018 24015G25KT 9999 SCT030 TEMPO 0912/0918 26020G35KT SHRA BKN025TCU BECMG 0916/0918 26012KT PROB30 TEMPO 0918/1018 26015G30KT 4000 SHRA BKN020TCU::271,27,6.13/282,40,-0.24/292,43,-3.24/290,44,-14.11/293,41,-29.94/297,38,-43.07/302,42,-48.24/299,48,-46.11/299,49,-46.76
  4. Finn/Shaun, Thanks, don't work overtime on this one
  5. Otto, Not sure what you are saying, but this is definitely a bug in the Airbus X! I am pretty sure that this was a restriction programmed in to the systems at a late stage to save frames ... We will hopefully see this one listed together with many others on the yet-to-be-published list of issues.
  6. Thanks Shaun, Well, please define "it" - or better, get hold of someone that does know! It's been 10 days now ...
  7. There is something amiss in the way that N1 % is displayed in AirbusX. Take a close look when you start the engines and you'll see the following sequence: ... 3.8 3.9 3.1 4.0 4.1 4.2 ... 4.8 4.9 4.1 5.0 5.1 5.2 and so forth. Happpens through the entire range, but is easier to spot during slow changes, also happens when reducing N1. My assumption is of course that the above sequence represents the following progression ... 3.8 3.9 3.10 4.0 4.1 4.2 , but only one decimal is shown. Now, I'll leave it up to others to state whether this is just a display problem or the Airbus FADECs use a revolutionary new numbering system. Note that I'm using the BAW A320 in FSX with SP2, maybe those with FSX + Acceleration are seeing things differently?
  8. Every time you change the altitude you must either push (managed mode) or pull (selected mode) the button in order for the new value to be activated. You can crosscheck on the PFD where the new value should be shown at one on the ends of the altitude tape.
  9. Could be any thread, but this is yet another one completely ignored by Aerosoft Support. If it wasn't for a few enthusiastic forum members (Paul G. and Andydigital spring to mind) there would be no help at all for those that need it. Bit laughable really, when you look at this quote from the FAQ at the top of the forum: Q: Any known issues? A: Of course, there's over 200.000 lines of code. Best to check here. But you know Aerosoft, our internal projects are always serviced very fast. Small things we'll handle in a few hours, larger stuff that might need some testing in a day or so. C'mon Aerosoft, show that you still care for your customers!
  10. I never have FSX crashing when exiting an AirbusX flight. Never.
  11. You answered your question in your first post Looks like the FSG08 is the culprit here.
  12. Bob, This is not aimed at you, but Aerosoft ... Why on earth was 1.21 released with something like this not fixed??? Says a lot about the "quality assurance" department, or maybe the managerial procedures
×
×
  • Create New...