I saw in another forum somewhere that a guy said he was happy he found the website that shows how to get the flytampa ksea into fsx but didn't share a link. Does anyone know how to do this or even know the website? I would like to get all the legacy products to work if I can. Thanks.

 

Scott

It looks like the website is no longer up. Sorry. I know that the developer of the patch was active on the forums and was very helpful to me in getting KSEA to run. I don't remember his name. I will try and find his name so you can PM him. 

 

EDIT: 

 

I tried to find his name but I couldn't> i have to take off but a quick search landed me these results I hope they help. 

 

Try this link. The original link is provided by user Paul J

 

http://forum.avsim.net/topic/409403-flytampa-ksea-patch/?hl=%2Bflytampa+%2Bksea+%2Bfsx+%2Bpatch

 

 

The FlightZone KPDX and the Flytampa KSEA only work with the ORBX PNW in conjunction I think!..

The FlightZone KPDX and the Flytampa KSEA only work with the ORBX PNW in conjunction I think!..

 

I have never tried it with the default by I have used with ORBX and SimSavvy and it works fine. 

 

 

Yeah same for me! I love flying KSEA - KPDX with the Majestic Q400! 

I co-developed the patch. For some reason my partner dropped off the grid. Haven't heard from him in a few years and he hosted the patch. 

is there a particular reason why Fly Tampa doesnt want to revisit doing KSEA properly for FSX?

is there a particular reason why Fly Tampa doesnt want to revisit doing KSEA properly for FSX?

I read somewhere that the default Seattle area is a frame rate killer in FSX.  Add to that a detailed KSEA with add-on aircraft and its off to OOM county bud!

I read somewhere that the default Seattle area is a frame rate killer in FSX.  Add to that a detailed KSEA with add-on aircraft and its off to OOM county bud!

 

I have no issue with frame rates at KSEA with UTX or default, at least no more then say KSFO, KLAX. It's a different story with ORBX PNW which is why I don't use it. (I only have a 3Ghz C2D system.). I think another reason FT doesn't do KSEA, is they would have to produce 2 versions. One for default/UTX and the other for Orbx PNW, as elevations are different.

Yeah - I still have the SEA patch from Anthony and Lawrence! - and still have it installed, running with DX10. If anyone would like it, please pm me.

 

All the Best, 

I read somewhere that the default Seattle area is a frame rate killer in FSX.  Add to that a detailed KSEA with add-on aircraft and its off to OOM county bud!

I think that was the majority of cases a few years back. Now with much better hardware, KSEA is decent. I get about 20fps which is good for me. CYVR I have with FSDT and the PNW and that sits around 18-22.

As for OOMS, that is all relative. Depends how much extras your running and to what detail. I get worse performance oftentimes on the east coast because of the plethora of airports and AI. In the PNW there is so much coast line and mountains to draw, that is the bottleneck. If you manage it properly, there is no big issues like before. If airports like KLAX are done in that urban jungle there is no reason not to have KSEA with Boeing being the pinnacle of it all. 

I so long for a good fsx PDX & SEA

 

Sent from Samsung Galaxy Note 2

 

 

 

@ High Towers

 

I have learned my lesson around Vancouver. With FSDT CYVR, Orbx PNW, REX, UT2, FSAddon Vancouver, NGX its a guarantee OOM!! I just had high expectations out of FSX but have since discovered what VAS is all about....somehow cant help to think that KSEA would be no different but like you said its all about how you manage it all.

is there a particular reason why Fly Tampa doesnt want to revisit doing KSEA properly for FSX?

 

The coast line is a nightmare for them. If you to the forums and read you will find it.

@ High Towers

 

I have learned my lesson around Vancouver. With FSDT CYVR, Orbx PNW, REX, UT2, FSAddon Vancouver, NGX its a guarantee OOM!! I just had high expectations out of FSX but have since discovered what VAS is all about....somehow cant help to think that KSEA would be no different but like you said its all about how you manage it all.

 

The thing you got to understand, some of the techniques used by developers are great if you can get them to run, but are not officially supported by FSX. 4096 textures look great, but they push the sim to it's limit, that's why you get the OOMs with Orbx PNW. The FSX SDK itself states the texture limit for FSX is 1024x1024x32. It's great if you can get it work, but don't be surprised when it doesn't. One of the reasons I stopped using PNW was I was flying a fight from JFK to KSEA so I had PNW activated, and I kept Ooming before I even got off the ground at JFK. Set back to default (UTX) no problem. This was consistently repeatable. Still running FSX in 32bit Vista I have found there are ways to manage it, but it's a little inconvenient. For the NGX use the low res VC option. Also if you can reduce the size of the external textures to 1024x1024. Really you don't lose that much, and FSX will be more stable. The best way to manage it though, is to control what addon DLL's get loaded at startup. Add the following line to each addon section in the dll.xml file to each addon you don't always use for every flight (Mostly aircraft addons). You don't need to load Captain sim dll's when you are flying the NGX and vice versa! Don't put it on dll's you want loaded all the time, like FSUIPC.

 

<ManualLoad>True</ManualLoad> - If the line is already there but set to False, just change to True.

 

Now when you start FSX it will ask you if you want to run the dll, say no to all but the ones you are using for the current flight. As I say a little inconvenient but worth the effort!!