• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Maryadi's MV22B Osprey Rel2.0 released

Hi Maryadi and Rob,

Regardless of how I configure the previous aircraft prior to loading, the nacelles remain in horizontal position and refuse to move.

Have combed the manual, tried changing from aileron trim to spoiler axis for control and still nothing.

Andy

I too had problems and then just started the engines. It was nice that the nacelles then tilted to 60*.
I still can't manually tilt them so I guess I'm going to flunk flight school.
 
Saved Flights

If someone would be so kind to package up a couple of saved flights, one with nacelles @ 0*, and another with them @ 60*, everything ready for flight.?
Your fellow pilot trainees would be much appreciative while we work our way thru flight school. I'm going to try a little mayo and mustard on the flight manual
to see if it will help....:banghead:
 
Hi Maryadi and Rob,

The model looks fantastic and I am desperate to fly it but.....

Regardless of how I configure the previous aircraft prior to loading, the nacelles remain in horizontal position and refuse to move.

Have combed the manual, tried changing from aileron trim to spoiler axis for control and still nothing.

At a loss. Running P3D v4.1 with registered FSUIPC under Windows 10 on P:\ drive dedicated to P3D

I've got Dino's F-35B and the VTOL gauge works perfectly in that.

Any clue greatly appreciated. Many thanks

Andy

I too had problems and then just started the engines. It was nice that the nacelles then tilted to 60*.
I still can't manually tilt them so I guess I'm going to flunk flight school.

I had the same problem.
Please checked ,if you have another "rcb-gauges / VSTOLControlIPC_Function.xml" in your default gauges folder.
If so, back up,or rename the VSTOLControlIPC_Function.xml file from your MV-22B_Osprey / Panel /rcb-gauges folder.
It seems they block each other and the nacelles rotation doesn't work.
 
VERY IMPORTANT REMARK ON P3Dv4

I had the same problem.
Please checked ,if you have another "rcb-gauges /
VSTOLControlIPC_Function.xml
" in your default gauges folder.
Maybe this is the answer to such problems !!!!

NEVER, and I emphasize NEVER, should you have a file named VSTOLControlIPC_Function.xml in your main /Gauges/rcb-gauges/ folder.
Not sure how such a file ends up there, because I can't remember ever making an addon that puts this file in the main .../Gauges/rcb-gauges/ folder.

The problem stems from the new gauge-search order in P3Dv4, which is different then in previous P3D versions (and FSX).
In FSX / P3Dv2/3 the program searches first in the local panel folder of an aircraft; however, P3Dv4 appears to search in the main (whatever your assigned as default) /Gauges folder first.
And since I use the filename VSTOLControlIPC_Function.xml in ALL my VSTOL implementations (30+), it means that P3Dv4 may load the wrong .xml file.

No idea why LM has changed the search order in P3Dv4, but it can introduce many problems with loading gauges.
IMHO a bad decision (from a compatibility point-of-view) ....
The "strong" point of FSX / P3Dv2/3 was, that whatever gauge is in your local aircraft panel folder, always has preference over the one in the main/default Gauges folder.
Which makes version control of gauge file versions with the same name a non-issue; unlike in P3Dv4.

Rob

PS: the MV22B Rel2 doesn't require FSUIPC anymore ; but having it installed doesn't do any harm either ...
 
I had the same problem.
Please checked ,if you have another "rcb-gauges / VSTOLControlIPC_Function.xml" in your default gauges folder.
If so, back up,or rename the VSTOLControlIPC_Function.xml file from your MV-22B_Osprey / Panel /rcb-gauges folder.
It seems they block each other and the nacelles rotation doesn't work.

Thanks, nothing in the main gauges folder.
I am running FSX Acceleration.
 
If someone would be so kind to package up a couple of saved flights, one with nacelles @ 0*, and another with them @ 60*, everything ready for flight.?
Your fellow pilot trainees would be much appreciative while we work our way thru flight school. I'm going to try a little mayo and mustard on the flight manual
to see if it will help....:banghead:
Packaging saved flights is not a solution for such problems, because it will introduce more problems then it solves.
With all possible variations in installed addon's (like scenery).

