Hey everybody!
If you caught the last dev stream you probably heard Asobo name drop us again as a potential partner for helicopter development.
Please help us signal boost this tweet with a retweet or like (or both!) in full transparency we’ve reached out to their team multiple times since the inception of our Airbus H135 but it’s been radio silence from their end.
https://twitter.com/hypeaircraft/status/1411008214045499392?s=21
Why is MS ignoring your emails if they need help with helicopter development? Perhaps @Jummivana or @Skeedorr can help.
I don’t want to assume they are ignoring our emails, maybe we are going to spam or they have been incredibly busy - I actually just realized I missed an important email from 5/25 at work that is getting me in a little trouble right now 
I just want to them to know if they want to talk that so do we!
Include Hype !
I saw that and heard Jorg say it himself that he was very impressed by the H135 by Hype Performance Group.
This news that there has as yet been no direct communication between the entities is surprising given what was said…but strangely inline with other disconcerting revelations about MSFS internal handling of information and communication
I’m still experiencing weird flight model issues with the latest version:
As you can see it still displays the same “digital” movements as described before, but now not just on the yaw axis, but the vertical position. You can see in my video how it moves in big jerky steps, there is nothing smooth, gradual or organic about it, which really puts a dent in the enjoyment of the helicopter.
And yeah, that is still with the Modern flight model and everything set to realistic. Happens with or without autopilot.
The wind is a bit variable as far as the direction goes, but it shouldn’t have that much of an effect at those windspeeds. And even if it did, the helicopter shouldn’t “teleport” to a new position every couple of seconds but transition in altitude gradually.
We’ve long believed that this behavior is due to how Asobo chose to add turbulence to the fixed wing flight model. People have noted that visiting the area again in a small GA aircraft will produce a similar (but obviously less annoying) effect.
I’ve been investigating performance for weeks and sometimes this effect can also occur if you have hangs on the main thread, but I don’t think that’s what you are seeing above. Slowing down may help but obviously again that’s not much of a solution for you.
Yes. I am having the same problem. Shortly after takeoff while in level flight it’ll suddenly careen violently left or right. I was also having a similar problem with other MSFS aircraft…I had to reload Windows 10 (for another issue), reinstall MSFS, and got new Logitech rudder pedals (I use the Saitek x 52 Pro joystick and throttle). I also noticed that the joystick twist grip rudder was still enabled and when I deleted that, I haven’t had the problem in any fixed wing planes…it was apparently conflicting with the pedals. But I am not able to sustain any flight in the H135 without losing control and crashing. I am a long-time helo pilot in P3D and was excited that somebody created a helo for MSFS. But I cannot figure what the source of this latest problem is.
The only thing you should be aware of is that inverted flight is prevented, and you will fall out of the sky if you attempt to do so. I don’t think you’re doing this, but some people have mentioned that somehow they trigger this in level flight, and hear “the screeching sound” and then fall out of the sky.
What you are describing has been controls failing. Multiple people have come to discord with something similar, and every time have come back later saying they had a joystick that was bad (the pots going bad I suppose), or an extra one connected that would mostly be dormant and then suddenly activate and start issuing crazy commands. The way you described it, it does not match any other issue. If you are finding it very uncontrollable all the time then maybe you didn’t enable all the systems, but again, you describe successful flight for a short time then a control runaway/hardover.
Thank you so much Guy’s ! Your talented Team remind us of the Halcyon day’s of FSX Gold when David Maltby , Rick Piper and many other gifted people were providing the Flight Sim community with well Rendered Aircraft at great cost in time and effort to themselves.
We will be more than happy to pay for your forthcoming Work and thanks again for your generous contribution to our beloved Sim.
Kind Regards.
ps. We were out walking with our Collies this morning and the Wiltshire Air Ambulance flew overhead.
Beautiful shots, and thanks for the kind words 
Likewise,… Beloved Co Pilot is the Screen Shot Whizz.
She’s sitting here with the Pooch’s. i can assure you that all Tails are a Wagging and especially BCP’s who say’s Thanks for the compliment.
ps. WOW ! We just watched the Promo. Superb Job !
pps. Our new Helicopters are being prepared in their Hangers. Thanks David !
I have performance issues with the cockpit view of the EC 135 helicopter. In the cockpit view, my frame rate is bad, stuttering, choppy.
I have a 2080ti video card. I don’t have a performance issue. I only have problems in the cockpit of the EC 135 helicopter. In my opinion, digital instruments as well as helicopter systems cause performance degradation, stuttering, intermittency.
Carenado, Aerosoft, PMG aircraft are not a problem. So the fault is with the EC 135 helicopter.
What is causing the problem? Is the developer working on the solution?
Thank you for your answers
Hello, this question was also asked and answered on our Discord so I will share for others who come across this thread. The following is from our lead developer David Amenta.
Yes this is a reasonable concern. H135 avionics/displays are too heavy and this results in both slightly lower overall fps and sometimes the work causes a CPU hit which results in a stutter. I knew this would happen when I did H135 as I didn’t know what the performance considerations were. The H135 panels were a learning experience and prototype, they were made from mixing Asobo avionics into a new style but it was not until the end where I understood how all the components worked. I have been investigating performance for the past month since it was mentioned and have made some discovery, but am not rewriting H135 panels in the meantime. H145 avionics are currently much smoother, but I also cannot rule out that some will still say there is some stuttering. H135 should be compared to something like A320 in terms of complexity, not C152. Nonetheless I want it to be as fast as possible so the graphics can be complex but still be used all the time. Currently I have new panels optimized for drawcall/vram tradeoff, as well as some techniques to defer work when a frame is detected as being outside of the budget already (load balancing between frames). Additionally, in H145 you will be able to turn OFF all of the main displays (except the IESI), and the performance will be better as it will actually stop updating (doing work) for those displays. H135 “display power off” functionality is not correctly implemented, and does not conserve resources.
For H135 there is a file called LOW-END-PC.cmd in the package, if you run it, and restart the sim, it will disable the copilot displays, which can help conserve some resources as well
Flying the H135 in FS2020 is really fun. Lovely.
However, one thing that get me “confused” is the present algorithm for the camera placement in “external view” mode. Especially when hovering and transitioning from forward to backwards flight. The camera spins in sometimes confusing ways. I usually then have to switch back into the cockpit to stabilize the flight … and stop me head from spinning. 
So I guess this is one of the areas where FS2020 is still waiting for proper “heli support”.
camera placement is the equivalent of gold plated doorknobs in terms of what needs to be done in the sim to support helicopters. It’s literally the last of the last things to be done.
I have no insight into the Asobo work/code base … so I have no clue what they need to or want to change/or add in order to “support helicopters”.
For me: The H135 is flying … really nicely. So at least I am already enjoying helicopters in FS2020 and I am gladly crowdfunding the H145 effort. HPG is doing a great job.
That said, I am convinced that Asobo has different people on different parts of the system. And “fixing the camera” bug will most likely not be on the to-do list of the “heli flight physics team”.
I also would not consider the camera behavior a “useless luxury” (gold plated doorknobs) … as it is a primary means to maintain orientation while flying. It is a key source of joy … or frustration.
Now I do not even know who really controls the placement/motion of the external “follow me” camera. Does HPG have control over that? I am assuming they do not … but maybe I am wrong.
Besides that I have seen a similar “camera bug” when flying the King Air … sometimes the camera starts spinning around the aircraft vertical axis … which is really disturbing on final approach. Perhaps those two strange camera effects are related.
… just to provide a little more context to that “camera bug”. It feels to me like the following is happening:
I have the feeling that the H135 motion patterns … especially in “hover” or when transitioning to reverse flight … tend to trigger this bug way more frequently then I see this problem in my KingAir.
You can definitely see the inspiration in our work 
