HPG claims a lot and nothing of that is or was true and the only time they are “active” or say anything is when they get called out for.
I expect there is probably something in the update that has a blocker that is why they did not include it with SU3. As that is why the C17 update isn’t included but at least Miltech have provided us that reason on their Discord.
Where as it’s still radio silent from HPG. The problem is with HPG they’ve been quite lacking on communication for a while and normally take a big discussion on their server to get a statement. They are a small team so I can understand that but even if the message was brief it is something to go of.
Hopefully we have some news from them soon though.
2 Likes
Hi everyone!
We turned over an update for the H225 in July that contained multiple fixes and enhancements. Our understanding was that our H225 update would be included in SU3. We are now understanding that our update instead ship alongside SU4. Unfortunately we do not have any details on why our update did not ship with SU3, but we will request some feedback from Microsoft and relay any additional information that we’re able to.
Below is the changelog that was previously communicated for our H225 update:
General Fixes
• Fixed issue where pilot avatar loads into backseat on “Ready to Fly” screen
• Resolved issue causing missing copilot
• Corrected LOD rendering bug on ESC Menu
• Fixed issue with helicopter losing textures and turning gray at LOD 7/7
• Addressed missing thumbnail images on Departure/Arrival screens
• Fixed aggressive stuttering after entering Pause Menu or crashing in career mode
Crew and Positioning
• Corrected pilot and copilot positioning in SAR/Cargo configurations
• Fixed cargo hold LOD issues when zooming in/out
• Adjusted rescue worker spawning behavior (now spawns as actual rescue worker, not pilot)
UI and Camera
• Checklist cam now properly focuses on N1
• Removed debug text AIRCRAFT.UI_INSTRUMENTATION from Configure UI
• Fixed display errors in the mass and balance menu; seats now show correctly and passengers spawn
Flight Controls and Simulation
• Gamepad mapping for collective input now functional
• Collective and throttle now respond correctly to both gamepad and key binds
• Fixed issue with aircraft behaving as if it were flying when on “Ready to Fly” screen
• Cold and dark state now correctly disables panel functionality
• Engine crank switch inputs now correctly mapped (no longer inverted)
Startup & Shutdown
• CTRL + E now properly triggers Auto Shut Down
• Auto start now functions as intended
• Aircraft no longer shuts down automatically on the “Ready to Fly” screen
• Resolved issue where skipping manual engine startup rendered aircraft inoperable
Checklist and Interactions
• Player avatar no longer clips through the aircraft
• External preflight checklist and interactables now available
• Checklists are now properly localized across all supported languages
LOD and Visuals
• Fixed EXT LOD texture issue on Pause Menu
• Addressed INT LOD clipping
• Tail number from Settings now correctly displays on aircraft
• Livery artwork has been updated and corrected
21 Likes
Mr. Jorge, 5 years of stories, lies, and smoke and mirrors,
please fix things now.
Enough of this fooling around. That we are all not fools.
3 Likes
See.. these are the types of updates we need from the developers, atleast we know that something is getting done about it, just a shame that Asobo prefer not to let their paying customers know what’s going on, just ignore our questions unless it suits theM, and before anyone pipes up saying they do, there have been many many questions regarding the issue with the collective and other thing with other aircraft which are totally ignored
5 Likes
Inoperable aircraft. The collective cannot be operated with keybinds. Only the “next detent” and “previous detent” keybinds work, which means either 100% or 0% collective. It cannot be flown in this state.
Another issue: most of the tooltips don’t state what the switch is for, they only display the status. Like you highlight a switch and it says “Off”, but not what that switch actually is.
5 Likes
One would think Asobo, the main developer behind MSFS24 dont have any Microsoft Oversight, like at all
Quality Assurance is lacking in more than just microsoft these days!
Its like theyre trying to speedrun “too big to fail” concept, while simultaneously crashing and burning!
1 Like
The C17 Update 2 have a major issue, Miltech is very transparent on this …
Stop bashing Asobo, is not Asobo is Microsoft. If a update have a issue, is not release is simple. Jorg say early this year, communication with HPG is not easy …
If I recall correctly, he also said that not all updated aircraft would make it to SU3 and would be included with SU4.
the fact that aircraft updates are tied to gigantic SU updates that take 3-4 months to develop needs to end. We need WEEKLY aicraft updates. Most stock planes in MSFS24 have serious issues that need to be addressed right now, not in 3 months.
27 Likes
… or allow the community to create mods for the aircraft and helis.
Put simply: the clever people amongst us will do the work Asobo is supposed to. And fast.
6 Likes
honestly, no. I want fixes to be vetted by some kind of official entity, though optional user fixes are welcome in any case, as long as they’re not bundled with the sim
1 Like
Why? Even initial releases aren’t vetted by anyone at all it seems
Slippery slope. Once you accept that planes are “randomly fixed” by random people there’s absolutely no hope.
Again I’m ok with it being user side not mandatory, it should just not be in the sim: I realize as it stands it’s horrific, but I want to hope for a better future, not just “keep the ball we’re off”
1 Like
The majority of default MSFS airfcraft that have been brought to a high(ish, some might claim) standard are those with a Working Title influence in them.
And IIRC WT started by providing mods long before Asobo noticed them.
So, yes, I am all in favour of allowing the community to patch all the broken stuff. We’d have a half-decent H135 by now if that was the case.
6 Likes
Black screens and not working buttons here on SU4 beta when spawning on parking.
Ok, it’s on the beta but… 
The only walkaround I found is to do a “control+e” start, then turning on the GPU and the rest of the electrics manually
*It’s on the Beta and did not by now receive the updated version that was handled over to Microsoft as per the last developer stream.
1 Like
that’s the point of the “it’s on the beta but… “
Just to inform people
BTW, since someone brought that up, yes, we are waiting since february for updates to SEVERAL premium deluxe edition airplanes like this one and the C17. And it’s not the aircraft devs fault, they are also waiting the updates to be pushed.
So let’s see if on SU4 we FINALLY get the updates.
4 Likes
really appreciate this heads up
1 Like