7 hours ago, gaab said:

But I just realized that it is targeted to GTN 750 while I am using the RXP GNS530 V2.

I already updated the Milviz options to use the rxpGNS2!GNS_530_1 instead of rxpGNS (rxpDrop!Stack does not exist anymore...)

Should I use your updated Autopilot with this configuration ? I am currently using the C310_XMLGauges version.

Up to yourself as to if you want to use the new autopilot, adding it is very much a cut and paste type of operation to the panel.cfg files which are just text files. Once the entries are in place you can just comment or uncomment either AP, which is easy enough given there are only the two panel.cfg files to edit. Also NotePad++ is excellent for editing text.

I only have the two GTNs myself, so yeah feel free to update the 2 x panel.cfg in panel.rxp530_430 & panel.rxp530_430_WX with the rxp v2 options (whatever they maybe).

Those two panel configs already have the autopilot changes included so you could either migrate over the new autopilot entries to your 2 panel configs or vice versa for your GPS values.

Also I just noticed the panel.cfg in panel.rxp530_430 has a MilViz WX reference it shouldn't have, just comment it out like below.

[Vcockpit13]

//gauge00=MV_WX!WX,  0,0,512,380

Feel free to drop your newly modified and tested panel configs in separate spoilers and I'll use them to update the two existing panel.cfg

Cheers

 

Hi Rogen,

As usual the update for the RXP GNS530 V2 was much longer than anticipated ...
The mods have been tested in V5 and V6
The WX with Roland works in V5 - in V6 I get the "No Radar Link!" blue message.
I think it is an installation issue if ASP V6... I have to investigate...

You will see that I have proposed a move of two lines to insure consistent values of the Elevator Trim
(the model uses L:DHC2_ElevTrimPCTValue while the sim logic of the AP modifies directly A:ELEVATOR TRIM PCT)

Spoiler

// This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com
// Built Thursday, June 19, 2014 at 16:37 FSPS Build:22767

// Addendum to DHC2_Community_Update_v1.2 by @Rogen on https://www.avsim.com
// panel.rxp530_430_WX
//
// panel.rxp530_430  for the NO wx version
// just comment [Vcockpit13]  gauge00 = ..\panel\RolASNRadar!ORadGauge

// Updated for rxp GNS530 V2 - NO GNS430 (I don't have it) => default Milviz disabled
// Using KAP140_DHC2 by @Rogen on https://www.avsim.com
//

// tested in P3D V5 and V6

[Window Titles]
Window00=Main Panel
Window01=Autopilot
Window02=Reality XP GNS 530 WAAS

[VIEWS]
VIEW_FORWARD_DIR=10.000, 0.000, 0.000

//--------------------------------------------------------
[Window00]
Background_color=0,0,0
size_mm=1024
position=1
visible=0
ident=MAIN_PANEL

//--------------------------------------------------------
[Window01]
BACKGROUND_COLOR=1,1,1
size_mm=255,85
//window_size_ratio=1.000  
position=8
visible=0
ident=Autopilot

//window_size= 0.500, 0.128
//window_pos= 0.500, 0.180

//gauge00=..\panel\C310_XMLGauges!MV_KAP140_PopupDisplay,  0,0,255,85
gauge00=..\panel\KAP140_DHC2!MV_KAP140_PopupDisplay,  0,0,255,85

//--------------------------------------------------------

[Window02]
size_mm=100,100
window_pos=0.000000,0.000000
window_size=0.191406,0.247917
visible=0
always_visible=1
zorder=99
background_color=0,0,0
ident=15531
gauge00=rxpGNS2!GNS_530_1, 0, 0,100,100

//--------------------------------------------------------

[Vcockpit01]
Background_color=0,0,0
size_mm=256,256
visible=0
pixel_size=1024,1024
//texture=$C310_VC_02
texture=$vpanel

gauge00=..\panel\DH2!passenger,  0,0,1,1
gauge01=..\panel\BeaverSystems!BeaverTables,  0,0,1,1
gauge02=..\panel\DH2!DHC2_SysEvents,1,1,1,1
gauge03=..\panel\DH2!DHC2_Systems,1,1,1,1
gauge04=..\panel\amsinterop!amsinterop,1,1,1,1
gauge05=..\panel\DH2!console_rxp530_430,1,1,1,1
gauge06=..\panel\MV3DSound!MV3DS,  0,0,1,1,SimObjects\\Airplanes\\DHC-2 Beaver Milviz\\DHC-2_XML_Sounds#55

