Cristiano Mueller

Hi Bob; I don't know if what he is doing is right or not. But, there is a channel at YT (https://www.youtube.com/user/My737Channel/featured) from a 737 pilot. I wrote to him some months ago, asking about the 737 startup. This is what he wrote in reply about the hyd pump: "Regarding the hyd pumps, 1 and 4 (ENG1 and ENG2) remain on at all times (to prolong solenoid life). 2 and 3 (ELEC2 and ELEC1) are turned on before the engines start, and off after the engines shutdown." So, I'm using this procedure since then. I hope I could help.

Same here, using FSX. When starting from cold and dark, you need to close and then open the front door again, to GSX recognize it as opened.

Beautiful words, Mr. Randazzo. Rest in peace, Tom.

Kyle; I know this is no joke (finally!!!!)... LOL Maybe my google translate has not translated in the most effective way. What I mean is that maybe the weather radar is only to divert attention to "something else" that is appearing in the picture.

It isn't the weather radar. The weather radar is just a gimmick. But what could it be? Anyway, thank you very much for sharing, Kyle. Looking foward.

Hi guys. Let me ask one thing. I have the 777-200 sp1c version. My next step will be to buy the -300 expansion. So, it will be the sp1c of the base package with the sp1d of the expansion, right? It will work? Or prior to install the expansion I will have to install the sp1d of the base package too? Best regards Cristiano Mueller

Hi Aaron; are you using some weather addon? There is a Tab's post here in the forum (which unfortunately I can not find) talking about the weather injection and possible differences in internal and external pressure of the aircraft, causing the doors do not open. This may seem strange, but a friend of mine had this problem with the 777. He began the flight loading a REX Theme in FSX. No door opened. When he carried a default weather, everything went back to work. I hope to have helped.

Hi Richard you can find one here: http://library.avsim.net/download.php?DLID=178453 Cheers.

I must say that this has solved my problems. RC4 ATIS and ASN ATIS now have the same values.

Hi guys; I'm with Ray. Moreover, taking into account that in real life is the air control who has the responsibility to guide you through the airspace, no matter what FMC tells to you. So, if RC tells me "down!!", I obey.

Hi Adi I will try this tonight, but this seems to be more a NGX problem than a SweetFX problem. Perhaps due to the way the cockpit is designed or coded, I don't know. Because with other "heavy" aircraft (PMDG MD-11, Airbus Aerosoft) this doesn't occur. I found this topic, and this topic and saw that not just me is suffering from it. Another thing that I want to test is to run FSX in fullscreen and windowed mode. Maybe that makes a difference (But flying in window mode will be disappointing. I always flew in fullscreen). After the results, I come back here to inform. Cheers mate.

