Are you planning on making sample missions available so that people can create their own, which would integrate with the tablet, triggering stuff when you drop or pick something (or someone) up somewhere? If it’s easy enough I would be interested in doing a couple of things like that for the Osprey.
Yes and no:
-
The CH47D has a closed mission system. Only the development team can create missions due to the way it currently works. This is mainly due to cross-platform compatibility. A significant number of our users are on Xbox, and it is against our product philosophy to release products or features that only work in one platform.
-
A similar mission system will eventually come to the MV-22, after this system has matured enough on the CH47D. It is an easier platform to iterate and expand this module as the product has been developed around the “missions” component. The Osprey will require modifications, the addition of loads, etc. to make it fully compatible with the mission system.
So at this time, the mission system is entirely closed, and will remain closed. However, we are currently in R&D of a tool that will open up the possibility of on-demand custom missions across all our products, including carriers; and across platforms. More on that in a few weeks.
Find list of LVARs here:
Please beware that I cannot provide much assistance with these. The aircraft is not necessarily designed with hardware binding in mind as you may have noticed, but rather for correct interaction with the WASM Module.
For this reason, setting some of these LVARs may result in CTDs, as WASM is prone to crashing.
You should be able to set the MFDs, CDU and other buttons just fine.
Can you clarify that?
Do PC’s use the WASM module, or is it only applicable to the Xbox?
This only applies if you want to do complex hardware keybinding (eg. fly the aircraft entirely with hardware buttons, not using the mouse at all), and therefore only applicable to PC.
Thanks.
Perhaps I don’t understand what the MARYADI Lvars are, or what WASM modules are (and whether my PC uses them.)
I do have a PC. My goal is for ALL aircraft controls to be mapped to my cockpit peripherals, thus eliminating the mouse as much as possible. I realize that’s a lofty goal, and not always achievable. I’d like to know why…
Does my PC use WASM?
Are MARYADI Lvars related to mouse emulation?
WASM is a technology used by most, if not all payware 3rd party aircraft that allow complex features, such as custom flight model, complex systems, etc. Its a compiled module that runs in the background of the simulation, manipulating the simulation parameters.
LVARs are local variables that are manipulated and read by the WASM module to communicate with the different aircraft components - such as the buttons in the cockpit. Clicking a button will communicate a function to the WASM module via LVARs. Maryadi is just the name of the dev who programmed the Osprey inner workings, hence the naming convenction.
Unfortunately that’s as far as I can go in terms of explaining how to map functions to hardware buttons. I have very basic hardware myself so this is not my area of expertise, and this requires some significant level of understanding how the inner workings of aircraft in the sim works, and how the sim interacts with external hardware. There are communities dedicated to these stuff.
Ps - these concepts apply to any other 3rd party aircraft out there.
Thank you. I’m quite familiar with LVars, AVars, BVars, etc.
I use SPAD to map them to events on my Streamdecks and other peripherals.
By your explanation there are certain Vars used by 3rd party developers that work by communicating through the WASM module, thus can’t or at least should not be mapped.
So some mods use WASM, and those are used for both PC’s and Xbox. Correct?
I worked on this over the weekend, before the very useful google doc. MV-22B Osprey Axis and Ohs (AAO) Scripts for Microsoft Flight Simulator | MSFS
Thank you for sharing your scripts. Perhaps these scripts for lights, probe and AP will be useful as well. They are made for Axis and Ohs but the xml file should show what’s going on to Spad users.
Thanks so much @LikedHare478430! Got them today on the Discord and have been binding everything I can. The Osprey is a great real life aircraft and flying it in the sim shows me exactly why the military wanted it. You guys did a great job, and thanks for the frequent updates. This will be my go to aircraft for a good while! And I now know the CH47D will get the same attention so that will be next.
1 Like
Did the Osprey break at some point? The engines just flicker failure nonstop and won’t ever start.
Did an update break it?
1 Like
Not on my side … the Osprey still works as it used to since the last update.
Given that the MSFS 2024 trailer showed the Joby Aviation e Air Taxi this might open up the possibility for a more “native” new Osprey flight model in 2024.
The Joby is in essence a 6 Proprotor version of the Osprey 2 Proprotor.
The benefit could be that under MSFS 2024 that noticeable “kick” when the Osprey is switching between the two flight models might no longer be exist.
At this time we do not have any info if there will be native support for tilting proprotors. The flight model may very well be similar to the Osprey - in which custom physics are injected for the VTOL portion. This is also how the volocopter and Pelican (both Asobo’s VTOL aircraft) worked in MSFS2020.
Hence, until we have certainty of how the Air Taxi FM works, there is little to be done in that regard.
4 Likes
Yay! More scope for missions from Miltech amazing and growing support group eco system, can’t wait 
2 Likes
Major update? the major update id like to see is your v22 implemented in DCS!
1 Like
Not anytime soon, unfortunately… There are many roadblocks to overcome before that’s a possibility.
Finally getting an update and it still will fly like a brick ? 