MV22B Rel1.0 released

freded · May 8, 2017

Postbaer61 said:
Hi Mark,

1. I use reshade : https://reshade.me/ , but i use FSX Acc and not P3D, so i don't know how it works for you.
For P3D user i recommend http://ultimaterealismpack.weebly.com/

2. Your entry is correct, if there is no entry after texture= , it describes the default aircraft texture folder
in this case the ui_variation="grey" USAF ( see in post #256 )
See post # 267 for another USAF repaint. ( i think is still WIP )

Hi Postbaer61,

I cannot find anything about a USAF variation in post #256; nor anything about a USAF repaint on post #267. (I assume you are referring to this forum, viz. 'outhouse.com/sohforums'?)

I shall investigate ReShade and UltimateReal when I have the time...!

Mark

kalong · May 8, 2017

freded said:
Hi Postbaer61,

I cannot find anything about a USAF variation in post #256; nor anything about a USAF repaint on post #267. (I assume you are referring to this forum, viz. 'outhouse.com/sohforums'?)

I shall investigate ReShade and UltimateReal when I have the time...!

Mark

Hi Mark,

the title for air force is using CV-22B, for the letter it should be around top/beginning of aircraft list, instead MV-22B (with start letter is "M") around middle of the list.
but if you still have a problem,maybe you could do some trick on texture list arrangement.

this stock [fltsim.0] inside aircraft.cfg

Code:

[fltsim.0]
title=CV-22B Osprey USAF
sim=MV-22B
model=
panel=
sound=
texture=
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"
ui_type="cv22b Osprey"
ui_variation="grey"
ui_typerole="Tilt Rotor"
ui_createdby="Maryadi"
description="First operational Tilt Rotor"

copy and paste below other fltsim.xx, xx in list number. change the parameter make them look like this, please compare the different

Code:

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

then you make a folder make the name "texture.003" (no quote). inside folder "MV-22B_Osprey" and along with other texture name
go to folder "texture" and copy this file:
- CV-22B_badan.dds
- CV-22B_brutu.dds
- CV-22B_mesin.dds
- CV-22B_ngisor.dds
- CV-22B_Swiwi.dds

then paste in new folder that is "texture.003" (no quote)

then go to folder "texture.dragon" the copy this file:
- texture.cfg

then paste in "texture.003" (no quote).

DONE. you already make new custom aircraft texture

freded · May 9, 2017

kalong said:
Hi Mark,

the title for air force is using CV-22B, for the letter it should be around top/beginning of aircraft list, instead MV-22B (with start letter is "M") around middle of the list.
but if you still have a problem,maybe you could do some trick on texture list arrangement.

this stock [fltsim.0] inside aircraft.cfg

Code:

[fltsim.0] title=CV-22B Osprey USAF sim=MV-22B model= panel= sound= texture= 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" ui_type="cv22b Osprey" ui_variation="grey" ui_typerole="Tilt Rotor" ui_createdby="Maryadi" description="First operational Tilt Rotor"

copy and paste below other fltsim.xx, xx in list number. change the parameter make them look like this, please compare the different

Code:

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

then you make a folder make the name "texture.003" (no quote). inside folder "MV-22B_Osprey" and along with other texture name
go to folder "texture" and copy this file:
- CV-22B_badan.dds
- CV-22B_brutu.dds
- CV-22B_mesin.dds
- CV-22B_ngisor.dds
- CV-22B_Swiwi.dds

then paste in new folder that is "texture.003" (no quote)

then go to folder "texture.dragon" the copy this file:
- texture.cfg

then paste in "texture.003" (no quote).

DONE. you already make new custom aircraft texture

Thank you, Maryadi!

I've done all that and the [fltsim.0] aircraft CV-22B Osprey USAF now appears in the 'Select Vehicle' list in P3D.

But there is no CV-22B Osprey USAF-2 in that list... I even copied the 'thumbnail.jpg to texture.003, in case that was the problem. Perhaps I should close and re-open P3D for it to find the new aircraft? Or perhaps it won't find the new one because it has a similar 'Vehicle Title' ?

Ah! P3D has now found the 'new' CV-22B. Perhaps it just needed a little time! Its engines were stopped but I managed to start them.

Thank you again, Maryadi, for your help - and especially for your wonderful aircraft. Quite the best!

Mark

Chris Sykes · May 10, 2017

Has anyone got any issues with the landing lights on the latest version of P3d?

kalong · May 10, 2017

Chris Sykes said:
Has anyone got any issues with the landing lights on the latest version of P3d?

can you make it specific?

Chris Sykes · May 10, 2017

kalong said:
can you make it specific?

two attached to the light pods and two floating in the air above the cockpit.

kalong · May 10, 2017

Chris Sykes said:
two attached to the light pods and two floating in the air above the cockpit.

can you check your [light] on aircraft.cfg, and disable all light by add " // " ( no quote) before light.xx= . . .
all light should be embeded in model polygon. no extra light setup in aircraft.cfg. except @Heater make new light for blink at start.

if problem still persist, just check issue rise on latest update from P3D.

freded · May 12, 2017

Adding 2D Gauges to Panel.cfg

Hi,

I am trying to add a couple of 2D gauges to the Osprey's panel.cfg. Has anyone else tried this and did you succeed?

I thought this would be useful when flying the Osprey in an outside view, e.g. 'Spot'

Here is my attempt. Don't know why it's so small. Can't find how to enlarge it:-

Anyway, if you look closely :untroubled:

you 'll see that there is a PFD in the top left corner and a NAV gauge at top right. Only problems are that neither display can be altered as there are no buttons around the gauges; and the NAV gauge has no map. But if you click on the buttons in the corresponding 3D panel, the 2D gauge changes accordingly.

I haven't (yet) found out how to make the map appear in the NAV gauge... Anyone achieved that?

Here is an excerpt from my modified Panel.cfg file for anyone to use:-

// MV/CV-22B/C created by maryadi
// VTOL from Rob Barendregt
// GPS Map from fsdeveloper comunity
// See comment for added gauges.
// Version: Beta 2.0

[Window Titles]
Window00=PFD/MFD 1
Window01=PFD/MFD 2
Window06=TEST (DEBUG)
Window07=EVENTS (DEBUG)
//Window08=CAMERA (FSX ONLY)

VIEW_FORWARD_DIR=-1.000, 0.000, 0.000

[Window00]
size_mm=512,512
window_size= 256,256
window_pos= 0,0.07
Type=SPECIAL
gauge00=Mar_MV22B!mar_pfd, 0, 0, 512, 512 ,1

[Window01]
size_mm=512,512
window_size= 256,256
window_pos= 0,0.07
Type=SPECIAL
gauge00=Mar_MV22B!mar_pfd, 0, 0, 512, 512 ,2

If you try this, be warned that the NAV gauge won't appear where it's shown in the image above. It'll be superimposed on the PFD. I haven't been able to place it where I want it in spite of trying several variations. I had to drag it (kicking & screaming!) to the top right corner...

Mark

freded · May 12, 2017

freded said:
Hi,

I am trying to add a couple of 2D gauges to the Osprey's panel.cfg. Has anyone else tried this and did you succeed?

I thought this would be useful when flying the Osprey in an outside view, e.g. 'Spot'

Here is my attempt. Don't know why it's so small. Can't find how to enlarge it:-

Anyway, if you look closely you 'll see that there is a PFD in the top left corner and a NAV gauge at top right. Only problems are that neither display can be altered as there are no buttons around the gauges; and the NAV gauge has no map. But if you click on the buttons in the corresponding 3D panel, the 2D gauge changes accordingly.

I haven't (yet) found out how to make the map appear in the NAV gauge... Anyone achieved that?

Here is an excerpt from my modified Panel.cfg file for anyone to use:-

// MV/CV-22B/C created by maryadi
// VTOL from Rob Barendregt
// GPS Map from fsdeveloper comunity
// See comment for added gauges.
// Version: Beta 2.0

[Window Titles]
Window00=PFD/MFD 1
Window01=PFD/MFD 2
Window06=TEST (DEBUG)
Window07=EVENTS (DEBUG)
//Window08=CAMERA (FSX ONLY)

VIEW_FORWARD_DIR=-1.000, 0.000, 0.000

[Window00]
size_mm=512,512
window_size= 256,256
window_pos= 0,0.07
Type=SPECIAL
gauge00=Mar_MV22B!mar_pfd, 0, 0, 512, 512 ,1

[Window01]
size_mm=512,512
window_size= 256,256
window_pos= 0,0.07
Type=SPECIAL
gauge00=Mar_MV22B!mar_pfd, 0, 0, 512, 512 ,2

If you try this, be warned that the NAV gauge won't appear where it's shown in the image above. It'll be superimposed on the PFD. I haven't been able to place it where I want it in spite of trying several variations. I had to drag it (kicking & screaming!) to the top right corner...

Mark

Hi again,

As you will have seen, the image I uploaded is a perfectly acceptable size. So what was I complaining about?

The answer is that this was the first time I had uploaded an image to this site and when I did, I was disappointed that it was a little thumbnail. Not realising that it would appear much larger once the posting was actually, er, posted...

Mark

flewpastu · May 12, 2017

ok im done with this repaint, Ive added some panel lines and smoke and grunge and wear and tear. I need to get permission from some of the contributors here that have added their lines and shadows, Ive added some wheel well textures from an old repaint but cant find the author who did that so I prob wont include those textures. I also added some wear and tear to the interior panels and recolored them to suit me, so you may not want to use those should you not like them. I should be able to upload this repaint this weekend should the wife not have me doing something else lol. Please let me know what you think of this repaint, these are not hi res pics bcause I use screenhunter for pics and its not the best but its free .

Bill

flewpastu · May 12, 2017

and a few more

kalong · May 13, 2017

freded said:
Hi,

I am trying to add a couple of 2D gauges to the Osprey's panel.cfg. Has anyone else tried this and did you succeed?

I thought this would be useful when flying the Osprey in an outside view, e.g. 'Spot'

Here is my attempt. Don't know why it's so small. Can't find how to enlarge it:-

Anyway, if you look closely you 'll see that there is a PFD in the top left corner and a NAV gauge at top right. Only problems are that neither display can be altered as there are no buttons around the gauges; and the NAV gauge has no map. But if you click on the buttons in the corresponding 3D panel, the 2D gauge changes accordingly.

I haven't (yet) found out how to make the map appear in the NAV gauge... Anyone achieved that?

Here is an excerpt from my modified Panel.cfg file for anyone to use:-

// MV/CV-22B/C created by maryadi
// VTOL from Rob Barendregt
// GPS Map from fsdeveloper comunity
// See comment for added gauges.
// Version: Beta 2.0

[Window Titles]
Window00=PFD/MFD 1
Window01=PFD/MFD 2
Window06=TEST (DEBUG)
Window07=EVENTS (DEBUG)
//Window08=CAMERA (FSX ONLY)

VIEW_FORWARD_DIR=-1.000, 0.000, 0.000

[Window00]
size_mm=512,512
window_size= 256,256
window_pos= 0,0.07
Type=SPECIAL
gauge00=Mar_MV22B!mar_pfd, 0, 0, 512, 512 ,1

[Window01]
size_mm=512,512
window_size= 256,256
window_pos= 0,0.07
Type=SPECIAL
gauge00=Mar_MV22B!mar_pfd, 0, 0, 512, 512 ,2

If you try this, be warned that the NAV gauge won't appear where it's shown in the image above. It'll be superimposed on the PFD. I haven't been able to place it where I want it in spite of trying several variations. I had to drag it (kicking & screaming!) to the top right corner...

Mark

nice work,
you can't customize "gauge size". cause that gauge would be fix at certain size (512x512) or it will have weird displayed.
I thinking a HUD for it. but no have source pic for it. must be an authentic HUD for osprey.

freded · May 13, 2017

kalong said:
nice work,
you can't customize "gauge size". cause that gauge would be fix at certain size (512x512) or it will have weird displayed.
I thinking a HUD for it. but no have source pic for it. must be an authentic HUD for osprey.

Thanks for the compliment, Maryadi !

I don't want to customize the size of the gauges, just to be able to add the map to the NAV gauge and move it to where it shows in the image. If I try changing the value of 'window_pos', the gauge shows up mostly hidden in the top left corner. For example:-

[Window01]
size_mm=512,512
window_size= 256,256
window_pos= 768,0.07 // 0,0.07
Type=SPECIAL
gauge00=Mar_MV22B!mar_pfd, 0, 0, 512, 512 ,2

I've tried other values but they just make it worse.

Perhaps you can make it work?

A HUD would be great for the Osprey. I hope you can find a source pic for it.

Mark

letourn · May 13, 2017

A nice video for the HMS

https://www.youtube.com/watch?v=aAfGSdB_-9M

kalong · May 14, 2017

freded said:
Thanks for the compliment, Maryadi !

I don't want to customize the size of the gauges, just to be able to add the map to the NAV gauge and move it to where it shows in the image. If I try changing the value of 'window_pos', the gauge shows up mostly hidden in the top left corner. For example:-

[Window01]
size_mm=512,512
window_size= 256,256
window_pos= 768,0.07 // 0,0.07
Type=SPECIAL
gauge00=Mar_MV22B!mar_pfd, 0, 0, 512, 512 ,2

I've tried other values but they just make it worse.

Perhaps you can make it work?

A HUD would be great for the Osprey. I hope you can find a source pic for it.

Mark

this my 2D dll gauge on other project

Code:

[Window02]
size_mm=480,350
window_size=1 // change this to resize gauge
position=2
BACKGROUND_COLOR=0,0,0
alpha_blend=0.95
VISIBLE=0
ident=HUD
zorder=4

gauge01=UV-4 UAV!UA-4_HUD,       0,  30, 480, 320 // never change 480, 320 value or it will have strange display on gauge.

see every comment ( // )
to customize gauge size, use window_size= xx. value 1 exact same size with gauge.
for customize position, use gauge position. i.e . . . 0, 30, . . .

kalong · May 14, 2017

letourn said:
A nice video for the HMS

https://www.youtube.com/watch?v=aAfGSdB_-9M

that good source. thanks letourn.

one thing to be note with HMS is camera requirement. extra camera will give loss of FPS. as Osprey give little drop fps when in VC mode.
I ask rob to make camera down, air refuel gauge with make camera as small as possible.
let try every possibility first, decide later ... always move on

freded · May 14, 2017

kalong said:
this my 2D dll gauge on other project

Code:

[Window02] size_mm=480,350 window_size=1 // change this to resize gauge position=2 BACKGROUND_COLOR=0,0,0 alpha_blend=0.95 VISIBLE=0 ident=HUD zorder=4 gauge01=UV-4 UAV!UA-4_HUD, 0, 30, 480, 320 // never change 480, 320 value or it will have strange display on gauge.

see every comment ( // )
to customize gauge size, use window_size= xx. value 1 exact same size with gauge.
for customize position, use gauge position. i.e . . . 0, 30, . . .

Maryadi,

Thanks again... I've messed around with Panel.cfg's on many flight sim aircraft but still forgot that the first two values after the gauge name in 'gaugexx=' determined its position on the screen.

My new arrangement is:-

[Window00]
size_mm=512,512
window_size= 256,256
window_pos= 0,0.07
Type=SPECIAL
gauge00=Mar_MV22B!mar_pfd, 0, 0, 512, 512 ,1

[Window01]
size_mm=512,512
window_size= 256,256
BACKGROUND_COLOR=0,0,0
Type=SPECIAL
gauge00=Mar_MV22B!mar_pfd, 376, 25, 512, 512,2 // These are the changes

- and this puts the NAV gauge where I want it.

But I still need to add the map to this NAV gauge. Is there some way of doing that?

Mark

kalong · May 14, 2017

freded said:
Maryadi,

Thanks again... I've messed around with Panel.cfg's on many flight sim aircraft but still forgot that the first two values after the gauge name in 'gaugexx=' determined its position on the screen.

My new arrangement is:-

[Window00]
size_mm=512,512
window_size= 256,256
window_pos= 0,0.07
Type=SPECIAL
gauge00=Mar_MV22B!mar_pfd, 0, 0, 512, 512 ,1

[Window01]
size_mm=512,512
window_size= 256,256
BACKGROUND_COLOR=0,0,0
Type=SPECIAL
gauge00=Mar_MV22B!mar_pfd, 376, 25, 512, 512,2 // These are the changes

- and this puts the NAV gauge where I want it.

. . .

But I still need to add the map to this NAV gauge. Is there some way of doing that?

Mark

this the map:
gauge07=mv-22b!peta, 0,0,508,508

you can put behind nav gauge. put it after nav gaugexx = ( bit forgot with XML hierarchy code)

just to be note: using more map gauge can make fps drop.

freded · May 15, 2017

kalong said:
this the map:
gauge07=mv-22b!peta, 0,0,508,508

you can put behind nav gauge. put it after nav gaugexx = ( bit forgot with XML hierarchy code)

just to be note: using more map gauge can make fps drop.

Maryadi,

I finally got it right... This is a section of my panel.cfg that puts the map in the NAV gauge for the 2D views. I can't make the map transparent, so the compass rose is not visible. You can change the range of the map only by going to a 3D view of the panel and clicking on the RNG button. The same goes for any other parameters in the NAV screen.

Perhaps other people will find this useful for when they are flying the Osprey with an external view.

Thanks for your help with this little project, Maryadi! :encouragement:

NOTE: Add these lines to your Panel.cfg file (with Notepad) after 'VIEW_FORWARD_DIR'.

// PFD for external views
[Window00]
size_mm=512,512
window_size= 256,256
window_pos= 0,0.07
Type=SPECIAL

gauge00=Mar_MV22B!mar_pfd, 0, 0, 512, 512 ,1

// NAV and Map for external views
[Window01]
size_mm=512,512
window_size= 256,256
Type=SPECIAL

gauge00=Mar_MV22B!mar_pfd, 376, 25, 512, 512,2 //Original: 0, 0, 512, 512 ,2
gauge01=mv-22b!peta, 398, 37, 92, 160 // Map

Here's the result:-

Mark

freded · May 15, 2017

Sorry, guys, I forgot to tell anyone using my 2D addons that you have to add these two lines to your Panel.cfg:-

[Window Titles]
Window00=PFD/MFD 1 // Copy this line below 'Windows Titles'
Window01=PFD/MFD 2 // Copy this line below 'Windows Titles'

Hope it all works for you!

Mark

MV22B Rel1.0 released

Charter Member

Charter Member

Charter Member

Charter Member

Charter Member

Charter Member

Charter Member

Charter Member

Attachments

Charter Member

Charter Member

Attachments

Charter Member

Attachments

Charter Member

Charter Member

Attachments

Charter Member

Charter Member

Charter Member

Charter Member

Attachments

Charter Member

Charter Member

Attachments

Charter Member