Sign in to follow this  
amalishkin

P3D V3.3 incompatible Sceneries

Recommended Posts

Could we start a list of all scenery products that are not working with V3.3 i think it would help people make a decision to move or not, some of us moved and are early adopters and maybe can help others to make sure they know what they jump in.

 

 

I have following that are not working:

 

 

Aerosoft PAFA

Aerosoft PANC

FlyTampa LOWW

 

 

More coming.

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Aerosoft LPFR

Taxi2Gate LTBA

 

I bet the aerosoft list will grow like mad. Just a hunch.

Share this post


Link to post

Vienna is out? Can anyone with 3.3 check FT's Copenhagen please? If not also Orbx's Oslo? If uk2000 airports are off the list for the time being, it would be helpful to know whether EKCH and ESSA are working.

Share this post


Link to post

Remember that the right thing to do is to put some well deserved pressure on the developers of these sceneries instead of just stop upgrading P3D versions. Developers/resellers like Aerosoft are really spoiled when it comes to not having to release any updates ever. If they whink that they can still handle P3D as they handled FSX, i.e. release an addon and never update it, they are dead wrong. They are the ones that should lose money because of this. LM is moving forward, they are doing the right thing. it's time for the 3rd party developers to wake up if they still want to get our money.

  • Upvote 2

Share this post


Link to post

I agree partially... I don't see Aerosoft (or any other developer) updating 10 year old sceneries for this new version, nor do i expect them to do that. It would be nice, but i don't see it happening.

  • Upvote 2

Share this post


Link to post

I do also see an other problem: V3.3 breaks - "by design" - the compatibilty with older airports, forcing developers to work with the P3D SDK (which is fine). We customers however are urged to buy those P3D-compatible sceneries again, which are not necesarily better than the old ones (see Aerosoft Berlin Tegel, EDDT). At this point you have spent the money twice for the same airport.

 

If LM should decide to jump on 64bit with version 4 (maybe at the end of this or next year), yet again, you are forced to buy all the 64bit-compatible airports. This would be the 3rd time for the same airport within a short period of time. Development requires losses, we all now. But I had wished that the loss of compatibility would occur only when changing the platform fundamentally.

Share this post


Link to post

Please Note: 

 

Regarding Updating Prepar3D using the Update Installers:

 

Yes,  there is Some Airports that have been effected,  But If your Updating Scenery and if you have FTX Global Base,  you need to Run the FTX Global Installer again.

 

When you Update Scenery,  The Textures in Scenery\World\Textures are over written back to Default again and this will directly effect ground Textures, Thus effecting Global Base

 

Before you post problems,  Be sure to run the FTX Global Installer again (if you have it)   you don't have to Uninstall it,  Just run the Install again 

 

Re-Run FTX Orbx Libs again as well 

Share this post


Link to post

I agree we don't have to purchase "P3D compatible" sceneries all over again - If they're sold/advertised as compatible and being compiled with FS2002 tools, we're actually being fooled by the developers - There should be a free update for all of them.

 

I find it hard to believe we're purchasing airports compiled with 10-year-old tools :(

  • Upvote 1

Share this post


Link to post

Gary Summons has already responded and is going to update his airports - but it is going to take a while.

 

Read this post for more info....in short he is happy that LM are doing away with legacy code even if it is going to cause some headaches in the meantime

 

http://www.uk2000scenery.org/forum/index.php?topic=8548.0

  • Upvote 1

Share this post


Link to post

Aerosoft made a very good statement in regard of the loss of compatibility with recent v3.3, and I am 100% conform with that:

 

Mathijs Kok: "What is clear however is that P3D will be a less attractive platform for many developers. Making these updates on an existing product could easily eat up the profit on a product. And you run the same risk in three months."

 

http://forum.aerosoft.com/index.php?/topic/112689-info-regarding-the-problems-with-p3d-33/#comment-758919

Share this post


Link to post

I don't see Aerosoft (or any other developer) updating 10 year old sceneries for this new version, nor do i expect them to do that. It would be nice, but i don't see it happening.

 

For me, it is also not even close to be reasonable to ask this from the developers. ONLY from those addons where explicit P3Dv3 compatibility is granted in the product description we can ask an update from the developers. Everything else is up to them, either they have time and resources to do it, or not. We can certainly not ask a scenery to be updated that we installed into our P3Dv3 by using migration tools or by telling the installer that our FSX folder is called Prepar3d. That's one of the reasons why I started to use almost purely P3Dv3 compatible addons since my switch over from FSX, I was somehow expecting this was going to happen sooner or later.

  • Upvote 1

Share this post


Link to post

Aerosoft made a very good statement in regard of the loss of compatibility with recent v3.3, and I am 100% conform with that:

 

Mathijs Kok: "What is clear however is that P3D will be a less attractive platform for many developers. Making these updates on an existing product could easily eat up the profit on a product. And you run the same risk in three months."

 

http://forum.aerosoft.com/index.php?/topic/112689-info-regarding-the-problems-with-p3d-33/#comment-758919

I was thinking about this last night, and if I were developing a product for P3D, it ls like trying to take aim at a moving target.  Look at all the updates that developers have created in the last few months and they are probably counting on having to do this again when 3.4 comes in in a few months. 

Share this post


Link to post

This is a great thread but, also, we need to have a list we can maintain...e.g. aggregated and marked as fixed when they are.

  • Upvote 1

Share this post


Link to post

 

 


That's one of the reasons why I started to use almost purely P3Dv3 compatible addons since my switch over from FSX, I was somehow expecting this was going to happen sooner or later.

 