//--------------------------------------------------------
[Vcockpit02]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$VC_01
gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller,  0,0,1024,1024,0

[Vcockpit03]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$VC_02
gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller,  0,0,1024,1024,1

[Vcockpit04]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$VC_03
gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller,  0,0,1024,1024,2

[Vcockpit05]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$VC_04
gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller,  0,0,1024,1024,3

[Vcockpit06]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$VC_05
gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller,  0,0,1024,1024,4

[Vcockpit07]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$VC_06
gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller,  0,0,1024,1024,5

[Vcockpit08]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$VC_07
gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller,  0,0,1024,1024,6

[Vcockpit09]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$VC_08
gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller,  0,0,1024,1024,7

[Vcockpit10]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$VC_09
gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller,  0,0,1024,1024,8

[Vcockpit11]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$VC_10
gauge00=..\panel\Milviz_Lighting_Gauge!lightcontroller,  0,0,1024,1024,9

[Vcockpit12]
file=C310_VC_05.bmp
size_mm=512,512
visible=0
pixel_size=512,512
texture=$VCNL_03

[Vcockpit13]            
file=C310_VC_05.bmp
size_mm=512,512
visible=0
pixel_size=512,512
texture=$C310_VC_05

//gauge00=MV_WX!WX,  0,0,512,380
// Embed the Roland Weather Radar fully into the bezel. Also note the Roland Weather Radar requires Active Sky Next (ASN).
// As the Roland Weather Radar is embedded there are click spots within the display mouse scroll wheel functionality to control On/Off. Tilt, Range and Gain.
// The spots are left of the centerline, below are the options for the gauge and note only a single instance of the gauge per aircraft will function.
// sweep    Simulates the radar beam sweep.
// ghost    Disable text drawing.
// beam        Display the radar beam.
// icing    Enable Icing alert display (red star, 1 to 4 along icing severity).
// nogps    Disable the use of Gps buttons to set radar parameters.
// starton    Force the gauge to ON after startup.

gauge00 = ..\panel\RolASNRadar!ORadGauge,  0,0,512,361, sweep|beam|icing|nogps|starton

//--------------------------------------------------------
[Vcockpit14]
//file=C310_VC_02.bmp
Background_color=0,0,0
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$C310_VC_02
//gauge00=rxpGNS!GNS530, 0,0,512,373
gauge00=rxpGNS2!GNS_530_1,  0,0,609,447
gauge01=..\panel\C310_XMLGauges!FBS_GTX330,  0,376,512,136
//--------------------------------------------------------
[Vcockpit15]
file=C310_VC_01.bmp
Background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$C310_VC_01
//gauge00=..\panel\C310_XMLGauges!FBS_GNS430_1, 0,367,640,262
//gauge01=..\panel\C310_XMLGauges!MV_KAP140Display,  0,767,640,163
//gauge02=..\panel\C310_XMLGauges!MV_KAP140Servos,  0,0,1,1
gauge01=..\panel\KAP140_DHC2!MV_KAP140Display,  0,767,640,163
gauge02=..\panel\KAP140_DHC2!MV_KAP140Servos,  0,0,1,1
gauge03=..\panel\C310_XMLGauges!KR 87 ADF,  0,630,640,134

 

Day=255,255,255
Night=255,255,255
Luminous=240,86,92

[Default View]
X=0
Y=0
SIZE_X=8191
SIZE_Y=6143

Spoiler

//////////  RealityXP.GNS.ini  for V2  ////

