Morph

Solved by switching back to dx9 mode

Hi, Started flying my loved MD11F again in GEC colors, sadly there seem to be a problem where the wing light switches behave like a master switch for all the exterior lights (when they are selected on) except for the logo light. I've tried a reinstall but it does not help. Any ideas?

Problem: FSX stops responding when zooming in to ground level at EHAM (Mega Airport X Scenery) on the G1000 Recreate: Park at EHAM spot K11, start up, zoom in. Im crashing when zooming in from the "normal map" to the airport ground chart. I've tried using the latest amd beta driver and the newest one but there is no change. Works fine on every single other airport ive tried this far (different 3rd party and stock fsx scenery).

I completely agree, I also think about this sometimes and realise that we are in fact stuck with something just because its the best thing we can get (right now), and we keep dumping money in it, its really sad to see 3rd party developers having to limit their creations because of the limitations that FSX poses upon them. Imagine if simulation games were as popular as these moba games, then we would have had an insane sim experience I think. P3D is not that impressive at all imo. But when you look at it from an outside perspective, we are the nerds, we have our community, our super tweaked and modded / personalised FSX files, our online vatsim/ivao communities that essentialy are mods for FSX. It's a small niche living on something old but gold, it could be better but at least we have something that works!

How much did HiFI pay you to announce/do this? B)

Amazing, on the second page and still zero indication of what is causing my problems, just TONS of offtopic trash that I hope gets moderated (wake up?). Why flag this as your "official" support forum when all you get is.. nothing? I will repeat this flight without a weather engine active and see if I can recreate it. As for MH370 I did not know this forum was filled with oversensitive people, and because I can't edit the thread start post I can't remove the irrelevant connection that I did that actually has no impact on my in-game FSX problem. Deal with it.

I can't understand anything of what you just wrote or how it's relevant to my post, I'm not trying to guess anything at all about the investigation, if you believe so then you must have read my post completely wrong. If you actually read my posts I've flown this thing countless of hours without any problems. As any flight I do with the PMDG T7 i left the LNAV/VNAN engaged from takeoff and it has always followed the flightplan I have entered until this date, clearly there is a problem dont you think? This day I had a lot of stuff that came up which ment I had to leave it running for hours, with no failures and no corrupt flightplan it should have followed it instead of heading hours off course with the LNAV/VNAV still active like it was on course but doing s turns. I am a consumer and I bought a product which is not doing what it is supposed to do, regardless if I am at the controls or not, period.

I'm using OPUS. Thanks for all the replies, I know from other addons that weather might put the autopilot into severe S-turns, however it would still stay on course (just banking left and right). When I looked at my flight route it had made a very sharp turn south (not according to flightplan) and then kept doing the "S" thing for hours. I've read a lot about the accident, i've even tried to help them find wreckage by looking through more than 5k satellite image tiles, and just as the AF447 incident I am very interested in trying to understand what actually happened that day. Then suddenly when I fly my PMDG 777 (which has worked perfectly fine for the countless hours I've flown it), and out of nowhere it decides to put me on almost exactly the same flight path as the accident aircraft, doing weird S turns all the way. I think that is an extremely rare coincidence. Now enough of that, this topic is not about my "lack of good taste" or MH370, its about the T7 in FSX.

Such sim behaviour? It was just a coincidence, stop crying, what happened was tragic but I think it was pretty insane that I ended up exactly right where MH370 had ended its journey. as for the autopilot it has never happened to me before and ive flown countless of hours both with and without being at the controls. Back on topic: Why did this happen? LNAV/VNAV was active and it was still cruising but miles off course, no sim acceleration was used at all.

I took off from VHHH (heading towards EDDP), climbed to cruise level, disconnected from vatsim and went away from my computer. After 8 hours I come back and i see that my aircraft is making weird S turns and the autopilot is screaming at me. What really surprises me is that it turned left in chineese airspace to a heading of 180 and headed straight down through thailand/malaysia and ended up all the way exactly about where the wreckage from MH370 was found outside perth. Is this a known "feature" / bug?

