139 Helicopter - MSFS2020 CFD Test
Вставка
- Опубліковано 21 гру 2022
- Video Review by Helisimmer: • A Lama, A Huey AND a D...
Review: www.helisimmer.com/articles/p...
Starting to configure the dynamic flow management values, the possibility of attributing the detailed parameters of the structure of the blades, the weights, the dimensions and their adaptive balancing to the simulation environment, allow complete customization to achieve extremely high realism. The 139 is a twin engine with very high power and managing it is not easy, in these tests there is no assistance or SAS to set the engine values with the same performance described in the real manuals. It is very satisfying to develop with all these details, personally I have never seen anything like this on other home simulators. Great Job ASOBO!
#aw139 #msfs2020 #helicopterx1
Cannot wait for this in MSFS2020!
Looking fineee
great! as someone who comes from DCS and only uses helicopters I can't wait to try it out (when possible)
Thanks Diego! It's not easy and I work alone, maybe some well-known brands will be able to develop it before me
🎉❤Danke 🎉❤
Any idea what kind of timeframe you are looking at before making it public? Awesome work
Thanks so much!!! The work is very complex and the AW139 has thousands of systems that I will have to import from my model for P3DV4/5. Besides ASOBO has to solve some problems related to Engines... I'm working hard on it, thanks for your support.
It looks good. One question... does it autorrotate???
Hi Carlos! I'm currently writing the values with the engine at 100% to replicate the performance as per the manual. Then, with the same development criterion of 2.1/2.2 for P3D, I will check the loss of efficiency caused by weight and balance, OAT, single Engine, and later also the autorotation, and if something does not respect the specifications of the manual, I will use the simvar for motors and the 'acceletarion_body' imported and extended from the old P3D. It took two years for MSFS to develop something serious and now they have! If you take a look at the cfg of their Cabri G2 you will see how many parameters they have added for the management of rotors, fuselage, motors, etc... if you watch some videos on the web of the cabri g2 you will see the various progresses, here an autorotation: ua-cam.com/video/5WTBbmW_HQE/v-deo.html
Great Job! I am really struggling with rotor inertia and drag. It's like the rotor is in space somewhere and spins forever. If you would counter that with parasitic drag, you would get an abnormal drift. Do you have the same problem on your project?
Evreything based about flight model you are working on. If you use values imported from a 'legacy' model ( with .air ) you will need to convert 'air data', but if you use a completely new flight model like mine ( use_modern_surfaces = 1 ) you need to write correctly the rotors and fuselage data, this guide it helped me a lot:
docs.flightsimulator.com/html/Content_Configuration/SimObjects/Aircraft_SimO/flight_model/helicopter.htm
@@Helicopterx1 Thanks a lot for the reply. Yes, I use the new CFD model and it's not imported. All data is correct and measured either by myself or taken out of the manual. I even have the correct data for rotor MOI.
I am aware of what the values do, but the problem is the following:
Whenever I add some amount of drag, either induced or parasitic, it hangs around 10° left in hover (counter clockwise spinning rotor). If I decrease drag the rotor keeps spinning forever and can't be controlled by the engines anymore (as if it was in space and has no inertia at all).
That's the reason I wanted to now, if you've had similar difficulties. I noticed that this would also happen in the cabri or the 407.
By the way, I am really looking forward to see your beauty come to live! It looks very promising!
@@benking2086 Similar problem happened to me when I started editing the legacy values but once I disabled all the old legacy values and tested the empty_weight_pitch/roll/yaw_MOI values, weight, position and RPMs of both rotors millions of times and wrote some variables to replace some default PIDs I'm managing to write the correct parameters for the engines. It is a known problem which has also been communicated to ASOBO and which some developers are experiencing, we hope they will be resolved with the new updates.
@@Helicopterx1 Again, thank you very much for your answer. I really appreciate that you took your time.
I even could sort out some of the problems by just watching your video! That was very helpful. I basically had to do it your way by trail and error a thousand times restarting the flight and find out what's responsible for my hickups.
So again, thanks for sharing!
@@benking2086 It is a pleasure for me to collaborate and help, I hope you will be able to solve the problem, if you need any other information write me ;)
When is it coming?
It's still too early, the development is very complex and ASOBO has to solve some problems related to Engines
Any updates? =D
Here some news: ua-cam.com/video/ESFQ6iIpxZ0/v-deo.html www.helisimmer.com/articles/progress-aw139-msfs
It will be a payware right?
Yes :)