HF beta 1.0.6

[FinnJacobsen]

TOD no appearing on route in display until you press VNAV? and you have to press near TOD because it is not then activated? In a Boeing there is TOD displayed in any mode on a route map.

+1

How to know when Your near TOD and should arm VNAV and no TOD is indicated.

Also the altitude setting is odd, since it does not change from FL to Feet in a logical way (I find it should change from Feet to FL when set above TA and back from FL to Feet at TL).

Also When I decrease the altitude with FL indicated, once I reach FL010 (1000 ft) it changes to 9999 feet and cannot be set lower.

This is with TA at 3000 and TL at FL030

[B747F]

TOD no appearing on route in display until you press VNAV? and you have to press near TOD because it is not then activated? In a Boeing there is TOD displayed in any mode on a route map.

+1

How to know when Your near TOD and should arm VNAV and no TOD is indicated.

Also the altitude setting is odd, since it does not change from FL to Feet in a logical way (I find it should change from Feet to FL when set above TA and back from FL to Feet at TL).

Altitude indicator changes FL to feet with your altimeter setting if STD it displays FL is that realistic I am not sure of it.

[FinnJacobsen]

TOD no appearing on route in display until you press VNAV? and you have to press near TOD because it is not then activated? In a Boeing there is TOD displayed in any mode on a route map.

+1

How to know when Your near TOD and should arm VNAV and no TOD is indicated.

Also the altitude setting is odd, since it does not change from FL to Feet in a logical way (I find it should change from Feet to FL when set above TA and back from FL to Feet at TL).

Altitude indicator changes FL to feet with your altimeter setting if STD it displays FL is that realistic I am not sure of it.

I would think that Baro/STD shouldn´t affect the readout, but rather actual TA and TL

The problem is with a TA/TL set to 3000/030, flying at f.ex FL190, my next VNAV waypoint is the final ILS altitude of 1500 ft.
Since I´m above FL030, my baro setting is set to STD. Now decreasing the set altitude should then decrease in FL steps of 010'th until I get below TL030, then further decreasing the set sltitude should decrease with indications in feet with steps of 100th.
But now doing so will see FL goes down to FL010 and decreasing below that, sets the indication of 9999 with no other way to decrease, other than changing baro setting from STD to Baro, but I´m still flying in am altitude region where FL is used.

[Ephedrin]

Giving some help before B747F lands .....

Yes the right way to assign all the engine levers are "Send to FS as normal axis" and then yse "Axis xxx set".

Then ensure that no calibrationa re applied to these axis' in unde the "Joystick Calibration" Tab by pressing the "Reset" button in the upper left corner of each axis calibration box inorder to remove the "SET -SET-SET" buttons.

After that - run MWAMS and set each axis with it´s Min, Max and detends. Ensure that You have chosen the right axis. When moving the hardware axis, YYou should see a bar going left/right, indicationg the levers possition - otherwise You have selected the wrong controller and/or axis.
To be sure I press "Save" and the "Save Default" for each axis I set.

Another way is to use FSUIPC to read the values from the Axis' for where I want the detends to be set., and then open the Axis.cfg file from MWAMS and manually typing them.

The Axis.cfg file can be found here: C:\Users\[user name]\AppData\Local\MVAMS\Configurations\KingAir350i\

My Axis.cfg looks like this (For a CH-Product THQ) -Note that I have set the "single" actions to the same values as the seperate actions i.e f.ex [THROTTLE] to the same values as found in [THROTTLE1] & [THROTTLE2]:

[THROTTLE]
reverse=-16383
beta=-14173
idle=-8321
max=16383
invert=1
[THROTTLE1]
reverse=-16383
beta=-14173
idle=-8321
max=16383
invert=1
[THROTTLE2]
reverse=-16383
beta=-14173
idle=-8321
max=16383
invert=1
[PROP]
feather=-16383
min=-13132
max=16383
invert=1
[PROP1]
feather=-16383
min=-13132
max=16383
invert=1
[PROP2]
feather=-16383
min=-13132
max=16383
invert=1
[CONDITION]
off=-16383
lowidle=-12352
highidle=16383
invert=1
[CONDITION1]
off=-16383
lowidle=-12352
highidle=16383
invert=1
[CONDITION2]
off=-16383
lowidle=-12352
highidle=16383
invert=1

