Page 1 of 1

Osprey updates

Posted: 24 Aug 2016, 09:15
by Firebird
Gents,
As some of you may be aware there were some teething problems with the 4 recently released V-22 packages.
All 4 packages have been updated with the fixes.
However, if you would just like the changes they are attached here individually. They are in the some hierarchical layout as the original packages.

The changes consist of each aircraft.cfg file has two updates that makes the aircraft more stable on approach plus should eliminate the crashes on landing that some experienced.

In addition to this in the Miramar/Yuma package there is an updated afcad for Miramr that eliminates 3 issues.
1. No comms.
2. Aircraft not getting clearance to parking when exiting 24R.
3. ILS realigned and re-positioned.

Re: Osprey updates

Posted: 24 Aug 2016, 10:39
by Joseph29
I put all the V-22's in a single folder. With these updates all I need is everything below the aircraft entries right?

Re: Osprey updates

Posted: 24 Aug 2016, 11:37
by bismarck
Joseph29 wrote:I put all the V-22's in a single folder. With these updates all I need is everything below the aircraft entries right?
Yes

Giorgio

Re: Osprey updates

Posted: 24 Aug 2016, 12:13
by Firebird
I couldn't have put it better myself.

Re: Osprey updates

Posted: 24 Aug 2016, 15:27
by clickclickdoh
Joseph29 wrote:I put all the V-22's in a single folder. With these updates all I need is everything below the aircraft entries right?
You might want to spend some time watching the HMX-1 and Futenma Ospreys to see if combining them has a negative effect. If I remember right from the early development stages, John and I tweaked the V-22s using two different sets of data. The USAF and Miramar V-22s are based on a King Air where as the Futenma and HMX-1 are based on his UH-60. We needed two different performance profiles on approach to allow some to land in tight spaces and some to do a more smooth landing. If you suddenly find V-22s not being able to get into 500 ft runways put the originals back in.

Re: Osprey updates

Posted: 24 Aug 2016, 16:28
by John Young
So long as the aircraft entries are copied over from the 4 individual files to the common aircraft.cfg file, you should be fine. Each entry will carry with it the intended "Sim=" entry, ie, "V-22" or "V-22_long_roll".

John