Please understand that the time of occurrence of dusk is not at the exact time as specified by the dusk option within FSX, rather 8-10 minutes PRIOR. Same goes for dawn, which is 8-10 minutes AFTERWARDS.

 

 

 

@timest  - now if only I had known that before release

What is the name of the file to disable?

 

Thanks,

Dirk.

 

This is aircraft specific(obviously) - for the MV B737, you can refer this thread for the names:

 

http://www.milviz.com/forum/viewtopic.php?f=86&t=3381

 

There were 7 or 8 files to be renamed.

 

IT WORKS!

 

 

Post Edit 2:  Stevejp....I'm just took off from an island in the Caribbean and your water fix is fabulous!  It looks just every bit as good as being driven by DX9, BUT....BUT...I now have that beautiful frothing wave crest action that really makes it virtual.  You see the wind upon the waves that is not there driven by DX9.  Thank you...this works...and works very well.  I had never messed with my Shader Folder, just installed your program.  Ran it, set it up...and was flying driven by DX10 in five minutes.  WOW....

 

 

Wow, what a post I don't know what to say, I am embarrassed  - err thanks!

 

I am sure glad it worked though.

 

I should point out that the water is all Aces btw my only contribution in that respect is to correct the tone.

Wow, what a post I don't know what to say, I am embarrassed  - err thanks!

 

I am sure glad it worked though.

 

I should point out that the water is all Aces btw my only contribution in that respect is to correct the tone.

Steve....THANK YOU!   I also thank myself for pulling the trigger....I'm running with features, that I could NEVER use driven by DX9...and now, I'll be a raving lunatic DX10 fan-type-person.

Bloom, man...Blooooooooooooooooooom....and not one drop from 30 FPS!!!!!!!   Yeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeehaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaw~!

Wow, what a post I don't know what to say, I am embarrassed  - err thanks!

 

Sorry Steve, we should have warned you .Don't worry, he's like this most of the time.  :smile:

 

@ Sesquashtoo :  :wink:

Here's a thought: I do not have the PMDG, but one possibility is their engine smoke effect is the culprit. I had serious a FPS hit with the MV 732 due to the way they are calling their engine smoke effect. Particularly awful with spot view during takeoff, but impacting me even in the VC (I have no idea why). Two workaround options for me - convert only Simple Lights and Effects with the fixer, or rename the smoke effect used by the MDL so it could no longer be used. (I chose the latter for now.) I believe this is linked to my GPU choking on particulate nature of the effect (similar to clouds performance) with SGSS enabled. Anyway, something to look at.

 

There is file called Dx10.ini in c:\Program Data\DX10SceneryFixer  - do take especial care editing it mind.

 

There is a section

 

[ExcludeEffects]

ballast.fx=1

 

You can add the names of any  effects that seem troublesome so e,g

 

ConcordeSmoke.fx=1

 

and it wont convert that effect

 

Disable effects before you add the line then enable afterwards.

Seems you like it, Sesquashtoo... LOL

There is file called Dx10.ini in c:\Program Data\DX10SceneryFixer  - do take especial care editing it mind.

 

There is a section

 

[ExcludeEffects]

ballast.fx=1

 

You can add the names of any  effects that seem troublesome so e,g

 

ConcordeSmoke.fx=1

 

and it wont convert that effect

 

Disable effects before you add the line then enable afterwards.

 

Excellent!

Sorry Steve, we should have warned you .Don't worry, he's like this most of the time.  :smile:

 

@ Sesquashtoo :  :wink:

Only Paul...when it is deserved...if this was a bust...I would not have come back here to make a point of saying so...that is not my M.O.  

 

Not only is this a Genuine All Smiles, Mitch Thumb's Up...but for the VERY FIRST time since having bought FSX  all those years ago...I now have everything...every slider at MAX, every bullet (Bloom, Flare....what have you.....) all in the full-steam-ahead, and I did not drop ONE FPS, in doing so, driven by DX 10 in combo with Mr. Steve's Super Duper, DX Kick-In-The-Pants Fixer.....  or  Steve's DX10 Fixer, for short.    Fabulous, man....hey folks, you reading this post....YOU decide for yourselves if running FSX FULL OUT with every graphic position firing on all cylinders, is worth the one time hit of $35.00.  That's it...that's all....   For myself....FSXG and Steve's DX10 Fixer combo....is truly FSX(11).  As close as you are EVER going to get....and my one final word...ok...two final words.    IT WORKS!

Seems you like it, Sesquashtoo... LOL

This last one month, has turned out to be rock n' roll!  

 

1. FSXG

2. Steve's DX10 Fixer

 

J, I have gone back to Extremely Dense on both my main sliders, and have clicked Bloom and Flare back on for all time...and WOW....Dusk over FSXG is eye popping!

 

Oh yes....you're right, I seem to like it, and will get no sleep tonight.........nope.....very little........------------------------------------------------------------------------------------------------>

I have read on this thread where people are asking the simple question....if I purchase this software/fix...what will I get for it..what will I gain?

 

I hope to answer at least some of that with a little mini report.

-------------------------------------------------------------------------------------

 

I bought the program about 1 1/2 hours ago.  I ran the installer, put in the info from my purchase that it required it..and it unpacked with no issues.

 

I then ran the program, and was met with the single option mask.  It really is easy, folks.  You lead to the FSX folder and install the two libraries you need to.  That being done, you click on each SHADER mask and then pick what you want to have happening in that SHADER.  Simple...and done in less than 5 minutes, without even reading the manual. It is quite clear and intuitive.

 

