Great news. Bit odd though because yesterday or the day before Scott of A2A posted that making their planes v3 compatible could be very complicated and that it would come at a cost... which on its own was also odd because there already are users who us A2A planes in v3...

 

Ah but that's probably meaning compatible  in the "new " structure mode, whereas the beta testing used the v2.x type installer in v3 beta - i.e. the 2.x folders structure - and that is what the current A2A in v3 people are using . . .

I am willing to install the A2A Pipers via the old installers and suffer the consequences when it is time for P3D v3.1. The default GA planes are just so blah!

Tired of all this.  LM have recommended something, but appears most/all developers not going to do at moment - apart from Mindstar that is ;-)    OrbX won't, LM will live with it for example.  v3 works pretty good.  Having lived with various updates/hotfixes reasonably well, don't care a monkeys whether a 3PD uses  "old" structure or a "new", just want it now.  Did I say P3D v3 works pretty good?

 

I'm sure a lot would appreciate if we get back to Rich's original posit.   Tell us what what works, whether in old structure or a new, providing it's a developer installer method, not a hack.

 

Did i say v3 pretty good? Just get it, try it, hope the 3PDs get their stuff out ASAP so we can stop argueing and get flying. 

 

So as Rich said, what works with v3?

On FSUIPC, if you install the latest non-beta production release into FSX or P3D V2 and register it, then install the 4.945a beta, it'll find and install to P3D V3 on its own and then you should get a registration window that lets you keep the existing resitration.  At least that's how it worked for me.

 

Regards

 

 

Thank you for info. Have just uninstalled v.2.5, so i wait in Pete to sort it out. ;-)

So as Rich said, what works with v3?

 

Thanks Mike I was shooting for a thread I could go to and see what I could load next without having to do the google search every hour lol

From airdailyx

 

NEWSLETTER FROM 29PALMS STORE

You are receiving this e-mail since you have registered for our Newsletter. Thank you! 

Wanna walk around your biz-jet at Twentynine Palms? You can! The scenery is now fully compatible with Prepar3D v3 and open for exploration with P3D's new avatar feature.

If you bought the scenery from our shop, you can find the new installer in your order history. KTNP has been updated to v1.11, changelog:

• Sandstorm night shading fixed

• Airport layout now compatible with P3D v3

The other shops should have the new installer online soon, probably early next week

 

=====================================================

 

Also Zinertek hd works for runway and building textures

Ok... this is easy. Assuming that the order of entries in the texture.cfg file is the order of searching for a given file (it should be)... then whichever version of a physical file you find first is the one that gets used.

So is what we're running into here a situation where developers who currently overwrite (any?) core sim files can (a) install their content o/s the core folders; and (b) maintain the primacy of their material simply by adding an entry in the right order in the relevant cfg file ?

 

Would/should this work for absolutely every core file? effects? textures? simobjects? landclass lookup tables? custom autogen definitions? living world stuff? Cheers k

I fixed the installer of FS Global Ultimate to support Prepar3D v3 (UNOFFICIAL)

 

The new installer could be found here:

http://1drv.ms/1LZLhhL

 

 

p.s. If someone would like know technical details how the installer works - contact me.

 

I'm very curious to see how popular texture replacement products like for example FTX Global or REX will solve the challenges imposed by the new recommendations.

 

Ok... this is easy. Assuming that the order of entries in the texture.cfg file is the order of searching for a given file (it should be)... then whichever version of a physical file you find first is the one that gets used.

 

The version of the physical file found first will be the default file in the folder containing the texture.cfg. To my knowledge textures have to be missing from the folder containing the texture.cfg before the sim goes looking in the fallback folders defined within. If that's the case (and it always has been from FSX through v2.5) there's no way something like FTXG will work in an external folder, they'll have to overwrite the default files or the sim will simply ignore the FTXG files in the fallback folder, satisfied because it found the defaults in Scenery\World\Texture.

 

I don't have v3.0 yet, maybe I'm missing a big piece of the puzzle but I don't think so.

The version of the physical file found first will be the default file in the folder containing the texture.cfg.

The "texture.cfg" referred to is the one in the P3D programdata folder Jim.

 

It got introduced in v2.something.

 

Mine looks like this, the last entry is my own:

[Entry.0]
Title=Default Textures
Path=Texture
Type=Global
Required=True
Active=True
[Entry.1]
Title=Default Global Scenery Textures
Path=Scenery\Global\Texture
Type=Global
Required=True
Active=True
[Entry.2]
Title=Default World Textures
Path=Scenery\World\Texture
Type=World
Required=True
Active=True
[Entry.3]
Title=PZ_Inc Textures
Path=F:\PZ_Inc\Texture
Type=Global
Required=True
Active=True

I should think it was possible to "get in" before the stock textures by rearranging the sequence in this file, but I haven't tested it yet.

 

- JP

I fixed the installer of FS Global Ultimate to support Prepar3D v3 (UNOFFICIAL)

 

The new installer could be found here:

http://1drv.ms/1LZLhhL

 

 

p.s. If someone would like know technical details how the installer works - contact me.

Thanks!!

No hope Rich, the threads been hi-jacked . . .

GREAT NEWS from A2A just now on their forum:

 

"Just an update - I'm happy to say that so far we've seen no issues with the release version of P3D V3, so we're working on P3D V3 installers now and these will be available to all A2A P3D customers free of charge. We will be releasing these as soon as we can."

 

So the installers aren't available yet but they will be soon and free of charge too!

Thanks Jeroen, this are really great news! The default GA planes coming with P3D are a bit underwhelming, aren't they?

 

Kind regards, Michael

The default GA planes coming with P3D are a bit underwhelming, aren't they?

 

 

 

Understatement of the year. :wink: I need my Comanche badly!!!

 

And yes, it's great: after A2A Scott's initial posts about the updates I was a bit scared we had to wait long and pay big time so I am very happy to hear things have changed for the good this fast!