[GNS_530_1]
; is the master device if true.
MasterDevice = true
; connects to: 'PFC_STACK','PFC_430','PFC_530' or any '#PID' (#D002 for PFC_430)
; no value connects to first found, 'OFF' disables connection.
HardwareDevice =
; hardware selector number or -1 to disable.
HardwareIdx = -1
LinkHsi = false
LinkCrs = true
LinkObs = true
LinkVor = true
UseSimGpsCmds = true
UseAirData = false
UseFuelData = false

Spoiler

////////// Mod in MV_KAP140Servos.xml  ////////
////////// Synchronise actual  A:ELEVATOR TRIM PCT with L:DHC2_ElevTrimPCTValue in order to solve
////////// the "brutal" Trim reset to zero at AP_Master Off
////////// After line 38 of MV_KAP140Servos.xml
//////////
    <Element Name="PITCH Calc">
        <Select>
            <Value>
                (A:ELEVATOR TRIM PCT,percent) d (>L:DHC2_ElevTrimPCTValue, percent) 2 / 50 + (>L:DHC2_ElevatorTrimPCT, percent)
                (L:KAP140_AP_Master,bool) !
                if{
                     (A:YOKE Y POSITION, percent) sp0
                     (L:DHC2_YokeYPosition, percent) (>L:KAP140_DampVar,number)
                     @Damped(l0,0.500,KAP140_DampVar) (>L:DHC2_YokeYPosition, percent)
<!--                     
                     (A:ELEVATOR TRIM PCT,percent) d (>L:DHC2_ElevTrimPCTValue, percent)
                     2 / 50 + (>L:DHC2_ElevatorTrimPCT, percent)
-->                     
                     quit
               

Thanks for the initial mod 1.2. I learned a lot while "fighting" with RXP GNS (LVL mode was new for me), Autopilot and Milviz MVASM 😉

Cheers

Gérard

A small quick fix to "switch off" the fake GNS430

[Vcockpit15]
//file=C310_VC_01.bmp
Background_color=1,1,1

On 8/12/2024 at 4:53 AM, gaab said:

Hi Rogen,

As usual the update for the RXP GNS530 V2 was much longer than anticipated ...

Hey gaab,

Ta for those items, I've cleaned up the remainder of the AP gauges code and have reviewed the variables in operation and all looks good, I'll be definitely including in the next update (a hot fix really).

I've a few other items on my plate atm before I can get back to it.

Cheers

Pic showing variables.

Hey Folks,

There has been a couple of questions regarding Gross Weights of the Beaver float plane.

There is a Beaver manual included within "\SimObjects\Airplanes\DHC-2 Beaver Milviz\Manual\" which I've image enhanced with rotation, deskew and OCR where a search for "weight" will bring up all references.

But to cut it short, gross for std. float planes is 5090, however this changes for STOL versions where the gross is 5370.

Note the empty weight will also vary as floats and STOL kits do add additional weight.

If you want to review take a look at each plane's [WEIGHT_AND_BALANCE] config in the aircraft.cfg file where you'll find notes regarding.

I'd performed research when putting it all together and it's based on various documents I'd located on the internet.

Actual MTOW for the Beaver can vary between 4820 up to 5600 depending on kits, equipment, engine and type of loadout, e.g. 5600 is achieved with a Turbine engine conversion with various other specific equipment and loadout.

But for the sim version you're looking at 5090 for float, 5100 for wheeled and 5370 for STOL with varing empty weights depending on the equipment.

Cheers

On 8/13/2024 at 7:30 AM, Rogen said:

I'll be definitely including in the next update (a hot fix really).

Line 477 of MV_KAP140Servos.xml

(A:AUTOPILOT VERTICAL HOLD VAR,feet/minute) 100 + 1500 min max (>K:AP_VS_VAR_SET_ENGLISH)
max should be deleted

I am not sure if this has impact on the sim, 
but I can say that this created an exception while checking it in Infix2Postfix

My two cents 😉

Gérard

(A:AUTOPILOT VERTICAL HOLD VAR,feet/minute) 100 + 1500 min max (>K:AP_VS_VAR_SET_ENGLISH)

 

10 hours ago, gaab said:

Line 477 of MV_KAP140Servos.xml

(A:AUTOPILOT VERTICAL HOLD VAR,feet/minute) 100 + 1500 min max (>K:AP_VS_VAR_SET_ENGLISH)
max should be deleted

I am not sure if this has impact on the sim, 
but I can say that this created an exception while checking it in Infix2Postfix

My two cents 😉

Gérard

Aha, good find and I can see the syntax error relating to the use of min max together where either of those operands require 2 individual values in order to choose a min or a max value.

That said looking at the code section as a whole, we find it under the LUA "UP KEY" element where given there is a up key, there will also be an opposite down key.

 

Here we have 2 x code sections where line 1 below (being the "DOWN KEY" code) doesn't cause a Infix2Postfix exception, and line 2 (being the "UP KEY" code) does cause an Infix2Postfix exception.

1. (A:AUTOPILOT VERTICAL HOLD VAR,feet/minute) 100 - -2000 max (>K:AP_VS_VAR_SET_ENGLISH)
2. (A:AUTOPILOT VERTICAL HOLD VAR,feet/minute) 100 + 1500 min max (>K:AP_VS_VAR_SET_ENGLISH)

If we look at the result of Infix2Postfix on the DOWN KEY (line 1) we can see the code is setting the max value of  AP_VS_VAR_SET_ENGLISH (reference vertical speed in feet per minute), which appears to be a valid logical function when using negative values.

(K:AP_VS_VAR_SET_ENGLISH) = max( ( (A:AUTOPILOT VERTICAL HOLD VAR , feet/minute) - 100 ),-2000 ) ;  

 

So if we apply the same logic to the exception causing  UP KEY (line 2) we have the same logical function as the DOWN KEY using positive values for up and without rasing an exception.

(K:AP_VS_VAR_SET_ENGLISH) = max( ( (A:AUTOPILOT VERTICAL HOLD VAR , feet/minute) + 100 ),1500 ) ;  
 

But we also have to ask ourselves "is this what the author intended", well, we can also trial removing the + operand which provides the 2 values required for min/max, does not result in an Infix2Postfix exception and gives us the below code line.

 (K:AP_VS_VAR_SET_ENGLISH) = max( (A:AUTOPILOT VERTICAL HOLD VAR , feet/minute),min( 100,1500 ) ) ; 

However, to myself the above line is not what the author intended as min(100,1500) will always be 100, and as a whole, the logic appears flawed.

 

There is a further option being the use of min instead of max where given the use of positive values, I feel min is the operand to go for as the author might have typed min but accidently left the max operand in place, i.e. from a cut and paste.

Anyway...with the above review out of the way I'm going to set the line as per below which satifies both infix to postfix and vice versa, while also providing the opposite of the DOWN KEY function setting 1500 as the maximum the up button allows.

(A:AUTOPILOT VERTICAL HOLD VAR , feet/minute) 100 + 1500 min (>K:AP_VS_VAR_SET_ENGLISH)

 

Cheers

Hi Rogen,

You probably know better then I, that in every model/gauge you will find this type of construct to insure that a variable stay inside a range of value.

       <Click Kind="LeftSingle+RightSingle+WheelUp+WheelDown+DownRepeat">
         (M:Event) 'LeftSingle' scmp 0 ==
         if{ (L:SwitchFLTLts, enum) -- 0 max (>L:SwitchFLTLts, enum) }
         (M:Event) 'RightSingle' scmp 0 ==
         if{ (L:SwitchFLTLts, enum) ++  20 min (>L:SwitchFLTLts, enum) }
         (M:Event) 'WheelDown' scmp 0 ==
         if{ (L:SwitchFLTLts, enum) -- 0 max (>L:SwitchFLTLts, enum) }
         (M:Event) 'WheelUp' scmp 0 ==
         if{ (L:SwitchFLTLts, enum) ++  20 min (>L:SwitchFLTLts, enum) }
       </Click>

So, no doubt that it was a typo 😉

Can I send you a MP concerning the Milviz DHC3 Otter.
I have some issue and would like to ask your opinion.

Thanks

Gérard

 

Edit

I found my issue with the Otter - stupid enought : was the rudder badly configured which was event flooding the connection between the GNS530 and the AP.

Thanks to "dsd_p3d_event_logger_x64" which allowed me to fing it.

BTW, if you are interested I fixed a typo in the external model (by patching) which created several event errors...

Gérard

On 8/21/2024 at 7:31 PM, gaab said:

Hi Rogen,

You probably know better then I, that in every model/gauge you will find this type of construct to insure that a variable stay inside a range of value.

       <Click Kind="LeftSingle+RightSingle+WheelUp+WheelDown+DownRepeat">
         (M:Event) 'LeftSingle' scmp 0 ==
         if{ (L:SwitchFLTLts, enum) -- 0 max (>L:SwitchFLTLts, enum) }
         (M:Event) 'RightSingle' scmp 0 ==
         if{ (L:SwitchFLTLts, enum) ++  20 min (>L:SwitchFLTLts, enum) }
         (M:Event) 'WheelDown' scmp 0 ==
         if{ (L:SwitchFLTLts, enum) -- 0 max (>L:SwitchFLTLts, enum) }
         (M:Event) 'WheelUp' scmp 0 ==
         if{ (L:SwitchFLTLts, enum) ++  20 min (>L:SwitchFLTLts, enum) }
       </Click>

So, no doubt that it was a typo 😉

Can I send you a MP concerning the Milviz DHC3 Otter.
I have some issue and would like to ask your opinion.

Thanks

Gérard

Yes indeed, such is the case, however I prefer to both review and ponder as well, given I've found lots of invalid code in models as well as gauges.

In anycase... problem solved 😄

Cheers

On 8/22/2024 at 2:12 AM, gaab said:

Edit

I found my issue with the Otter - stupid enought : was the rudder badly configured which was event flooding the connection between the GNS530 and the AP.

Thanks to "dsd_p3d_event_logger_x64" which allowed me to fing it.

BTW, if you are interested I fixed a typo in the external model (by patching) which created several event errors...

Gérard

Always interested, perhaps start another separate thread for the Otter.

I have had a few people asking if I was going to do a similar thing (as per the DHC2).

That way all can be combined.

Cheers

Community Update version 1.3 now available !

This 1.3 update focuses on AutoPilot improvements and also includes RXP GNS530 V2 panel configuration additions, thanks to @gaab for his contributions.

The spoiler below contains the details for those interested.

And happy to followup on anyone's questions via this forum thread.

Cheers

Spoiler

===============================================================================
PREAMBLE:
===============================================================================
Description: MilViz DHC2 Beaver update package.
Contact:     PM @Rogen on https://www.avsim.com
Dated:       30/08/2024
Version:     1.3
Name:        MilViz_DHC2_Community_Update_v1.3.zip
-------------------------------------------------------------------------------

===============================================================================
ARCHIVE SIZE:
===============================================================================
The package is approx. 20 KB zipped.

Disclaimer:
-------------------------------------------------------------------------------
This package assumes a person has knowledge of Prepar3D, Windows File and Folder
structuring and knows how to delete and copy files and folders.

I've tested the processes described and all has been fine on my own P3D installs.
Meaning as long as the instructions are followed a user should also have no issue.
NOTE: Am happy to help via the AVSIM forums should assistance be needed.
-------------------------------------------------------------------------------

 

===============================================================================
VERSIONING:
===============================================================================
Version = 1.3
This is an update release for the MilViz_DHC-2_Consistency_and_Flight_Model_Update
v1.2 and contains just the updated items only. It is intended for P3D v5+.

NOTE: the version 1.2 update should be installed prior to this 1.3 update.
-------------------------------------------------------------------------------

 

===============================================================================
RELEASE NOTES:
===============================================================================
MilViz_DHC2_Community_Update_v1.3.zip (P3D_v5+)
-------------------------------------------------------------------------------
Contains the following folder.

MilViz_DHC2_Community_Update_v1.3\SimObjects

NOTE:
-------------------------------------------------------------------------------
The package folders themselves contain just the updated items only.

This update contains changes to the AutoPilot gauge units and panel.cfg changes
to suit the RXP GNS530 v2.

The "SimObjects" folder within "MilViz_DHC2_Community_Update_v1.3" is
intended to be copied to the main P3D root folder to update an already installed
AND UPDATED instance of the MilViz DHC-2 Beaver.

For example:
-------------------------------------------------------------------------------
1), You must first install the appropriate MilViz DHC2 Beaver as defined in
    update v1.0 below.

2), You must then install the "MilViz_DHC-2_Consistency_and_Flight_Model_Update"
    (v1.0) as per its docs.

