Great 🙂

Can wait for the update...

Gérard

On 7/29/2024 at 3:26 PM, Rogen said:

Use MVAMS to select the 750 and unselect the weather radar and be sure the sim is not running when changing MVAMS options.

Aviod messing about with the pre-configured named panel configs as MVAMS expects everything to be on the up and up to function properly.

Given there are 10 aircraft type folders, 14 panel configs and 38 model files, it's one of the more complex installs for what it is and MVAMS is the tool to use to manage the configuration.

With so many panel configs and aircraft types it's easy to get out of place.

Cheers

Got the 750 up and running and all is well. However, when using the Shift + X keys for the AP and GTN750 popups, they're both squished (top to bottom). I can manually resize these but have to do it every flight. Is there something in the panel.cfg that I can change to make this permanent?

Thanks, Mark

Edited August 2, 20241 yr by newtie
sp

On 8/3/2024 at 3:36 AM, newtie said:

Got the 750 up and running and all is well. However, when using the Shift + X keys for the AP and GTN750 popups, they're both squished (top to bottom). I can manually resize these but have to do it every flight. Is there something in the panel.cfg that I can change to make this permanent?

Thanks, Mark

Panel config sizes for popups can be adjusted, they were originally coded to a custom size and window position where I've commented out.

All the operational panel.cfg files are held in \SimObjects\Airplanes\DHC-2 Beaver Milviz\

Where common windows are assigned in each of the panel.cfg files.

• Autopilot is [Window04]
• The GTN 750 will be [Window02] in the GTN 750 panel.cfgs

The details for panel.cfg files are located at, http://www.prepar3d.com/SDKv5/sdk/panels_and_user_interface/panels/panel_configuration_files.html

Try adjusting the size in the gauge[number]=  for the gauge you want to change the size of and see what you end up with.

Once you've got it suiting your desired look you can migrate the values over to the other panel.cfgs, noting all configs have the autopilot, and only the panel folders that include the 750 in the folder name will include the actual GTN 750, you'll also see one folder named as panel.GNS750_WX, this is intentional as it appears MVAMS is coded for that particular name to set the GTN750 and WX.

So just to confirm it's not a problem I have to cater for in the coming update...

• What's your screen mode ?
• Widscreen enabled in the P3D config ?
• Is the layout below what you see as default ?

My screen modes are typically DSR modes of 2560x1440 or 3840x2160 if the going is good (Lossless Scaling is allowing me to ramp up in many areas).

Cheers

Hi Rogen-

I found the SDK yesterday although it was pure experimentation that helped. I have the GTN located and sized correctly for my needs in the RH upper corner. I will tackle the AP tomorrow as I copied portions of the panel.cfg into a text document and made notes. One thing I’ve found is there is no right click, close window function. Shift+4 works fine tho’. Thanks for checking in. I haven’t installed 1.1 as I know your update will hit soon.

23 minutes ago, newtie said:

One thing I’ve found is there is no right click, close window function. Shift+4 works fine tho’.

Ok np, just keep your settings aside as the v1.2 update will set defaults.

I don't see your right click issue, both the AP and GTN750 have the standard default right click close window option here.

Also the Autopilot is assigned to Shift + 5 and the single GTN750 is Shift + 3, if you've changed the mapping to Shift + 4 be aware the update will set std. defaults.

For the GTN the right click popup operation is enabled on the main screen, that is right click on the GTN's main screen of either the popup or VC unit to open or close it as a popup. It's an RXP function enabled in the RXP GTN ini configuration.

Cheers

Interesting. Question..Is the GTN supposed to be added after I add your modifications? Didn’t change the mapping, that I’m aware of.

Edited August 4, 20241 yr by newtie
Add

Not quite sure by what you mean ?

Do you not already have the RXP GTN series ?

 

Sorry. I add the GTN 750 (which I own) using the main menu drop down RXP menu to replace the existing gage which is the Flight1 gage (which I don’t own). Is this the correct way?

Edited August 4, 20241 yr by newtie
..

Arh nope...

The panel configs are all preconfigured, all you need to do is use the MilViz MVAMS app to select the GTN 750 unit.

MVAMS labels the GTN as Flight 1 but the configs are preset set to RXP GTN units.

Essentually MVAMS updates all the aircraft.cfg files to point to the chosen GPS panel folder.

