Seattle Airports X 1.1 with new KSEA this weekend.

[trisho0 23]

Found that only one Developer of KSEA scenery can share SODE in FSX with P3Dv4. We need to decide which KSEA scenery will be installed if we have both sims as FSX and P3Dv4. We can't have T2G KSEA with DRZEWIECKI DESIGN Seattle KSEA due to double jetways even if one of the KSEA scenery is disabled.

[trisho0 23]

3 hours ago, Nemo said:

wrong citation.

Developer updates is needed then?

[DrzewieckiDesign 91]

7 hours ago, trisho0 said:

Found that only one Developer of KSEA scenery can share SODE in FSX with P3Dv4. We need to decide which KSEA scenery will be installed if we have both sims as FSX and P3Dv4. We can't have T2G KSEA with DRZEWIECKI DESIGN Seattle KSEA due to double jetways even if one of the KSEA scenery is disabled.

Hey.

This is not really correct. When our KSEA is deactivated, it also removes our KSEA SODE content, so everything is done automatically and there are no active files left. On the other hand, to de-activate T2G's KSEA you probably need to manually remove their SODE files from C:\ProgramData\12bPilot\SODE\xml and C:\ProgramData\12bPilot\SODE\Simobjects folders. Or maybe their config panel is able to temporarily disable the airport completely? Obviously, if their SODE jetways are not removed, you are going to see double jetways.

For the mesh issues, please make sure that you have AEC (ORBX) disabled for all included airports (or just run AEC and check the result) ...and that our product is on the very top of the scenery list.

Edited April 30, 2018 by DrzewieckiDesign

[Benjamin J 751]

So what's the verdict? it sounds like they are pretty much about equal visually as well as performance wise? I have T2G, but would get DD's KSEA if it means better performance.

[Wise87 1,281]

9 hours ago, DrzewieckiDesign said:

Hey.

This is not really correct. When our KSEA is deactivated, it also removes our KSEA SODE content, so everything is done automatically and there are no active files left. On the other hand, to de-activate T2G's KSEA you probably need to manually remove their SODE files from C:\ProgramData\12bPilot\SODE\xml and C:\ProgramData\12bPilot\SODE\Simobjects folders. Or maybe their config panel is able to temporarily disable the airport completely? Obviously, if their SODE jetways are not removed, you are going to see double jetways.

For the mesh issues, please make sure that you have AEC (ORBX) disabled for all included airports (or just run AEC and check the result) ...and that our product is on the very top of the scenery list.

If I remember correctly some of your airports are not listed in AEC.

[Wise87 1,281]

9 hours ago, DrzewieckiDesign said:

Hey.

This is not really correct. When our KSEA is deactivated, it also removes our KSEA SODE content, so everything is done automatically and there are no active files left. On the other hand, to de-activate T2G's KSEA you probably need to manually remove their SODE files from C:\ProgramData\12bPilot\SODE\xml and C:\ProgramData\12bPilot\SODE\Simobjects folders. Or maybe their config panel is able to temporarily disable the airport completely? Obviously, if their SODE jetways are not removed, you are going to see double jetways.

For the mesh issues, please make sure that you have AEC (ORBX) disabled for all included airports (or just run AEC and check the result) ...and that our product is on the very top of the scenery list.

If I remember correctly some of your airports are not listed in AEC.

[trisho0 23]

11 hours ago, DrzewieckiDesign said:

This is not really correct. When our KSEA is deactivated, it also removes our KSEA SODE content, so everything is done automatically and there are no active files left. On the other hand, to de-activate T2G's KSEA you probably need to manually remove their SODE files from C:\ProgramData\12bPilot\SODE\xml and C:\ProgramData\12bPilot\SODE\Simobjects folders. Or maybe their config panel is able to temporarily disable the airport completely? Obviously, if their SODE jetways are not removed, you are going to see double jetways.

Stan, glad to see you here in this thread and congratulations for all of your amazing sceneries.

I have T2G KSEA in FSX with DD Seattle Airports X without DD KSEA.
Also, installed only DD Seattle Airports X complete in P3dv4. T2G KSEA not installed in P3Dv4.

SODE from DD is injected in FSX T2G KSEA.
SODE works fine in P3Dv4 with DD Seattle X.

So, only one Developer KSEA can share SODE for now.