I took off from VHHH (heading towards EDDP), climbed to cruise level, disconnected from vatsim and went away from my computer. After 8 hours I come back and i see that my aircraft is making weird S turns and the autopilot is screaming at me. What really surprises me is that it turned left in chineese airspace to a heading of 180 and headed straight down through thailand/malaysia and ended up all the way exactly about where the wreckage from MH370 was found outside perth. Is this a known "feature" / bug?

Which is quite absurd since we are in the year 2013 and that "someone" could actually be a single "if" statement in a script checking it automatically. This is unacceptable in my opinion, and it has now gone 4 days without anything. PMDG - 10/10 product experience and quality, but this "customer service" is pretty bad...

Hi, As the title states, I purchased the extended download service for the 747x three days ago and still nothing. I have followed instructions and created a support ticket with my order ID. "EXTENDED DOWNLOAD SERVICE ORDERS: Your purchase has been recorded in your account. In order to receive access to your download, you must open a Re-Download ticket in PMDG's Support Portal:http://support.precisionmanuals.com" So what is the problem? I read that it normally takes up to 24 hours but its been way over 48 hours.

Aaaand scrolling through all the nonsense shitposting, here is finally the answer that I waited for, sad to hear but thank you. As for the other boeing models, IMO I think that the 767 is the one that needs to be done now, since it is by far the most outdated one (we already have a good 757 by QW/CS). The 787 might also be an interesting choice since its very easy to transfer from flying the T7. I think we've reached the point where the FM matters a lot but with a crappy 3d model and texturing makes the whole aircraft obsolete. (I'm talking about the current maddog, it feels old even though the FM is excellent. It needs a PMDG/Majestic refurb. Cheers.

Has PMDG ever considered creating the best FSX maddog? In my opinion it's one of the sweetest aircraft out there flying right now and is a very popular aircraft.Any thoughts?

So.. How's everyone doing?

This is why we can't have nice things.

haha yeah, I wonder when we will start seeing these threads popping up "Just bought new rig nvidia GTX TITAN, low fps!!!" and all the drama that it will cause.

This was not really directed to (your) the most recent discussion in this thread, I've just been skimming through tons of similar threads where I read the same thing all over again and watching people tweak really weird stuff without getting any result. The settings I proposed in my last post were intended to be like a "neutral" starting point in terms of effects vs performance. My computer setup turned out to work great which means I can have that dense autogen scenery slider all the way up, and the cloud distance maxed out, (which I dont use since its useless when using REX because of the fog "DOF" like effect it has.) I also tend to stay away from bloom since it makes my current ENB series config look unrealistic. Those were the only settings that were "mid-low" except for the bloom and lens flare, so I'm not quite sure what you mean by "WAY HIGHER SETTINGS". This game is 7 years old, newer graphic cards wont help imo, a gtx200 series can do the job just as well as the newer 690 series and above, personally I believe that it's all about getting that 4Ghz clock stable.

