Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

mpetr

Members
  • Joined

  • Last visited

  1. Yes, you've just got yourself an upgrade (don't really know how much it is going to help, though), but that is by no means "the CPU for NGX". Sandy Bridge "K" CPUs are the ones for NGX, ORBX whatever. If you want my opinion, I think the i5 2500K is the best, but there will be others saying the i7 2600K/2700K is the one to get. Anyway, Sandy Bridge has been the CPU for FSX for quite a while and by the looks of it, it will remain so for the next 9 months at least. I will second what was said above, better get your money back if you still can.
  2. Yes, that is exactly the solution I have described in my second post above, except that I improvised myself the power adapter. Thanks.
  3. Found what the problem was with the Saitek Yoke. Daniel, I see that you've already ordered a yoke so this info may not benefit you, but I'm going to post it anyway in case it helps someone, especially since a lot of people that I am aware of have given up using the Saitek Yoke because of the problem I've described above. I'll do my best to explain the solution from what my friend told me (who is a PC hardware technician). Okay, so it seems that the Saitek's connection cord from the computer doesn't have enough voltage to "transmit" the information from the Yoke to the PC. Because of this, the information sent from the yoke to the PC becomes erroneous and this is why the aileron axis drifts to the right thus ruining everything. So the yoke needs an additional 5 Volt/1.5A to make the "information" go from the yoke to the PC freely. Notice that the yoke has a 5V/1.5A power port. In this port you need to plug in a modified PC power supply or whatever else you can find that can "feed" 5 Volts into the yoke. From here on, everything just works perfectly. Even though English is not my primary language, hope I did a pretty good job with this explanation and hopefully it can help somebody who has the same issues. The Saitek Yoke is my favourite now, but I still would not recommend it over the CH unless you have at least some technical knowledge. Regarding the PFC yokes, I would really like to test them one day but so far I have never owned one. Blue Skies!Marius
  4. I just purchased a Saitek Yoke after many years of flying with the trusty CH. From almost all points of view the Saitek is better, but I'm experiencing a HUGE problem that I've read a lot of people are experiencing and I've been unable to find a fix.The problem is that the aileron axis is drifting to the right making straight and level flying impossible. Yes, you can trim the ailerons, but that's not a solution. There are two walk-arounds: unplug and replug the yoke during the session, but the problem will reappear after a certain period of time. The second walk-around is deleting some registry data to have the problem fixed only for it to resurface the next time you boot your computer. As you can see, none of these fixes is permanent and doing this over and over gets pretty old quite fast.If I will ever find a solution to this problem, then the Saitek yoke will be far better than the CH, but until then... CH remains my favourite controller. At this moment, I do not recommend the Saitek Yoke.If anyone can help with this issue, then suggestions are welcome and highly appreciated, of course! (not meaning to highjack the thread as this info may benefit the OP aswell)
  5. Now that's the attitude of a true winner ! However, the real question is... can this kind of attack be prevented in the future?
  6. Happy Birthday Captain Randazzo!
  7. Absolutely great work, PMDG! I think I can already congratulate you on producing another stunning masterpiece that will change the way we look at flightsimming for years to come!
  8. That's all I wanted to hear. Many thanks for the answer Ryan. Keep up the great work! Once again PMDG is revolutionizing the FS world with another outstanding product - and just as about all the people around here - I can't wait for release.
  9. Well, I feel like I'm on the right way now. Reducing the trim setting with 1.0 less than the calculated FMS trim helped a lot. Releasing pressure on the yoke before engaging AUTOFLIGHT also helped. The plane will now maintain a steady 20 degree nose-up pitch as commanded by the F/D after engaging the A/P. Even though the speed still falls steadily a little bit below V2+10 there's no risk to get it into speed protection as the plane lowers its nose. I must say I'm happy with the results. Thank you all for the help!
  10. Markus, just to make sure I understand correctly, so I have to release any pressure on the yoke and then engage AUTOFLIGHT? This makes sense. I'll try a flight tomorrow and I'll let you know the results. Thanks a lot for your suggestion.
  11. Well, I read the tutorial the day the PMDG MD-11 was released and I am an experienced MD-11 flier. It's just the recent 1.2 update when the plane's takeoff performance was changed that I started to notice this behavior. The weights are correctly set up. Just an FYI, if you have an incorrect TOCG set in the MCDU it will give you a message. That is just what I'm thinking to do on my next flight in order to confirm the theory about the FMS wanting an incorrect STAB trim. I'll do this. Thank you all for your suggestions.Maybe my MD-11 installation is corrupt. I recently reinstalled my OS and this is when the problem appeared. I installed the 1.0 version and then directly the 1.2 update. I skipped the 1.1 because it was no longer available on the website and because the 1.2 update replaced the same files as the 1.1 update with newer versions. But still - could the fact that I skipped the 1.1 update be the problem here?In order to duplicate this, is anyone that has installed both the 1.1 and 1.2 updates willing to do a test for me? Just load the plane and send the following info from the Load Manager: 2/3 pax and 50,000 lbs of fuel. Then program the FMC as on a normal flight (complete the F-PLN INIT, WEIGHT INIT, enter your route on the F-PLN page and then enter the details on the TO/APPR page). Then let me know if on the TO/APPR page the FMS wants a 5+ STAB trim. You don't have to complete the flight, just complete the preflight phase and let me know what is the value the FMS wants for the STAB trim.If anyone is willing to "waste" their precious time in order to help me out and do as I said above, I would appreciate it incredibly much.
  12. This has been bugging my head for a while now so I thought I should finally post this. First of all, I usually start my flights with 2/3 pax load and not above 50,000 lbs of fuel, as I don't normally do long hauls. I set the STAB trim to the value indicated on the TO/APPR page, which is around 5.2-5.5 . I engage the ATS and apply full throttle (I don't use any FLEX data but I'm thinking to start using it soon). As the altimeter rises, I retract the gear and follow the FD pitch which usually commands a 17.5 nose up degree pitch. Okay, so I'm holding +17.5 degrees until 400 feet RA, when I engage AUTOFLIGHT and release the pressure on the yoke. This is when the plane starts to rise and hold a 25+ deg pitch up attitude, rapidly losing airspeed to Vmin. The airplane starts to lower the nose, but way too slow (about 1deg/5 seconds) to maintain an airspeed. Not even engaging PROF at 1500 feet RA doesn't make the plane to lower the nose faster. So, how do I get out of this deteriorating situation? - Either the plane reaches the initial level off altitude and the airspeed is rising again - or - the airspeed decreases to Vmin, which is the point the plane will start to lower it's nose like it should be in order to avoid the stall. Then, the rest of the flight goes as planned (normal).The aftermath:I think that the STAB trim is the problem here. Having it set to 5.5 it makes the plane to pitch up so steeply after engaging AUTOFLIGHT and the AP doesn't have the power to lower the STAB trim quickly after takeoff in order to climb normally. But then, why is the FMS wanting a 5.5 STAB trim on takeoff if it knows it will deteriorate the initial climb?I hope I am not the only one having this problem and I also hope a solution can be found soon. If I takeoff manually until the initial level-off altitude, then I have no problems. I apologize in advance for the long write-up as it is a bad habit of mine.
  13. Thanks for the input Ryan. Good to know the J41 flies well. The MD-11 is great but if I do a mistake it's hard to recover (in my case anyway). Thanks again for the input.
  14. Just press "A" when in the Virtual Cockpit to change the view points. I love flying from the VC because it makes for such a realistic experience. Getting used is the only problem, but it's certainly worth the effort!
  15. Robert, that Virtual Cockpit is amazing! At least now I'll have a reason to buy TrackIR (finally!). :( By the way, how friendly is the J41 to be flown manually? I am looking for an aircraft that really is a pleasure to fly, not like the MD-11. Don't get me wrong, the MD-11 is awesome but awful slippery and unforgiving. It makes you to think ahead of it, but do one mistake and you'll get into trouble, especially in crowded airspaces. I really hope the J41 will be a dream to fly, can you please confirm if this is true?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.