• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Cessna U206G Soloy Mark 1 V3.0 is available

I found the type certificate in the LBA's database and I figure that's all I need. The gauge, if anything, is supposed to be universal and the 206 is just the test bed. So it's probably going to be torque, ITT/EGT, prop RPM and oil as limiting factors.
Not sure if compressor stalls are an issue for turboprops as much as they are for pure jets.
 
I've got the 206 in the simulator. If I may, here's some more things I found:

1) In U206G_sound.ini, get rid of the absolute paths. E.g. "Sound00=Soloy_sound/click.wav" is all it takes to play the sounds, so you can install the U206 anywhere.

2) Adding the clickspot to the sun visor glass would make them easier to use.

3) To avoid the "both or none" problem for the props, mil anteanna/cargo pod and nav radios, modify the respective clickspots in config.xml like this:

Code:
<Area Left="99" Top="211" Width="22" Height="23">
        <Tooltip>Display 3 Blade Prop</Tooltip>
         <Cursor Type="Hand"/>
         <Click>0 (>L:proo3,enum) 0 (>L:pro5,enum)</Click>
      </Area>

       <Area Left="99" Top="261" Width="22" Height="23">
        <Tooltip>Display 5 Blade Prop</Tooltip>
         <Cursor Type="Hand"/>
         <Click>1 (>L:pro5,enum) 1 (>L:proo3,enum)</Click>
      </Area>

...

       <Area Left="99" Top="470" Width="22" Height="23">
        <Tooltip>Antenna Custom</Tooltip>
         <Cursor Type="Hand"/>
         <Click>(L:antenne_costa,enum) ! (>L:antenne_costa,enum) 0 (>L:cargo_pod,enum)</Click>
      </Area>

       <Area Left="99" Top="525" Width="22" Height="23">
        <Tooltip>Cargo Pod</Tooltip>
         <Cursor Type="Hand"/>
         <Click>(L:cargo_pod,enum) ! (>L:cargo_pod,enum) 0 (>L:antenne_costa,enum)</Click>
      </Area>

      <Area Left="472" Top="211" Width="22" Height="23">
        <Tooltip>Display Garmin 530 430</Tooltip>
         <Cursor Type="Hand"/>
          <Click>0 (>L:garm,enum) 0 (>L:gtn,enum) 0  (>L:kln,enum) 0 (>L:rxp_garm, enum)</Click>
      </Area>

      <Area Left="472" Top="262" Width="22" Height="23">
        <Tooltip>Display GTN 750 650</Tooltip>
         <Cursor Type="Hand"/>
          <Click>1 (>L:garm,enum) 1 (>L:gtn,enum) 0  (>L:kln,enum) 0 (>L:rxp_garm, enum)</Click>
      </Area>

      <Area Left="472" Top="313" Width="22" Height="23">
        <Tooltip>Display KLN90B</Tooltip>
         <Cursor Type="Hand"/>
          <Click>1 (>L:garm,enum) 0 (>L:gtn,enum) 1  (>L:kln,enum) 0 (>L:rxp_garm, enum)</Click>
      </Area>

      <Area Left="472" Top="364" Width="22" Height="23">
        <Tooltip>Display RXP GNS 530 430</Tooltip>
         <Cursor Type="Hand"/>
          <Click>1 (>L:garm,enum) 0 (>L:gtn,enum) 0  (>L:kln,enum) 1 (>L:rxp_garm, enum)</Click>
      </Area>


4) A clickspot on the door lock lever for opening and closing the doors would be nice. Not sure if there's a default one. Give me a shout on FSDev if you need code.

5) Some descriptive tooltips for the custom cockpit controls (e.g. glareshield light switch) would also be useful.

6) Not sure what the VA-1A indicates in the real U206, but switching to "VA-1A!VA-1A main" in the panel.cfg makes a bit more sense to me.

7) Is the ammeter in the cockpit functional?

8) Is the cowl flap and alternate air control the same? Because the red knob labeled "alternate air" is inoperative and the cowl flap lever is labeled "alternate air".

9) I've made a quick and dirty GPU gauge that will run FSX' APU when the GPU is displayed while stationary on the ground to provide endless electrical power. Also plays (inappropriately powerful) start, running and shutdown sounds. Message me on FSDev, if you want to implement it.
 
