Hi,

 

I am just a little confused on the pnw installs, primarily the patches,  as some of these appear not to be compatible with p3d2 for one reason or another. The comments about this are a little bit confusing.

I do own the Estonia migration tool, and I know it installs the patch's properly as far as location ect, but are the patch's actually compatible with p3dv2?

 

Any help would be much appreciated.

 

Regards

Bob

Hi,

 

PNW (as most of the other ORBX areas) is not yet compatible with P3D2, and ORBX advises against installation using a migration tool.

 

The only P3D2 compatible areas so far are AUS, IRL and NIR.

 

Kind regards, Michael

Hi,

 

PNW (as most of the other ORBX areas) is not yet compatible with P3D2, and ORBX advises against installation using a migration tool.

 

The only P3D2 compatible areas so far are AUS, IRL and NIR.

 

Kind regards, Michael

 

Hi Michael,

 

I did see that the installer is only compatible with p3d 1.4. - I know that the migrator tool will install all of the pnw patch's but I guess there must be an issue with the textures or something because many who have it installed in p3d2 have issues. I wish someone could explain if it is an improper install or just an incompatiblity with the textures or something else internal with ORBX.

 

Bob

I installed PNW into P3D2 and apart from some minor display issues (e.g. wrong tree textures which can be easily fixed) it works fine! Definately worth trying. However, once Orbx releases the P3D2 versions of the NA regions, I will do a clean install of P3D2 to make sure everything works perfectly.

 

 

but I guess there must be an issue with the textures or something because many who have it installed in p3d2 have issues. I wish someone could explain if it is an improper install or just an incompatiblity with the textures or something else internal with ORBX

 

PNW isn't compatible yet: that's the only real 'issue'. That migration tool is one of the worst addons ever (imho of course) because it causes a lot of problems: you can't simply install incompatible addons into P3D v2 with that tool and expect things to work. If that tool hadn't been available, that would have saved us a lot of useless topics. (It amazes me so many people actually paid money for it...!)

But what is the problem with the PNW region in P3D2? The only problem with the Orbx regions is really the Orbx libraries (apart from the errors in P3D2 itself, like the white boxes error). Since Orbx has released a preliminary version of the Orbx libraries for P3D2, all the regions work fine in P3D2... Performance is excellent, which is the main problem with addons that are really incompatible (like addons made for FS9).

PNW isn't compatible yet: that's the only real 'issue'. That migration tool is one of the worst addons ever (imho of course) because it causes a lot of problems: you can't simply install incompatible addons into P3D v2 with that tool and expect things to work. If that tool hadn't been available, that would have saved us a lot of useless topics. (It amazes me so many people actually paid money for it...!)

 

I'm surprised, Jereon. I paid for it, and it really simplified my life when migrating from FSX to P3D 1.4. Orbx PNW is a perfect example: I have the base product on DVD, FSX-only. The patches (we are up to 7 now) flip-flopped back and forth between having a path for P3D to FSX-only, but using the EMT made this a non-problem.

 

I think your first sentence is the better summary.

All, it would seem to me too, that the install location of the product is all that EMT claims it can do. It would also seem more important that when FTX Central is running or executed, and one moves from North America to default and visa-versa is where most of the issues come into play. ORBX does make a considerable amount of references to other files and their entries, that if not managed properly, a fault will most likely occur. At least this has been my experience. So those little associated exe files can be a problem. As far initially setting up those file pointers when PNW is initially run with EMT, I think it does a good job. I was really wondering why so many had texture issues. I personally believed just from a logical point of view that a texture is a texture and who cares who made it. If that texture is not where it is supposed to be then logically that could cause an issue. I wish I knew more because I really am hooked on the ORBX regions and airports. Not having this scenery is like flying one of the crappy default aircraft offered in FSX.

 

Bob

As Scenery designer, and by no means am I comparing myself to the likes of Arno, or Scruffy, but I have done some projects in FS 2004 and FSX, I would like to know what is it that makes my and professional scenery objects from Orbx, compatible or incompatible with P3Dv2 as opposed to P3D v1.4.

 

Yes I know that this might be moved to Scenery Design area, but I think it could be helpful for those of us that do scenery design to learn from the mistakes/experiences of pros like Orbx.

 

Regards,

Chas