On 9/17/2024 at 9:52 AM, mslim said:

Rogen thanks for all your good work. It was quite an undertaking for you no doubt. I went back and did the cleanup and then did all the updates in sequence. I flew a wheeled and a straight float iteration and everything seemed good. The autopilot seems much improved.

I'm used to leaning piston engines for altitude. Before and after the updates, the mixture control didn't seem to have much effect either on the cylinder head temp or the running of the engine. I know this was likely the result of the MV designers.

Hi @mslim, yeah it did take a while to pull it all together, a lot of review and documenting the structures to understand how it was intended to function.

Being 10 different aircraft with some 38 models meant attention to detail and a methodical process was needed and the result is an aircraft I really enjoy flying.

I especially like the new flight model and that MVAMS now works reliably, plus it has functioning circut breakers, something which is pretty rare.

Yeah mixture adjustment isn't as wide as the lever implies but it does function and need adjusting at altitude.

Cheers

woah, super late to the party.

just downloaded dch-2 and 3.

Sent PM for v1.0 update.

 

thanks Rogan

On 9/22/2024 at 1:15 PM, Brianwhtn43 said:

woah, super late to the party.

just downloaded dch-2 and 3.

Sent PM for v1.0 update.

 

thanks Rogan

Thanks Rogan,

Look forward to flying with updates

Brian

[url=https://ibb.co/jZttWL9][img]https://i.ibb.co/TqyybHD/IMG-20250124-161540861-HDR.jpg[/img][/url]

I guess I've done something wrong!

Why do I have research how to put an image in a forum post 🙂

Edited January 24, 20251 yr by davidk64

[img]https://live.staticflickr.com/65535/54285749948_ccc57f5a2b_c.jpg[/img]

Okay how about this. Well I think it's right.

I've surely done something wrong in installing the updates. But since the cleanup takes some time I thought I'd check first in case there is a simple fix before repeating the process from scratch.

Edited January 24, 20251 yr by davidk64

Hi @davidk64,

You just need to paste in a valid supported URL pathed image, no need to wrap it like for older type forum's (like LM's one).

Or you could create a link like this.

Image when pasted directly.

 

From the looks of it you're using a location outside of the main sim itself.

Is it an addon path ?

Or a symbolic linked path perhaps ?

The Milviz Beaver DHC2 has many dependencies on paths, its not at all designed or intended to be placed into an addons path although it may work if symbolic links are configured.

Just follow the package's included instructions and it will all work Ok.

What version of sim are you using by the way ?

Cheers

Edited January 24, 20251 yr by Rogen

Funny how you can't edit your post after a minute or two! I'm using P3D v5 and yes was trying to put in add-on location. I've been doing that with everything in conjunction with Lorby. Or is it that once someone else replies you can't edit a post?

I was trying to follow: 

 

Edited January 24, 20251 yr by davidk64

3 minutes ago, davidk64 said:

Funny how you can't edit your post after a minute or two! I'm using P3D v5 and yes was trying to put in add-on location. I've been doing that with everything in conjunction with Lorby.

I was trying to follow: 

Yeah I do find it problematic at times when edit ability drops off, but it's usually quite a bit longer than a minute, unless it's based on reputation, recent post count or something else along those lines, a mod should be able to answer with definitely.

Some aircraft designs just will not handle an add-ons path and the DHC2 is one of them, it's actually very complex with some 10 aircraft type folders, 14 panel configs and 38 model files plus MVAMS needs to be able to find it all for configuration.

Sometimes you've just got to accept this is going to be the case (as it is for the DHC2).

Be sure to *exactly* follow the instructions and don't leave any steps out and if you want to be running the weather radar you'll also need Active Sky and for the GTN you'll need the RXP units.

Cheers

On 1/24/2025 at 11:43 PM, Rogen said:

Some aircraft designs just will not handle an add-ons path and the DHC2 is one of them

 

Hello,

First of all, thank you @davidk64 who allowed me to discover by chance this Rogen topic published over a year ago and his awesome [Milviz DHC-2 Beaver Update].

From P3Dv4.5 to v5.4 I've installed most of my add-on Sceneries, Aircraft, Rotorcraft, Carrier and even RXP GTN 750, Active Sky, all orchestrated by the great Lorby A.O.

Of course, this requires rigorous installation and knowledge of Lorby A.O., but just like Roger's [Milviz DHC-2 Beaver Update] installation requires too.

Many of these add-ons were considered not to work outside the path simulator.
However, for example I was able to entrust the external installation of the Milviz BEll UH1 to LORBY A.O. without any major issues:

Above installation path 

MVAMS  works fine

And RXP GTN 750 panel-mounted

So I'd be very interested to try the [Milviz DHC-2 Beaver Update] complete installation by add-on.xml method (with RXP GTN 750). 
And for this reason I obviously sent a PM to Rogen for V1.0 update. 

Regards

 

1 hour ago, Recciosilva said:

So I'd be very interested to try the [Milviz DHC-2 Beaver Update] complete installation by add-on.xml method (with RXP GTN 750). 

