MSFS MV-22B Osprey Release 3.0

[rcbarend]

Maybe you saved your flight with the HMD window open ??
In that case: you need to reload the aircraft after loading that flight, because 2D-window screen coordinates are saved in flight files; and overwrite the specified position in the panel.cfg ....

By the way:

window_pos= 1.0, 1.0 makes no sence, since that places the top/left of the 2Dwindow at the bottom/right position of the screen; so you won't see it ...LoL
Try 0.4, 0.4, which should place it appr. in the center of the screen. And then try to increase the values if you want it more to the right/bottom position.​

Rob​

 

[shortleash]

Maybe you saved your flight with the HMD window open ??
In that case: you need to reload the aircraft after loading that flight, because 2D-window screen coordinates are saved in flight files; and overwrite the specified position in the panel.cfg ....

By the way:
window_pos= 1.0, 1.0 makes no sence, since that places the top/left of the 2Dwindow at the bottom/right position of the screen; so you won't see it ...LoL

Try 0.4, 0.4, which should place it appr. in the center of the screen. And then try to increase the values if you want it more to the right/bottom position.

Rob

I believe I was using the saved flight. I will test tonight starting fresh. thanks again for the help.

 

[Heater]

Landing onboard LHD-6.... I usually have a hard time landing on boats, but this one actually wasnt bad

 

[shortleash]

Kalong,

not a big deal, but I noticed that I have to keep the APU on to keep Gen 3 and 4 green. This wasn't the case on the V1 model. I figure, once the engines are up and running and all the Gen's are green, one should be able to secure the APU.

thanks

 

[kalong]

the Gen 3 and Gen 4 in electrical display, it was secondary APU and GPU both aren't implemented yet. now it use APU as main source and not yet effect to the system.

 

[Duane293]

Loving the model. Everything working fine and simple enough to operate, however I cannod get the HUD/HMD to function. I'm assuming the manual reference for this is:

6.1.5.8 Night Vision Goggle/Heads Up Display (NVG/HUD). Feature still limited in functionality. Use the 3-way switch OFFON-ADJ to activate (Only OFF-ON currently functional). If NVG/HUD does not appear, ensure the switch is in the ON position, and not in Adjust (ADJ) position.

If so, I've looked at all 3 positions of this switch, and cannot seem to get it visible. Is there something I'm missing/ need to change in order for it to work? As mentioned, everything else functions fine.

Thanks

 

[rcbarend]

Loving the model. Everything working fine and simple enough to operate, however I cannod get the HUD/HMD to function. I'm assuming the manual reference for this is:

6.1.5.8 Night Vision Goggle/Heads Up Display (NVG/HUD). Feature still limited in functionality. Use the 3-way switch OFFON-ADJ to activate (Only OFF-ON currently functional). If NVG/HUD does not appear, ensure the switch is in the ON position, and not in Adjust (ADJ) position.

If so, I've looked at all 3 positions of this switch, and cannot seem to get it visible. Is there something I'm missing/ need to change in order for it to work? As mentioned, everything else functions fine.

Thanks

- In which flightsim version is this ??
- Did you change anything in the panel.cfg ??

Rob

 

[Duane293]

- In which flightsim version is this ??
- Did you change anything in the panel.cfg ??

Rob

FSX Acceleration. Using the same setup that V1.0 worked under, and installed V2.0 and removed 1.0 as directed. Followed the installation steps in 1.3 of the manual, including the 32bit panel part. Not touched the .cfg file apart from that.

 

[kalong]

hope you not use saved flight from Rel 1.0, it became an issue. make new one from rel 2.0.
make sure switch at ON position.

 

[pinkjr]

And this is how we rock the Osprey!

 

[Duane293]

hope you not use saved flight from Rel 1.0, it became an issue. make new one from rel 2.0.
make sure switch at ON position.

No, started flight from new. I’m pretty sure the switch is ON. I’m sure I saw a short video of the HMD being enabled and what was happening with the switches, but can’t find it now.

 

[kalong]

strange, it use simple code.
please check another switch, at rotor tip light. observe that rotor tip light at correct position as it describe, i.e. normal, top light. I suspect reverse switch happen, which is it ON but switch at OFF position.

 

[Duane293]

strange, it use simple code.
please check another switch, at rotor tip light. observe that rotor tip light at correct position as it describe, i.e. normal, top light. I suspect reverse switch happen, which is it ON but switch at OFF position.

Sorted it. By you mentioning the rotor tip light it made me look into that switch. The notification shows that it was for top light, but the actual position was for bottom. Once I'd switched to the opposite it was registering the HMD fine.

Many thanks

 

[FACV1218]

MV-22B Osprey Release 2.0
https://www.dropbox.com/s/j7dm8glcoxvc4ri/MV-22B_Osprey_Release_2.0.zip?dl=0
or
https://drive.google.com/file/d/1M0f7VyXItatMSzkHU_BwfWzClB0y7t7w/view?usp=sharing
or
http://www.sim-outhouse.com/sohforums/local_links.php?catid=213&linkid=23297

Always read the flight manual first.

general update:
- work in FSXA, FSX-SE, P3D v1, v2, v3 and P3D v4
- change VC model.
- massive re-code as compensation of VC change.
- update FDE and VTOL (overall behavior still similar)
- new lighting (system and render)
- minor change on external model, Rel 1.0 livery still work (there slightly different on nacelles/engine)
- add compatibility to use in hoist/sling load