3), When the above v1.0 update has been successfully completed the
    "MilViz_DHC2_Community_Update_v1.2" can be installed.

4), When the above v1.2 update has been successfully completed the
    "MilViz_DHC2_Community_Update_v1.3" can be installed.

5), Use MilViz MVAMS to configure your desired loadout and GPS/WX combos as the
    default is configured as Passengers and the 2 x MilViz GPS units with no WX.

    MVAMS labels the GTNs as Flight1, however RXP units are the pre-configured
    GTNs that MVAMS will install.

    P3D should not be running when MVAMS is used.

    It maybe required to run MVAMS with Admin privileges depending on your P3D
    install location and Windows rights assigned.
-------------------------------------------------------------------------------

 

===============================================================================
FEATURES:
===============================================================================
Changes include the following:

Thanks to fellow enthusiast gaab @ avsim for items 1 to 3.
-------------------------------------------------------------------------------
1), Autopilot server changes where the AP will now manage the elevator trim as
    well as the elevator.

    The change stops a sudden reset when the AP is turned off preventing the
    flight control issues such a reset incurs.

2), Correction of a syntax error in the AP VS up button max value setting management.

3), Configuration of 2 x panel.cfgs for the RXP GNS530 v2 noting the GNS430 is
    disabled.

4), Add code to reset the KAP140_AltHoldFeet variable to zero when avionics power
    is off or the autopilot circuit breaker is pulled.