You'll see the aircraft.cfg will change its date in windows and there will also be an Aircraft_backup.cfg  with the same date created.

For the single GTN750 panel folder (panel.GTN750) you'll see these notes in the top of the panel.cfg.

// 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
// TBM 18/10/2023 Adjusted size and position of Autopilot popup window.
// TBM 27/10/2023 Set up the panel.cfg for the rxp 750 GTN GPS.
// TBM 29/10/2023 Tidied and tested up panel.cfg and set windows to a common Window0x config.

[Window Titles]
Window00=Main Panel
Window02=Reality XP GTN Unit 1 (managed)
Window04=Autopilot

Looks like I have some work to do tomorrow.. 😂

I'm all set Rogen, followed the direction here after full reinstall. I'll install your mods sans 1.1 and wait for 1.2

Thanks for all the help.

Thank you Rogan!

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.

Edited August 5, 20241 yr by Zylx

Hey Folks,

DHC2 Beaver update v1.2 is now available to download...

The previous v1.1 update is superceeded by the v1.2 update and can be applied overtop for anyone who has already applied the v1.1 update.

Remember...

• you must install the correct version of the Beaver from MilViz (see update v1.0 docs).
• you must update the Beaver to the v1.0 update by carefully following the docs (lots of inconsistancies to fix).
• with the above two items done the v1.2 update can be applied overtop.

NOTE: the v1.2 update will reset all the aircraft.cfg files to the default of the MilViz Passenger configuration with the Milviz 530/430 GPS units and no WX radar.

• Use MVAMS to reset your configuration making sure P3D is not running when re-configuring.
• Also MVAMS may need to be run with Admin rights depending on where P3D is installed and how Windows rights have been configured.

The following spoiler contains a snip from the readme included in the archive.

Cheers

Spoiler

===============================================================================
PREAMBLE:
===============================================================================
Description: MilViz DHC2 Beaver update package.
Contact:     PM @Rogen on https://www.avsim.com
Dated:       07/08/2024
Version :    1.2
Name:        MilViz_DHC2_Community_Update_v1.2.zip

 

===============================================================================
ARCHIVE SIZE:
===============================================================================
The package is approx. 450 MB zipped and ~1 GB unzipped.

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.
-------------------------------------------------------------------------------

 

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

MilViz_DHC2_Community_Update_v1.2\SimObjects

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

If you are not running P3D v5+ there is no specific need for this v1.2 update
although you can install it in P3d v4.5 to take advantage of the RXP, WX and
other changes.

The "SimObjects" folder within "MilViz_DHC2_Community_Update_v1.2" 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), Only when the above has been successfully completed should the
    "MilViz_DHC2_Community_Update_v1.2" be installed.

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

    MVAMS labels the GTNs as Flight1, however RXP units are the actual pre-configured
    GTNs.

    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.

5), Refer to the section in this file titled "P3D v4.5 MilViz WX" for details on
    swapping to the MilViz WX radar.
-------------------------------------------------------------------------------

 

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

NOTE: There is no need to install the previous v1.1 update as this update supersedes
      the version 1.1 update.

Major changes:
-------------------------------------------------------------------------------
The v1.2 update includes changes to cater for single click VC RXP GTN button
operation where the RXP GTN 750 and GTN 650 are the two targeted RXP GPS units.

It also corrects the VC GTN knob rotation direction to match that of the GTN when
popped out.

The Autopilot has 3 NAV functions replaced to improve AP reliability.

The default Livery aircraft number textures have been updated to show the correct
number on the cockpit plate.

The default WX weather Radar is defined as Roland's Radar and requires Active Sky.

The default panel is set to the MilViz 530/430 GPS with no WX.

The default aircraft configuration is defined as Passenger.

The MilViz MVAMS application should be used to configure the plane and GPS etc.

NOTE: Although MVAMS labels the GTNs as Flight1, they are actually pre-configured
      RXP GTN units.
-------------------------------------------------------------------------------

 

P.S.  The Beaver Ballad song sent to me by a fellow enthusiast, it even includes the N1117F.

 

Edited August 7, 20241 yr by Rogen
Beaver Ballad

Hi Rogen,

I just downloaded your 1.2 update - thanks. 🙂

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.

Any suggestions are welcome.

Thanks - Gérard