- Messages
- 76
- Country

Hello All,
I am really hoping that someone within the community can help me out here. First off, I am not a developer by any sense of the word. a lot of this stuff is total Greek to me. Not to say, that I don't have a willingness to learn.
My issue: I downloaded Flightport's freeware Cessna/ Soloy 206 planes from SOH. The T206H (all variations) and the U206G. Both Mark I and II, v2, v3, and v4.
I installed the v4 of the planes and test flew them. The looks and sound were great! The flight dynamics are not right or I have some issue going on.
Each plane, no matter the model or variation of the planes tend to pitch up extremely, the more throttle, the more upward pitch. I tried backing off the throttle to 3/4 and even 1/2, all it does is pitch down into a nose dive.
Some of the things I have attempted to try and resolve the issue:
1. Swap the .air files between the different variation of models. - Result: no change for most, some responded with little power
2. Substitute a different developers excellently working C206 .air file - Result: Little to no take-off power (acceleration)
3. Subbed out by using Microsoft's default 208 .air file - Result: same as attempt #2 (moved like a snail)
4. Went to Flightport's website to get assistance for their product, to discover that they no longer support FSX and do not appear to be developing for it any longer.
I love the work that the dev(s) put into the looks and sounds of the planes and I'd really like to utilize them in the simulator for some of my Alaska bush flying.
I was hoping that someone here at fsdeveloper might have came across the same issue with these Flightport Cessna/Soloy (Mark 1 & 2) 206's and had a guided hand towards a fix or possibly a corrected set of .air files for them.
If there is a possibility that this is something a non-developer, like myself can capably fix with the correct tools, then I'm willing to try to fix it on my own. At least that way, when I run into this type of issue in the future, I might just be capable of making the fix for myself, versus asking for help all the time.
Heck, who knows... I might even learn enough to help out the next ME that is in need of assistance.
Any and all help or guidance is very much appreciated. If there is anything I can provide, that will help in a solution, please let me know.
Thank you in advance
~WEB~
I am really hoping that someone within the community can help me out here. First off, I am not a developer by any sense of the word. a lot of this stuff is total Greek to me. Not to say, that I don't have a willingness to learn.
My issue: I downloaded Flightport's freeware Cessna/ Soloy 206 planes from SOH. The T206H (all variations) and the U206G. Both Mark I and II, v2, v3, and v4.
I installed the v4 of the planes and test flew them. The looks and sound were great! The flight dynamics are not right or I have some issue going on.
Each plane, no matter the model or variation of the planes tend to pitch up extremely, the more throttle, the more upward pitch. I tried backing off the throttle to 3/4 and even 1/2, all it does is pitch down into a nose dive.
Some of the things I have attempted to try and resolve the issue:
1. Swap the .air files between the different variation of models. - Result: no change for most, some responded with little power
2. Substitute a different developers excellently working C206 .air file - Result: Little to no take-off power (acceleration)
3. Subbed out by using Microsoft's default 208 .air file - Result: same as attempt #2 (moved like a snail)
4. Went to Flightport's website to get assistance for their product, to discover that they no longer support FSX and do not appear to be developing for it any longer.
I love the work that the dev(s) put into the looks and sounds of the planes and I'd really like to utilize them in the simulator for some of my Alaska bush flying.
I was hoping that someone here at fsdeveloper might have came across the same issue with these Flightport Cessna/Soloy (Mark 1 & 2) 206's and had a guided hand towards a fix or possibly a corrected set of .air files for them.
If there is a possibility that this is something a non-developer, like myself can capably fix with the correct tools, then I'm willing to try to fix it on my own. At least that way, when I run into this type of issue in the future, I might just be capable of making the fix for myself, versus asking for help all the time.
Heck, who knows... I might even learn enough to help out the next ME that is in need of assistance.
Any and all help or guidance is very much appreciated. If there is anything I can provide, that will help in a solution, please let me know.
Thank you in advance
~WEB~