Stating P3Dv3 compatibility does not guarantee 3.3 compatibility though, I have many V3 compatible sceneries that apparently no longer work in 3.3

No point in buying any more sceneries if point releases are going to break them, especially with 64bit on the horizon when we will most likely have to buy them all over again.

 

3.2 is fine anyway.

Share this post


Link to post

Hi again.

 

This statement from Aerosoft isn't customerfriendly.

I am willing to pay 10 dollars more per airport and scenery if aerosoft keep them up to date.

But now i have bought many scenerys from aerosoft, that i can't use anymore? And this wasn't the first time. I have scenerys from P3D V2 wich doesen't work in V.3.

What do you think, will i buy in the future? Aerosoft? I don't think so.

What will they do, if other customers think like me? Quality and service (this includes updates) should be a attribute of a company like Aerosoft.

When they could't offer this then shouldn't they stop to develop for P3D.

 

LM said long before that they don't provide the legacy developement tool anymore.

  • Upvote 1

Share this post


Link to post

Hi again.

 

This statement from Aerosoft isn't customerfriendly.

I am willing to pay 10 dollars more per airport and scenery if aerosoft keep them up to date.

But now i have bought for many scenerys from aerosoft, that i can't use anymore? And this wasn't the first time. I have scenerys from P3D V2 wich doesen't work in V.3.

What do you think, will i buy in the future? Aerosoft? I don't think so.

 

The problem of AS is not the statements they give regarding "older" sceneries where not even v3 compatibility is written on the box, the problem is what is stated a little bit lower in this AS thread. For me, this is not at all surprising and simply is in line with all other ridiculous support behaviours over at the AS forums. Those guys are always right, never to blame and actually don't really care about their customers. Statements like this are driving me furious...

 

"If you bought a V3 Product since the release of P3D V3.3 and this does not work, we are more then happy to find a solution for you, but only if you bought it after the release of V3.3 with the Product Information say P3DV3."

 

This is just illustrative of how AS always tries to dodge responsability, unbelievable...

  • Upvote 1

Share this post


Link to post

Its a new dynamic for some of the older Devs to adjust to - In years past the FSX franchise was frozen for a very long, long time (after SP2/Acceleration release in 2007) and so they appear stubborn to adjust to a new era of Flight Sim where LM are actively improving their product. 

 

Devs such as AS - It will be to their detriment in the near future to stone-wall customers in the present. There are plenty of smaller developers with ambition who will take the business. 

Share this post


Link to post

Aerosoft made a very good statement in regard of the loss of compatibility with recent v3.3, and I am 100% conform with that:

 

Mathijs Kok: "What is clear however is that P3D will be a less attractive platform for many developers. Making these updates on an existing product could easily eat up the profit on a product. And you run the same risk in three months."

 

http://forum.aerosoft.com/index.php?/topic/112689-info-regarding-the-problems-with-p3d-33/#comment-758919

 

If they (and others) would have strictly followed P3D requirements (P3D SDK) there would be less problems now and in future.

  • Upvote 4

Share this post


Link to post

If they (and others) would have strictly followed P3D requirements (P3D SDK) there would be less problems now and in future.

 

Interesting statement.

If PMDG, ASN, GSX, FS2Crew, A2A, ORBX, SODE and a dozen of other - innovative - companies followed JUST the FSX or P3D SDKs, you wouldn't have any of their products. Neither in the past nor today.

Share this post


Link to post

Interesting statement.

If PMDG, ASN, GSX, FS2Crew, A2A, ORBX, SODE and a dozen of other - innovative - companies followed JUST the FSX or P3D SDKs, you wouldn't have any of their products. Neither in the past nor today.

 

Second interesting statement... Funny enough that PMDG, ASN, GSX, FS2Crew, A2A, ORBX and SODE all work with Prepar3d v3.3. The statement of nemo is obviously only regarding the development of sceneries, no? And just read Gary Summons explanation why his UK2000 sceneries are incompatible, this is quiet enlighting. But of course, you will never ever hear such a honest statement from those ridiculous guys over at Aerosoft. They continue to blame others when one of their products is not working. It was always like this and will always be like this.

  • Upvote 4

Share this post


Link to post

 

 


Second interesting statement... Funny enough that PMDG, ASN, GSX, FS2Crew, A2A, ORBX and SODE all work with Prepar3d v3.3. The statement of nemo is obviously only regarding the development of sceneries, no?

 

The original statement mentions the SDK.

So sceneries should strictly follow the SDK, whereas other products are allowed to use complementary methods?

BTW, some of the products you name are only compatible with 3.3 after an update.

Many sceneries will be updated too, but because of the huge quantity involved, it's a slightly different and much longer path...

Share this post


Link to post

Aerosoft made a very good statement in regard of the loss of compatibility with recent v3.3, and I am 100% conform with that:

 

Mathijs Kok: "What is clear however is that P3D will be a less attractive platform for many developers. Making these updates on an existing product could easily eat up the profit on a product. And you run the same risk in three months."

 

http://forum.aerosoft.com/index.php?/topic/112689-info-regarding-the-problems-with-p3d-33/#comment-758919

 

Omg, just read the thread at aerosoft. Can't believe somebody is almost openly threatening to sue them !

Talking about legislation and regulation, call your lawyer, and all this BS !

Have to admit I lol'd.

What will happen when 64bit releases ? Do you think he will threatens them physically :lol:

Share this post


Link to post

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
Sign in to follow this