So many people tweaking so many different settings and parameters outside FSX,it just makes me cringe. I am using TONS of add-on scenery, GEX, UTX, ORBX, about every single aerosoft airport there is, flytampa, you name it, also flying the NGX a lot and I have no issues at all, and here's how I did it: First of all, I dont think it matters if you re-install FSX or remove anything, In fact messing around with registry entries tends to do more harm than good in most cases, just tweak on the go, even if your FSX runs like total crap right now just follow me on this, Start by deleting your fsx.cfg and forget it, clearly its not working properly. Go to your settings and use these parameters to start out with: GRAPHICS TAB: - Resolution (Highest set possible at 32-bit, I run 1920x1080x32) - Framerate UNLIMITED - Anti-Aliasing ON - Anisotropic Filtering SELECTED - Global Texture Resolution Very High - Preview DX10 OFF - Lens Flare OFF - Bloom OFF - Advanced Animations ON AIRCRAFT TAB: Not much to change here, however, I tend to keep "Aircraft casts shadows on itself" OFF, because it looks terrible. (Keep aircrafts casts shadows on ground on! Looks nicer!) SCENERY TAB: This is perhaps the most important tab of them all, the changes here drastically impact FPS. ALL SLIDERS MAXED OUT, EXCEPT THESE: Water Effects: Pull back one notch from max setting Autogen Density: Normal Ground shadows: OFF WEATHER TAB: Cloud draw distance: 0% you can fine tune this later, just leave it at zero for now. Detailed Clouds selected and Cloud coverage density: Maximum TRAFFIC TAB: All at zero, yes 0%, no AI Traffic for your poor CPU. This can be increased later, the key of this "guide" is to start small. Now hit OK and shut down FSX. Great! You've come this far, before we start up FSX, make sure you are running your DEFAULT settings on your nvidia/catalyst control center, also disable all forms of forced settings (like AA), if you are running more than one card please disable the SLI/CROSSFIRE now. OK, now fire up FSX load up a default flight, default aircraft with clear skies during daytime and fly around for a minute or so and take a note of your FPS. Now, end your flight, exit the game completely and go to: http://www.venetubo.com/fsx.html Follow the instructions and upload your FSX.CFG to the site, let it tweak it for you and then download the tweaked version and replace your original FSX.CFG, make sure it overwrites it properly. When all of this is done, fire up FSX and load up the exact same default flight that you did before the tweak with clear skies and a default FSX aircraft, fly around for a minute or two and look at your fps. If you still are not happy, go back to your settings and lower the autogen density to zero, also roll back one notch on the scenery complexity. Now repeat your "test flight", still with clear skies and a default aircraft. Going from Full screen to windowed mode (ALT+ENTER) can also be worth trying, use whatever gives you the better fps. My current computer specifications, built in the spring of 2011. Windows 7 64bit 2600k running at 4.4 Ghz 16 GB of some cheap RAM Two XFX Radeon 6950 cards (crossfire not enabled when playing FSX) Also im running FSX from my 500GB cheap slow WD drive while my OS runs from a 120GB SSD, surprisingly there was almost no difference from running FSX from my SSD. In my opinion, the key of getting your FSX to run smooth is CPU speed and violent abuse of your .cfg file, if you're not happy - delete it and start from scratch. Re-installing FSX is the last thing you want to do as it is time consuming and frustrating because it's often not the source of the bad performance. I hope this helps out a bit, dont make it too complicated just mess around with the sliders and you will find your own settings, if anyone has any questions feel free to ask.

Exactly, and thus my statement: "You basically just re-quoted what he said? lol " Both will calculate the same thing = get you close enough to where you want to be at a specific altitude, you will never be spot on due to wind changes, un-even airspeeds and so on unless you are using an A/P to have the green banana calculate it for you on the go

Not quite sure what you're trying to say, you both calculate the same thing lol Im at FL300 and should be at 10'000ft for an approach at a specific point, so therefore I need to calculate when to initiate my descent in order to descend 20'000ft. means (20'000 /1000) * 3 = roughly +60NM (just as Nathan said), now to calculate what FPM you need by using your current airspeed: Cruising at 430kts means 430/0.2 = 2150 fpm for optimal rate of descent Now with what you said; FL / 3 = dist. to start decent ex:cursing at FL240, 240/3=80, start decent 80 nm out FL200/3 = 66NM Sinkrate = half the GS x 10, ex: my GS is 240kts, 240/2x10=1200 f/m, or 24/2=12 & just add two 00's =1200 f/m 430/2 = 215x10 = 2150 fpm Any thoughts?

I jumped into the Q400 from the NGX and its basically the same but a turboprop lol, the FMC works a bit more like the airbus FMGS when doing routes (more clicking less typing), I actually find it more ergonomic to handle than the FMS in the NGX. The only big difference is having to deal with the condition levers/prop feather and having no autothrust, you are in control of the throttle all the time (which makes the VNAV mode a bit tricky to understand coming from the ngx) but its no big deal, just do the included tutorial flight in the .pdf you get when you purchase it and you will get a hang of it. You will love it!

2600k just because it overclocks so damn easy and does not get hot, I've run mine on 4.5ghz the last two years (with a massive aircooler), but it does the job very well.

You basically just re-quoted what he said? lol