SergioPT
Members
-
Joined
-
Last visited
Everything posted by SergioPT
-
I also observe this (kind of like a moiré pattern)and it is a little bit annoying, specially on the MFDs. This also happens to me with the NGX, but the way the displays brightness is controlled in the 737 makes it possible to get rid of the "blueish" background, leaving it totally black, and thus eliminating the problem. Unfortunately, in the 777 you can't do this apparently. If someone comes up with a solution (I tried several AA settings to no avail), it would be very much welcome.
-
So... was it expected or did "we" amaze you? :blink:
-
It looks like the FMC in the T7 is rejecting any waypoint entry in the form of AANNN (two letters + 3 numbers). Just to see if it was a validation issue, I edited the wpnavfix.txt file (navdata fixes) and changed PR634 (unselectable in the T7 fmc) to PRT34. After that change, I could select the "new" PRT34 waypoint both in legs and in the cdu FIX page. I believe this is something that needs to be fixed, although I don't see it mentioned in the issue tracking thread...
-
-
-
Hi Howell, my request was aimed at the OP, since he is the one with a faulty (?) .wx file ^_^
-
Can you post here the contents of the .wx file (the part you copied from AS2012)?
-
Actually, these points are often used in "fly direct" instructions even without a STAR assigned, providing you have RNAV. In low traffic periods, I have witnessed approach controllers instructing aircraft that have just entered / are about to enter the TMA to fly direct to PR634 (these waypoint corresponds to the begining of a "right base" for LPPR rwy35 and traffic often proceed for visual approach after PR634).
-
Thanks for the input, Omar. Let's stick to the PR634 intersection example. It is part of published procedures (see attached AIP capture). Also, it is present in the "wpnavfix.txt" airac file from navigraph (see second attachement). As I said, in the NGX FMC I can enter it either in the FIX page or in the legs as a waypoint. Not so in the T7... It is a somewhat common real life practice (also on IVAO) for the approach controller to direct traffic to one of these intersections, shortning the approach whenever possible. I just want to know (and ideally understand) why the T7 FMC behaves differently from the 737 regarding this.
-
I am unable to select terminal area intersections in the T7, either as a fix or as a direct to waypoint. For example, at Porto (LPPR) I can not select "PRXXX" ( like PR634 or PR633) in the FMC (unless they are present in the installed STAR) like in the 737NGX. I know that the FMCs from these two birds are different, so I wonder if this is correct and, if so, how should I proceed if the approach controller asks me to "fly direct PR634"?
-
I did gave Opus a try about 2 months ago. In the end, I came back to AS2012 (superb product with the SP2). Main reasons were cloud shifts during flight (something that is a real show stopper for me) and very unstable winds on approach, not in accordance with the METAR. I must say that I only fly in Europe (don't know if the weather data for the US is different) and with online realtime weather. I don't know if they overcame these issues in recent updates or even if there was something I could do to avoid them (configuration seemed straight forward to me, but you never know). AS2012 with SP2 is, as far as I am concerned, the best weather engine out there (I have OPUS, REX and AS2012), at least for high flyers using online weather. The work they did with visibility when inside / crossing a cloud layer is just superb, IMHO. Also, no issues with winds, temps or pressure abnormal changes.Thanks a lot Steven and KaiserMitsu. This was driving me crazy :-) . Cheers!Thanks for the reply, Steven. The bell is not related to aircraft power (I always have an active power source - apu or ext - when I shutdown the engines). It seems to be something external and it seems to play from outside the aircraft. I thought that it could be a jetway warning, but it plays even if no jetway is available...Hi, Great product, couldn't fly without fs2crew since I've been exposed to it :-) Quick question: after shutdown, I always get a ringing bell sound, that I believe is fs2crew related... Any way to disable it? Kind regards,"and you are where doing what short of who?" :lol:Hi, See if this thread helps: http://forum.avsim.net/topic/375683-2d-cockpit-view-problem/page__hl__cockpit+viewFrom memory, I believe that if you have PMDG option set to "Heading Select" after take off (as opposed to "Wings Leveled"), Heading select will be automatically selected shortly after take off. If so, maybe FS2Crew is "pressing" Heading select a second time, deactivating it... As I said, this is something that occurred to me as a possibility, but I am not able to test it right now. Maybe something you could have a look.Try dimming the PFD/ND/DU displays brightness a little (via the knobs on the console just below), so that the background is completly black (without any grey/blueish hue). It did the trick for me.forum.avsim.net/topic/348682-fail-op-and-fail-pass-in-ngxsettings/Hi,Have a look at this thread:http://forum.avsim.net/topic/345372-my-new-panel-lighting/Rgds,Affirm. Completely unistalled, installed base package, applied SP1. Just to be clear, I am able to change it in the options menu but when I am programing the FMC during preflight, the TA is set to 18000 ft by default, ignoring my input in the options menu. Of course I can go ahead and up select 4000 ft or whatever I like. It's just the default value that I am unable to change...Since the first release, and even now with SP1, there is no way I am able to set default transition altitude to 4,000ft. Even though I set it in the options menu, whenever I start a new flight and program the FMC, the TA defaults to 18,000ft (I think it was 17,000ft prior SP1). Any hints? Thanks in advance....When you drive right in the middle of two lanes on the highway and feel proud about it.
