SAS should never be deactivated - you will get warnings and it is considered an emergency IRL. You should also see a more significant torque-induced yaw, that will require more pedal to compensate. Though it is not as violent as you may see on other helicopters. (This is accurate)
The limits described above are based on the MH60 NATOPS manual, with some adaptations to the simulator.
Yes, very smooth-precise-stable hovering, taxing, landing or taking-off, SAS off or on, and without any helicopter help switched on, in the Simulator settings.
Would be impressive to have it also in the own FS24 career-mission.
What I have noticed when I was in online with a SAR version and others online with other versions, was that they had the GPU cart attached still in the air flying, when close to those helicopters.
Testing and flying more, usually SAS and autotrim enabled are the same practically for flying sportive and sharp turns close ground etc., similar like when all them are off, though sometimes after being flying during sometime, SAS and autotrim get like glitchy or less permissive similar when the autopilot is also on, like if they enter in a less permissive mode?, and the cure-workaround is disable SAS-autotrim and re-enable them after, not a big problem neither.
Just wanted to provide a general update on a few pending topics:
MH60 NATIVE FS24 - RELEASE ON MARKETPLACE
After a long (and honestly, frustrating) marketplace ingestion process, weāre happy to announce that the MH-60 has been fully approved for release. Itās now queued for the next available release window, most likely Monday next week.
While we canāt confirm the exact date with absolute certainty (as final scheduling is in Microsoftās hands), everything on our side is greenlit and ready to go.
Once the MH-60 is released and available across all vendors, weāll move straight into the next round of MH-60 updates. A full changelog will be shared in the coming days.
MILTECH SIMULATIONS MISSION HUB UPDATE
Weāve been hard at work on the first major update for Mission Hub over the past few weeks. This update focuses mainly on bug fixes, optimization, stability improvements, and a handful of the most-requested features.
All core development work is now wrapped upāweāre currently finalizing a brand-new mission pack. The update will launch with 12 new missions set around the world (including some inspired by current events), plus 6+ community-made missions.
Release is scheduled for September 24th on MiltechSimulations.com
and IniBuilds. Thereās been a small delay due to hardware issues during testing, so thanks for bearing with us.
This update also adds the necessary changes for full Xbox compatibility. The Xbox release (for both 2020 and 2024) will follow shortly after the PC rollout.
Forgot to add - we are also working on (and starting to upload) a Youtube Series on Mission Hub. Tutorials, tips and tricks. We just uploaded the first two videos:
Thatās fantastic news! I play MSFS on the GeForce Now cloud gaming service, where weāre limited to the Marketplace only (even though itās the PC version), and Iāve been eagerly waiting for this moment since the release of the MH-60.
Weāre happy to announce that MH60 is now officially released on the MSFS2024 Marketplace, for PC and Xbox!
We are excited to finally bring you the full native MSFS2024 version of the aircraft, after a few delays caused by ingestion issues. We are also pleased to share that the aircraft has been ranked among the top reviewed in the MSFS Marketplace.
It initially showed on the 2024 MP as the newest a/c but labelled as a 2020 model. I went ahead and purchased it anyway and tried a flight from the San Diego CG station but was getting a regular stutter every few seconds. Restarted the sim and decided to try Kodiak to see if the performance would be better. The MH60 was no longer selected and had been replaced with the default C172. Reselected the MH60 and my cockpit views had been reset. I suspect that the streamed model was initially the 2020 version but had now been replaced with the 2024 model, causing the a/c and cockpit view resets. It no longer has the 2020 label in My Library.
Flying around Kodiak the performance was good. Night flying around NYC was ok but there were signs the system was struggling with occasional stutters and ATC audio break-up. Still flyable though, including a landing at MK Studios KLGA.
I was able to create a FP using the Miltech web based planner and get it loaded. Nice that this works well on Xbox. Looking forward to the Mission Hub.
Ugh Iāve been loving flying the MH60, so so happy Question - and forgive me if itās been asked or talked about before but I canāt see to find it - Will there be the ability to use NVG from the cockpit view? I read somewhere that it exists already? Can anyone help Thanks
NVG is currently only possible from a shaders level (Reshade or Nvidia Shaders, PC only). That being said, we are experimenting with other solutions that may work on Xbox, even if itāsnāt proper NVG.
Iāve experienced an intermittent cockpit lighting issue. When night flying with all seven of the overhead rotary lighting switches turned up Iāve had a bright white light illuminating the cockpit on three separate occasions. Each time Iāve found that turning the Glare Shield rotary to off has fixed the issue fror me on Xbox. I was flying MP with a friend on PC and he had the same issue. His wasnāt fixed with the Glare Shield to off but one of the other rotaries. I donāt remember which.
Generally the cockpit lighting has performed as expected although it would be nice if there was a way of dimming the white and NVG lighting activated by the switch above and behind the pilotās left shoulder.
Xbox performance and stability have been pretty good. I did have what seemed to be a WASM crash where I lost all displays and had no AP controls. I was able to land and shortly after the displays came back and the a/c leapt into the air. I think Iād been in RadAlt hold at the time of the suspected WASM crash.
This doesnāt sound like a WASM Crash, but rather a low-VRAM āAvionics Blackoutā. Neither the autopilot system nor the displays run on WASM. It is also consistent with landing and recovering the systems - as VRAM consumption decreases, the aircraft loads again normally.
This is unfortunately quite unpredictable on Xbox, and largely depends on the area youāre flying, other addons installed, etc.
These arenāt dimmable IRL, at least AFAIK. Will take a look at potential solutions, perhaps could be a configurable option on the CONFIG submenu of the Keyset.
If this occurs again, pls send us a screenshot/video via our support channels ( Contact )
Donāt think Iāve seen this one before