I'll send you the link but personally I wouldn't bother with attempting add-on.xml pathing for this particular aircraft, noting I did give xml pathing a go myself prior to deciding to leave it as installing into the sim itself.

All the different aircraft types have walk-back dependencies to a main set of folders, files and configs, plus there are executables to consider as well, e.g. the MilViz lighting executable.

You might be able to install outside of the sim via NTFS symbolic links, but that's about it without significant reworking of components and config pathings, but that said you're welcome to trial it out of course.

Hey, do keep us updated though.

Cheers

1st question:
I guess I shouldn't check the Weather Radar Version/P3D version5 option
since it's the Roland Radar that's installed by the V1.1 update ?

Thanks

2 hours ago, Recciosilva said:

1st question:
I guess I shouldn't check the Weather Radar Version/P3D version5 option
since it's the Roland Radar that's installed by the V1.1 update ?

Yes or no... doesn't really matter unless your version of P3D is one where the MilViz WX radar actually works, in any case the updates will set the various config files to use Roland's Radar regardless, where if you've a supported version of P3D you could swap back to the MilViz WX by commenting/uncommenting the appropriate panel.cfg entries, that is assuming you've chosen to install the MilViz WX.

P3D <= 5.2 is the v5 version where the MilViz WX should work, I personally run P3D versions 4.5 & 5.3 where 4.5 runs the MilViz WX and 5.3 runs Roland's Radar.

Also you might want to review this entire thread as the v1.1 update was superseeded by v1.2 e.g. here and you'll note the 1.1 update is not included in the provisioned links.

So install and update process is...

• Install the DHC2 via the stated package version.
  • Perform the cleanup of files as per instructions.
• Install v1.0 update.
• Install v1.2 update.
• Install v1.3 update.
  • Configure for P3D v4.5 or v5 as per here
• Review MilViz manuals.
• Configure MVAMS (note P3D must NOT be running when configuring with the MVAMS app).
• Fly.

Cheers

Edited January 28, 20251 yr by Rogen

Thank you for these useful clarifications

As I always do, especially with Lorby A.O., before starting the installation I first take care to plan every part of your process exactly as you specify:

21 hours ago, Rogen said:

So install and update process is...

• Install the DHC2 via the stated package version.
  • Perform the cleanup of files as per instructions.
• Install v1.0 update.
• Install v1.2 update.
• Install v1.3 update.
  • Configure for P3D v4.5 or v5 as per here
• Review MilViz manuals.
• Configure MVAMS (note P3D must NOT be running when configuring with the MVAMS app).
• Fly.

 

When I started to install the DHC2, I didn't expect the setup to display the unchecked Weather Radar option by default.
Hence my question: is it really useful to install WX radar it if it has to be replaced afterwards?

Which you've clearly answered.

So I won't check Weather Radar option because I'm setting up Roland Radar for P3DV5.4 and I've already Active Sky installed for a while.

First step Install the DHC2 via the stated package version :

Outside installation completed

MVAMS opens up automatically with Milviz packages installed

Next step v1.0 update install with Cleanup of files

Cheers

Hello Rogen,

I was deeply impressed by the work you provided into the cleanup process.

About this item I wish to clarify a specific point (but maybe I'm wrong ?)

It's about the [texture.N5347G] of the [DHC-2 Beaver Milviz Straight Floats].
With the Cleanup process applied and the V1.0 update files installed.
In the end, this folder is without the [Beaver_floats_v2.dds] file, which is clearly installed in the other 6  [texture.xxxx] files.

I have checked the zip file [MilViz_DHC-2_Consistency_and_Flight_Model_Update.zip] 
and its folder [DHC-2 Beaver Milviz Straight Floats] \[texture.N5347G] does not contain this file.

Except for this detail, everything went clearly with the installation of V1.0 update.
Next step  V1.2 Update

Cheers

On 2/1/2025 at 5:13 AM, Recciosilva said:

Hello Rogen,

I was deeply impressed by the work you provided into the cleanup process.

Thanks for your kind words.

 

On 2/1/2025 at 5:13 AM, Recciosilva said:

bout this item I wish to clarify a specific point (but maybe I'm wrong ?)

It's about the [texture.N5347G] of the [DHC-2 Beaver Milviz Straight Floats].
With the Cleanup process applied and the V1.0 update files installed.
In the end, this folder is without the [Beaver_floats_v2.dds] file, which is clearly installed in the other 6  [texture.xxxx] files.

I have checked the zip file [MilViz_DHC-2_Consistency_and_Flight_Model_Update.zip] 
and its folder [DHC-2 Beaver Milviz Straight Floats] \[texture.N5347G] does not contain this file.

Those Beaver_floats_v2.dds files are not all the same, and in the aforementioned instance there never was a file of that name within the  N5347G livery, meaning the model will fall back to the texture.cfg paths to find the file it is looking for.

 

On 2/1/2025 at 5:13 AM, Recciosilva said:

Except for this detail, everything went clearly with the installation of V1.0 update.
Next step  V1.2 Update

Happy to hear all is progressing.

Cheers