ESGG

Thanks, pretty much new things to learn about Linda, but seems to be very usefull.

Hi! Just moved to P3D and got the PMDG B737NGX. Was trying to set up my VR Insight MCP Combo with the help of LINDA. Think I got it to work now, and understand how I can change assignment for buttons etc. But what about the display window? Now i have some text about "FL" with "00" below and "APU" with "0C" below. I just want the MCP to look like the "old" display when I didn't used Linda. Regards Johnny

Hi! I also use W10 and had no problems at all after my upgrade. Are you using multiple monitors? In that case make sure the one where the RC-window is displayed in are active (click somewhere inside that window before trying to make a call). Regards Johnny

Do you use the FMS Data Manager or Manual Install? Suggest you make a Manual Install and make sure the installer points to the correct folder where the PMDG Navdata is stored. Regards Johnny

Just a quick-check you can do, is RC responding to anything else? If you try to press 1 to request a higher altitude or 9+1 direct to? And if you use more then 1 monitor, are you sure your main screen is where you have been pointing with the mouse last time (just press it on any empty spot in that screen). An other thing you can do is to give the radio to "Otto" and see if everything works as planned in that case (ctrl+shift+k by default). I normally give the radios to Otto when ready for taxi and then let him do the radios until parking after landing. Since you, as the pilot flying, would normally not working the radios irl that is probably the most realistic way to use RC. Regards Johnny

Hi! Can confirm I also have had this issue once, after a clean install of FSX and latest version of ASN. I just ignored the instruction to turn, and not long time there after RC was giving me a heading towards the field and transfered me to APP. But have made a couple of flights after that, also to the same airport, and having no problem, so really have no clue what was causing this. The only thing that was a little special at that time was that the actual QNH was very low, around 970 mbrs. By the way, the "unable" option is only there when you flying props I think. Regards Johnny

I'm using Night Enviroment for Sweden together with ORBX FTX Global and I must say it improves the nightlfeeling a lot. You will be able to see citylights more distant away and from higher altitudes. Regards Johnny

As Norman suggest, use the AS ATIS instead. Load your flightplan in to AS and then you listen on 122.02 or if you have the X-gauge installed check Destination Weather. Im not sure why RC dont seems to be able to read the weather correct, but that should not be a problem if you follow the advices above. Regards Johnny

I ve noticed that the after take-off checklist seems to be a "dummie" or? What happened was that I forgot to call for "gear-up" after "postive climb". After a while I was wondering why the ac was climbing so slowly and noticed the gear was still down. Obviously there is actually no check of the position of the gear when the co-pilot silently perofrming the after take-off checklist. Is this a bug or supposed to be like this? Regards Johnny

Well, now I get a little confused. My understanding was that many is using RC with P3DV2. I know there was a bug in P3DV2 making it impossible to save flightplans with the default flightplanner. Not sure if that had something to do with the problems before. I never save and restoring flights with RC if that is still a problem. I always make my flightplans with FlightsimCommander and just export them to the folder where RC picks them up I think and the run it (FSX). Regards Johnny

Hi! I'm thinking of moving on to P3D, since there is an advanced aircraft (Majestic Dash 8-400Q) together with FS2Crew now offically is working in P3D. The only thing missing then is RC. I have been trying to figure out how to have it installed but still a little bit confused. I have RC and FSX installed and working on the same computer as I will use for P3D. Do I have to have a separate installation of RC for P3D? I still want to have the possibilty to use it with FSX. Would be nice to have a simple step-by-step-gudie on how to intall it in to P3D. Regards Johnny

Well, if u using ASN and set up a flightplan within it, why dont just use it for the weather? 122.00 will give you departure weather and 122.02 the arrivals (at any distance I think). When you have the wind it will not be to hard to figured out the the most probable runway in use. By the way, your co-pilot in FS2Crew will set the transpondercode for you if you ask him to do so. Regards Johnny

Are you using more then one monitor? If so, if you must make sure the monitor where RC-window is displayed is active. Just click anywhere on that monitor and then RC will capture your keystrokes again. Regards Johnny

I moved up from a 27" monitor to a 42" LED-TV a couple of months ago and I think it's great. I have it wall mounted as well and is sitting around 1 meter from it (3 feet) and it's working fine. Regards Johnny

Sorry for that, I see that now. Seems to work. Thks Regards Johnny

Hi! I just made a flight using Ver1.2 I don't hear any groundcrew answering with "GO AHEAD" when I call "GROUND FROM COCKPIT". Arriving at the stand after landing, if I call for "PLEASE CONNECT EXTERNAL POWER" there is no answer, but they do connect the GPU and confirm it's connected afterwards. Also, if I make the enginestart with GPU connected, I suppose they would give me clearance to start engine 2 first and then when GPU is disconnected number 1, but they tell me I'm clear to start all engines when I tell them I'm ready for enginestart. The tutorial is not very clear on this, so perhaps that is not how the procedure should be, or it's not fully supported. Regards Johnny

Do not include the waypoints in the SID in the flightplan you use for RC. The first fix should be where you leave the SID and joins your airway or direct route. Then RC will let you do whatever you want until you reach the first waypoint in your flightplan. If that waypoint is more then 30 miles out from your departure airport you have to tell RC in the Controllers tab when you set it up you are going to follow a DP (altitude or no altitude restrictions). Regards Johnny