Hello let me make a correction: for some reason, my FSX acted strangely when the first test. Yesterday I repeated the test, deleting all entries of the cameras in the aircraft.cfg, and leaving only the entry of Ezdok. Well, the virtual cockpit remains normal (I don't know why the 2D panel appeared the first time). Finally, the virtual cockpit is not altered by the deletion of the cameras. However, the transitions between the Ezdok views continue with that flash, as seen in the video I posted. This is all I can say for now. I'll be testing a few more things to see if I can get a satisfactory result. Thanks for your help.

Hi; Aircraft.cfg has 15 camera definitions, 14 by PMDG and 1 by Ezdok. What I did: I deleted the 14 entries and I just left the Ezdok entry. What happened? In the virtual cockpit, all side views, up, down, everything was normal. But when I looked straight forward (the position to fly) what appeared was the 2D panel. In the video of the previous post, I left the First Officer camera entry in the configuration, and deleted the remaining 13 from PMDG. The virtual cockpit was nomal, but flashes returned. What I mean by no virtual cockpit is the following: look at my video, in all the planes I have pre-defined positions in ezdok. When I delete the entries, the views remain the same. But imagine when I'll look ahead the virtual cockpit disappears and 2D panel appears. When I look to left, or right, or up, any direction, I'm "inside the virtual cockpit" again. I hope I have made myself clear. In Portuguese it would be much easier. Thank you for your attention

Tested. And unfortunately it did not work. And I can not delete all cameras definitions in aircraft.cfg and leave only ezdok definitions, because otherwise I lose the front view of the virtual cockpit. The side views are normal, but when I look forward, the 2D panel appears. But you were right: when I deleted all camera settings, there was no problem in the view changes. But I did not have a front view of the virtual cockpit, only the 2D panel. So I left only the First Officer's camera setting, to not have problems displaying the virtual cockpit. But still the problem persists. I made a very short video showing how this happens in the NGX and other aircraft. Any help will be appreciated. Thank you very much.

You're fast, man!!!! Thank you for the suggestion. I will give it a try tonight and then I post the results. Thank you again. By the way, your simtweak page is very good!

Hi guys; First of all, congratulations on the idea of making a support for SweetFX. I've tried to use SweetFX several times, but always end up bumping into the same problem. I fly a lot with the NGX, and I use Ezdok for the views. What happens is that when I switch from one view to another, the screen blinks. It's like the SweetFX shuts down and turns on again at each change of view. And this only happens with the NGX. In any other aircraft that I use, it will not appear. Is there a way to fix it? The FSX is from "another world" using SweetFX, but this flashing screen makes me upset. Here are my specs: 1. Windows 7 2. FSX DX9 3. nVidia 650 GTX Ti Boost 2GB 4. I'm using nVidia Inspector according to Tab's (PMDG) post. Sorry for my English, it is not my first language.

Hi Stephen; The advice about adjusting the wind direction before loading the flight works like a charm. No more problems on departure and neither on approach. Thank you very much.

Stephen, I don't know if you saw my edited post. I think you were answering while I were editing, but there is something I can do about that? This has been very common in my approaches. Or for example, on my last flight, bound for SBPA (runways 10-28), the wind direction was 300, or something similar, and yet Radar Contact instructed me to land on 10. I kept thinking "runway 10 has ILS, the 28 does not have." Perhaps this is why the approach was guided in this way. But there would be a problem of Radar Contact, and not of Opus, right? Opus pointed me the correct wind during approach, but some takeoffs of AI traffic were made on runway 10. And I had to ask for approach and landing at 28.

Stephen; Reading again what you wrote, I believe that the NOAA's site is the more reliant and easiest way to do the "wind injection". I will do some flights tomorrow (here in Brazil is World Cup time, but I don't like football) and I see what I will get. The "startup weather injection" for me is solved. No doubts. But in the destination airport, the weather/wind direction will solve automatically?

Hi Stephen; Ok, now I understood. What I mentioned about "misinterpretation the weather" was just the fact that I may eventually use a different source than the Opus uses. For example, a site that had a longer update than the Opus source. I do not know if I made ​​myself clear right. About "real weather - static" I thought I could just select it to download the current weather conditions, and then Opus overwrites with its data. Anyway, my question was solved. Now, it's time to fly and test. Thank you very much. Edit: Stephen, sorry, just one more question: and the runway changes on approach, can I do something about that? Sometimes I'm approaching, and the App says "expect approach runway x"... then I do the set up of the ILS course/frequency and seconds after, he says "expect approach runway y"

So I would have to check the "user-defined weather" option and manually put the wind direction? And this wind direction, I would find within the Opus program? Or I could find another way? Because my fear is putting the wrong wind direction, depending on my source/Opus source. I do not know, but for me the "real world weather (static)" option seems to be more reliable. Because, theoretically, eliminate the likelihood of me to mistake the interpretation of weather.