Thanks a LOT! Yes, that's what I've figured out too now. I did it using the axis.cfg as MVAMS somehow doesn't save the correct axis values, while the levers are parallely next to each other the saved values differed by up to 2000. Using the cfg works perfectly!!

The only remaining issue: My Prop 1 lever in the aircraft always snaps back into feather. It moves with my hardware prop 1 lever as long as I move it but as soon as I stop the lever in the aircraft snaps back. This also happens when I click and drag it with the mouse. Prop 2 and all other levers are fine.

[B747F]

Giving some help before B747F lands .....

Yes the right way to assign all the engine levers are "Send to FS as normal axis" and then yse "Axis xxx set".

Then ensure that no calibrationa re applied to these axis' in unde the "Joystick Calibration" Tab by pressing the "Reset" button in the upper left corner of each axis calibration box inorder to remove the "SET -SET-SET" buttons.

After that - run MWAMS and set each axis with it´s Min, Max and detends. Ensure that You have chosen the right axis. When moving the hardware axis, YYou should see a bar going left/right, indicationg the levers possition - otherwise You have selected the wrong controller and/or axis.
To be sure I press "Save" and the "Save Default" for each axis I set.

Another way is to use FSUIPC to read the values from the Axis' for where I want the detends to be set., and then open the Axis.cfg file from MWAMS and manually typing them.

The Axis.cfg file can be found here: C:\Users\[user name]\AppData\Local\MVAMS\Configurations\KingAir350i\

My Axis.cfg looks like this (For a CH-Product THQ) -Note that I have set the "single" actions to the same values as the seperate actions i.e f.ex [THROTTLE] to the same values as found in [THROTTLE1] & [THROTTLE2]:

[THROTTLE]
reverse=-16383
beta=-14173
idle=-8321
max=16383
invert=1
[THROTTLE1]
reverse=-16383
beta=-14173
idle=-8321
max=16383
invert=1
[THROTTLE2]
reverse=-16383
beta=-14173
idle=-8321
max=16383
invert=1
[PROP]
feather=-16383
min=-13132
max=16383
invert=1
[PROP1]
feather=-16383
min=-13132
max=16383
invert=1
[PROP2]
feather=-16383
min=-13132
max=16383
invert=1
[CONDITION]
off=-16383
lowidle=-12352
highidle=16383
invert=1
[CONDITION1]
off=-16383
lowidle=-12352
highidle=16383
invert=1
[CONDITION2]
off=-16383
lowidle=-12352
highidle=16383
invert=1

Thanks a LOT! Yes, that's what I've figured out too now. I did it using the axis.cfg as MVAMS somehow doesn't save the correct axis values, while the levers are parallely next to each other the saved values differed by up to 2000. Using the cfg works perfectly!!

The only remaining issue: My Prop 1 lever in the aircraft always snaps back into feather. It moves with my hardware prop 1 lever as long as I move it but as soon as I stop the lever in the aircraft snaps back. This also happens when I click and drag it with the mouse. Prop 2 and all other levers are fine.

Prop1 could have 2 assignments it did it to me read the sections of fsuipc.ini

[FinnJacobsen]

B747F...

No - I had the exact same problem. I experimentet alot, even setting my hardware prop lever 1 in FSUIPC to control both prop levers. Still no. 1 prop lever in-game jumped back and forth. So something is porked in the MV code.

Ephedrin...

I had this too and I don´t really know how I fixed it.

I think I fixed it by changing all the values near 16383 to this number. F.ex the value was just set to 16382 in the axis.cfg, I then changed it manually to 16383, but I´m not whether that was why I got it fixed.

Sometimes my right Power lever acts up - starting to pulsate up and down a ½ inch with a 1 second interval. reloading the KA350i then helps.

I think Milviz nneds to look further into their code, cause it seems too finicky.

[Ephedrin]

B747F...

No - I had the exact same problem. I experimentet alot, even setting my hardware prop lever 1 in FSUIPC to control both prop levers. Still no. 1 prop lever in-game jumped back and forth. So something is porked in the MV code.

Ephedrin...

I had this too and I don´t really know how I fixed it.

I think I fixed it by changing all the values near 16383 to this number. F.ex the value was just set to 16382 in the axis.cfg, I then changed it manually to 16383, but I´m not whether that was why I got it fixed.

Sometimes my right Power lever acts up - starting to pulsate up and down a ½ inch with a 1 second interval. reloading the KA350i then helps.

