That’s because they are piston engines, not turbines.
Doesn’t clear it up. Cowan can say whatever they want in “their” documentation. The fact is, that throttle in the H1256 is a “twist” throttle. The throttle on my Virpil collective is a “twist” throttle. Would be great if the H125 was updated to use my setup properly as IRL and as other helicopters have since SU12 was released. This is one of many issues with the H125 and other Cowan helis.
Also, was flying with a friend in multiplayer a few nights back. The cockpit on his aircraft was missing while I was viewing it from my H125. His aircraft was just a shell of the external fuselage. We intend to test further to see if it is in fact the H125. Wouldn’t be the first time a dev didn’t test their LODs in multiplayer. ATSims Cri-Cri comes to mind.
The mini 500 is a turbine.
In my point of view, it is all there to make even Turbine Helicopter Throttles to work with an axis. He is using a LVAR for the turbine Throttlegrip in his 206. All he needs to do is to add a mapping of this LVAR to any free AXIS in the SIM. He could even use something like the tiller_axis or propeller axis or spoiler axis or whatever axis is not used by the heli. It is just a few lines code in the interior xml in a update section. Maybe he isn´t aware of this function - but it is possible.
But I want to make clear: I tip my head and have a gigantic respect for him. His Helicopters still are a sign, that he is very skilled and competent.
Kind Regards
JayDee
I can confirm that the cockpit looks a bit too big in VR.
I’ve flown countless times in the real machine and for my purpose, the cockpit seems a bit too big.
Are you positively sure about that? The real one has a 48kw rotax engine and was a light kit heli, so I’d be surprised if the sim one is a turbine?
Read documentation, aware of throttle issues re MSFS.
However no amount of clicking the throttle to “flight” will increase my RPM above 276 which results in not able to fly.
This is using Hot start CRTL+E and not spawning running as that has throttle at proper RPM.
Yes, I own the product. It amazes me how much effort people go through to prove others incorrect when they themselves are the uninformed.
Ever since SU12 there’s a dedicated throttle axis for helis. So, he should be good to go from that perspective.
Yeah I know, but maybe it really doens´t work for turbine engines. I can not exclude this possibility by 100%.
I asked the question out of interest, there is no need for the informed or not commentary.
I don’t know why cowansim don’t ask you to work on H125 phisic. ![]()
Good job.
Thank you!
Just realized the VSI in this is inaccurate. For instance a vertical speed of 500 on the gauge reads as 1000 on the HUD VSI. The Cowan MD-500 has the same issue, though the error isn’t as severe on that one. Guess I need to check the 206 as well…
FYI I Was able to fix this by editing the interior xml and changed the value for the VSI animation from 6000 to 3000. I went to test this with the 500 which also has a discrepancy albeit smaller, but there’s no VSI animation like the 125 and also the 206.
This worked for me a lot better.
Is adjusting the static bank angle the best solution though? With these edits I find I need to add quite a bit of lateral trim every time I adjust the pitch trim. Conversely, someone posted a similar edit for the 500 which doesn’t adjust the static bank but instead adjusts the incidences of the tailplanes and the trim issues aren’t present with those edits.
I hear you, but it may be a good tweak for him. I’m thinking it’s hard to make flight model tweaks that work for everyone because of the vast range of control set-ups for helis. I have full-size controls with dampers and no springs, and it’s an improvement for me with no glaring downsides I’ve seen yet. Your complaints about trim are completely transparent with my set-up. MSFS helis seem to have too much control coupling, but that’s a sim issue.
The biggest issue for me (that’s specific to the AS350) is the governor. The PID values really need some work. I am used to rotor RPM (NR) exceeding the high limit if you need to reduce the collective a lot for descent (not a realistic behavior, but the XP Cowan AS350 has the same problem). But NR is all over the place any time you need to make larger inputs. The other night I somehow ended up in some greater-than-moderate turbulence from live weather while flying straight and level. The thing I noticed was that NR was fluctuating from 250-450 in response to the turbulence and my cyclic inputs. The controls became incredibly sloppy and I departed from controlled flight twice. I recovered once, but crashed the second time. I am not an excellent helicopter pilot by any means, but I can fly without crashing. That was pretty annoying to me. Haven’t seen this behavior in the 407 or the other two Cowan birds.
Released Finally today on Xbox Marketplace ![]()
Thoroughly enjoyed flying this on release day and waaaayyy too late into the evening. The AStar combined with the Aerosoft North Sea Landmarks was a real 4/20 miracle. ![]()
Was so excited to see the Flight for Life Denver St. Anthony’s hospital livery! I see this beauty flying over our area all the time IRL. Now I just need a better St Anthony’s helipad Addon for Xbox! ![]()
As others said this bird is sensitive. Definitely took time to wrangle and bumped down my cyclic sensitivity. It feels similar in to the B206 to me, especially when taking off/hovering/landing. I always have to give both helis a couple of whacks of trim up, otherwise when taking off they have the tendency to pitch forward. I’d rather push forward on the cyclic for small movements than be pulling back. Basically I don’t think the reset trim is set to neutral on these two. Trim feels like its set with two or three clicks of nose down trim to start.
Otherwise another outstanding piece from Cowan. I look forward to many hours rippin and tearin around windmills and ships in the North Sea!
Threading the needle…


