Aircraft compatibility in Prepar3D V4

I can't understand why it causes a CTD. There are no exe or dll entries so you wouldn't expect any problems.


Ian
 
Same for me too... CTD every time. Sometimes it gets as far as showing the Vulcan in the preview window, others not.
 
IanHenry said:
I can't understand why it causes a CTD. There are no exe or dll entries so you wouldn't expect any problems.
Ian
Click to expand...

The problem is caused by something in the B2.air file, when I tested with an .air file from another add on, the Vulcan loaded fine, I could successfully complete the complex start up procedure and fly the beast.

The 1st thing I noticed when I opened the B2.air file in AirEd is that it has lots of obsolete FS2002/FS2004 legacy records. I attached a fixed version of the B2.air file to this post, I did not have time to test it thoroughly so if you find issues please post your feedback.
 

Attachments

  • IRIS_VLCN_P3Dv4_AIRFILE_FIX.zip
    2.8 KB · Views: 2
The Queen Of The Skies in P3Dv4 format has been around for a while, now the Empress Of The Skies has arrived too. ( A2A's incarnation that is)

a2aconnie64.jpg
 
hschuit said:
The problem is caused by something in the B2.air file, when I tested with an .air file from another add on, the Vulcan loaded fine, I could successfully complete the complex start up procedure and fly the beast.

The 1st thing I noticed when I opened the B2.air file in AirEd is that it has lots of obsolete FS2002/FS2004 legacy records. I attached a fixed version of the B2.air file to this post, I did not have time to test it thoroughly so if you find issues please post your feedback.
Click to expand...

Thank you so much, that really is appreciated, it looks like your going to make a lot of people very happy. I'll test it as soon as possible.


Regards,
Ian
 
hschuit said:
The problem is caused by something in the B2.air file, when I tested with an .air file from another add on, the Vulcan loaded fine, I could successfully complete the complex start up procedure and fly the beast.

The 1st thing I noticed when I opened the B2.air file in AirEd is that it has lots of obsolete FS2002/FS2004 legacy records. I attached a fixed version of the B2.air file to this post, I did not have time to test it thoroughly so if you find issues please post your feedback.
Click to expand...

HUGE thanks for this!!!! :applause:

I no longer get CTDs. I've only tried to start her up once though and failed. This may be because I'm very rusty and did something wrong, or perhaps something else is up? I'd be interested to hear other's experiences.

A quick look around and to my eye everything is as it should be besides materials for lights/buttons in the VC.
 
hschuit said:
The problem is caused by something in the B2.air file, when I tested with an .air file from another add on, the Vulcan loaded fine, I could successfully complete the complex start up procedure and fly the beast.

The 1st thing I noticed when I opened the B2.air file in AirEd is that it has lots of obsolete FS2002/FS2004 legacy records. I attached a fixed version of the B2.air file to this post, I did not have time to test it thoroughly so if you find issues please post your feedback.
Click to expand...

Just one problem that I've found, the airbrakes don't work. Is there anything we can do to fix that?


Regards,
Ian
 
IanHenry said:
Just one problem that I've found, the airbrakes don't work. Is there anything we can do to fix that?

Regards,
Ian
Click to expand...

The Vulcan is not easy to operate, so are the airbrakes... You need to make sure you have hydraulics power, they only work once you have managed to get the engines running.
And that is not all, the airbrakes have 4 stages and use the flaps keys F5/F6/F7/F8 to operate.

Edit: Don't forget to enable the Powered Flight Controls (PFC), you have to click a whole bunch of red lights on the left console, they all must be off and turned dark.
 
The Vulcan starts and the Vulcan flies! :jump:

I was just rusty on my startup sequence... 100% operator error!

I'm over the moon! :biggrin-new:
 
hschuit said:
The Vulcan is not easy to operate, so are the airbrakes... You need to make sure you have hydraulics power, they only work once you have managed to get the engines running.
And that is not all, the airbrakes have 4 stages and use the flaps keys F5/F6/F7/F8 to operate.

Edit: Don't forget to enable the Powered Flight Controls (PFC), you have to click a whole bunch of red lights on the left console, they all must be off and turned dark.
Click to expand...

Thanks, I'd forgotten about that.


Ian
 
I haven't moved to v4 yet (soon), but I'm following this thread with interest.

Has anyone tried any of the Nemeth Design choppers yet in v4, in particular the MD902 Explorer? ND has been pretty dormant lately.

Also,has anyone tried any of the Vertigo Studios aircraft in v4? I'm particularly interested in knowing if their F9F Panther and F8F
Bearcat will work. Like ND, VS also seems very dormant.

I'm hoping the ND's and VS's aren't going to become "lost to the ages", as was so aptly said on another thread.

Thanks - Rob
 
Rob, I got the Vertigo Panther working in P3Dv4 but it took a fair bit of surgery:

- The FSX version uses a 32bit DeadPixel sound module to support cockpit sounds, I have replaced this with Doug Dawson's 64bit DSD sound module. This is not simple, I needed to trace the DeadPixel WAV names and local vars and write a new DSD sound.ini file for them.

- The VS_F9F_Blueprint.CAB configuration/load mgr gauges depended on the 32bit VS_F9F_BPC.gau file, I had to re-write the XML code and update the aircraft.cfg station_load entries to make the load mgr work with 64bit XMLTools.

Anyway, if you can live without the cockpit click sounds and load mgr, the jet is usable as it is in P3Dv4. There is always the option to enter the payload weights manually I guess.
 
hschuit said:
Rob, I got the Vertigo Panther working in P3Dv4 but it took a fair bit of surgery:

- The FSX version uses a 32bit DeadPixel sound module to support cockpit sounds, I have replaced this with Doug Dawson's 64bit DSD sound module. This is not simple, I needed to trace the DeadPixel WAV names and local vars and write a new DSD sound.ini file for them.

- The VS_F9F_Blueprint.CAB configuration/load mgr gauges depended on the 32bit VS_F9F_BPC.gau file, I had to re-write the XML code and update the aircraft.cfg station_load entries to make the load mgr work with 64bit XMLTools.

Anyway, if you can live without the cockpit click sounds and load mgr, the jet is usable as it is in P3Dv4. There is always the option to enter the payload weights manually I guess.
Click to expand...

Thanks for the info! Yes, beyond my programming knowledge and hunt-and-peck typing capabilities. Although never say never. I suppose
similar will apply to other VS planes. Still not as bad as could be, with gauges in the panel or outside animations not working, or CTD's as
soon as you try to load.

Thanks again for the info! - Rob
 
RobM said:
I haven't moved to v4 yet (soon),

Like ND, VS also seems very dormant.

I'm hoping the ND's and VS's aren't going to become "lost to the ages", as was so aptly said on another thread.

Thanks - Rob
Click to expand...

Its because nemeth have ceased development, they closed shop back in Jan15

however 95% of ND helos work fine in v4

people are reporting the ND store to some internet watch dog as they continue to sell products but offer no support via forums or emails
 
jeansy said:
...

however 95% of ND helos work fine in v4

...
Click to expand...
The Huey and Chinook work OK.

The Carenado C185 Bush works well, just one GAU for the gear on the amphibian version.
Their 206G has a LOT of GAUs, because I need the 206 I've been working through replacing the gauges with C185 equivalents...easy for the round dials, hard for the radios...
Vertigo Vans and Stearman on the list to try soon.

Cheers
Keith
 
See AH/JF list, 4th one down:

Changes include:



  1. P3D v4 compatibility added
  2. FDE improvements
  3. New custom fuel system (including fuel transfer and crossfeed)
  4. New custom autopilot/flight director system with improved usability
  5. New BEA livery included for -500 variant
  6. NAV/GPS switch fixed
  7. Altimeter scaling fixed
  8. Electrical panel fixes

I haven't tried it yet though...
 
You must log in or register to reply here.
Back
Top