Important note:
1. This package are pre-configure for P3D v4, read Chapter 1 on Flight manual for usage in FSX.
2. Release 1.0 saved file aren't compatible with Release 2.0. if you have installed Osprey for Release 1.0 and ever saved it, then you need to delete all file with extension *.mv22
3. Use this thread or in SOH for question, issue and problem rise while using this package.
4. feel free use your screenshot / video to any website.
5. it may NOT be sold, modified, re-distributed and/or uploaded to other website in any shape or form.
6. Same as Release 1.0, it freeware / Donation-ware.

Thanks to:
1. Allah SWT, GOD all mighty that give me everything.
2. My family for support and time.
3. Rob Barendregt (VTOL gauge Owner)
4. Jonathan Bleeker (C++ expert)
5. Doug Dawson (sound and event log gauge Owner)
6. Bill Leaming (lighting render, texture and other small but wonderful stuff)
7. Josh Stewart (Beta tester and his video)
8. All fsdeveloper.com admin/member who give a hand/help that I can't mention one by one
sorry if there any miss spelling.


edit:
Who need a Paintkit:
https://www.dropbox.com/s/1i489m8tl270dgr/MV-22B Osprey_Paintikit 2.0.zip?dl=0
or
https://drive.google.com/file/d/1nICJA6ceQGXvpbNGjDaioqarlEZMemLo/view?usp=sharing

hi ,my name is Cesar Alvarez from Colombia and o fell in love with your V-22,and have been in school with it for two weeks ,well ,three with this one,just wanted to say thank you for this great helicopter/plane ,i have Microsoft flight simulator steam edition ,here are some shots of my last urban patrol this week

Sent from my SM-G610M using Tapatalk

 

[d_stickman]

Seems to me that the MV-22 rotates much slower when using the rudder pedals while in a hover using v4.2 compared to how it responds in v3.2. Is this just my imagination or are their other people experiencing the same problem? If so is there any possible fix to get it to perform a bit faster using the rudder pedals?

 

[JB3DG]

That is very likely possible. In earlier versions of P3D as well as FSX, there is a bug where the units for rotational velocity do actually get multiplied by 3.28 which is the conversion to feet/sec as defined in the SDK documentation. This was fixed in v4 so that if you send in degrees or radians/sec you get degrees/radians/sec.

@rcbarend You might want to check this.

 

[rcbarend]

That is very likely possible. In earlier versions of P3D as well as FSX, there is a bug where the units for rotational velocity do actually get multiplied by 3.28 which is the conversion to feet/sec as defined in the SDK documentation. This was fixed in v4 so that if you send in degrees or radians/sec you get degrees/radians/sec.

@rcbarend You might want to check this.

Hi Jon,
You are spot-on.
I first stumbled onto this bug when I used my VSTOL XML coding (dimensioned for FS9, overwriting ROTATION VELOCITY BODY Y via FSUIPC "hacking" in the sim) in FSX (where FSUIPC used SimConnect).
Causing the effect of my coded yaw value to be 3.28 times higher in FSX then in FS9.
But I wasn't aware that this bug is solved now in P3Dv4 !
Meaning that if one uses my VSTOL code (dimensioned now for FSX) in P3Dv4.2, the resulting yaw effect is 3.28 times less then I intented.

Question (since I don't have P3D myself): has this bug been solved in all P3Dv4.* versions, or starting with P3Dv4.2 ??

The solution is to make an update of my VSTOL gauge(s), in which I check the flightsim version.
In XML, I already use Lvars for this (provided by Doug's XMLsound module), but I'm not sure these Lvars work for P3Dv4 as well. (i.e. if I can distinguish each P3D version the same as in FSX by it's Build number).
I'll start another thread on that.

@d_stickman: in the mean time, I'll explain how you can solve this yaw problem yourself, in a next post.

Rob

 

[d_stickman]

Thank you, Sir, that would be awesome. We have a big Military event coming up at the end of the month. Any Vatsim rated VSO pilot can attend, check it out at http://www.vatmilex.com/

 

[rcbarend]

Seems to me that the MV-22 rotates much slower when using the rudder pedals while in a hover using v4.2 compared to how it responds in v3.2. Is this just my imagination or are their other people experiencing the same problem? If so is there any possible fix to get it to perform a bit faster using the rudder pedals?

See my previous post, that explains this.

How you can solve this for now (on your P3Dv4.2):
- Edit the file ...\panel\rcb-gauges\VSTOLControlIPC_Function.xml with a simple pure-text edittor, like Windows Notepad. (make a backup first !)
- Find the value 0.06 or 0.09 and replace this value with 0.29.
NOTE: whether you find the value 0.06 or 0.09 depends if you have installed my Addon1 for the Osprey Rel2 or not; but in both cases, these numbers are unique ..
- Save the file.
- Start P3D, and load the Osprey Rel2.
- Do a vertical takeoff, hover, and check if the aircraft yaws a full 360-degrees circle in about 20-25 sec at full rudder (which is what I intented).

Works Ok now ??

Rob

 

[d_stickman]

What specifically do I edit or is it in my case all the areas where I have 0.09?