FREEWARE AIRCRAFT AND PREPAR3D V4.2

[papituwall]

This is a small not exclusive list of FREEWARE aircraft working in P3D V4.2

INTRODUCTION:

In theory, P3D V4 native aircraft should be considered those airplanes that have been developed/100% modified for P3D V4 and are installed outside the program folder (in Documents). They are launched through their corresponding "addon.xml". This is what is done for example by A2A, Restauravia and some other.
Other aircraft are installed in Simobjects and normally are "100% compatible" P3DV4.
For the purposes of this list I will not distinguish them.

The rest are a variety of FSX aircraft that I have installed in P3D V4.2 and that work with minor faults.

FS9 aircraft don't work in any way, some FSX (few) also not work (normally they are old models).

The general issue (solved) is : Not sound in some items in VC - related to D.Dawson x32 sound gauge, he has published a x64 replacemet. Lots of info in internet.
This mainly affects to "clic" sounds. If you do not care much about listening to those sounds, you can bypass to change that gauge.

NATIVE OR COMPATIBLE

Restauravia: Fouga Zephir & Magister and Dassault Mirage IIIB
Maryadi: Boeing Osprey
Lagaffe: Cessna C150
Yannick Lavigne-Fred Banting-Rob Young,Bluebear: Robin DR400

FSX INSTALLED IN V4

Restauravia: Breguet Alizé, Dassault Etendard, Caudron 460
Dino Cattaneo: Boeing T45, Macchi MB326, Lockheed Viking, Grumman F14, according Dino, minor issues in fuel system.
Milton Shupe: Aero Commander AC560, De Havilland DH60 Puss Moth, Beech18, Spartan Executive
Jahn and others: Douglas C47
UKMIL: Blackburn Buccaneer
Virtual over Italy: Air Tractor
FSX 737, Alrot enhanced: Boeing 737
Tim Piglet Conrad: Embraer A-29, Morane Saulnier MS760, Pilatus PC6 This planes have sound aliased to FSX default planes that are not in P3D, they require a new sound file. Piglet's planes look better than in FSX (maybe because HDR).
LDR Development: Ryan Navion
Ants: De Havilland Tiger Moth

[pete]

Anything FSX native should work & there are 1000's FSX native aircraft.

[Jetranger]

WE can only HOPE that the "FREEWARE" creators & Developers are allowed the same "HOT FIX" and UPDATE to PREPAR3D V4.2 as the Payware Developers ??

So, Lockheed Martin messed up, or so we think and "assume", hopefully they are NOT up to "something sneaky", they aren't telling the rest of the community about, like those dimwits who tried to roll out that disastrous MS Flight a few years ago, that flopped after pissing users off with all the Phony Hype they tried to sell.

Time will tell, within a few months or longer what the real story is gonna be, and the effects it may have on everybody, users & developers.

this may get very inter - esting,, as Schultz would say from Hogan's Hereo's

This surfaced from PMDG's RS Randazzo within the last 20 hours / 2/15/2018

Captains,

As I posted late last night, it appears that some changes were made to the final release version of the "update to Prepar3D v4.2" that were "not part of the versions" giving to the testing community at large, and these changes have had an "unusual impact on the PMDG 747-400" in particular.

By way of making sure we are all talking about the same thing:

Users of our PMDG 747-400 have been reporting that "after updating to P3D v4.2", it was "not possible to use the 747-400" unless first entering the sim using one of the default aircraft.

We have determined what causes this and we are in the process of testing a prototype fix to eliminate the issue for P3D v4.2 users.

I don't want to go into too much detail at this point, but it does appear to be something "Lockheed Martin decided to change" that is "NOT" documented in the SDK.

We will take it up with them, as the change will have a long term effect on users of products like FS2Crew, and as such it probably needs to be addressed by Lockheed Martin long term.

In the mean time, give us a bit of time to validate these tests and once we are comfortable that we aren't breaking anything else in order to fix this- we will push the update to you via our auto-updater. I will also post an announcement about it here as well.



ADDITIONAL VERY IMPORTANT NOTE:

A few folks in the another thread mentioned that they were seeing problems in other PMDG products. We have not seen any verifiable reports that could be duplicated for problems in other products but you are welcome to report them to our support team if needed.

I would also like to remind everyone that we have many tens of thousands of customer data points that we work with community-wide, so it is VERY easy for us to spot actual problems and separate them from problems that single users see that are not necessarily indicative of a problem with our products.

So please: during the complex process of upgrading a sim platform, please keep in mind that many other things you have installed (FSIUPC makes a great example in this case) might need an update from a developer and cause wide ranging problems that are hard to pin down.

Please take the time to remove things and reinstall them in an organized fashion and you will likely find the hassles can be minimized for everyone involved- and you will help to provide the community as a whole more valid data than simple jumping up and down on whatever product you happened to be trying to use when the sim acted wonky.

As is always the case- if/when we find a problem in compatibility between the constantly evolving P3D v4 and our products that can be verified and traced- we will fix it.

I hope we will push this hot-fix to you all during the day Thursday. Stay tuned!


So far to date according to other forums the update also BROKE the FREEWARE AI Carriers - FSUIPC - and a host of other FREEWARE utilities either to be discovered or mentioned .