I'm starting to get OOM errors with a few of my addons. I never got these errors before because my last computer didn't have the ability to run at the high graphics setting on FSX as this one is capable of doing.I have been using winxp32 bit for a long time and I would like to upgrade to a 64 bit system to utilize my 4gigs of ram and avoid the OOM errors. I was thinking of upgrading to winxp64bit instead of win7 just because I am familiar with xp and also I could probably avoid any incompatability issues that win7 may have, not to mention I can pick up xp64bit for 60 bucks. Can one of you gurus tell me if there is any reason to goto win7 instead of winxp64bit for a dedicated FSX computer? Any limitations, incompatabilities?ThanksJB

If your only reason for changing OS is to help FSX, then I suggest going to XP 64-bit.This is because Microsoft changed the way audio works in Vista and Windows 7 under DirectX. This - oddly - SEEMS to be responsible for the "missing textures" problem which afflicts some users of the "heavy" add-ons from PMDG and LDS. This is a serious problem, if it arises.However, for purposes other than use of FSX, Windows 7 is IMHO a far more attractive OS than XP.Tim

Having upgraded to Windows7 64 bit and installing MD 11X I have several problems.The cockpit instrument panel is 'greyed out' with no instruments displayedThe menu add-ons has no PMDG itemsHave uninstalled and installed again with no change !Is there any resolving of these issues on the horizon ?RegardsAllan

Having upgraded to Windows7 64 bit and installing MD 11X I have several problems.The cockpit instrument panel is 'greyed out' with no instruments displayedThe menu add-ons has no PMDG itemsHave uninstalled and installed again with no change !Is there any resolving of these issues on the horizon ?RegardsAllan

AllanThis is not the "missing textures" problem which I mentioned in my last post. It sounds more like a problem with the user account control system in Vista and Windows 7. This slaps a sort of lock onto the "default" folder locations for installing application files and seems to prevent the PMDG installer from "writing" everything that needs to be "written" in the default FSX folder.The solution which works for me and others is this: (1) install FSX (and all add-ons) to a dedicated hard drive or, at least, to a directory OUTSIDE the "Program Files" or "Program Files (x86)" directories (for example, use "C:\fsx" or "D:\fsx"); and(2) run FSX with "Administrator" privileges.Purely from the perspective of FSX, Windows 7 64-bit has no particular advantages (or any advantages, so far as I am aware) over XP 64-bit, provided you have at least 4GB RAM. If you have less than 4GB RAM then theoretically you MIGHT benefit from the new WDDM1.1 introduced with Windows 7: this sometimes uses less system RAM than formerly, but I am not aware of anyone with out of memory errors under XP 64-bit finding that they go away under Win 7 64-bit, so the benefits are pretty marginal at best.Just to be clear: I am not saying that Win 7 is bad: for most purposes, it's a notable improvement on XP, IMHO. But specifically for FSX, I do not think it has anything special to offer, and it may make your life more difficult. The "missing textures" issue is the biggest problem I am aware of, as it cannot always be solved and solving it at all involves lowering your sound quality notably. But there is another niggling problem which you will encounter if you need to add scenery folders under Win 7: this one is much easier to resolve, but it does show that FSX has been somewhat out-paced by OS development.Tim

Thanks for all the replies. Until I hear otherwise, I will plan on getting WinXp64Bit...JB

That is the missing texture issue?

I'm ordering a new PC today and will be going from 32-bit XP on my old PC to 64-bit Windows 7 along with a partition running 64-bit XP. I want to use the new Windows 7, but also want to be able to use my software that will only run right on XP. As for 64-bit, I want to be able to use more than 4GB of RAM which I currently have in my 32-bit PC, but XP only recognizes 2.75GB of it. I think 64-bit is the way to go.

That is the missing texture issue?

JeffIf you're curious, take a look at the PMDG "General" forums, where the topic crops up quite often under one guise or another. The longest and most tedious thread, but the one which generated the solution, is called "Black/disappearing textures? Some bizarre news", here: http://forums1.avsim.net/index.php?showtopic=249782But you're on XP 64-bit, so you shouldn't suffer from it.Tim

JeffIf you're curious, take a look at the PMDG "General" forums, where the topic crops up quite often under one guise or another. The longest and most tedious thread, but the one which generated the solution, is called "Black/disappearing textures? Some bizarre news", here: http://forums1.avsim.net/index.php?showtopic=249782But you're on XP 64-bit, so you shouldn't suffer from it.Tim

Well, I will be on XP64bit after all the help on this thread. Actually, just ordered it for 60 bones. Not a bad deal for xppr64bit.JB

JeffIf you're curious, take a look at the PMDG "General" forums, where the topic crops up quite often under one guise or another. The longest and most tedious thread, but the one which generated the solution, is called "Black/disappearing textures? Some bizarre news", here: http://forums1.avsim.net/index.php?showtopic=249782But you're on XP 64-bit, so you shouldn't suffer from it.Tim

Yes, I know... http://www.simforums.com/forums/forum_posts.asp?TID=32223

Hey Nick,I just wanted to report back that your advice of switching back (upgrading - LOL) to WinXP_x64 was right on the money. My test-flight (before and after), using the PMDG MD-11 from JFK to LAX, is now flawless, without any of the missing textures or CTD issues that were noted on Win7 using the exact same hardware and clocks.Thanks again for those wonderful "How To" threads. I hope you keep backups of those threads - they're priceless! Not so much as a learning experience anymore, but as a checklist (reminder) of the proper reinstallation process.

Just like I know that more than likely the 5870 ATI shimmer/perf issue will not be resolved with drivers The ONLY stipulation is the XPx64 disk MUST BE A FULL SP2 INSTALL FROM CD and not the web based download/update for SP2There is a reason for that.. and I do not have time to explain it.. the install must be XPx64 SP2 (a-b or c) from the CD and then correctly UPDATED at Windows Update. See this post for install and optimize details: http://www.simforums.com/forums/forum_post...D=183578#183578Nice to see you Tim.. I sincerely hope all is well. I am traveling so if I dont get back here, . God Jul!

Just like I know that more than likely the 5870 ATI shimmer/perf issue will not be resolved with drivers

The shimmering is resolved with Super Sample AA, but not without a performance hit once in the clouds.

The shimmering is resolved with Super Sample AA, but not without a performance hit once in the clouds.

Uh huh.. which has been the issue since day one and exactly what I posted

Uh huh.. which has been the issue since day one and exactly what I posted

I don

I don

If it was possible... when you get there, let me knowThe 4000 series wont do it (and beat the 285) and the 5870 may or may not, it depends on the access ATI allowed,... but I also know their core AA method too so I wont hold my breathnot saying it wont because I have nerver broken down their new core design ML.. just relaying based on being a hardware engineer dating back to Apollo and not a internet repair shop tech with a PhD

I don