That being all done, I had already had FSX in DX 10 Preview mode, as I had wanted to see for myself the A/B of it all, before using Steve's program.  Well, to start I had black squares where lights should be all over my FSXG virtual world.  I had runways, asphalt, and concrete flicker, I had A.I. planes that showed no textures, but flat grey...etc. I had water that was a very light blue (quite horrendous actually...) but did have better wave and 'froth' animation on the crest tops.  

 

So..I saw that for the most part, if you had ORBX regional and/or FSX Global, you would have visual artifacts during the day and no FSXG vector lights during the night.  In otherwords, you would NOT be using DX10 at all.

 

I then put into place by running the Steve's DX10 Fixer menu, all that it corrects...and fired up FSX again.  Remember, I was already in DX10 Mode, and the Menu Mask noted that from the first.  I set myself up with my default flight, and noticed right away that I had now...all my Orbx FSXG scenery restored to that visually achieved in DX9 mode...all working, and looking great.  I noticed that my FPS, were still in the locked in 30 FPS range.  I then took to the active and took off out of Michigan's KFNT (Bishop Intl.)

 

Everything looked fine, and as what you would see running DX9.  I had absolute smoothness of flight and animation.

 

I then started to 'add load' to see if my locked 30 FPS could be maintained as it WOULD NOT have been running under DX9.  I first fired up the universal BAD BOY....BLOOM. Usually, my FPS would drop by half or more under DX9.  What happened with DX10 running with Steve's modifications?   30 FPS, and they maintained no matter my view, or outside in SPOT Mode.  Amazing performance horsepower gain.  I then added FLARE, and again, nothing below 30 FPS, maintained. I was stunned.  I have all sliders on the left side of the FSX graphics menus at full all the time, including water. That was with DX9 as well.  What I next changed was that I had been running with Scenery Complexity at Very Dense, rather than Extremely Dense, and same went for AutoGen.  Well, I next cranked them back to their respective Extremely Dense (the highest available) setting, and went back to my flight. NO DROP IN FPS.  Still 30.  Now  you must realize, that I have all graphic functions enabled and am running FSX truly full out....with everything ACES programmed into it.

 

Still....an amazing 30 FPS locked within the sim---being maintained.  So easily stated, with using Steve's DX10 Fixer program, and DX10 Preview Mode, I now can achieve a no-compromise performance from FSX. I have flown for over 1 hour and 15 minutes with the sim at FULL BORE, including of course, the infamous   performance and FPS killer; Bloom.

 

FSX, full out folks...no slider crippling the coding output, Bloom giving wonderful atmospherics to clouds, sky, and aircraft fuselage, and light systems...all of it...and with an i7-975 Extreme CPU running at an overclock of 4.02 GHz and a EVGA Signature Overclock GTX680 2 GB negotiating the graphics to the monitor....I am able to run FSX as ACES coded and envisioned it...via the much technically better driven DX10 ---full out, and all features FINALLY----enabled and adding their contribution to a simply fantastic flight simulator experience. Full out...and over an hour in flight, with a 3rd party intricate cockpit....and no CTD. No OOM's!

 

Whether the above experience is worth the $35.00 ticket to play in this sandbox....is strictly up to you, the reader.  Only you can make that decsion, and not anybody else's opinion, good, bad, or indifferent.  My final comment within this post, is that other than FSXG, this was the best  'other' purchase hand's down, this year, that was not dedicated scenery. It GIVES YOU a true, and legitimate DX10 running environment.  I do not have any Fly Tampa (FT) airports or any other custom airport other than from ORBX, and I can tell you, that all ORBX properties work DX9'esque, and look fabulous, the regions... and the airports, day or night. Lights work, runways are lit up...and you only need to advance down one to have a DX10 blast......and the resultant sim wide performance kick-in-the-ample-pants!

 

Signing off, this mini performance review,

 

Cheers!

Just installed this after sitting on the fence and loaded up a night take off in my PMDG 737-700 at FlyTampa's Chicago Midway.   I turned on Bloom for the first time ever.   Fired up VoxATC and let it load in a lot of Ultimate Traffic 2 aircraft.   All lighting was fixed.  No grey textures.   Even MORE FPS than before and with aircraft every where.   I am going to fly this around for a little while and see what else I can make this bad boy do.   So far, worth the $35.

Just installed this after sitting on the fence and loaded up a night take off in my PMDG 737-700 at FlyTampa's Chicago Midway.   I turned on Bloom for the first time ever.   Fired up VoxATC and let it load in a lot of Ultimate Traffic 2 aircraft.   All lighting was fixed.  No grey textures.   Even MORE FPS than before and with aircraft every where.   I am going to fly this around for a little while and see what else I can make this bad boy do.   So far, worth the $35.

So, I didn't exaggerate?   There you have it.....

@Q_Flyer - Try disabling  effects.

 

If that fixes it then there is an option on the menu bar to reduce the set of effects that are converted.

 

There is a further (undocumented as yet) method to exclude individual effects - pm if you think this might be needed

 

Thanks Steve - As suggested by an earlier poster (to whom I'm also thankful), I think we've nailed the individual effect that is responsible for the performance drop ;  fx_PMDG_NGX_engsmoke.bgl.fx

 

.......... I am discovering an amazingly more frame rate friendly NGX with this effect disabled!

 

So yes, DX with the fixer is now just hands down better with every add-on for me now... the future is so bright now, with this fixed up DX10 world.

 

Well done sir!

If the DX10 fixer is all that great why don't somebody show before and after screenshots ?, it would really help Steve sell it.

If the DX10 fixer is all that great why don't somebody show before and after screenshots ?, it would really help Steve sell it.

I dont have any issues with DX9, no crashes or OOMs, but I also would like to see some head to head comparison shots of DX9 and DX10 shot at the same location.

 

The only reason I would switch is if DX10 looks better, but its hard to say since no one posts comparison shots.