Paul do you know when its planned to be released? Is it delayed? Thanks

Great, thanks for the info Paul.

 Must !!??  Do you really mean that Steve by releasing his software is responsible to Which add-ons YOU installed in FSX ?

 

I will just be glad to use FSX in DX10 with most issues fixed, the most important benefit for me is no more OOM, if say, 5 % of my add-ons do not work properly, I will gladly stop using them...

 

Alain from Montreal

Flytampa is the 5% of my add-on scenery BUT in this 5% is my local airport!

 

What they've been saying all along is that the airports they are testing, including ft all work. They aren't about to come out and say that all airports are guaranteed to work, since they can't possibly test them all. Up until the point that this tool is released, these are freeware developers, and its not reasonable to expect them t purchase every single addon available in order to test it. Perhaps they should have a larger beta team, but that has problems too. I know you're all willing to volunteer, but lets face it, all you want to do is play with it for free for awhile, not actually put in the real work that's required to test.

Paul does FT Boston Logan work in dx10 Yes or No that simple if it does I'm in big time, let me know please.

 

PS No jaggies and crap like that in dx10 just could not deal with my local KBOS not working in dx10 - thanks to Paul for helping to get it up and running nice.

Flytampa is the 5% of my add-on scenery BUT in this 5% is my local airport!

So is mine, Montreal/CYUL but I could live without...with difficulty and regrets if it means other benefits; it's all a matter of balance, and choices

 

Happy flying

 

Alain from Montreal

Wow FT needs to step it up as They may start loosing a lot of business 

Yup, if you scroll down to the bottom of his post here, the fixer is intended to fix the nav and strobe lights as well: http://stevesfsxanalysis.wordpress.com/2013/06/21/dx10-scenery-fixer/

 

Hi Dylan,

Do you know if the nav/strobe fix he's applying to the payware add on is the same fix from the "how to" guide that involves replacing 7 files?  Thing is, I've already inserted the 7 files and it didn't fix it. 

The default Baron and my CLS MD-80 lights all work perfect in DX10, but everything else not so good.

I may not have made my earlier post/question clear. When Steve says "The experimental fix also seems to works for planes with embedded lights." does embedded mean lights which are part of the model (mdl) and not the aircraft.cfg? Thanks for any and all insight into this.......

Correct, Bob. "Insight?" Huh?  :lol:  Sometimes a fix is unexpected, but I've not really been involved with lights, other than the PNW lights and what 's been tested/fixed for JohnV.

 

The light fix is not the same, Maurice: The patches can't do, or don't work in the same manner as that in the app. 

 

Richard - you're right: I used to have FT on a pedestal, but no more - FSDT   :im Not Worthy:  (and a few others) have caught up very well, haven't they! I visit St. Maartens ocasionaly, and still use a converted KSEA, but that's about it. I don't have Boston, Rich: it's one of my favourites, too, and will be in the "East Coast Route" if ever I get around to it. A lot will depend upon CYYZ, and who builds it first.  :Thinking: 

 

Shawn - thanks for you help, bud! There are a couple of problems in announcing an airport as being "compatible": 1). three months after the test, and one "update" is pushed out from the developer, and it's suddenly not compatible.. Duh!  2). If tested early in the beta stages - it could become incompatible again - caused by another small change in the fixer app, but simply forgotten that it did need testing again. 

 

Drumsonly! - your check is in the mail, and I hafta say - I've loved your doggie avatar since the first time I saw it!!  :lol:

 

:drinks:

So Paul i think in a round about way the FT scenery will not be fixed by this dx10 fix, thats not good news but I think I all ready new the answer, thank you.

No - that's not what I'm alluding to - I'm very confident that the DX10 Scenery Fixer will indeed fix the FT airports - even some of the older ones.

 

I simply like to fly the dumb ol' Maddog (LH) up and down the West Coast, USofA, as there is a string of very nice DX10-friendly airports that all work with Steve's (beta's) application. CYVR - KSEA - KPDX - KSFO - KLAX - KSAN - KPHX - and on back up. This was similar to the KSEA - KPDX - and down, using Dreamfleet's beautiful B-727 in the old FS9 days.

 

If you do a search for "DX10" on the FT forum you'll find a lot of "DX10? - Turn it off", even when talking about the two airports that are advertised as being compatible.

I've contacted FT with regard to DX10 a coupla times, and it's always the same response - "The market's too small" "It's too much work", and so on, so.... I support those whom I think merit that support.

Paul, do use nvidia inspector? If so can you post your settings?

 

Sent from Samsung Galaxy Note 2

 

 

Here ya go, Eric. 

 

The "4"x S and "4"x SGSS are mirrored in the fsx.cfg in order to get AA in the sim, per below:-

****************************************************

[GRAPHICS]

 

MultiSamplesPerPixel=4            

 

// Must have for good AA. Using 8 is a huge performance killer for a very small improvement

//This is tied to Transparency SuperSampling (SGSS), and should be the same number as that set in NI, otherwise FSX will take the lower of the two numbers.

 

MultiSampleQuality=4   //  Can be 4 for better performance. Can use up to 32x AA

*****************************************************

 

FXAA is "Allowed" and "On", so that we can have a "jaggy-free" rotating aircraft.....

"BioShok" Is selected under AntiAliasing Compatibility, so that we can get AA for ground shadows.... 

 

There's a bit more - you can find it in the How-to, it's mostly up-to-date.

 

Hope this all helps!

The light fix is not the same, Maurice: The patches can't do, or don't work in the same manner as that in the app. 

 

Thanks Paul.  That's great news.