Hi guys; I'm a little confused about which procedure to follow, so I would like your help. I was on the Radar Contatc 4 forum discussing about traffic patterns, especially the problem of "wrong direction" traffic in departures and approaches. I use RC4, Opus and World of AI in my flights, so I was trying to understand what I did wrong to make this happen. Then, seeing the FAQ page of you, I found this: Weather keeps changing erratically Ensure you don't have any other software packages injecting the weather and disable the FSUIPC weather options (registered version). In FSX Free Flight, Weather, set your FSX Current Weather to any weather theme, just don't enable the real world weather options. Check that no other weather engines are running. If flying online don't inject weather from FSInn etc. On your "getting started" page, I found this: Ensuring AI Traffic uses the Correct RunwayTo ensure your AI traffic uses the correct runway you can do one of two things, 1. Check the current wind and specify that wind manually within FSX before loading the flight. It doesn't matter about any other weather parameters since Opus will update it, but it will allow you to stipulate what the wind is going to be (matching the RW) BEFORE the flight is loaded. 2. Simply select RW Weather in the FSX Weather settings, update the FSX weather and ensure at least the correct wind has been injected. This requires that your point of departure is a met station and has a valid METAR in the now almost defunct Jeppesen database. Again this will set the wind BEFORE the flight is even loaded. Now you can take your time, process your flight plan, specify your intended destination and cruise altitude and finally instruct Opus to generate and load the weather. The Opus LWE will automatically put the sim back into custom weather mode. Using this simple procedure will always ensure your AI traffic start out using the correct runway. So, let me see if I understood this: As I am using AI traffic, should I select "real world weather (static)" and leave it there, correct? The "wather themes" mentioned in the FAQ page does not apply here, right? Or I'm doing a damn mess?

Guys; just to add, I found this here (http://www.opussoftware.co.uk/opusfsi/opusfsx_getting_started2.htm) "Set your FSX Current Weather to any weather theme, just don't enable the real world weather options unless you are using AI aircraft. If you are using AI aircraft then select RW Weather in the FSX Weather settings, update the FSX weather and ensure at least the correct wind has been injected. This requires that your point of departure is a met station and has a valid METAR in the Jeppesen database. This procedure will set the wind BEFORE the flight is even loaded. Now you can take your time, process your flight plan, specify your intended destination and cruise altitude and finally instruct Opus to generate and load the weather. The Opus LWE will automatically put the sim back into custom weather mode. Using this simple procedure will always ensure your AI traffic start out using the correct runway." I will visit the Opus Forum. Any news, I report back.

Hi Ron; thanks for your reply. I will have to check my FSUIPC settings. My default flight is "the default" (trike at Friday Harbor). About the FSX weather options, I always set the last option "user..." (I'm not in front of the PC right now, I can't remember correctly) but it's the last one, and then I run Opus. And dynamic weather is always off. Maybe I have to choose "Clear Skies" as you sad. Well, my wife will kill me tonight, but I will need to do some tests.... Thank you once again.

Hi guys; I'm having this "problem" too, but it does not bother me that much. But taking advantage of this topic is open, let me relate what I've been watching. First of all, I must say I use Opus Weather. And these changes of runways are quite frequent for me, both on takeoff and on approach. Let's take the example of a flight I made a few months ago, from VIDP. The control guided me for takeoff on runway 29, as seen in this passage: Once reaching on runway 29, the takeoff was cleared. Note that when turning on the TCAS, there is another aircraft approaching in the opposite direction: Shortly after takeoff, note that the TCAS alarm sounding: So I'm trying to find a solution for this. I do not believe the problem is in RC, quite the contrary. To my understanding, the weather addon is leaving the RC "clueless". I may have to disable updates earlier in the approach. But there is still the change in takeoff. And just for the record, it takes me around half an hour between starting the simulator/weather/RC, do all the procedures for loading baggage / passenger; only then to ask for permission to takeoff. But anyway, I say again: I'm not complaining about it, I'm just trying to bring to you what I've been experiencing, to see if we come to a common denominator. Forgive me for my English, Google Translate does not always do the job.