pilotguy365

I have never owned a previous version of Active Sky only REX and Weathermaker (which I no longer have) and I still get the perfunctorial stuttering issues

I'm not being mean or caustic in any of this statement, but you could have just run the Xgauge wizard again for the uninstall option. Either way however we are both experiencing the same problem and the same TEMPORARY solution apparently fixes it :) Now, if we could get some developer insight on this perhaps we might derive a permanent fix

I haven't found it. I'm at the same point you are. Mine will actually stop my frames for about 1 second four times in a row at a perfect constant time passage. It happens whenever I'm up at cruise altitude and doesn't really happen on the ground. I just uninstalled Xgauge to fix my problem, but I know there's another way. I can pretty much trace my problem down to the Xgauge moving map. It seems to go into the low FPS mode whenever its updating my position on the map which I have no idea how to fix unless I just don't let it worry about updating position by uninstalling it altogether.Regards,Tony N.

So wait did he fix the problem? How did you fix the problem? I was having the exact same problem. My installation has been shaky thus far. The first installation was giving me constant rapid little wind changes which I think was due to the fact that I still had not unchecked all the weather settings for REX, but anyways I uninstalled everything and then reinstalled and have unchecked all other weather settings but ASA and it works but I had this exact same problem which I found I could fix as long as I don't have Xgauge installed any ideas?Thanks,Tony N.happy holidays!

You can make this message disappear I believe in the fsx.cfg file somewhere in there has to do with messages or whatever if you CTRL+F in the FSX.CFG. However, as you probably know, always make a backup of the cfg before you make any changes. I'm assuming that's what he's done in his sim.Thanks,Tony N.

To everyone in this thread,thanks for your replies even you yourself Yves. I bought FSUIPC4 (albeit hesitantly even though I know it pays off). In order to fix this I simply deleted the joystick (rudder assignments) for left and right toe braking in FSX and reprogrammed them with FSUIPC4 as per Yves' recommendations. I checked the Filter boxes for each after having clicked the set boxes to set each axis for left and right toe brakes. Afterwards I gave the beginning IN value a small leeway as to prevent any spiking from my pedals. My autobrakes work like a champ now and I finally feel at ease. I wish PMDG would look into this problem as I feel that perhaps it could have been solved otherwise, but I suppose this is a quintessential example of the immeasurable value of a user to user FS community here in the PMDG support forums.All help greatly appreciated,Tony N.

OK well I bought it and I checked filter for the brake settings and my autobrakes still do not work anything I'm doing wrong?Tony N.

Yves,Thanks for the tip. I'm still a bit irritated though. I haven't had any PMDG representative say anything to a 20+ response thread about autobrakes and now I figure out that I might have to spend 40 dollars to get it to work. I'm still thoroughly happy with the product overall just a bit let down that I need to pay 40 more dollars for brakes to work. I never had to do that with the 747 or the Level D, but now I HAVE to do that for the MD11? Can someone please confirm this is the ONLY way to fix this problem before I go and spend 40$?Thanks,Tony N.

Alright perhaps the PMDG people can help me with this.I have now run 3 ILS approaches into DFW's 35L. Each with three different variables.1st: ILS Approach into 35L with no controls (no Saitek X52 or pedals) and the autobrakes,spoilers, and reverse all work2nd: " (with Saitek X52 only) and the autobrakes, spoilers, and reverse all work3rd " (with both Saitek and Rudder Pedals) and the spoilers, and reverse work correctly, but the autobrakes fail to initiate HOWEVER THE ABS DISARM/DISC LIGHT FAILS TO SHOW ANY DISCONNECT.I need some input as to why this is. My rudder pedals have dead zones on both the rudder axis and both toe brake axis'. I'm thinking it could be a PMDG MD-11 problem much like the 744X with some preset value the Pedals keep sending to FSX. Any help would be GREATLY APPRECIATED.Thanks,Tony N.

