ualani

Go ahead and post the pics and provide details as to what objects they are. I have all RWY12 objects working in DX10.

What is the model and what object library is it from? I'll take a look at it to see if I can fix it for you.

navysub, Shoot me a PM and I can convert the files that you need in order to be FSXDX10 compatible. As part of the RTMM team I've done it a million times with files in our extensive scenery libraries. http://return.mistymoorings.com/

Just for fun I opened the FSX folder in an Explorer window, clicked on the Fixer icon and got the "FSX is running" message; closed the window and the message went away. Who'd have ever thunk it? Live and learn!

Did another system reboot and the problem went away. Oh well!

I've been using The Fixer from the very beginning and I just upgraded to 2.8 Installation went fine, installed libraries, etc. Now when I attempt to run The Fixer I get a message that says "Please close FSX before running DX10 Scenery Fixer." The only problem is, is that FSX isn't running and I haven't run it since my last reboot. I'd try uninstalling and reinstalling, but I can't uninstall the libraries in order to do it. Help!

You can download the default shaders from here http://www.nzfsim.org/index.php?dsp=downloads&f_sort=fixer

FSX may have been orphaned by MS but certainly not by it's enormous user base, which will be there for years to come. Look at the huge fan base that FS2004 enjoys after all of these years. P3D still has huge comparability issues that need to be addressed before it gains anywhere near the following that FSX currently enjoys.

Hold the shift key as you zoom and it will zoom in (or out) at a much slower speed.

Huh? Have you ever taken a look at the "How To" guide? With your rig you should get much better FPS and visuals if you set it up properly. I do agree that maybe he should meticulously try the ver. 3.2.2 of DX10 fixes to get a basic feel for life inside the DX10 world before going whole hog..

"With all due respect, I do think that it is pretty clear that the "Dx10 preview" must be set. It might otherwise be called the Dx9 fixer?" The Fixer automatically enables DX10 so you don't need to put a check in the Preview box.

Image backup, image backup, image backup...on a regular(weekly) basis! Saves a WHOLE ton of frustration and panic.

I never had any problems with EZDOK using ver 3.2.2 of the earlier DX10 fixes or with the fixer presently. EZDOK seems to be a strange bird at times for many users.

The KB2670838 update caused all kinds of problems on my Win 7/64 system; everything from keeping Windows Live Mail from starting to keeping FSX from starting as well. Took me a while to track it down as the culprit.

Why wait for the fixer and just go ahead and dip your toe into the water now?

I always "loved" the hair pulling, frustrating OOM and various other crashes in DX9 that I never get anymore with DX10. Really makes DX9 worth still using doesn't it? NOT! I'd be willing to bet that if you post your specific problems here that someone could help you in tracking down your artifact problems and minimize them.

This is exactly why that 99% of the time I don't buy software the instant it hits the market. Having said that, Steve's DX10 fixer will be in the 1% when he finally releases it.

This probably is a dumb question but does legacy aircraft mean ones not originally designed for FSX, but for previous FS versions?

Sounds like you are perfectly happy with DX9 therefore DX10 should be of no further consideration in order to meet your needs, standards and requirements. Some people only drink Coke and some only drink Pepsi. Its all personal preference. At the moment, DX10 is a compromise within the FSX experience. Come to think of it, compared to what DX10 offers, DX9 is now a compromise as well. To each his own and I'm glad that you're happy with what you have.

If you followed all of the instructions to the letter and took your time setting things up, the advantages are completely obvious. "Improved stability? Improved FPS? Better lighting?" Yep. All of the above. And tons more.

I thought I was pretty computer savvy, but boy, I'm really confused now. To reiterate: One SSD drive is partitioned. OS on first partition ("C" drive), FSX, utilities, etc. on 2nd partition ("J" drive.) This is on the faster of my SSD's. Second SSD ("I" drive) holds more FSX related stuff (utilities, large scenery files, etc.) So essentially I have 3 SSD's dedicated to FSX. There's also 2 HDD's on the system I use for my every day stuff. So then, what is the 100 mb file that I should put on the "C" SSD drive and how do I put it there? Is that the heap file? Should the swap file go on the "I" drive, or could I put it on one of my HDD's? OR since everything is running smoothly, should I just leave well enough alone? (Why fix it if it 'aint broke?) I'm dizzy!

OK, I'm going to show some ignorance here, so if this has been explained I'm missing it, so please be patient. I dual boot my system (Win 7 x 64 on both boots). One boot configuration (my main one) is used for my everyday stuff and applications, stored on 2, 1TB HDD's. My other "system" boots off of a 120 gb SSD, divided into 2 partitions. One partition holds the OS and a few utilities and the second partition contains FSX and related applications, I also use a 2nd 120 gb SSD for my ORBX sceneries and more FSX related stuff. I like this setup because I overclock my system when I boot to my FSX setup,(4.2 ghz from an I7 950) have configured the OS to a bare bones state, and have setup the system and FSX using the famous "Nick N" setup guide. I have also set up FSX to run DX10. I took a lot of time setting up the system, researching how to "properly" configure everything, and I am extremely pleased with the results. I have a 99% crash free, 0% OOM configuration. So...my question is...I'm using a 3072 gb paging file on my SSD/FSX system drive (6gb system ram). Should I change it using the MS "Fix It" scheme, manually change it, or just leave well enough alone? Will a larger paging file make a difference on an SSD system?

He probably deleted his original FSX profile in inspector, which means its gone until he reinstalls Inspector. I did that too by mistake.