is there a quick way to see the TAS ?
Without a GPS to show you? No. You would have to do the math or use the telemetry feature with Navigraph. Little Navmap will also display it. There is no TAS indicator in the aircraft itself.
the GPS shows GS, same as the HSI
is there a way to change GS for TAS with the gps?
You can change one of the user fields on the PMS GTN to display TAS.
1 Like
There is a page on the gps to calculate TAS built in. One of the aux pages.
1 Like
So, I’ve got about 70 hours on my King Air presently, with both engines’ wear at 90% (I put the wear on them in the first couple flights, wear has been stable since then). Despite all my flying in the Northern Australian heat, I have never been temp limited, only ever torque or power leaver limited.
In my RW experience, including many years of flying B200s around the same area, we were always temp limited during the climb. Somewhere between 10K’ and 15K’, whilst increasing the power leaver during climb to maintain climb torque, we would hit our ITT limit. Always well before reaching full forward on the power leavers. Granted these were smaller engines than those on a B350 (so maybe they were worked harder), and they definitely weren’t 70 hours from new.
Saying that, I’ve never experienced the same with the BS King Air. Whilst increasing the power leaver to maintain torque during the climb, I always reach full forward well before I reach ITT redline, or even a lower limit such as 780°, which many RW operators impose to improve engine life.
Can anyone with RW B350 experience tell me if they are ever temp limited. Secondly, can I expect the engines to slowly run hotter and become temp limited, the more hours I put on the BS aircraft? Or lastly, is this just a limitation of the MSFS turboprop simulation? (Which has been poor for generations, so I understand completely.)
8 Likes
I might have asked this question before, but is beta range fully implemented on this plane now? Or does it go straight into reverse like all other turboprops due to limitations in the sim?
1 Like
beta range isn’t implemented yet
Im having issues adding liveries - Im downloading and unzipping into the community folder but they dont show up in the livery list- Other liveries for different acft work fine…Is there something Im missing?
Two possibilities:
-Make sure there isn’t an extra folder level, which often happens when unzipping. It should be Community\[Liveryfoldername], and directly under the LiveryFolderName should be a layout.json and manifest.json and other files/folders. I’ve done this a few times…easy mistake.
-Make sure the sim’s not running when you put things in Community. FS2020 registers all Community folder items when the FS2020 starts.
Also make sure the liveries are for the Blacksquare model. If you install a livery made for the Asobo king air, you need to do some complicated conversion per the manual to get it work on the Blacksquare plane.
Hi all!
I did both of these so far- the liveries were specifically for the BlackSquare and the path should be right-
- Does this look incorrect?
Looks correct. Was this downloaded from Flightsim.to? Was it the one below? I’m in the middle of a flight, but can try installing it later.
Oh, one thing I noticed…there are spaces in your folder name. None of my subfolders underneath Community has spaces, just dashes or underscores, so thinking this might be the problem. Try renaming the folder accordingly..I think the folder name is arbitrary.
Well, not complicated, takes less than 5 mins to do a conversion job that drops into the existing paint structure ( rather than some unnecessary duplication ). From memory some of kychungdotcom 's paints come with that structure already, if you need examples.
Spaces should be fine.
That’s a vital thing when operating a turboprop. Do you have any idea if and when this will be implemented?
Welp, I installed this livery, left the spaces in the name, and it works fine for me “as is”. Not sure why it doesn’t work for you.
AFAIK there’s been no news of it coming. Their recently released TBM does have those features, so maybe they’ll do it but there’s no official announcement yet
Ok so I’m a bit surprised this worked but…
Jaydee posted on the PILOT’s Dash-7 topic this mod to add beta range to that aircraft. Out of curiousity I took his code, changed it a bit to work with just the 2 engines the KA has, and it seems to work!
So if you want Beta in your King Air here’s what you do:
- go to your bksq-aircraft-analogkingair folder and make a backup of engines.cfg
- open engines.cfg and change the minimum_on_ground_beta to 15 and save
- go into the model folder and make a backup of AnalogKingAir.xml
- open AnalogKingAir.xml, scroll down to line 443 and make sure it says
</UseTemplate> - Press enter to make a new line and paste the following code in:
<UseTemplate Name="ASOBO_GT_Update">
<FREQUENCY>60</FREQUENCY>
<UPDATE_CODE>
(A:GENERAL ENG THROTTLE LEVER POSITION:1, Percent) 0 < if{
1 (>A:PROP BETA FORCED ACTIVE:1, Bool)
15 (A:GENERAL ENG THROTTLE LEVER POSITION:1, Percent) 15 / 30 * + (>A:PROP BETA FORCED POSITION:1, Degrees)
}
els{
0 (>A:PROP BETA FORCED ACTIVE:1, Bool)
}
(A:GENERAL ENG THROTTLE LEVER POSITION:2, Percent) 0 < if{
1 (>A:PROP BETA FORCED ACTIVE:2, Bool)
15 (A:GENERAL ENG THROTTLE LEVER POSITION:2, Percent) 15 / 30 * + (>A:PROP BETA FORCED POSITION:2, Degrees)
}
els{
0 (>A:PROP BETA FORCED ACTIVE:2, Bool)
}
</UPDATE_CODE>
</UseTemplate>
Save and try it out. I think I’ll do the same for the Caravan and post it over on that thread. Again, thanks to Jaydee for the code. 
edit: updated the code to the one JD sent below
7 Likes
The King Air has slightly different settings in the engine cfg.
And since it dont have a marked DISC position you could simplify it a bit:
(A:GENERAL ENG THROTTLE LEVER POSITION:1, Percent) 0 < if{
1 (>A:PROP BETA FORCED ACTIVE:1, Bool)
15 (A:GENERAL ENG THROTTLE LEVER POSITION:1, Percent) 15 / 30 * + (>A:PROP BETA FORCED POSITION:1, Degrees)
}
els{
0 (>A:PROP BETA FORCED ACTIVE:1, Bool)
}
and the same for the second. And dont forget to change the
minimum_on_ground_beta=10 in the engines.cfg to
minimum_on_ground_beta=15
for the caravan use
(A:GENERAL ENG THROTTLE LEVER POSITION:1, Percent) 0 < if{
1 (>A:PROP BETA FORCED ACTIVE:1, Bool)
15.2 (A:GENERAL ENG THROTTLE LEVER POSITION:1, Percent) 20 / 30.2 * + (>A:PROP BETA FORCED POSITION:1, Degrees)
}
els{
0 (>A:PROP BETA FORCED ACTIVE:1, Bool)
}
and
minimum_on_ground_beta=15.2
Cheers
5 Likes