HF beta 1.0.6

[Taguilo]

The issue with the Milviz KA350i is how the AP altitude setting changes from FL to feet - something does not work correct.
Fying at f.ex FL190 with a TL of FL050 and baro set to STD, should still make it possible for You to dial in 2000 ft for the AP altitude setting f.ex when preparing the descend to the altitude depicted on the approach chart for ILS GS capture.
The change from FL to feet should be when the AP altiude setting goes below the TA/TL set on the VNAV Climb and Descend page.

Presel altitude displays in FL format when STD baro is selected.
From POH:

• The digital preselect altitude readout
shows in cyan above the barometric
altitude scale. When the barometric
pressure setting is not standard, the
readout shows in up to 5 digits. When
is set to STD, the readout shows as a
3 digit flight level preceded by an FL
legend.

You can try out the described situation, and You will see that when dialing down the AP altiutde setting, the readout goes down to FL010 (1000 ft ) and then changes to read 99999ft and not possible to dial further down. The readout should indicate FL down to FL030 (as set for TL) and thendial down from 2999 to 0 ft.

Please see : https://milviz.com/forum/viewtopic.php?p=96160#p96135

Thanks!

Tomas

[FinnJacobsen]

The issue with the Milviz KA350i is how the AP altitude setting changes from FL to feet - something does not work correct.
Fying at f.ex FL190 with a TL of FL050 and baro set to STD, should still make it possible for You to dial in 2000 ft for the AP altitude setting f.ex when preparing the descend to the altitude depicted on the approach chart for ILS GS capture.
The change from FL to feet should be when the AP altiude setting goes below the TA/TL set on the VNAV Climb and Descend page.

Presel altitude displays in FL format when STD baro is selected.
From POH:

• The digital preselect altitude readout
shows in cyan above the barometric
altitude scale. When the barometric
pressure setting is not standard, the
readout shows in up to 5 digits. When
is set to STD, the readout shows as a
3 digit flight level preceded by an FL
legend.

You can try out the described situation, and You will see that when dialing down the AP altiutde setting, the readout goes down to FL010 (1000 ft ) and then changes to read 99999ft and not possible to dial further down. The readout should indicate FL down to FL030 (as set for TL) and thendial down from 2999 to 0 ft.

Please see : viewtopic.php?p=96160#p96135

Thanks!

Tomas

hmmm...
Makes not alot of sense for me.

How can You then select AP altitude of f.ex 1500 ft when flying at FL190 ?
Baro is at STD so readout can only be in FL with steps of 010. You do not want to set baro to QNH before descending to TL.

[Taguilo]

hmmm...
Makes not alot of sense for me.

It makes sense. FL always reminds you that you are flying with baro 29.92, especially if by any chance you descend below FL altitude and don't change baro to local.

How can You then select AP altitude of f.ex 1500 ft when flying at FL190 ?
Baro is at STD so readout can only be in FL with steps of 010. You do not want to set baro to QNH before descending to TL.

You can select FL in 001 steps ie FL012 - FL013, etc. Please check my previous message.

Tomas

[FinnJacobsen]

hmmm...
Makes not alot of sense for me.

It makes sense. FL always reminds you that you are flying with baro 29.92, especially if by any chance you descend below FL altitude and don't change baro to local.

How can You then select AP altitude of f.ex 1500 ft when flying at FL190 ?
Baro is at STD so readout can only be in FL with steps of 010. You do not want to set baro to QNH before descending to TL.

You can select FL in 001 steps ie FL012 - FL013, etc. Please check my previous message.

Tomas

Ah -Ok... I actually think I start to see how it´s meant to work.

[xender]

Guys i have a question:

Should we report bugs in this thread, or we must create new ones?

[matpietsch]

Guys i have a question:

Should we report bugs in this thread, or we must create new ones?

viewtopic.php?f=105&t=5263

[neweye2fly]

Has anyone had an issue assigning lights using HF2 beta 1.0.6 I am using a GF-T8 switch panel and the landing and strobe lights work just fine but that's it. I have used FSUPIC logging to see what commands are used for each lights and have set my switches accordingly but no luck switching the lights on or off.

[Sharpedge]

Can I install this over the top of the initial install or do I need to uninstall first. I'm leaning towards the uninstall of the 350 but the hotfix file is slightly smaller so I thought I would ask.
Thanks

[doodlebug]

I'm not sure the installer will let you.

[B747F]