But if I read this:
""
I too had problems and then just started the engines. It was nice that the nacelles then tilted to 60*.
""
it means that everything works as it should.
If you then still can't move the nacelles up, it means there is a problem with the keys/buttons you have assigned to "Aileron TRIM" . See last section (bullit-4 of the FlightManual)
What if you assign other keys (Not on the Numpad) to "Aileron Trim (left)" and "Aileron Trim (right)" ??

Rob
 
Sorry for bringing up the problem with the additional textures/liveries that were presented above: -MV-22_Texture_Package_2.0.zip_
I don't succeed to get them displayed im my P3Dv4. (I'm not a flightsimulation beginner, doing these these for many years, but this time no success)
Is there any advice, please?

Greetings
Dieter
Win10 Pro 64 bit - RAM 16GB - 3 SSD each 500GB - 1 HD 1TB/Intel(r) Core(TM) i7-7700K CPU 4,2 GHz - Nvidia GeForce GTX 1080 - P3Dv4
 
Sorry for bringing up the problem with the additional textures/liveries that were presented above: -MV-22_Texture_Package_2.0.zip_
I don't succeed to get them displayed im my P3Dv4. (I'm not a flightsimulation beginner, doing these these for many years, but this time no success)
Is there any advice, please?

Greetings
Dieter
Win10 Pro 64 bit - RAM 16GB - 3 SSD each 500GB - 1 HD 1TB/Intel(r) Core(TM) i7-7700K CPU 4,2 GHz - Nvidia GeForce GTX 1080 - P3Dv4

Someone else reported that the texture package crashed his P3D v3 with those textures (Gray Eagle is his name i believe). Is this happening to you as well, or are they simply not showing up in P3D list?
If so, could you retrace how you installed it and let me know on this thread?

Ill look into it as well to see if i can find any issues with the package, if so, ill update it on Simviation.
 
I don't experience a crash/CTD. The texture isn't showing in the P3Dv4 list.
I tried all of your textures from version 2.0 completely- any success.
Now I just choose one texture =>texture.hmx1_01 - no success either.

Installed it in aircraft.cfg like this:

[fltsim.0]
title=Bell-Boeing CV-22B USAF
sim=MV-22B
model=
panel=
sound=
texture=af
kb_checklists=
kb_reference=
atc_id_color=0xff000000
atc_id=0033
atc_airline=Air Force
atc_flight_number=0033
atc_parking_types=RAMP
ui_manufacturer="Bell-Boeing CV22"
ui_type="USAF"
ui_variation="grey"
ui_typerole="Tilt Rotor"
ui_createdby="Maryadi"
description="First operational Tilt Rotor"

[fltsim.1]
title=Bell-Boeing MV-22B Marines dragon
sim=MV-22B
model=
panel=
sound=
texture=dragon
kb_checklists=
kb_reference=
atc_id_color=0xffffffffff
atc_id=8830
atc_airline=Marines
atc_flight_number=0000
atc_parking_types=RAMP
ui_manufacturer="Bell-Boeing MV22"
ui_type="Marine"
ui_variation="dragon"
ui_typerole="Tilt Rotor"
ui_createdby="Maryadi"
description="First operational Tilt Rotor"

[fltsim.2]
title=MV-22B HMX-1 01 VIP Transport
sim=MV-22B
model=
panel=
sound=
texture=hmx1_01
kb_checklists=
kb_reference=
atc_id_color=0xff000000
atc_id=168280
atc_airline=Marines
atc_flight_number=168280
atc_parking_types=RAMP
ui_manufacturer="Bell-Boeing"
ui_type="MV-22B Osprey"
ui_variation="VIP Transport 01"
ui_typerole="Tilt Rotor"
ui_createdby="Maryadi"
description="Marine Helicopter Squadron One (HMX-1) is a United States Marine Corps helicopter squadron"

[fltsim.0] and [fltsim.1] come with the Maryadi-package, [fltsim.2] is yours.
I deleted the | in title=MV-22B HMX-1 01 VIP Transport

Dieter
 
No sound issues from the FSX-A users? I get start-up and then nothing, external is fine.

kalong, I know many pages are WIP still, but on the ICING page is the temp in Celsius or Fahrenheit? If you plan to expand the HMD, the system looks like the same we used in the UH-60 if you need any real world help.
 