>Just a quick update on my earlier post. I am using a Saitek>yoke and throttlesI'm using Saitek X52 with ProFlight Rudder Pedals. I just did 3 RTO's and 3 Landings using Slew and one time the autobrake rejected a take off. All of the other events had no disconnect of the autobrakes, but no engaging either. One of each of those was performed with controls disabled CTRL+K to no availTony N.

Bill,thanks for your suggestion. I am aware of the foot pedal problem as I have had that before with other aircraft, but since then I have had deadzones on my pedals for a while now as well as the throttle. Another thing is that the ABS light never comes on so I know my pedals arent disconnecting as when i tap the brakes they do. There is something internally wrong with the aircraft or the way it interacts with foot pedals much like when the 744X first appeared.Thanks,Tony N.

Hello everyone,I made a post yesterday about abnormal stopping distances for the MD11, which I have now pinpointed to being an autobrakes problem. My autobrakes do not engage upon touchdown or throttles idle (in case of RTO). I read a thread from Jan 14th about this same issue on the 744X having to do with Pedals and Throttles. Is it possible that the same issue exists on the MD11? If not I am at a loss. keep in mind I'm setting the autobrake and spoiler and all that jazz with no ABS OFF/DISC light whatever it says. It simply does not brake. Any help would be greatly appreciated. I had no problem in the 744X with these same pieces of hardware.Thanks,Tony N.

Sorry for the many posts, but I am now aware that my autobrakes are not working. I have just done three consecutive landings one with only reverse and spoilers. One with RT, spoilers and Auto brakes minimum and one with all of the above but manual braking. My auto brakes are definitely not working. Can anyone help point me in the right direction as to why they might not be working?Thanks,Tony N.

>>>So would you say then that you needed about 6-7k feet >>This is still way too much for a typical MD-11's landing>weight. You should be able to bring her to a complete stop in>not more than 4000-5000 ft. >Touche then I am obviously doing something incorrectly. I have no idea what it is. I just completed a flight from KSDF-KPHL and at PHL landed 9R at flaps 50 @ 148 VREF+5 and upon touchdown within the TDZ immediately began holding F2 with autobrakes Medium *High Decel checked* and what I thought was spoilers deployed as the PMDG native co pilot said so (but on replay they don't deploy?) I know they were armed though and i was able to turn off at U about 3/4 of the available 10,500 and that was only because i used manual braking to make it there i was about 80knots 1 thousand feet short of it so i knew i needed to use some stronger braking. I have no idea if this is good or what.Thanks,Tony N.

>>Will have a look had yesterday a flight EGLL / LEMD and runway>18R>Was a flight with FS2Crew and CATIIIB landing with autobrake>at min set... and with RC4 + ASX...>>We had exit Z10 but could have take a much earlier one but>that one don't exist lol :-)So would you say then that you needed about 6-7k feet (sorry for the feet i know Europeans typically use Meters) of runway from touchdown to exit (around 20 kts)?Thanks,Tony N.

You're totally correct about that. However, I did a visual approach today into DFW I only intercepted the Localizer and then disconnected both autopilot and ATS. I know I landed within tdz at a decent if not slower speed and I still only managed off just short of the 36L threshold and one time within the threshold. Where are you managing to exit? BTW let me know when you finish that scenery until FSDreamTeam finishes KDFW.Thanks,Tony N.

Thanks for the reply Andre,You seem to have good luck with your landings :) where do you manage to usually get off the runway and with what autobrake setting (if any)?Thanks,Tony N.

good lord! I couldn't have put it better. I'm glad someone sees this. I am by no means saying anything is wrong. I am simply imploring whether or not this is correct? I'll have to ask my uncle who's been flying UPS MD-11's for a long time where he ends up exiting the runway or when he disconnects the autobrakes. I've had the 747 come in close to 140 something knots and it manages to slow down to 60-80kts in about 1/3 of the runway letting me exit about 5-7 feet down the runway. The MD however like I said in my original post often makes me disconnect and stand on the brakes to ensure I don't plow through the fence :)

