MV-22B (1.3.3) - A Few Questions and Notes
Miltech Simulations/Maryadi team,
I am absolutely loving the MV-22B Osprey and Amphibious Ready Group package -- it is such a thrill for me, from starting it up from dark to takeoff, landing to BFWS at the end of a flight! A few rapid-fire questions and notes from my latest experiences with the product (mind you: the MV-22B and ARG package are the ONLY addons/mods I have on my MSFS install):
-
I'm not seeing any notes about the 1.3.3 update. Anything to account for flight ops-wise?
-
Prior to 1.3.0, the MSFS "My Logbook" would ID the variation of Osprey I flew based on the livery (e.g. - "CV-22 US AIR FORCE" when I selected the 8-SOS livery). Now the aircraft is only identified as "MILTECH SIMULATIONS - MARYADI MV-22B OSPREY." Any chance this can be reverted to show the name of the variant/livery used as before?
-
More notably regarding "My Logbook": the MV-22B is no longer logging takeoffs and landings in the respective logbook columns, despite that I always start my flight departures on tarmac and am landing and parking at my destinations. It's confusing why these aspects of the flight are now going unrecorded in the logbook.
-
The taxi ribbon assist no longer appears when using the MV-22B after taxi instructions have been given by ground. I've tried multiple parking locations and multiple airports. It used to work, right? Might this and my above finding that the logbook isn't recording takeoffs and landings be somehow connected? Like MSFS isn't recognizing the aircraft's location on the ground for some reason? In troubleshooting, the taxi ribbon works for MSFS's included aircraft, just not the Osprey.
-
Any way to stop MSFS from using the MV-22B model as AI traffic? When I spot other Osprey, it's only on airfield ramps and they are always missing one set of blades and the other set is spinning/clipping into the ground with nacelles in the horizontal position, but never taxiing or flying. A bit of a funny scene but I'm hopeful for a fix, even if that means they aren't used by the AI.
And a couple "neat to haves" for consideration:
-
Love that the aircraft loads up in maintenance mode with the blades in an inverted Y; however, maintenance mode isn't an option after shutdown. Might it be possible to get a maintenance mode configuration via the BFWS menu?
-
In flight, the ramp ought to be able to open level with the fuselage. It appears the "LVL" printed text callout is there near the ramp button, but the ramp goes either full open or full close. Would love for this to be possible to simulate a personnel deployment/extraction while in a hover.
All-in-all, thank you for bringing what must have been a super challenging aircraft to model to MSFS. I look forward to many more flights to come!
Regards,
Dustin
Miltech Simulations @MiltechSimulations-
Last version released is v1.3.1. Just checked and it seems the MS Marketplace changed the version numbers, apologies for that. V1.3.3 on the MS Marketplace is equivalent to V1.3.1 elsewhere.
-
No changes have been made on the aircraft.cfg file for the logbook to change the way it displays the variations, except for perhaps changing the ui_typerole to enable the Osprey to use helipads. I'll look into it, but very likely is a MSFS Change in the way it handles the variations, instead of an aircraft change.
-
Again, no idea what may be going on with the logbook. It could be that since the MV-22B is now recognized as a Rotorcraft, the sim handles things differently with regards to the logbook.
-
Same thing, may be related to the change of UI_typerole to Rotorcraft.
-
Open the aircraft.cfg in the installation path of the aircraft, and Change isAirTraffic=1 to isAirTraffic=0 at all of the [FLTSIM.X] entries found in the cfg.
-
This is already possible, use "Fold Horizontal" instead of "Full Stow"
-
This is already possible if you have the door switches on the overhead in the correct position. Refer to the manual, point 3. https://docs.miltechsimulations.com/v/product-docs/aircraft-and-systems/aircraft-systems/overhead-panel
- E@EXEventure
Thanks for the quick reply! I double checked a few things and could use some assistance. My responses below:
-
Got it! Thanks for the clarification.
-
Understood.
-
I see. No biggie. Just thought I'd check.
-
Dang. As if MSFS taxiway signage and markings weren't confusing/broken enough, not having access to the taxi ribbon with this aircraft is a bummer.
-
This is where I could use some help: I'm not seeing the aircraft.cfg file anywhere. I acquired the Osprey/ARG package via the in-game store (if that info helps in determining where it's located). I've meticulously worked through the miltechsimulations-aircraft-osprey-mv22 folder and subfolders, manually sorting through the files and using the File Explorer search. The only CFG files I am finding for the Osprey are as follows: texture, panel, target_performance, model, gameplay, cockpit, cameras and ai (and the ai one has no "isAirTraffic=1" line). I know the aircraft.cfg file must exist ... is it somewhere other than the main miltechsimulations-aircraft-osprey-mv22 folder?
-
"Fold Horizontal" folds the blades. I'm looking to put the nacelles back to horizontal position with the blades in an inverted Y, just as the aircraft starts when I load up a flight and start cold on the tarmac. One of the "MAINT RED," "MAINT GREEN," "MAINT WHITE" options that are crossed out would put the aircraft back in the horizontal nacelles, blades inverted Y config. I understand replicating all three would be a bit pointless for the virtual world, but would be neat to have access to one to put the Osprey back to bed in a maintenance config. I appreciate the consideration.
-
Hmm. No matter how I set the buttons, the ramp just goes full down. I've tried on the ground, in flight ... no change. The ramp is either full down or up, no level/horizontal positioning. Maybe the "Speed >1kts: Ramp is leveled" trigger is not functioning?
Again, thanks for being so quick to respond to my original message. I know this product has been out for a bit now, but I just got back into MSFS (last played in the FS2004 days) and have been absolutely enjoying the Osprey. Just wanted to share a few of my observations, for whatever it's worth.
Regards,
Dustin
Miltech Simulations @MiltechSimulations-
MS Marketplace encrypts some files, so it may very well be the case that aircraft.cfg is encrypted and therefore not accessible nor editable. In that case you won’t be able to edit the file, unless you contact us via email for license transfer to our website.
-
Can you please provide screenshots of how you’d like to fold the blades? You should be able to achieve it on the BFWS Menu + moving nacelles manually to the position you desire.
-
Make sure the middle switch is set to AUTO and doors are opened. As soon as you take off or increase speed, doors should automatically move into the leveled position. I can check later, but 99% sure it works fine
- E@EXEventure
Very much appreciate the quick replies! Bummer to hear about the aircraft.cfg file being inaccessible for me having purchased through the in-game store. As for the ramp, I'll have to give it another try a bit later, but here's what I mean with being unable to get the aircraft back into a blades inverted Y maintenance mode after flight/engine shutdown:
Above is how the aircraft loads in, in a maintenance mode with blades locked in the inverted Y. From what I can tell, this is the only time the in-game aircraft can exist in this config, currently. When I attempt to go back to this config following flight/engine shutdown, there's no way (using BFWS or by rotating the nacelles) to get blades back into the inverted Y. Rotating the nacelles horizontal, the props rotate freely (since they aren't locked via a BFWS menu operation) and end up clipping through the ground, as shown here:
As mentioned in my previous post, the "MAINT RED," "MAINT GREEN" and "MAINT WHITE" options in the BFWS menu (with the real aircraft) would achieve what's seen in the first image. Having access to at least one of those options in-game could enable the inverted Y for aircraft parking. As for now, the only horizontal config after flight/engine shutdown is a full stow or folded horizontal.
-
-
-