Black Square Steam Gauge Overhaul - King Air 350i

did you check after the recent update, everything must be in the AnalogKingAir.xml

on the first lines got those

	L Turbine Temperature:		"L:BKSQ_KINGAIR_ITT_L, number"
	L Propeller Torque:     	"L:BKSQ_KINGAIR_TQ_L, number"
	L Gas Generator RPM:		"L:BKSQ_KINGAIR_NG_L, number"
	R Turbine Temperature:		"L:BKSQ_KINGAIR_ITT_R, number"
	R Propeller Torque:     	"L:BKSQ_KINGAIR_TQ_R, number"
	R Gas Generator RPM:		"L:BKSQ_KINGAIR_NG_R, number"
	L Inertial Separator:		"L:XMLVAR_InterSep_L, bool"
	R Inertial Separator:		"L:XMLVAR_InterSep_R, bool"
	Oxygen Pressure: 			"L:var_oxygenPressure, number"
	Cabin Temperature:			"L:var_cabinTemperature, number"
	Pressurization Rate Set:    "L:var_pressurizationClimbRate, number"
	Cabin Press. Rate Actual:   "L:var_cabinClimbRate, ft/min"
	Cabin Press. Alt. Set:      "A:PRESSURIZATION CABIN ALTITUDE GOAL, ft"
	Cabin Press. Alt. Actual:   "L:var_cabinPressurizationAltitude, ft"
	Cabin Press. Differential:  "L:var_cabinPressureDifferential, psi"
	Att. Ind. Localizer	Flag	"L:BKSQ_KINGAIR_ATT_LOC_FLAG, bool"
	Att. Ind. GlideSlope Flag	"L:BKSQ_KINGAIR_ATT_GS_FLAG, number"
	Att. Ind. Localizer			"L:BKSQ_KINGAIR_ATT_LOC, number"
	Att. Ind. GlideSlope		"L:BKSQ_KINGAIR_ATT_GS, number"
	HSI Heading Bug Ring		"L:BKSQ_KINGAIR_HSI_HDG, number"
	HSI CDI Course				"L:BKSQ_KINGAIR_HSI_CRS, number"
	HSI CDI Needle 				"L:BKSQ_KINGAIR_HSI_CDI, number"
	HSI CDI Flag 				"L:BKSQ_KINGAIR_HSI_CDI_FLAG, bool"
	HSI GlideSlope Needle 		"L:BKSQ_KINGAIR_HSI_GS, number"
	HSI GlideSlope Flag 		"L:BKSQ_KINGAIR_HSI_GS_FLAG, bool"
	HSI CDI TO Flag				"L:BKSQ_KINGAIR_HSI_CDI_TO_FLAG, bool"
	HSI CDI FROM Flag			"L:BKSQ_KINGAIR_HSI_CDI_FROM_FLAG, bool"
	HSI Bearing Needle			"L:BKSQ_KINGAIR_HSI_BEARING, number"
	Battery Master 				"L:var_batteryMasterSwitch, bool"

 -->

indeed no mention about anti ice or ext power, but I guess if you scroll the file you may be able to find, don’t know if it will help, I hope so

EDIT :
line 3090 of the AnalogKingAir.xml there’s external power part
line 4208 start the anti ice part

I am reasonably sure (but not 100%) that the intended launch day is Thursday :slightly_smiling_face:

I didn’t watch his whole stream and apparently later on he clarified that it is indeed scheduled for Thursday. Thanks!

From the release notes:

  • Yaw Damper indicator on main panel autopilot mode annunciator will now illuminate.

Does it do that for you? For me, it remains dark even though yaw damper is on.

in the AnalogKingair.xml ( wich file can be found in …\ …\bksq-aircraft-analogkingair\SimObjects\Airplanes\bksq-aircraft-analogkingair\model )

dev made a typo error : line 9092

<NODE_ID>AutopilotPanelAutopilotPanelYawDamper_EM</NODE_ID>

must be replaced by :

<NODE_ID>AutopilotPanelYawDamper_EM</NODE_ID>

then it should work

Can you report that to Just Flight?

don’t worry I will report at JF & BS :wink:

I’ve almost got 100 hours in the Black Square version of the King and I see this Beta range thing pop up often.
What exactly do you guys mean with the Beta range is not right? Should it stop the aircraft quicker or less quick when reversing the props? The reason why I ask is my model stops on a dime. It almost feels like the reverse is too strong. Is this the issue you guys have?

Then lack of prop drag. When I land I put the props full forward when I have the gear down and the flaps down. It feels really draggy to me. I’ve done a couple of space shuttle landings in mine landing at 110 knots indicated. So I am confused every time this gets brought up. Just a noob here don’t be too harsh. :rofl:

There is more to beta range than just full reverse. There’s an entire range of movement there where the props go from flat to reverse pitch which allows fine control. When taxiing the props can go pretty much entirely flat or slightly reversed at idle thrust in order to control taxi speed without ever touching brakes or going into actual reverse thrust. That range isn’t really modeled well in MSFS. If you use a toggle to switch the axis to reverse, you can sort of do it.

Ahh i see. Thanks.

well beside Fabio, they announced it on their forum aswell

Thanks for the confirmation :slightly_smiling_face:

Quite happy with this since it will give me a couple more days with the King Air :+1:t2:

