My black screen issue is fixed. I'm not sure what it may have been that finally set it right but it's good across all 6' of screens!  

   Orbx lights still flicker randomly though.

 

Here's my DX10SceneryFixer testamonial:

 

First off, If you are a DX10 naysayer, nothing I'm about to say will convince you otherwise, and my intent is not to do so anyways.  Now that that's out of the way I've been using the Steve DX10 fix for months now and am savy to how it interfaces with FSX so I've already enjoyed some of it benefits.  But here is why my $32US was well spent this weekend:

 

1. By using a tool called the DX10ToolBox, which can only be found in the .exe folder, I now have DX10 VC shadows for

  A2A Cub, WoP3 Spitfire & P51, RealAir Lancair Legacy.

 

2. 16x AF in DX10 via NI (before you were stuck with the ingame AF); the difference this makes for the VC experience is huge, plus scenery textures are much clearer.

 

3.  UTX night lights no longer blinks (at least for the 10 minute flight I made around the SF bay area which used to be intolerable before the fix); though they still flash on/off due to the autogen effect (which is tolerable).

 

I don't use 3PD airports, nor none of the addon AC I own suffer problems which this tool can fix, so I can't speak to its effectiveness for these issues.

 

There is LOTS of confusion about DX10 AA in FSX.  Basically put, in DX10 there is ONLY ingame AA/AF, though AA settings can be modified by fsx.cfg entries in a limited but meaningful matter.  NI DOES NOTHING FOR AA in DX10, which is still true even with the use of this tool.  But the ingame AA can be augmented by using NI Transparency Supersampling with a setting of at least 2xGSSSAA.  4xGSSSAA really whipes clean the jaggies from the VC, rivalling DX9 AA though without the fuzziness that DX9 SSAA adds (IMO at least).  Also in DX10 the 4xGSSSAA doesn't hammer performance as it does in DX9.  The only "real" change this tool bring to NI is being able to set AF levels; all other DX10 AA behaviors are not changed by this tool (though the tool will set the fsx.cfg entries for you).

@TheFamilyMan - so you're saying that it's necessary to set AA in the DX10 Fixer, then set aggressive Transparency Supersampling in Inspector?

 

And is that what you mean by "2. 16xAF in DX10 via NI"?  Otherwise I'm confused about how to reconcile that statement with "NI DOES NOTHING FOR AA IN DX10."

 

Not trying to give you a hard time - I'm genuinely trying to figure all this out.

With respect to the FlyTampa products, especially OMDB and CYUL, still not showing up perfectly under the fixer, the ball is in Martin's court.  He and his team need to look at other types of textures to develop their PAPI and approach lights, as other great developers, like FSDT, have done.  There is nothing to lose by giving FlyTampa polite, constructive feedback in their forum.

 

 

And is that what you mean by "2. 16xAF in DX10 via NI"?  Otherwise I'm confused about how to reconcile that statement with "NI DOES NOTHING FOR AA IN DX10."

 

AF= anisotropic filtering is not AA, so those particular statements don't conflict.  I'm no video card whiz,  but my understanding is that you can use NI to augment the ingame AA with transparency supersampling, but that NI can't override settings like it can in dx9.  personally I have better AA in DX10 than I ever managed to get in dx9, but that may be more because I followed paul's guide in the dx10 forum to a T, and with dx9 I was basically just flailing around not knowing what I was doing.  in dx9 if I found good AA it always carried an unacceptable performance cost for me.  paul's guide and NI settings work well for me, I don't have shimmering, other than some of the default airport runways when viewed at  shallow angles.

OK.  I purchased it and went from DX9 to DX10... and it does look better.  One, no, ok, two questions:

 

1.  How to get rid of "jaggies" in the CP and the A/C exterior?

2.  Realistic airport lighting - runways and taxiways?

 

Best,

 

Kevin

 

 

AF= anisotropic filtering is not AA, so those particular statements don't conflict.  

 

Ah, sorry, you're right - I read too fast . Speed kills.

 

I think I'd better track down Paul's guide - I've got my DX9 working extremely well thanks to NickN but this is clearly a different story.

 

Many thanks!

 

Am not familiar with SweetFX - maybe I should be.  Best of both worlds?

 

We'll see, working on the Fixer now.

 

Dirk.

I think a LOT of confusion would have been prevented if Inspector had been mentioned in the Fixer's manual... Just a simple note about NI's (just as nIvidia's CP's) FSAA Mode and Setting having NO effrect at all on FSX would have made a lot clear for a lot of people. FSAA in DX10 only works by using two entries in the FSX.cg: MultiSamplesPerPixel=# and MultiSampleQuality=#.

 