I don't experience a crash/CTD. The texture isn't showing in the P3Dv4 list.
I tried all of your textures from version 2.0 completely- any success.
Now I just choose one texture =>texture.hmx1_01 - no success either.

Installed it in aircraft.cfg like this:

[fltsim.0]
title=Bell-Boeing CV-22B USAF
sim=MV-22B
model=
panel=
sound=
texture=af
kb_checklists=
kb_reference=
atc_id_color=0xff000000
atc_id=0033
atc_airline=Air Force
atc_flight_number=0033
atc_parking_types=RAMP
ui_manufacturer="Bell-Boeing CV22"
ui_type="USAF"
ui_variation="grey"
ui_typerole="Tilt Rotor"
ui_createdby="Maryadi"
description="First operational Tilt Rotor"

[fltsim.1]
title=Bell-Boeing MV-22B Marines dragon
sim=MV-22B
model=
panel=
sound=
texture=dragon
kb_checklists=
kb_reference=
atc_id_color=0xffffffffff
atc_id=8830
atc_airline=Marines
atc_flight_number=0000
atc_parking_types=RAMP
ui_manufacturer="Bell-Boeing MV22"
ui_type="Marine"
ui_variation="dragon"
ui_typerole="Tilt Rotor"
ui_createdby="Maryadi"
description="First operational Tilt Rotor"

[fltsim.2]
title=MV-22B HMX-1 01 VIP Transport
sim=MV-22B
model=
panel=
sound=
texture=hmx1_01
kb_checklists=
kb_reference=
atc_id_color=0xff000000
atc_id=168280
atc_airline=Marines
atc_flight_number=168280
atc_parking_types=RAMP
ui_manufacturer="Bell-Boeing"
ui_type="MV-22B Osprey"
ui_variation="VIP Transport 01"
ui_typerole="Tilt Rotor"
ui_createdby="Maryadi"
description="Marine Helicopter Squadron One (HMX-1) is a United States Marine Corps helicopter squadron"

[fltsim.0] and [fltsim.1] come with the Maryadi-package, [fltsim.2] is yours.
I deleted the | in title=MV-22B HMX-1 01 VIP Transport

Dieter
Do the Cv-22 and Dragon textures show ok for you? this is strange. Unfotunately I dont have a lot of experience troubleshooting problems like this. The only thing i could possibly think of is maybe the "Show all variations" checkbox isnt checked.
I know this is an obvious thing to say, but double check the texture.hmx-1 folder is in the right place, with 6 files inside of it, plus a backup folder.
Ill keep looking into this, sorry for the trouble.
 
Found the errant rcb-gauges folder.

Now have fully working nacelles.

Pleased to say just had a flight in VR and it looks awesome.

Many thanks for the help Rob.

Andy
 
New gauge

Would it be possible to get a new digital gauge that shows nacelle angle on line one
with airspeed right below it, black or transparent background..?
 
Would it be possible to get a new digital gauge that shows nacelle angle on line one
with airspeed right below it, black or transparent background..?

Your best gauge, by far, is looking over your left shoulder and checking on the nacelle position.
 
Would it be possible to get a new digital gauge that shows nacelle angle on line one
with airspeed right below it, black or transparent background..?

Why don't you fly in Spotplane view with the HMD view opened (Re-scaled if you like) ??
Because the HMD already displays this (and a lot more relevant info to be able to fly/maneuver properly in Spotplane view ....)

Rob
 
No sound issues from the FSX-A users? I get start-up and then nothing, external is fine.

kalong, I know many pages are WIP still, but on the ICING page is the temp in Celsius or Fahrenheit? If you plan to expand the HMD, the system looks like the same we used in the UH-60 if you need any real world help.

future update would be around gauge, including HMD, unfortunately I only have obsolete source (flight manual date 2006), which is slightly differ layout with operational aircraft (compare from photo at airshow).
any help would be appreciated.
 
Would it be possible to get a new digital gauge that shows nacelle angle on line one
with airspeed right below it, black or transparent background..?

you can trick the HMD gauge as it was 2D gauge, even though I not recommend cause it need exact handling.
 
Back
Top