Oh, one more thing for Thomas: If you're interested to add moving rain to the windows, give me a shout on FSDev. It's not much work.
 
Hi Bjoern,

very very great and helpful, it seems that most of points could be done. I will give you a call in FSDev - for APU and rain effects, that would be wonderful to get both in Mark 1 and upcoming Mark 2. I will finished modelling work on Custom model this weekend, Alexander will do the airfiles, again.
 
Bjoern,

attachment.php
 
Wow, now there is a lot of movement around - first, I got sdk of G600 of F1 with all I need. Its a nice work from modelling point of view. At least much work, but it is the same like GTNs, GNSs or RXP, so there is nothing special new. Bjoern sent all the info I need, thats great. Many thanks Bjoern!

Anyway, all these improvements are on the list with Mark 2, now. Later, I will send Alexander the first Mark 2 for adjusting airfiles and other improvements. Soloy Aviation sent us helpful contact informations about Mark 2. And last but not least, perhaps we have a new engine sound.

31718351nt.jpg

:wavey:

Thomas
 
I've paid good money for planes that weren't half as good as this. Many thanks, Thomas! A true masterpiece....
 
What a wonderful flight I had today indeed!!! Thanks to Thomas and his wonder-craft... :applause: Although the start-up procedure seems a bit sophisticated for my old brain.

But I think I'm doing smth wrong here. My only option was the auto-start. Well, actually I've tried to follow what's described on p.8 of the included manual. But whatever I try to start the engine manually, I always fail. XMLTools is installed and recognized by FSX. I checked the throttle - GROUND mode is on, fuel CUT OFF, propeller level IN. But the N1 needle doesn't go up to reach 13% when the starter is engaged, even when I open the fuel lever (back to IN position). Then, when the engine is finally started, plane starts rolling unexpectedly (even after autostart and throttle at 0%). Even the brakes can't stop the roll... Anyway... Continue experimenting. :mixed-smiley-010:

Any advice with manual startup?

PS: Also, anyone with performance tables / fuel /range data for this birdie? Google search was useless so far...
 
Last edited:
Wow, now there is a lot of movement around - first, I got sdk of G600 of F1 with all I need. Its a nice work from modelling point of view. At least much work, but it is the same like GTNs, GNSs or RXP, so there is nothing special new. Bjoern sent all the info I need, thats great. Many thanks Bjoern!

Anyway, all these improvements are on the list with Mark 2, now. Later, I will send Alexander the first Mark 2 for adjusting airfiles and other improvements. Soloy Aviation sent us helpful contact informations about Mark 2. And last but not least, perhaps we have a new engine sound.
Great news indeed!

Any frame rate hit with the G600 installed? I have the GTN units and they are fine on my system.
Just curious before making a second deep never-on-sale plunge into the wallet.
The G300 in the Flight1 Skycatcher was a total frame rate killer for me.
:ernaehrung004:
 
Sorry for bring up this very old thread and sorry if I offend any of you but I am wondering if I have to install XMLTools for FSX into my FSX Deluxe with SP1 and SP2? Is it possible to use this plane without XMLTools for FSX? Regards, Aharon
 
Sorry for bring up this very old thread and sorry if I offend any of you but I am wondering if I have to install XMLTools for FSX into my FSX Deluxe with SP1 and SP2? Is it possible to use this plane without XMLTools for FSX? Regards, Aharon
The XMLTools file is needed for realistic engine behavior. If you aren't interested in that then you probably don't need it. Question is, why not install it? It takes very little time and you get the best performance from an excellent airplane.
 
If you aren't interested in that then you probably don't need it. Question is, why not install it? It takes very little time and you get the best performance from an excellent airplane.

Easy answer: TOO SCARED to install XMLTools.dll into FSX because I do not want to mess up my FSX!!!!!! :biggrin-new::biggrin-new::biggrin-new:

Regards,

Aharon
 
Aharon, XMLTools.dll is absolutely harmless. You can use it with confidence, because only airplanes that have been programmed with it can use it.

For the Soloy´s it is, however, necessary to have right engine indicators.

But this threat is definitely the wrong one - V4 are the actual Soloys...

Thomas
 
Back
Top