Most work is done by using SGSS which is MANDATORY to get good FSAA. Also, SGSS should be the same as MultiSamplesPerPixel: if you have the latter at 4, you should also use 4xSGSS. It's a shame the manual doesn't mention SGSS at all (at least as far as I can remember... I will check that again this afternoon. ^_^ )

 

Secondly: the FSAA option in the Fixer is NOTHING more than a convenient way to add those two entries to the FSX.cfg. The Fixer itself doesn't 'do' FSAA. You can even skip the Fixer's option completely and add or edit those settings manually!

 

If for instance you use the fixer to set 2x FSAA it will add MultiSamplesPerPixel=2 and MultiSampleQuality=0 to your cfg. If you then manually change those numbers to 4 and 0 you will effectively have 4x FSAA. (When you open the Fixer after doing so, you will see the Fixer has read those settings and it will show 4x now! Of the dropdownmenu is blank, you have entered settings the Fixer doesn't know)!

 

 

So the Fixer's FSAA option is ONLY a simple interface to edit the FSX.cfg. There is no logic or system behind it doing something interesting. And you really need to set SGSS using Inspector for good FSAA.

$35 bucks is a lot of money?  $25 Euros?  Surely you jest.  Even in the crappy US economy, $35 buys you almost nothing.  ALMOST NOTHING.  A half tank of gas? A dinner without adult beverages for two?  A fifth of liquor?  See a movie with two kids?  That won't even buy enough salt for my fish tank to make 100 gallons, and I go through that very two weeks.  Steve has served the community well for FREE for many years, and if he wants to charge $35 for this, it's well deserved in my opinion.  I've always wanted to run DX10 and can't make it work even with all of the back door fixes out there.  If Steve's fix gives me DX10 ability for a measly $35, then I'm in.  Thumbs up, Steve.

Kattz, I reference that $35.00 to what it will purchase also, in using FSX.  It is like this, do I buy that new Yellowstone CRM airport just released from Orbx,with all the square miles of surrounding highly detailed scenery,...or do I buy a tool kit for the same asking price, that might give me all the visuals that DX9 offers, sans effort.  It's as simple as that, and I think, it is in the final analysis, as simple as that for a lot who have posted, not regarding any technical question, but the cost to even download it.  For myself, and I only represent myself here...I would more than not, rationalize spending $35.00 on a 'guaranteed'   (Yellowstone...etc) and proven, visual experience, than (obviously in my personal opinion and rationale) what I would consider a gamble on what I would end up with, after a 'sales final' purchase.  In fact, I was just thinking as I was posting to you...that too bad Steve did not partner with Flight1...because I WOULD have tried out this DX10 ToolKit KNOWING that it would not have been any financial gamble of any kind, due to Flight 1's stellar and industry-first customer satisfaction guarantee. I will tell you, I have bought many products through Flight 1, and on a couple, purchased BECAUSE I had a chance to recoup my money, if not satisfied. I have never to date, invoked that option...but the point I hope to make, is that BECAUSE of that option open to me....I purchased 'X' program.   Again, too bad Steve did not end up with marketing through Flight 1.  I bet there would have been a couple of 'sticker shock' posts, but a HECK of a lot more 'I bought it' with the option to request refund, but "...I did not....I like what I see, and it's a keeper!" Just my view and opinion. I wish Steve fabulous success, no matter how he brought this to market and for what final cost to the end user. You go guy!

I don't know if its my set up but the PMDG 737/777 (I know they don't claim DX10 support) does not want to play nicely, particularly at dusk, night etc in full screen.

 

When you click on VC with the arrow cursor it jumps back to windowed mode. Also the 'hand' cursors do not want to appear.

 

Anyone with similar probs? Still testing at the moment. Maybe new fsx.cfg required.

 

Edit: Fixed. Resolutions somehow got screwed up during install of Fixer .

I think a LOT of confusion would have been prevented if Inspector had been mentioned in the Fixer's manual... Just a simple note about NI's (just as nIvidia's CP's) FSAA Mode and Setting having NO effrect at all on FSX would have made a lot clear for a lot of people. FSAA in DX10 only works by using two entries in the FSX.cg: MultiSamplesPerPixel=# and MultiSampleQuality=#.

 