5), Additional code to set KAP140_AltHoldFeet variable to KAP140_AltitudeSelected
    (the "ALT SEL" knob value) when ALT is armed.

    The KAP140_AltHoldFeet variable holds the current altitude the autopilot will
    strive to capture and hold at, however the "ALT SEL" knob value and KAP140_AltHoldFeet
    were not linked in the original code, meaning setting the "ALT SEL" knob value
    and arming ALT made no change to the KAP140_AltHoldFeet altitude value.
    I've added additional code to MV_KAP140Display.xml to sync the KAP140_AltHoldFeet
    value to altitude selected (only) when ALT is armed.

    The following applies:
    When ALT is ARMed the "ALT SEL" value will reset KAP140_AltHoldFeet to the
    chosen altitude, noting a vertical speed should still be set for the AP to
    climb or descend expediently to the chosen altitude.

    When just ALT is displayed (not armed), the AP UP/DN buttons can be used to
    increment or decrement the KAP140_AltHoldFeet value in 20 feet values, noting
    the changes to KAP140_AltHoldFeet are not displayed in the AP, however the
    aircraft will climb or descend automatically at a maximum of 300 feet per
    minute till the Altitude is achieved.

    I've noticed when flying the STOL variants the AP will at times struggle to
    maintain altitude hold where speed is high (as the aircraft wants to climb),
    slowing down will generally help in this regard.
