geckuz

I am absolutely sure, I have a good computer knowledge. Computer is entirely stuck, hard reset in necessary. After a complete fsx reinstallation, dust removal, and video card change the problem still persists, only with the T7, I think I will park it in the hangar waitingo to buy a better pc.

Unfortunately it isn't the 8 10 minutes freeze. The entire PC gets stuck.

PC isn't overheating, already checked. I am not willing to remove all addons at the moment. Fsx is freshly reinstalled after a reformat. BTW they are mainly airports, and active sky next. Nothing more than that.

Hi all, every single time I fly the 777, at a certain point of the flight (sometimes minutes, sometimes hours), the computer freezes and sound in the background loops. Only way to recover is resetting the computer via reset button. This problem happens only when flying the PMDG 777, and got worse after the last update. Previosly it was happening less frequently. As of now, I cannot complete a flight. Video and audio driver are updated, and I already tried using the 22k soundset. Any suggestions? Regards Stefano Rossi

I don't think the "5-10 minutes FSX freeze" is 777 related. It happens to me with the 320 from aerosoft, And NOT with The T7. If you google "fsx freeze" there are posts of about 2-3 years ago about this matter. In this post http://forum.avsim.net/topic/432945-fsx-asn-8-minutes-freeze/ It happens with ASN. Someone is suggesting the culprit is a corrupted realtek onboard driver. Just my 2 cents Regards Stefano

Hi I noticed that it works correctly if you use the option with cart not visible. If you use the option with the cart visible it doesn't disconnect properly. Regards, Stefano

Hi Bryan, I do confirm I selected packs OFF in the t/o briefing, but after announcing "cabina crew seats for departure" ne turned OFF only pack #2. I'll do another FLIGHT tomorrow and see if I get the same result

Hi Bryan, first of all congrats for delivering us another first class product!! I have a small problem on takeoff: looks like the first officer is only able to switch off pack numer 2 and not number one (i shut it down manually), and the same happens during climb (only pack 2 is reactivated), had to activate number one manually. Am I missing something/doing something wrong here? P.S. The voice command - SET PACK ( ONE /TWO) TO ( ON / OFF ) works normally For the Probe/Window heat: when the light is estinguished, it is already in the Auto Position, it is switched on only in case of a malfunction, so it is not necessary to have it in the f/o flow. Regards, Stefano

Thank you Bryan, for sure I will make a backup first! :) So with these changes there should be no problems with the new service packs? Is it only for the Pro version or also for the Maddog2008 standard?

can you tell us which strings are to beinsterted in the .cfg in the menatime Bryan? Thanks! ;)

You're welcome Bryan :), glad to have helped ;)

I believe default bank angle is 25

There's an option that can be set in the maddog load manager (I don't remember the name.) when it is checked, the transponder work with the aircraft GSCM. So even if you set it to TA/RA IVAP's transponder will stay in standby until the aircraft in airborne, and it will go in standby as soon as the main gear touches on landing. This is also how it works in real life, mode S gets active only when airborne. Unticking that option causes the IVAP transponder to be linked only to the switch position in the panel (if you set TA/RA in the panel, it will also activate IVAP's transponder). In either case I believe you have to thick the option Read/write panel/cockpit offsets in the IVAP configuration. So please Bryan, do not add an option, since it could mess up with these things.Here's the link to a post on the Leonardo forum:http://www.flythemaddog.com/forum/index.ph...ransponder+IVAP

Hi guys, Hi Bryan,Windows XP Speech engine is indeed far more limitating than the windows 7's one. I moved my fs installation to win7, reinstalled fs2crew, and now all the speech commands that create difficulties under winxp are perfectly recognized (set speed set heading and so on). Making a manual approach commanding for speeds and vertical speeds was indeed a wonderful and realistic experience ;)

They are also not recognized... If it is a spelling proble, have you guys any suggestion for me?