I think Milviz nneds to look further into their code, cause it seems too finicky.

Thats it. The value was set to 16383 but 2^14 equals to 16384. The 4 fixed it.

[drobs2001]

This has been happening when descending through clouds, EPLB > EPWR



Pitot heat is on.

Had the same issue while climbing through clouds shortly after Takeoff in heavy snow fall out of ESGG.
All AI systems on.

[FinnJacobsen]

This has been happening when descending through clouds, EPLB > EPWR



Pitot heat is on.

Had the same issue while climbing through clouds shortly after Takeoff in heavy snow fall out of ESGG.
All AI systems on.

Seems that Pitot heat has failed then.
Maybe setting the Milviz pitot heat on doesn´t turn the "internal" P3D pitot heat on i.e "KEY_PITOT_HEAT_ON" / "KEY_PITOT_HEAT_OFF" -> (> K:PITOT_HEAT_ON) / (> K:PITOT_HEAT_OFF).

[Philippe Mendes]

Could someone please explain in detail WHAT to set in FSUIPC?? All I get is a jumping throttle lever, resetting detends in MVAMS and self-swapping assignments in FSUIPC between the levers of the KingAir.

I read I should use "direct" assignment and "axis throttle set". Assuming that "Direct" means "Send direct to FSUIPC Calibration" this is impossible. "Axis xxx set" is part of "Send to FS as normal axis".

Does "Don't cailbrate in FSUIPC" mean "don't use Send direct to FSUIPC calibration" or does it mean "do not use the Joystick Calibration page 3 of11"?

It would really be great if someone - preferably someone who actually got it working - could explain in detail and with CORRECT names of the functions what I have to do? I have no idea what I'm expected to do and I am certainly no "noob" when it comes to FSUIPC.

Right now this is really beyond study level. It's dissertation level.

Same here. Need a how to. Thanks

[Taguilo]

BARO SETTINGS:

Please check the image below:

Baro Settings.jpg (507.93 KiB) Viewed 2752 times

When FL mode altitude is not FAA standard (FL180) it must be defined in CDU - PERF - VNAV SETUP
Press B to select and insert the current baro pressure in all three altimeters.

Thanks.


Tomas

[Taguilo]

The problem is with a TA/TL set to 3000/030, flying at f.ex FL190, my next VNAV waypoint is the final ILS altitude of 1500 ft.
Since I´m above FL030, my baro setting is set to STD. Now decreasing the set altitude should then decrease in FL steps of 010'th until I get below TL030, then further decreasing the set sltitude should decrease with indications in feet with steps of 100th.
But now doing so will see FL goes down to FL010 and decreasing below that, sets the indication of 9999 with no other way to decrease, other than changing baro setting from STD to Baro, but I´m still flying in am altitude region where FL is used.

Hi,

For Preselected Altitude, you can manage hundreths by left/rigth clicking on ALT knob. See image :

Baro altitude.jpg (127.39 KiB) Viewed 2748 times

Tomas

[Regis9]

I tried calibrating my axes, using the workaround mentioned above to avoid crashes. In sim, when I move my throttle controllers, the controls only move from one end of the axis to the other with no gradual movement along the axis.

It turns out MVAMS was not creating an Axis.cfg file. I excluded the directory this file is in from my virus scanner and it works better now. I didn't realize this directory even existed or I would have done it sooner.

After a bit of fiddling and help from this thread I've got the throttle quadrant levers running now and they work like a dream! Taxiing is excellent now. Thanks guys.

[paul]

Pitot heat is on.

Hi,

What about Pitot Covers?

Tomas

They're off. I did have fairly severe icing (I needed the wing boots on!), but it wasn't especially extreme weather.

Once I was about 1000 RA it was fine.

[FinnJacobsen]

BARO SETTINGS:

Please check the image below:


When FL mode altitude is not FAA standard (FL180) it must be defined in CDU - PERF - VNAV SETUP
Press B to select and insert the current baro pressure in all three altimeters.

Thanks.


Tomas

I know.

Actually FL180 is mostly used in the US.
In Europe they range from 030 and up, depending on country and region, which again is depending on the highest ground in that region.

In Denmark we see 3000/030 and sometimes 5000/050, while in Germany they range from 5000/050 in northern Germany (where it´s mostly flat) to higher levels in the south due to higher mountainsf.ex the Alps.

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.

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.