Edit: We posted at the same time, Anthony. Aaaah! That must be why mine worked after I copied the whole FT KSEA into the Addon folder. So the process should be:- 1). Copy the original complete FlyTampa KSEA folder into the Addon Scenery folder.2). Remove all of the scenery files except those listed in the Installation Manual.2). Run the Patch installer.3). Rename the three OrbX .bgl files so that they are ".OFF" files. Now there are no black buildings. One needs textures!! DJ is also correct re the filename spelling of one of those files to be deleted.The specific file is:- FTX_PNW_objects_KSEA_BCN_PLC.bgl One other issue I encountered; the scenery files listed include a couple of files which I didn't find in the FT scenery folder; namely any of the _StatV.bgl's. Are these necessary? are these part of an FT update to the scenery? Lastly - "a great big THANK YOU for this patch" and the professional way that it's been announced and implemented. You guys deserve a medal...

Thanks for the feedback, Jose and PJ. We can now update the manuals and this posting will hopefully lead to a search engine indexed solution for anyone else experiencing problems. If you don't have the StatV's then you don't have the static vehicles. I believe that is an install option when you run the FlyTampa-Seattle executable.

Following the outstanding success of your SEA conversion - I thought I'd try the same with the PDX conversion, too. At PDX - all is well - great fix, and apart from a tiny flashing here and there - no problems - except - the old problem of Seattle area shorelines is back, I didn't look at the river, but certainly all the lake and Sound areas around Seattle, Renton, etc - we have the shorelines criss-crossing the water.... What has to be removed or changed to fix this, Anthony?

Hi All, When I downloaded the file for KSEA from myflightsimblog, and ran the installer It didn't create a separate KSEA folder in my addon scenery folder in FSX. I'm running win7 64 bit and have FSX in a separate folder on my C drive. What I had to do was create theFlySeattle folder and scenery sub folders manually. I tried the 64 bit version and then the 32 bit version. After runninig both with the same results, I gave up for the night with the last install being the 32 bit. I came back to it today and after rereading the instructions again and figuring out that I had to also use the textures from the FS9 version it came out quite nice!!! Let me suggest that you should include a specific instruction about also copying the textures from the FS9 version in the readme, the instructions were a little vauge in that area. I landed on rwy 34L and noticed a few bites were taken out of the left side, these were not visible from the air. I don't have any ORBX scenery in that area. I'm attaching an aerial screenshot. Ed Kammerman

Hi All, When I downloaded the file for KSEA from myflightsimblog, and ran the installer It didn't create a separate KSEA folder in my addon scenery folder in FSX. I'm running win7 64 bit and have FSX in a separate folder on my C drive. What I had to do was create theFlySeattle folder and scenery sub folders manually. I tried the 64 bit version and then the 32 bit version. After runninig both with the same results, I gave up for the night with the last install being the 32 bit. I came back to it today and after rereading the instructions again and figuring out that I had to also use the textures from the FS9 version it came out quite nice!!! Let me suggest that you should include a specific instruction about also copying the textures from the FS9 version in the readme, the instructions were a little vauge in that area. I landed on rwy 34L and noticed a few bites were taken out of the left side, these were not visible from the air. I don't have any ORBX scenery in that area. I'm attaching an aerial screenshot. Ed Kammerman