Well maybe I am just crazy haha that's probably what it is for me maybe I feel like I'm running out of runway. Just for reference though it is autobrakes disconnected at 60kts correct? And the standard for autobrakes being medium on low decel and low on high?Thanks,Tony N.

First of all,I want to give thanks to PMDG for a great MD11. On to the potential problem for me though. It's been a long time since I last posted in PMDG's forums as I have never had a problem with any of the products and when I have, I've lurked around for other people having same issues. This time though, I'm just trying to make sure I'm not crazy. Whenever I land the MD11, for instance today at DFW's 18R (which has 11,000 or more feet of runway [should be plenty]) I landed well within the TDZ at or right below my 147 VREF+5 target. Everything deploys correctly. I check that the spoilers are fully deployed the ABS are Medium with the High Deceleration box checked and when reverse thrust is available I hold F2 (although it appears to never get any higher than some odd 50% N1). If I don't disconnect ABs until 60kts I'll tend to be right at the threshold on the other side or like at JFK through the fence. I don't think its my throttle as I have set a deadzone well within any kind of error it has so that it might not stop reverse thrust from deploying. Are most people using manual braking? If I use manual braking I can make it no problem with brakes sitting at 40-50C. The 747X I've never had any landing problems with. No overrunning at all. Any help would be appreciated (as I have a feeling it's Pilot Error in this Case)Thanks,Tony N.

Alrighty,I'm back with a status report. I've changed the keys again just like you said and also just like any other time I've changed the keys. FSX reports the "Num 4 and Num 6" keys as being the keys for Decision Height Increase and Decrease. When I try the arrow keys they don't bank the plane in flight which is a good sign becuase that means they are assigned to the Decision Height. However, I just ran FS2Crew again all the way up to Before Takeoff Checklists and tried taxiing with the tiller and my newly set keys with no result. The tiller just sits there. I've tried clicking on the tiller in hopes that it wasn't active sometimes like the FSX default ATC window gets (I hope that made sense?). I think I'll just totally reinstall FSX and then SP1 follow it up with a reinstall of the 767 with its new Sp1 and then FS2Crew and see how that goes unless y'all have any suggestions :) I'll wait to hear back though before I go screwing anything else up :)Thanks,Tony N.

Ah!I thank you for your quick reply! I tried to remove the assignments and then "assign new key" and that in itself did not warrant any result. Would it be best to change a key and then exit and restart FSX? I've never had a problem with changing keys before. In fact, every time I have ever had to reinstall FSX I've never had any problem with replacing keys for landing gear and auto pilot disconnects and what not. I tried your suggestion and it did not work. I will go and try the arrow keys though. I'll report back shortly.Thanks,Tony N.

Hello everyone,I don't know who to address properly for problems with FS2Crew in this forum and for that I apologize. I would like to state, however, (before I reveal my problem in words) that FS2Crew is the greatest add-on to an add-on. The milieu the FS2Crew program provides is simply unsurpassed and very authentic and I can never find myself bored or rid of it. :) However, in order that I might use the tiller I have recently (30 min ago) tried to assign keys to the Decision Height Increase and Decision Height Decrease to no avail. I assigned Num 4 and Num 6 to each respectively and when I press num 4 or num 6 the only result is that view in the VC turns. I thought perhaps that meant the tiller was only for the 2D panel, but even so when I try num 4 or 6 in the 2D panel it simply looks left and right concordantly. I am at a loss and I've nothing else to look to for help other than the support here in this forum? Any help would be greatly appreciated.Regards,Tony N.

I totally agree on that idea. I think if you approached them the right way, they would compromise some sort of product which would make them more profit.

Roger thatNothing in the 2D Panel either I believe it was aces just deciding that the frames might already be low enough and adding extra effects wouldn't really help. Nevertheless, it would have been a good idea to have that as a checkbox in aircraft realism or something. Looking for a comment from ACES team or someone who knows how to add Windshield Rain Effects to aircraft.Regards,Tony N.