Jump to content
specialist

Compatibility with Orbx PNW?

Recommended Posts

Guys, we are still working, thanks for your patience and support.

 

It is much appreciated... 

 

All good things come to those who wait :)

 

 

I hate to bring it up too but I noticed one small error on the airport itself... There are multiple access roads that have a "YIELD" sign painted on the ground... The scenery has it misspelled as "YELD" ;) A very minor thing at this point though...

 

25f8ac2bb02f283a510fbf247abb7bb9.jpg

Share this post


Link to post
Share on other sites

I already test KSEA with FTX GLOBAL, FTX VECTOR (Disabling KSEA), PNW without any problem, it seems that all having FSGLOBAL is causing a problem, if you have FSGLOBAL, try this:

 

1) go to the following folder: FSGX2010 - Local Meshes - Scenery: change the extension of DX_KSEA.BGL file into DX_KSEA.seattle (in order to inactivate this file)

 

2) go to the following folder: FSGX2010 - NAM - Scenery: change the extension of DX015015.BGL file into DX015015.seattle (in order to inactivate this file

Share this post


Link to post
Share on other sites

I already test KSEA with FTX GLOBAL, FTX VECTOR (Disabling KSEA), PNW without any problem, it seems that all having FSGLOBAL is causing a problem, if you have FSGLOBAL, try this:

 

1) go to the following folder: FSGX2010 - Local Meshes - Scenery: change the extension of DX_KSEA.BGL file into DX_KSEA.seattle (in order to inactivate this file)

 