Hi Guys,Larry here from www.myflightsimblog.com and co writer of the KSEA patch. Please keep in mind that this is a Beta release and we really appreciate you all raising the types of questions that you have in this forum so we can iron out the kinks. Just to chime in and possibly answer a few questions. Just as Anthony had mentioned, We had some big time spamming issues on the old myflightsimblog forum page. In an effort to tighten security to eliminate spammers, I added the Rule that you would have to register by email. I tested it with my email and received an instant response when i simulated a new registration. Could it be that the email went to your Spam box? If others are having the same issue, let me know and I will remove the "register by email" requirement. I will post a link of this forum onto the myflightsimblog forum for those seeking info. Ed, by looking at the pic above, your runways do not match up with the satellite image, and it should match exactly. There is a new KSEA AFX file included with the patch. Looking at your pic, it suggest you may have another KSEA AFX or Afcad file in a higher anarchy than the one included with the patch. DO NOT place the afcad file that is in the old FlySeattle FS9 file into the new FlySeattleFSX scenery folder. Try placing the new FlySeattleFSX scenery file at the very top of your FSX scenery library and see if it makes a difference. We have had very limited testing of this patch WITHOUT the use of Orbx PNW in place. Also, the new Installer files on the website have been corrected to create a separate FlyTampaFSX file with both a "Scenery" and "Texture" subfolder. And YES, you should copy all textures from the original FlySeattle FS9 Texture folder to the new FlySeattleFSX texture folder. We will update the pdf manual to include these instructions. BTW, the only difference between the Windows 64 bit download vs the Windows 32 bit download is a slight variation in the directory path where the installer places the files on your HD. Otherwise, the files are exactly the same. We thought this might prevent some possible confusion. Thanks again for the input. Feel free to drop me an email anytime at [email protected]. I will continue to check back on this forum periodically as well. And thanks to Anthony for already answering so many questions. Larry

Hi Larry, The installer I used I downloaded yesterday 8/6, it came with nothing but some .jpg images the manual, readme and some texture files in a texture folder I have no AFX or AFCAD file installed other than the stock one that came with FSX. I'll move the scenery to the top of my list and see if that helps.BTW was somebody a little careless with that backhoe on the left side of RWY 34L Ed Kammerman

Hi Larry, The installer I used I downloaded yesterday 8/6, it came with nothing but some .jpg images the manual, readme and some texture files in a texture folder I have no AFX or AFCAD file installed other than the stock one that came with FSX. I'll move the scenery to the top of my list and see if that helps.BTW was somebody a little careless with that backhoe on the left side of RWY 34L Ed Kammerman

Ed, are you using Orbx's PNW? Their CVX file is what our merge requires to display the correct terrain elevation around 34L. If you've got it installed, make sure you pay attention to what Larry said about file hierarchy in the scenery library, et al.

Hi Anthony, I not using any of ORBX's scenerey at all. Or for that matter nothing from ORBX (no offense) the only scenery and terrain mods are FS Global 2010 and Ultimate Terrain USA with the latest updates. I checked out your freeware. Yup ther's lot's of dirt srips here in Idaho LOL Ed Kammerman

In my case is FS Genesis mesh creating issues?

Hi Anthony, I not using any of ORBX's scenerey at all. Or for that matter nothing from ORBX (no offense) the only scenery and terrain mods are FS Global 2010 and Ultimate Terrain USA with the latest updates. I checked out your freeware. Yup ther's lot's of dirt srips here in Idaho LOL Ed Kammerman

Haha that's why you're seeing the pits. Without the Orbx CVX file, you're not going to get the proper terrain elevation for the west runway. However, I hope you're still able to enjoy it.

Yes I am enjoying it, I'll just steer a bit to the right I could use that AFX file I'm missing.that didn't come with the installer Ed Kammerman

Yes I am enjoying it, I'll just steer a bit to the right I could use that AFX file I'm missing.that didn't come with the installer Ed Kammerman

I'm not sure we can send that file to you as its distribution would likely break the terms of use from Orbx.

Anthony - can you do anything about the coast/shoreline problem around Seattle - caused by the PDX install?

Anthony - can you do anything about the coast/shoreline problem around Seattle - caused by the PDX install?

The PDX install will not affect the Seattle merge. Not sure what you are referring to. If it is indeed affecting the Seattle area. I would uninstall it. Hopefully a new merge will be completed this winter.

According to Larry that AFX file came with the patch. Was that for use with the ORBX scenery only?

According to Larry that AFX file came with the patch. Was that for use with the ORBX scenery only?

It was designed for it. If you can get the field to function without having the Orbx scenery, use at your own risk. The two most important files for useability are the AFX and CVX files. We created the AFX that serves as the basic airport information - runways, frequencies, parkings, taxiways, aprons, etc. The CVX file controls the terrain elevation and flatten for the field and was created by Orbx and distributed exclusively with their PNW scenery. Because MS did not include the third runway at SeaTac with FSX, the terrain under it is not naturally flat. That is why you are seeing the pits.