I am a very happy user of the BS King Air adaption, however, I came across something I’d call a bug: flight plans are not loaded anymore into the GNS 530 with the 1.3 update. I read the instructions considering various avionics included in the King Air and my WT plugins are all up to date. But still, planned routes do not appear in the GNS system anymore and it’s really tedious to setup a complete IFR flight plan with these virtual knobs and switches. Anyone can confirm?

EDIT: weird… I had to uninstall the WT GNS plugin and reinstall it. Now it seems to work.

Yes, I can confirm :slightly_smiling_face:. I was just about to post much the same.

The flight plans are loaded correctly to the 530 when ‘Runway’ option is selected but not when the cold and dark state is selected (just before the ‘FLY’ screen). The Garmin starts up when I eventually flick the Avionics switch in the cockpit but not with a flight plan.

I also uninstalled the WT 530 mod in the Content Screen a couple of times too but it still didn’t work for me. I have no other Garmin mods installed in the community folder.

For point of reference I tried it in the Chancellor 414 from cold and dark and the flight plan loaded with the Garmin 530 okay do not sure if it’s something I’m doing wrong in the King Air or not. It seemed to work okay before the update from memory.

So I have a few questions regarding the new update.

  • do friction locks have any usage in King Air? They are movable and I don’t remember them moving before?
  • prop sound changes drastically on touchdown, it has since initial release. Is that realistic and intended?
  • did anyone test external failure commands? If so, which software is free and can send those command to KA?

Other than that KA now flies much better, it seems it has some weight and inertia to it, autopilot is also much more obedient. Excellent update!

That is because the MSFS flight model has two variables for minimum prop pitch (beta): in-flight and on-ground. If the on-ground value is significantly lower than in-flight, then the props will immediately go flatter on touchdown and cause the surge in RPM. You will find this behavior in most MSFS turboprops. I think that might be what you mean about the sound.

In v1.3 of the Analog King Air, he significantly increased the minimum on-ground beta value, which should improve the specific thing you’re describing, BUT it causes the props to idle much too slowly now (500-600 RPM when it should be more like 1000 at low idle).

I find it amazing that after all this time (since the beta WT530 was first released back in December or November) that users still don’t know of the limitations surrounding the use of the various GPS’s. The issues are described everywhere in release notes and warnings from both the WT/AAU1 product notes and the PMS50 product notes (and maybe TDS as well, I don’t know and don’t own it, and they have their own limitations), as well as constant reminders by people constantly posting in all the various addon threads without bothering to read a few posts up.

Release notes and manuals are there for a reason folks. Sorry to rant, I really should just ignore all the posts, but it’s frustrating reading the same posts over and over “why doesn’t the flight plan load properly?” in so many products, and people thinking it’s a bug in the airplane.

Given what I’ve seen from posts from WT, we’re going to have these problems for at least a year as WT finishes up the nav database fixes they are doing (which are definitely needed and the lynch pin to opening up all sorts of flight planning improvements), and hopefully they get to fixing the G3X sooner than later, or we’re going to constantly be hearing people wondering about this, unless people start reading release notes and manuals and web pages and posts explaining what’s going on.

I’d say “search” is your friend, but, I don’t know that people could know what to search for. I also realize that all the various GPS products and their integration is quite confusing. It took me a day or so of research to figure out what was going on back when the beta WT530 was first released. I also realize that the Marketplace WT530 is automatically installed, and people don’t realize that and it in itself is an issue. But it would be useful if people scrolled up in threads 5 or 10 posts on any given thread before they post bugs and whatnot. I realize we’re all excited by new releases and things, but… sigh

Maybe not everybody reads the same posts as yourself and is as expert and knowledgable as yourself regarding the WT mod.

If you are referring to a post that I and another poster made regarding flights not loading from ‘cold and dark’ (I guess you are) then all I can say is that it worked perfectly before the update and also works perfectly in the same circumstances with other AC.

Sigh … Rant over :slightly_smiling_face:

Nope, it does not. And won’t until the WT updates are finished across the whole product. Those planes that use the G3X will remain “broken” in regards to this, and people are going to have to read the pages where they download GPS from (PMS50 pages mostly, if you don’t use PMS50 or TDS products, you won’t notice problems except in planes that use a combination of GNS530/430 and the G3X). PMS50 does a fair job of explaining the issue, at least on his PMS750 product. I haven’t read there for a while, I hope he’s made it less confusing.

But, really, reading release notes is important. Take the SWS RV-10 for example. Milviz is working on upgrades to fix this, and so on…

I am not using the PMS50, TDS or the G3X and, yes, totally contrary to what you have posted I am having issues.

And I reiterate that I had no problem before the update but that I have now.

Anyway, my point is made and I will now leave it there and move on.

<< UPDATE >> 12/03/23 (for anyone else having similar issues)

Having read/re read the BS KA manual a few times and having spent many hours trying different combinations (those recommended in the manual plus a whole lot more as well), installing/uninstalling WT gns 530, rebooting PC, clearing cache etc etc,installing/uninstalling the KA mod I have found that other simers (in the working title discord and another forum) have the same problem getting a flight plan in the gns 530 even though it works okay in the pms 750 and EVEN THOUGH it worked in the gns 530 before the update. This isn’t the end of the world to be sure but it is a bit frustrating.

I think the best procedure here will be to file a ticket with JF and to make them officially aware of a potential issue and to take it from there. In the meantime I can use the free pms 750 so no big deal really. It’s just that I prefer the gns 530 and that use of that was one reason for buying the KA mod.