2) go to the following folder: FSGX2010 - NAM - Scenery: change the extension of DX015015.BGL file into DX015015.seattle (in order to inactivate this file

 

 

Still no joy...

 

While I have FSGlobal 2010 installed, it is not active in my scenery library (You can also see I have disabled Vector here too)

 

41936d8059edad20fdc75b38dfeb9ac4.jpg

 

 

I still get the same lowered terrain around KSEA, and the cliffs all round the airport boundary. I also followed your instructions and renamed those specific files in the FSGlobal 2010 folder, just to be thorough.

Share this post


Link to post
Share on other sites

Update to above post:

 

I have now completely removed FS Global 2010 from my system. It is no longer installed, and has been removed from my scenery library... The results (now with just Vector - KSEA disabled, and PNW) are shown below (same result as before):

 

2115c47e30aed6a164fc25480eac33a0.jpg

 

3cce496190e6674051f03d51f54bb85e.jpg

Share this post


Link to post
Share on other sites

So far, the only combination that allows the airport to function is to disable the FTX PNW mesh files... If I do this, then the standard default mesh is used and the airport does fit nicely.

 

 

 

Of course this is not an ideal solution as disabling the FTX mesh for PNW reduces the quality of a large part of the PNW package, and causes problems with other airport addons in that area, designed to fit with the FTX PNW mesh.

Share this post


Link to post
Share on other sites

I believe I can explain the issue... This theory fits with the results I (and others) are seeing...

 

Orbx FTX region airports all have hand crafted flattens to blend them into the surrounding terrain. In the case of KSEA, the terrain mesh itself is considerably lower than the airport elevation. This screen shows a small cross section of the PNW mesh at the south end of Rwy 34R. Note I have disabled the T2G KSEA and PNW KSEA (showing only the default KSEA airport). Once the edge of the airport boundary is reached, the drop off (green) creates a cliff between the airport elevation and the mesh below (though in this case, because the default KSEA has no airport boundary data, the runway end is floating):

 

8d43e3cb247ac4c0f7b9bf316c99d214.jpg

 

 

 

This next shot shows how Orbx has created a hand made cross section using sloped terrain flattens. This cross section creates the subtle bank and then blends into the PNW mesh. In effect, the flattens become a hand drawn mesh. Because the T2G KSEA when installed without the fix does not remove the PNW KSEA, these flattens still exist. this explains why my previous show the local surrounding terrain to be higher when the fix is not installed (the flattens are creating the correctly raised terrain).

 

09bc5bf154c7ae12b0ada12355c186f0.jpg

 

 

 

Finally, with the T2G KSEA and fix installed... The fix somehow (either via an exclude file of some other means) disables the PNW KSEA. This also disables the hand made flattens as these are a part of the PNW KSEA airport files. Without the flattens in place, the surrounding terrain is now drawn at the mesh height, not the flatten height, causing large, automatic drop offs and cliffs. Ideally, sloping flattens could be created that blend the new T2G boundary into the PNW mesh, similarly to how Orbx did with their KSEA. This would both blend the edges smoothly, and raise the surroundings to the correct elevation (getting rid of the drops and floating monorail etc).

 

12f0f1100be10c8c729293b15e660d0a.jpg

 

 

 

This also explains how disabling the PNW mesh "fixes" the T2G airport... doing so simply enables the default mesh and this default mesh is flatter and not reflective of reality.

 

 

 

Of course T2G are working on it, and this may already be known, but just in case... these screenshots help explain all the issues I have been experiencing... It also explains how Vector and FSGlobal configurations (whether installed, active, disabled or uninstalled) make no difference, at least to me and some others.

 

Take these as you see fit... They are just my theory, but it may help narrow down the search for a solution...

Share this post


Link to post
Share on other sites

Hello Guys thanks for your interesting posts. Just to sum up:

As also I've tried to explained in this topic: http://www.iflysimx.com/topic/1164-house-in-air-right-rwy-16c/if no ORBX PNW is installed there are two issues:

- One with FSGlobal: follow the abovementioned topic in order to delete the interferences. (Disable to BGL files)

- One with ORBX Vector: as frequently occured with T2G sceneries is important to disable KSEA AEC file via the VECTOR dedicated control panel. 

 

No issues (please refer to the pictures contained in the topic) are present

 

With ORBX PNW, it's another completely different situation. When this amazing scenery is installed the structure of this USA area is completely shaked up since this complex scenry contained different levels (mesh, terrain, etc).

 

Just waiting the T2G advancements and for sure you can have the compatibility in the next few days

 

Cheers

Share this post


Link to post
Share on other sites

Gents!

 

Again I can confirm Rob's findings and that Siberian Airlines' ones doesn't work if someone like me uses the "whole bunch".

 

Hope  T2G willluckyly find out  a complete solution...

 

Best for now!

 

Bert

FS MAGAZIN

Share this post


Link to post
Share on other sites

Guys, i test and test and i dont have problems, i had fsx without addon then i install ftx global, ftx vector, pnw and test it like that, then i install KSEA-T2 without patch and has problems with mesh, then i isntall patch and problems gone, its fully compatible with FTX GLOBAL, FTX VECTOR and PNW, i think is something else your problem, maybe a bad installation of the patch? check you library also if KSEA is up there please.

Share this post


Link to post
Share on other sites

Hi!

 

has someone installed a AFM-Mesh from the FSGlobal package - these are "micro-Meshes" to enhance airports to better fit with FSGlobal.

 

unfortunally they are installed in a folder completely outside FSG and scenery directories (../Pilots/AFM/...) and in many cases they worsen compatibility, especially where an airport brings it's own mesh.

Share this post


Link to post
Share on other sites

Guys, i test and test and i dont have problems, i had fsx without addon then i install ftx global, ftx vector, pnw and test it like that, then i install KSEA-T2 without patch and has problems with mesh, then i isntall patch and problems gone, its fully compatible with FTX GLOBAL, FTX VECTOR and PNW, i think is something else your problem, maybe a bad installation of the patch? check you library also if KSEA is up there please.

 

Very curious...

 

I am currently downloading the fix again, just in case there was a download issue which gave me a corrupted fix.

 

I am also downloading the manual installation files.

 

Thanks for your patience with us... I know we're a demanding bunch ;)

 

 

I'll post again once I my downloads have completed and I have tested again.

Share this post


Link to post
Share on other sites

T2G, did you ever talked with Orbx about the remaining issues? I reinstalled or rather uninstalled and installed everything during the last few days and it's still not working. Are you sure YOU installed everything correctly? With one of your first patches you replaced some important Orbx files with empty dummies. Did you restored them before working on further patches?

Share this post


Link to post
Share on other sites

Hi guys, any news on the fix and the compatibility with PNW by ORBX?

ORBX has 30% sales within 4 days and if someone can confirm that the mnual PNW fix posted on the T2G sit works, i'll take for sure PNW to improve my washington/seattle area

 

Thanks for your feedbacks really appreciated.

Share this post


Link to post
Share on other sites

Hi Guys.

 

   I hope not to repeat what everyone else is talking about, But I need to know step by step how to fix the Seattle Issue with the scenery. I have tried the installer and it is worse. I also notice that when I was checking out the airport about a thousand feet above the runway there was alot of flickering on the ground airport textures. I am not for sure what is happening here but any help would be great thanks.

Share this post


Link to post
Share on other sites

So far the best acceptable results:

 

PNW only- Install airport + PNW compatability pack then disable the FTX_NA_PNW07_MESH in the scenery library( uncheck the box no need to delete. The result is it looks nearly perfect.

 

PNW+Global+Vector -  same as above but also need to run vector config tool and disable Airport Eleveation Correction for KSEA.

 

In addition if you use FSGlobal2010 (The ORBX compatible version) -  To get rid of the cliffs on the south side by the water and the messed up roads you must disable the DX015015.BGL(just rename it to .disabled on the end or anything so that it won't try to open it as a .bgl) this is in your FSGlobal 2010/NAM/ folder (Thx to Siberian Airlines for this tip) in addition if you had the old airport flattening meshes (AFM)for this product there will be another file  -  see his post .AFM did exactly what AEC in vector does....

 

 

Yes it's not ideal to disable the PNW mesh  BUT the airport will look fine, I tried some PNW airports with it disabled and I haven't seen any problems. I've tested this in both P3D 2.5 and FSX.

 

If you are still seeing problems and you have vector there is a good chance your vector install was messed up. A lot of people got bad installs if they installed 1.2 on a clean install ( but people who updated through patches are not affected)

Share this post


Link to post
Share on other sites

I really dont understand why some people is having this problem, i recently purchase PNW and it include all services pack, using our patch all issue gone, this is very weird.

Share this post


Link to post
Share on other sites

So far the best acceptable results:

 

PNW only- Install airport + PNW compatability pack then disable the FTX_NA_PNW07_MESH in the scenery library( uncheck the box no need to delete. The result is it looks nearly perfect.

 

PNW+Global+Vector -  same as above but also need to run vector config tool and disable Airport Eleveation Correction for KSEA.

 

In addition if you use FSGlobal2010 (The ORBX compatible version) -  To get rid of the cliffs on the south side by the water and the messed up roads you must disable the DX015015.BGL(just rename it to .disabled on the end or anything so that it won't try to open it as a .bgl) this is in your FSGlobal 2010/NAM/ folder (Thx to Siberian Airlines for this tip) in addition if you had the old airport flattening meshes (AFM)for this product there will be another file  -  see his post .AFM did exactly what AEC in vector does....

 

 

Yes it's not ideal to disable the PNW mesh  BUT the airport will look fine, I tried some PNW airports with it disabled and I haven't seen any problems. I've tested this in both P3D 2.5 and FSX.

 

If you are still seeing problems and you have vector there is a good chance your vector install was messed up. A lot of people got bad installs if they installed 1.2 on a clean install ( but people who updated through patches are not affected)

This Actually Fixed the problem Slayer. Thank You. Maybe you should get a Job with Taxi2gate Lol The only thing that is an issue is there is still alot of flicking on the ground scenry of the Airport itself.   I believe it only happens when your about 700 to 1000 feet above the airport textures any tips what might be causing that.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×