Most work is done by using SGSS which is MANDATORY to get good FSAA. Also, SGSS should be the same as MultiSamplesPerPixel: if you have the latter at 4, you should also use 4xSGSS. It's a shame the manual doesn't mention SGSS at all (at least as far as I can remember... I will check that again this afternoon. ^_^ )

 

Secondly: the FSAA option in the Fixer is NOTHING more than a convenient way to add those two entries to the FSX.cfg. The Fixer itself doesn't 'do' FSAA. You can even skip the Fixer's option completely and add or edit those settings manually!

 

If for instance you use the fixer to set 2x FSAA it will add MultiSamplesPerPixel=2 and MultiSampleQuality=0 to your cfg. If you then manually change those numbers to 4 and 0 you will effectively have 4x FSAA. (When you open the Fixer after doing so, you will see the Fixer has read those settings and it will show 4x now! Of the dropdownmenu is blank, you have entered settings the Fixer doesn't know)!

 

 

So the Fixer's FSAA option is ONLY a simple interface to edit the FSX.cfg. There is no logic or system behind it doing something interesting. And you really need to set SGSS using Inspector for good FSAA.

All the information any user needs is available on the DX10 forum, including the "How To Doc".

As you had difficulty setting up DX10 before the fixer was released, you spent a lot of time with Paul who helped you.

 

This post is a smack in the face not only to  PJ, but also those that helped you.

 

BTW, I replied to your scathing post about me on the Orbx forum, read it, then read it again. Sometimes I wonder where you are coming from.

I think a LOT of confusion would have been prevented if Inspector had been mentioned in the Fixer's manual... Just a simple note about NI's (just as nIvidia's CP's) FSAA Mode and Setting having NO effrect at all on FSX would have made a lot clear for a lot of people. FSAA in DX10 only works by using two entries in the FSX.cg: MultiSamplesPerPixel=# and MultiSampleQuality=#.

 

Most work is done by using SGSS which is MANDATORY to get good FSAA. Also, SGSS should be the same as MultiSamplesPerPixel: if you have the latter at 4, you should also use 4xSGSS. It's a shame the manual doesn't mention SGSS at all (at least as far as I can remember... I will check that again this afternoon. ^_^ )

 

Secondly: the FSAA option in the Fixer is NOTHING more than a convenient way to add those two entries to the FSX.cfg. The Fixer itself doesn't 'do' FSAA. You can even skip the Fixer's option completely and add or edit those settings manually!

 

If for instance you use the fixer to set 2x FSAA it will add MultiSamplesPerPixel=2 and MultiSampleQuality=0 to your cfg. If you then manually change those numbers to 4 and 0 you will effectively have 4x FSAA. (When you open the Fixer after doing so, you will see the Fixer has read those settings and it will show 4x now! Of the dropdownmenu is blank, you have entered settings the Fixer doesn't know)!

 

 

So the Fixer's FSAA option is ONLY a simple interface to edit the FSX.cfg. There is no logic or system behind it doing something interesting. And you really need to set SGSS using Inspector for good FSAA.

 

Jeroen - thanks for putting it over so clearly/eloquently. I agree with you, the manual could/should mention NVI settings - and how it all relates. I'd have thought anyone that's prepared to dabble with DX10 at all will be using it (or the ATI equivalent). Steve obviously understands all this - but many of us don't ... and just make educated guesses. A couple of paragraphs from Steve would probably cut the length of this topic down to 10% of its size! He could change that bloody font as well, while he was at it :lol:.

 

Adam.

 

EDIT: Julian - without working out what's going on at ORBX (where I post a lot as well) I don't see any of this as a "smack in the face" to anyone (certainly not me, anyway).

Julian - without working out what's going on at ORBX (where I post a lot as well) I don't see any of this as a "smack in the face" to anyone (certainly not me, anyway).

 

Hi Adam, the point I was making is the info that Jeroen posted is available, and readily.Jeroen knows this, so i am bewildered why he as overlooked this fact. Especially the "How To" doc which should be used in conjunction with the fixer.

He has implied that most or all users are left in the dark on how to configure the fixer tool, and the setting up of ones graphic cards.

Avsim have a DX10 forum, and that is what it is for. Nobody has been left in the dark.

 

I am not going to post anymore about this, as I am still quite angry about the Orbx post, so in the interest of fair play I will continue anything DX10 now in the appropriate forum.

On the issue of people getting upset about the price, it isn't too expensive at all in my view, but comes to market after several highly priced "essential" fsx purchases have hit our wallets with rapid fire succession, 777, FTXG etc. Maybe the straw breaking the camel's back for some?

 

Patience might help.