Make sure your Fsuipc is up to date. When you "ask for weather", is that via the radio-option provided via ASN since you say you get the landing runway? When you load your flightplan in ASN you can take a look at the Briefing-page and make a note of the expected conditions at the departure- and arrivalairport. The weather at the destination may change depending on how long flight you are doing, but the departure weather should normally be closed to what is predicted by ASN-briefingpage when you check the ATIS via RC. As Ron say, RC will probably need a few moments to stabilise, but if you start RC just after you start FS2Crew I suppose it will take almost 30 minutes before you are ready for taxi, and during that time RC should have been able to do that. To make sure ASN is working correct you can check the default ATIS in FSX and compare to what you get from ASN. If that differs there might be a problem with the ASN. If you use add-on sceneries there might be runways closed for take-off and landings that RC is not aware off. If there have been no departures or arrivals when you first contact RC it will only be giving runways depending on the wind. If later there is an AI who is using another runway, RC will change his mind when it's time for you to taxi or start your approach. Make sure to run "makerunways" and rebuild you scenery if you have installed new sceneries. Regards Johnny

As I have understand it RC is not able to vectors for a straight-in. It will always try to turn you for base (90 degrees) and then final (30 degrees). If you approaching the field from the "straight-in direction" this normally have the result that you will be lined up for a very long final (25 miles not unusual). I have also noticed sometimes that when it tells you to turn final you have already passed the extended centerline and will never hit the localiser with the heading provided. On the other hand, it's not unusual for pilots to ask for a straight-in and then set up themselves for a 10 miles final so what I do is to request an IAP in this cases and just proceed direct for the final (I mostly fly the PMDG B737NGX so easy to set up a fix 10 miles out). Regards Johnny

"ON" can be very difficult to get the speechrecogniation to recognise, very often it will be taken as "ARM". In the NGX it's possible to use "SET" which is much more easy for the speechrecognition to handle, as an alternative. Perhaps something to be considered for the DASH.

At Majestic website, under Resources, Tutorials, Detailed Tutorial Flight Regards Johnny

Hi Bryan! Thanks for a quick reply as usual. I think you point me in the right direction with the engines. I never thought this part was important if you didn't use some hardware to control the engines. Now he starts them (even if he put the levers up to MIN), but most importantly not shut down my left engine any more when I call for the "climb below the line". The checklist thing. In Brendans tutorial (from the Majestics website) he says that the descent checklist is called for when passing transition level, which is logical since it's start with the altimeters setting and you pass that at 18 000 in the States. But in Europe you normally getting down to 6000 or 5000 before you pass transition level and set altimeters to local pressure. Off course the whole point is to have the speech recognition to understand as much as possible, but if you get stuck somewhere there is no way to come through. I have tested to use "skip" but I can not get it to work, even if I can see that the system is reading the word correct. FO is not continue with the next item in the checklist. In the NGX you normally have the responses the other way around for many things, like the voltage, PSI etc first and then "set" or "checked" as a separate word. That's making it much easier when you have problems with speech recognition, noise around or other stuff. I just have a feeling that some will think this one will be a bit to complicated to use, especially for us who have another native language then English. Finally, as I said in my first post, I never hear groundcrew say "go ahead", and today I also noticed they don't say anything when I tell them "we are ready for engine start". Not sure what they are suppose to say about that, but I was expecting something like the response you get with the NGX. Since I hear them when they connect and disconnect the ground power it's very weird, and I understand from others posts that some hear them say, at least in parts, "go ahead". Regards Johnny

Hi! First some small "things": When contacting the ground crew "ground from cockpit" they don't answer with "go ahead". But if I ask them to connect or disconnect groundpower they do that and the conversations is working between us. "Skip" is not working when you want to proceed with no action in the checklist. The Descent Checklist is not working very well for us flying outside US, since it starts with the altimeters, and at 10 000 when we are suppose to read it we are still on FL. And a "skip" is not working as I mentioned above. An option to have it "below the line"? Overall I think you get very little support with the altimeters since your co-pilot not monitoring either Transition Altitudes or Transition Levels, couldn't that have been included in the Briefing so he knew (and reminds you) when they are coming? Speeds is also something he don't to know anything about. Having the Vapp or Vref included in the briefing would have been nice, since this plane can loose speed very quickly when all is set up for landing and a second eye would prevent you to getting "slow and low". Just some ideas. For the commands I would say that perhaps it would have been better to take a more "conservative" way then to be 100% realistic. I A S is not the easiest combination of letters, even for native english speakers, at least couldn't we have been using "speed" instead?. The "Climb List thing" is to much, especially at that busy phase of the flight I think. Finally, the engine thing. Perhaps this have something to do with my setup, since no one else reported this problem. When I ask for Climb Checklist below the line ("Props 900, Below the line), the FO is shutting down my no 1. This have happened on every flight and for sure, an engine failure that often is not good for your heart :huh: I have been able to restart it, but then my no 2 have been going to MCP and get stuck there so I will have asymetric trust for the rest of the flight. Perhaps it's mentioned in the manual somewhere how to get rid of that. First I was thinking it was my throttle (I have a second quadrant programmed for the condition levers) but I have tried having it disabled and the problem is still there. Then I decide to let my FO take care of the engines all together. He starts no 2, but pulls the condition lever all the way up to MIN instead of START/FEATHER. When I ask him to start no 1 he confirms and and do the correct things overhead, but the condition lever never moves (and the engine is not coming on line unless I move it). So, any ideas whats going on here? As far as I can see I have no buttons or other controls programmed who can interfere with the condition levers. Thanks anyway for a good product, just a few things that have to be sorted out. Regards Johnny

Have the same problem. Their website is slow also.

If the STAR begins more then 40 nm out from your destination, just make sure to include that waypoints in your flightplan and you will be able to fly the STAR from the beginning. When you are within 40 nm and RC switches you to Approach, you just ask for an IAP approach and you will be able to continue the STAR.