Yes, absolutely. set course produces nothing also, with the flight level I get different results (E.G: once I said 240 ant it was set to 4000, another time it was set to 2400), never tried with "Altitude"... I noticed launching the Reco tool of the speech engine, that "to" and "two" are very often confused, even if I use an almost right pronunciation.These are the words (one per line) that for now I have inserted and spelled a few times as per FAQ procedure:select, set , speed, arm, auto, heading, alpha, bravo, one ,two, three, four, five, six, seven, eight, nine, zero, flight ,level, transition,now, line, gear, up,retract, flaps, slats, landingquite all of them work well now ( I had an hard time with "auto" at the beginning :( )

no, it is not visible in the green bar :(... any suggestions?

Hello Brian,first of all, great job! The best addon for the best aircraft ;)I have some problems with the "set speed" and "set heading" commands. E.G. if I want to tell the copilot to set a speed for me, first of all I issue the "Engage speed select" command without any problem. Then I say "Set Speed two two zero", but nothing happens. Same for heading. I've already trained the voice recognition with the procedure explained in the FAQs, but nothing changed for this command.A Request: Is it possible to add a Flight directors off command? Would be a nice addition for visual approaches ;)Another thing, when I exit flight simulator, I receive a GDI+ error ( Memory could not be written).RegardsStefano Rossi

You cannot disconnect the autothrottle by moving the throttles, you have to use the instinctive A/T disconnect buttons, located on the side of throttle 1 and throttle 3, or use the default FS key to disengage autothrottle (SHIFT+R)

This is just because the speed you selected is below the minimum speed for your flap/slat setting, MD-11 will never allow you to decelerate to a speed that is under manouvering speed for the selected flap setting. Increase your flap and you will reach 200kts.... I suggest you to read the manuals if you want to fly this bird, even if you just want to fly around....RegardsStefano

Do you use active sky? Could be wake turbulence simulation....Stefano

Peter, this is stated in the "PMDG Ops" of the website:"Panel window limitThe MD-11 uses a very advanced and unique system to deliver such high fidelity cockpit lighting and panel view options. FS has a 64 window limit for panels and by default the MD-11 uses up 61 of them. This means that you have to be aware of this and can only attempt to use a maximum of 3 other panel windows associated with other addons. This includes things like FS2Crew, the Active Sky radar gauge, ProFlight 2000 Emulator, and anything else that installs itself as a panel window.If you go over this limit you will lose MD-11 panel functionality and begin seeing problems with the panel lighting. If you are having issues with the panel, especially in the VC, first ensure that you are not trying to use more than 64 panel windows."Link:http://ops.precisionmanuals.com/wiki/PMDG_...AQ#Cabin_LightsRegardsStefano Rossi

Ok i'll try to answer to what I know :( Picture 1:Situation1: This is the normal behaviuor.Situation2. In this specific case you have an altitude constraint of 11000ft that will be cancelled once you pass the waypoint with that constraint. Vert Alert is advising the crew of an altitude change in profile mode, so that if the crew wants, can override this ( Perhaps you selected a lower altitude and the you put the knob back to 11000ft, or did you just reach 11000ft at the moment you took the shot?)Picture 2:Yes that is correct, if the aircraft has speed control (three dashes in the speed readout), it will select the best speed for the given flap setting.Picture 3:Same as picture 1 : there you have in the FMS an altitude constraint of 2200 feet, and you just passed 3200 feet. Even though you selected 1500ft in the altitude selector, the plane will go for 2200ft to meet the constraint, unless you clear it via the FMS or you fly over the waypoint for which the altitude constraint is set. 1000ft before reaching the altitude there is an aural warning in the MD11 saying "Altitude" and the triangle will briefly flash in amber.Picture 4:If you compare the picture with picture number 3 you can see that in pc 4 you have the radar altitude box showing 20ft, in picture 3 there is not.100FT should be the QNH altitude... as you can see you are about at 20FT RA and the altimeter is showing about 100ft.For the ILS: ILS is composed at leat of a LOC+GS. To have DME you have to tune a VOR on NAV2, you can check that on the approach plate, usually you find XXX DME required. There is also the ILS/DME that provides also distance measurement.RegardsStefano

But I took it as a joke, and I am joking too Alvega, no offense at all :(.. Furhermore my sarcasm was for those who stated that people with few posts couldn't have an opinion :( :(Stefano

LOL you're right =) ..... and I guess that 10 years of flight simming and a Microsoft certification in system administration don't count either :( Ok then, I will write one thousand posts with just 1 smiley each, and then post again here :(Stefano