Can I install this over the top of the initial install or do I need to uninstall first. I'm leaning towards the uninstall of the 350 but the hotfix file is slightly smaller so I thought I would ask.
Thanks

Uninstall unneeded. Delete the King Air simobjects folder and reinstall (you can also remove the p3d\milviz folder) I have not had any side effects to this

[Regis9]

I did not uninstall, but I noticed the installer deleting some files and things seem to be working fine so I’m not sure.

I do have to say, now that I have my throttle controls working I’ve been able to go for a few short VFR flights and it hand flies like a dream, lots of fun. Once the remaining bugs get smashed this is going to be a true top notch aircraft.

[thecoturnix]

I'm unable to make the throttles work in my TQ6. I have followed the above instructions to the letter but "Axis: Throttle 1 set" and "Axis: throttle 2 set" won't work, the levers don't move. If i assign one lever to "Axis: Throttle set" then both throttles move correctly showing that detents are ok (same values as Throttle 1 and 2 in the axis file). Of course i would like to use separate axes for each throttle but the moment i switch oner of them to Axis: throttle 1 or 2 it will stop working.

I have configured identically the throttle and separate throttle sections in the axis calibration window of FSUIPC, but it just won't work and i'm out of ideas. Any help appreciated.

[Slayer]

@chevelle,

Can you try to create a new saved flight from scratch and see if your GEN issue is fixed? I have tried to replicate your issue tens of times and I have had not one issue with the gens not coming online

Thanks for the help raptor, yeah, ive tried that as well, same issue. i just cant figure out what im doing wrong. First off, like i said the MVAMS current state option seems to be broken..as no matter what state i leave the airplane in she starts up with engines off (big problem when continuing a flight ) and avionics off, master on and all panel lights on max....so... I shut everything to off for a cold and dark panel. Master on, request ground power...when available i flip the ground power switch on the panel to on and ive got good power on gpu. I can turn on avionics etc and program fms. THEN, when we're ready to go (engines running), i flip ground power switch to off, disconnect gpu and give it a sec to shut down. Then i go to close the gens by going to on, then up to reset for a second and this is where its flashing power on for a sec..then it trips and i have no gen. I can repeatedly try to reset the gen only to have power for a second then nothing. Both engines, doesnt matter what i do. If i close the "gen tie man close" then i have power..but both gen lights are illuminated. The second i try to reset a gen it trips and no power. I have to restart the sim to get them back. Now, even if i restart the sim and open the same saved flight (usually sitting on the ramp from the last time i flew) if i dont mess with ground power..all works as normal.
NOW, i did finally get it to work..did the same as above and the left gen closed as normal..however..for some reason ive got another bug...with the new HF...ill start the right engine, all goes well, go to start the left engine and when i move the condition lever to idle nothing happens. Try using the ctrl shift f4 and still nothing.
Restart the sim and same old song and dance. Either no gens or i cant get number 1 to light off with the condition lever. Still very buggy as far as using the gens and condition levers.

On a side note, is there any progress or hope for fixing the ability to resume a flight with the condition you left everything in from the last flight.. obviously down the road..just wondering if this is on the list?

Also wanted to say, good job milviz..for what its worth, i know all this "bug reporting" may sound like complaints over this and that. Just wanted to reiterate, you guys have done an absolutely phenomenal job, hands down the best king air sim to date. Just looking forward to getting everything squared away over time.

This got me a few times.... Start switches are NOT spring loaded, if you leave a start switch engaged you will not successfully turn on gens. I reported this a couple of times in alpha....BUT this is how it works in the real thing , you must switch the stater back off after engine starts BEFORE turning on generators. Easy to miss, I know. Sorry if it was answered already. Also be careful with mapping of this switch on controls

[Lat3gr]

Hi team, great job so far with HF2. Couple of bugs noted:

1. The Bearing Pointer for the FMS is broken. Currently, it defaults to the DTK track as is shown by the course bar. Instead the bearing pointer should always point to the current "direct to" track(think like an ADF Needle, which is working correctly)

2. When intercepting an FMS track on the autopilot, you would usually select a HDG on the autopilot to intercept, then press NAV to arm it only. The autopilot will stay on HDG mode until getting closer to the track, and then swap to FMS mode to perform the intercept turn. Currently in HF2, the FMS will take over no matter what the HDG is and default to a 45 degree intercept. It is currently impossible to do a HDG intercept while having FMS armed.

Attached screenshot showing both bugs.

[metzgergva]

I see this too. Currently you need, as work around, arm late when you are close to make that turn.