MV22B Rel1.0 released

[rcbarend]

Hi, Rob
i'm using P3Dv4 ; win7 64 bit and installed the V2 Osprey as
described.
I have c++2015 all variants installed and have changed my
"AileronTrim" commands for the joystick.
I use the 64 bit Panel of course,
but the nacelles don't rotate.
After loading, the nacelles are in 90 or horizontal position and
the engines running and the props don't rotate until i set the flight controls
to "fly"position.
The Osprey flys as an plane but without VTOL function.

It sounds like you are using a flight that was made with Rel1 ..??

If so, try this:
Start P3D and create a flight with another aircraft.
Then load the MV22B via the Aircraft menu in that flight, and set all functions on the overhead display in correct position.
If working now, save this flight when in VC mode.

Rob

 

[MrZippy]

Ulrich,

On the top-left of each 4 MFD's, there is a small knob that sets the MFDs on (off/night/day).
The two MFDs visible on the picture shows they are in Off position. (use mousewheel to rotate them clockwise.)

See section 6.1.1 of the FlightManual !!!

Rob

+1 I was just about to show that! It pays to READ the manual before trying to jump in the cockpit to take off!

 

[rcbarend]

Please use other thread for rel2.0

FOR SUPPORT/QUESTIONS ON REL2.0, PLEASE USE THE THREAD TITLED "Maryadi's MV22B Osprey Rel2.0 released"

This thread was targetted to Rel1.

Thanks, Rob

 

[Postbaer61]

It sounds like you are using a flight that was made with Rel1 ..??

If so, try this:
Start P3D and create a flight with another aircraft.
Then load the MV22B via the Aircraft menu in that flight, and set all functions on the overhead display in correct position.
If working now, save this flight when in VC mode.

Rob

Thanks, Rob
I found the culprit.
I have had an older version of your rcb-gauges/VSTOLControlIPC_Function.xml in
my default P3D4 gauges Folder.
Deleted it and it works now. Yippee!!!

Cheers
Ulrich

 

[rcbarend]

Thanks, Rob
I found the culprit.
I have had an older version of your rcb-gauges/VSTOLControlIPC_Function.xml in
my default P3D4 gauges Folder.
Deleted it and it works now. Yippee!!!

Cheers
Ulrich

THAT's a problem I never would have guessed as a problem cause ... LoL
Anyway, glad it's solved ...

By the way ...do we have 2 Ulrich's in this thread ???

Cheers, Rob

 

[Postbaer61]

THAT's a problem I never would have guessed as a problem cause ... LoL
Anyway, glad it's solved ...

By the way ...do we have 2 Ulrich's in this thread ???

Cheers, Rob

LoL,
I have had a similar prob with a doubled sound dll,
thats why i found the culprit.

Attention notice, never copy any gauges
from one to the other sim, without checking them !!!

And ,yes coincidentally two different Ulrich's . LoL

Thanks for the efforts !

Cheers
Ulrich

 

[rcbarend]

LoL,
I have had a similar prob with a doubled sound dll,
thats why i found the culprit.

Attention notice, never copy any gauges
from one to the other sim, without checking them !!!

And ,yes coincidentally two different Ulrich's . LoL

Thanks for the efforts !

Cheers
Ulrich

PS: I'm working on a new version of my Addon4 for Rel2 (additional HoistSlingOperation features and inflight-refuelling/tracking/formation-flying).
I'll keep people informed in the MV22B Rel2 thread.
The good news is: I allready asked someone to test your C130 tanker addon in P3Dv4, and it seems to work perfectly !
Rob

 

[Postbaer61]

PS: I'm working on a new version of my Addon4 for Rel2 (additional HoistSlingOperation features and inflight-refuelling/tracking/formation-flying).
I'll keep people informed in the MV22B Rel2 thread.
The good news is: I allready asked someone to test your C130 tanker addon in P3Dv4, and it seems to work perfectly !
Rob

This are great news.
Thanks for info, that's what i've forgotten to ask.
I've tried your older inflight-refuelling gauge, but it
caused CTD's, i have read, fs9view:view is a
problem in P3D.
I have had updated the C130 a little bit, so its works
quite well in P3D4.

Ulrich

 

[freded]

Hi Pat,

