Prepar3D version 1.4 on 20th August

Lockheed-Martin have announced that the next version of their Prepar3D simulator, version 1.4, will be released as a full new download on 20th August 2012.

The new release is described as being primarily for addressing software bugs and performance updates, but in addition to this there are two new aircraft – the Mooney Acclaim from Lionheart Creations and T-6 Texan II from Iris Simulation Software – both names very familiar to the FS community. The update also brings certification for AMD’s “Eyefinity” multi-screen display technology.

Some questions and answers about the new release can be found on the news announcement at the Prepar3D website, here.

Just to clarify, the image above also includes 3rd party scenery from Orbx and is not representative of the default P3D landscape. Sorry!

0 0 vote
Article Rating
6 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
Ian P
Friday, August 17, 2012 18:41

Er, yes, Boerries. That’s what I said. 🙂

Boerries
Friday, August 17, 2012 17:02

H Ian,
look at the comments from ” imcp3137 ” and “dafyddp3d” at the end of the site.

Quote: “Quick query – will v1.4 installer require complete un-install of v1.3?”

imcp3137 says

“Yes, see above reply to my similar question.”

Not so good

Boerries

Ian P
Friday, August 17, 2012 16:55

Tell me about it. I downloaded and reinstalled two days ago!

The good news? It means I only have a handful of add-ons to put back in and most of those are simple ones. I think I’ll hold off on installing any more for now.

I did say in the article that it was a new full download. It’ll be interesting to see what the enhancements are, though.

Boerries
Friday, August 17, 2012 16:49

Outch! You need to reinstall P3d completly new, to get the new version, it´s not an update, it´s an upgrade. 🙁

Not so fine news for those who installed addons n P3d.

Boerries

Ian P
Friday, August 17, 2012 16:40

I decided it was so good that you needed to see it twice. 😉

Sorry about that; it was a copy and paste error while incorrectly correcting an earlier typo. Now fixed. Thanks!