(Exactly the same SODE issues with Tropical KDCAx in FSX with DD Washington X installed in P3Dv4.)

On the another hand, the T2G KSEA shows black squares around unless the DD Seattle X\Scenery, some Sea_FT...bgl files are off (Sea_FT_CN.bgl, Sea_FT_N.bgl, Sea_FT_S.bgl and Sea_FT_SS.bgl)

After renamed Sea_FT ...bgl files to Off ....

 

 

[trisho0 23]

11 hours ago, DrzewieckiDesign said:

For the mesh issues, please make sure that you have AEC (ORBX) disabled for all included airports (or just run AEC and check the result) ...and that our product is on the very top of the scenery list

I don't have ORBX or any other similar programs in none of my fs9, FSX and P3Dv4 sims (same PC machine)

[trisho0 23]

3 hours ago, Benjamin J said:

So what's the verdict? it sounds like they are pretty much about equal visually as well as performance wise? I have T2G, but would get DD's KSEA if it means better performance.

I prefer DD Seattle City X and Seattle Airports X in P3Dv4 sim. Unfortunately, Taxi2Gate KSEA must be removed if you have 2 sims because of SODE Jetways and others terrain issues. DD states their Seattle Airports X is compatible with KSEA T2G which you may want to find out with your machine. You may have different configuration. So, no verdict I guess ...... I wish to have DD KSEA in P3Dv4 with T2G KSEA in FSX but is nightmare to have 2 different ICAO developer in the same machine because SODE is sharing for both sims.

I think SODE programmers could add a feature settings allowing us to select or deselect airports from different sims in order to activate Jetways. From SODE we can deactivate the whole Jetways for a selected sim but not for individual airport. Maybe in the future SODE can bring up with more options.

 

[trisho0 23]

Found another FSX DD Seattle KSEA issue which it shows white bridges ....

I think is texture problem but don't know what texture file is doing that. Maybe a DD Seattle KSEA texture file from P3Dv4 could be used to fix. Any other thoughts?

Edited May 1, 2018 by trisho0
corrections

[Boomer 1,619]

Link to purchase please...reward my laziness.

[B777ER 2,486]

4 hours ago, Boomer said:

Link to purchase please...reward my laziness.

LOL! But I'm feeling even lazier so no link.

[Egbert Drenth 250]

8 hours ago, Boomer said:

Link to purchase please...reward my laziness.

Link

[Wise87 1,281]

Today I was able to install the updated version of Seattle Airports. I am seeing a few strange elevation issues. I see some minor issues around KSEA but there not deal breakers for me. but at KPAE I see a hill by the parking lot. 
https://prntscr.com/jcdruh

I did not have this issue with the initial release. 

I run P3Dv4.2
Mesh Resolution 5m
Texture Resolution 7cm
FS Global Ultimate - Next Generation FTX <--I tried adding the AFM - Aerodrome Flattening Meshes and it made the area worse. 
FTX Global BASE Pack 
FTX Global openLC North America
FTX Global VECTOR <---Ran the AEC auto update. Enable/Disable made no difference.

I also disable Global Mesh, FTX NA LC and the issue was still there.

[Boeing or not going 578]

4 minutes ago, Wise87 said:

Today I was able to install the updated version of Seattle Airports. I am seeing a few strange elevation issues. I see some minor issues around KSEA but there not deal breakers for me. but at KPAE I see a hill by the parking lot. 
https://prntscr.com/jcdruh

I did not have this issue with the initial release. 

I run P3Dv4.2
Mesh Resolution 5m
Texture Resolution 7cm
FS Global Ultimate - Next Generation FTX <--I tried adding the AFM - Aerodrome Flattening Meshes and it made the area worse. 
FTX Global BASE Pack 
FTX Global openLC North America
FTX Global VECTOR <---Ran the AEC auto update. Enable/Disable made no difference.

I also disable Global Mesh, FTX NA LC and the issue was still there.

Unchecking scenery in the scenery.cfg will not fully disable the scenery. Many altitude files remain in scenery \ world \ scenery

Scanning AEC checks only scenery.cfg unless you have Lorbys Addon-Organizer and use the export scenery tool. Scenery with add-on.xml are not found by AEC

Disable all Orbx files in Orbx regions for the airport if you have other airport scenery.  A CVX, Afcad, and objects bgl file

Edited May 1, 2018 by Boeing or not going