As to Hoist operations:
I just discovered a new trick to avoid the dreaded "broken cable" problem when flying around with an object attached to the hoist cable.
- When the object is attached, just hoist it fully up and load it "into" the aircraft with "Hoist/Sling (Attach/Release)" command (default key: 'O'). So it's added to the payload.
- Then fly towards the destination, at any speed with whatever maneuvering.
- When near the destination, reduce speed, go into VTOL config and wait until the aircraft hovers again at very low airspeed.
- Then "extract" the object with another 'O' command (so it's visible on the hook again), lower it, and release it when it's on the ground.

Of course, it's a bit cheating if your "object" is much larger in size then the V22 itself ..LoL ..; but at least it works, without the risk of a "broken cable" during transport flight.

Cheers, Rob

Hi Rob,

Am I right in thinking that the 'cheat' to prevent a broken cable will only work in Version 2.0 of the MV-22?
If so I'll have to go on patiently waiting for Maryadi to release it!

Cheers, and many thanks for your great work on this aircraft.

Mark

 

[MrZippy]

Hi Rob,

Am I right in thinking that the 'cheat' to prevent a broken cable will only work in Version 2.0 of the MV-22?
If so I'll have to go on patiently waiting for Maryadi to release it!

Cheers, and many thanks for your great work on this aircraft.

Mark

Why wait? It's available at a store near you. Hurry while the supply lasts! But wait, there's more...Just add an extra handling charge and you will get 2 for the price of one

OR....download now from the Warbirds Library

 

[rcbarend]

Hi Rob,

Am I right in thinking that the 'cheat' to prevent a broken cable will only work in Version 2.0 of the MV-22?
If so I'll have to go on patiently waiting for Maryadi to release it!

Cheers, and many thanks for your great work on this aircraft.

Mark

No, works in Rel1 too..
It's just standard behaviour of the FSX hoist function.
Beware though: don't unload an object from the payload to the hook at normal flying speed; it's guaranteed the cable will brake....

But as Zippy said: do yourself a favour, and download Release 2.0.
See Rel.2 thread in the FSX forum.

Rob

 

[freded]

No, works in Rel1 too..
It's just standard behaviour of the FSX hoist function.
Beware though: don't unload an object from the payload to the hook at normal flying speed; it's guaranteed the cable will brake....

But as Zippy said: do yourself a favour, and download Release 2.0.
See Rel.2 thread in the FSX forum.

Rob

Thanks Rob,

I hadn't realised Release 2.0 had been made public... I've got it now - so onward & upward, as they say!

Cheers,

Mark

 

[freded]

Maryadi or Rob,

Perhaps I'm being stupid (more than likely!) but I cannot see how to set the Transponder Frequency ('Squawk') in Release 1.0.

The manual only says: "...input using keyboard from -0000-9999- digit.", but what do you select before entering the digits?

I cannot find anywhere on the panel that says Transponder.

And yes, I know I could be flying in Release 2.0, but I want to continue and finish a flight that is in progress in Rel. 1.0, Before switching to 2.0...

Cheers,

Mark

 

[rcbarend]

Maryadi or Rob,

Perhaps I'm being stupid (more than likely!) but I cannot see how to set the Transponder Frequency ('Squawk') in Release 1.0.

The manual only says: "...input using keyboard from -0000-9999- digit.", but what do you select before entering the digits?

I cannot find anywhere on the panel that says Transponder.

And yes, I know I could be flying in Release 2.0, but I want to continue and finish a flight that is in progress in Rel. 1.0, Before switching to 2.0...

Cheers,

Mark

Mark,

The Transponder is button "Mode 3A CO" in the CDU-EICAS screen.
So enter the 4-digit Transponder code with the TAB key depressed (like entering a VOR freq.), then release the TAB key and click the button left to "Mode 3A CO"
Works the same in Rel1 and Rel2.

Rob

 

[freded]

Mark,

The Transponder is button "Mode 3A CO" in the CDU-EICAS screen.
So enter the 4-digit Transponder code with the TAB key depressed (like entering a VOR freq.), then release the TAB key and click the button left to "Mode 3A CO"
Works the same in Rel1 and Rel2.

Rob

Thanks Rob,

That worked. But why is the button labelled "Mode 3A CO"? There's no mention of this in the Manual and it's hardly intuitive!

Next question: Does the same methodology apply to setting VOR-1 & VOR-2 - because I've tried that and it doesn't seem to work. Where would the NAV Freq appear?

Cheers,

Mark

 

[rcbarend]

Thanks Rob,

That worked. But why is the button labelled "Mode 3A CO"? There's no mention of this in the Manual and it's hardly intuitive!

Next question: Does the same methodology apply to setting VOR-1 & VOR-2 - because I've tried that and it doesn't seem to work. Where would the NAV Freq appear?

Cheers,

Mark

PLEASE read section 6.1.2.3: EICAS of the flightmanual and look at the picture of the EICAS screen. Works exactly the same way for VOR1/2 as for Transponder.
And if you wonder why the Transponder is labeled

"Mode 3A CO": do a google search for this exact string (including the quotes) and it becomes clear.​

 

[freded]

PLEASE read section 6.1.2.3: EICAS of the flightmanual and look at the picture of the EICAS screen. Works exactly the same way for VOR1/2 as for Transponder.
And if you wonder why the Transponder is labeled

"Mode 3A CO": do a google search for this exact string (including the quotes) and it becomes clear.​

Rob,

Thanks for the Google reference. I had never seen the phrase "Mode 3A CO" used in any FS or P3D aircraft before - and I've flown many - which explains my mystification! The Transponder is always labelled as such, even in military aircraft.

Regarding the VOR1/ILS frequency: When I type for example "Tab-1087" on my physical keyboard, the digits do appear on the EICAS scratchpad, but when I then click on 'VOR1/ILS' the existing value there (in this case: 113.700) is not replaced by 108.7. This leads me to believe that the new value has not been entered into the NAV receiver. Why is this?

Apologies for bugging you about this, but I'd be surprised if nobody else has come across similar problems.

Cheers,

Mark

 

[rcbarend]

Rob,

Regarding the VOR1/ILS frequency: When I type for example "Tab-1087" on my physical keyboard, the digits do appear on the EICAS scratchpad, but when I then click on 'VOR1/ILS' the existing value there (in this case: 113.700) is not replaced by 108.7. This leads me to believe that the new value has not been entered into the NAV receiver. Why is this?

Because you are not typing the Dot character !! 1087 is a non-existing frequency !!
So:
With the Tab key depressed, type 108.7 on the main keyboard section (NOT the NumPad section, unless you are sure of the NumLock state)
Then release the Tab key, and click VOR1/ILS button.

And behold .....

 

[freded]

Because you are not typing the Dot character !! 1087 is a non-existing frequency !!
So:
With the Tab key depressed, type 108.7 on the main keyboard section (NOT the NumPad section, unless you are sure of the NumLock state)
Then release the Tab key, and click VOR1/ILS button.

And behold .....

Ah! But when I type the DOT key, no dot appears...

Shall try again!

 

[rcbarend]

Ah! But when I type the DOT key, no dot appears...

?????
What key are you pressing for the 3 characters after the word "appears" in your post ??? That is the Dot key (== Period, decimal point, whatever you name it).
Otherwise, I'm really lost .... Sorry