-------------------------------------------------------------------------------

 

===============================================================================
UPDATE INSTALLATION:
===============================================================================
Drag the SimObjects folder into the P3D root folder.

Allow Windows to copy the files allowing existing files overwrite.

Configure MVAMS for your desired GPS and aircraft config.
-------------------------------------------------------------------------------

 

===============================================================================
THE MAIN ARCHIVE CONTAINS THE FOLLOWING ITEMS:
===============================================================================

\SimObjects\Airplanes\DHC-2 Beaver Milviz\

The "DHC-2 Beaver Milviz" is the main folder for panel configs and gauges.
panel\
panel.rxp530_430\
panel.rxp530_430_WX\
RealityXP.GNS.ini

The "panel" folder contains.
KAP140_DHC2\            3 x updated autopilot gauges.
-------------------------------------------------------------------------------

 

===============================================================================
END:
===============================================================================

 

Hi Rogen,

7 hours ago, Rogen said:

Always interested, perhaps start another separate thread for the Otter.

Cheers

I will start a DHC3 thread when I turn back home.

Gérard

On 8/5/2024 at 11:50 AM, Zylx said:

Thank you Rogen!

All the Milviz Beaver needs now is a quality sound package.  I find the engine sound are not very good imo.  Other than that, it's a fantastic airplane package.

 

6 hours ago, Zylx said:

All the Milviz Beaver needs now is a quality sound package.

I use the Sonic-Solution BEAVER DHC2 SOUND which,  for 6 euros only, offerts a much better sound...

Gérard