Guys: I have P3D v5 and mostly fly A2A aircraft. The only non-A2A aircraft I fly are the MJ C-47 and the MilViz Beaver. Once in a while the guys I fly with on JoinFS and Discord plan a mission for non-A2A aircraft - this time it's in amphibs. I've flown my MilViz Beaver for a total of not more than 10 hours or so, but it's been working pretty well. Yesterday I took it out for a test flight. Took off, got up to about 4,500 ft and was flying along, when I heard a strange, popping sound. The airplane seemed to be OK, but I noticed on the external view that puffs of smoke were coming out of the cowling and occasional flames out of the exhaust stack. 

Was this just some sort of random failure, like maybe a burnt valve or cylinder failure? Or did I do something wrong? I try to run my engines by the book, but like I said, I'm not totally familiar with the engine in the Beaver. Maybe I leaned it too much, but it didn't show any signs of rough running - all the way until that popping started. 

Thoughts?

Thank you
 ATB

Was the outside air temp cold ?

Page 45 of the DHC-2-Beaver-Pilot's Flight Manual (located in \DHC-2 Beaver Milviz\Manual\ ) covers use of carb heat in colder weather (being as the Beaver is quite susceptible to cold outside air temps).

Also a search of the PDF for "carburettor heat" should bring up all relevant use of the term.

Cheers

Thank you, Rogen, for getting back. I'll check it out during our flight on Sunday (details at A2A Misfit Squadron MP flight "Amphibs to the Rescue"). 

I wrote down the various engine settings for climb and cruise. Maybe that engine problem I had was just a random event. I miss the A2A Shift+7 hangar for fixing that sort of thing. 

Seeya
ATB

Edited February 6, 20251 yr by Paughco

Most likely your issue was a need for carb heat, the engine can really play up if the outside air temp is low, where it's just a matter of the right amount of carb heat to resolve.

Yeah, A2A's are quite unique with their wear and tear, and there are other planes that have similar functions, e.g. Ant's Airplanes, plus I retrofitted a couple of different sets of wear and tear gauges to a few aircraft, works well enough but takes a lot of tuning to get them running appropriately.

The other Milviz aircraft are also pretty good, the King Air especially, and there is the Otter and Turbo Otter where the Turbo Otter is very easy to blow the engine if the engine gauges are not always kept in the Green range.

Good flying for Sunday. 🙂

Cheers

Interesting: The MilViz Beaver manual shows the mixture control as simply going from full rich at full forward to idle cutoff at full aft. The actual Beaver manual shows the mixture control as being in AUTO LEAN at full forward, AUTO RICH slightly aft of that, then FULL-RICH (I'm hoping it has detents in all those positions), then it goes back though a manual leaning range, finally to idle cutoff at full aft.

Here's a link to a web page that describes the mixture control: https://www.oldjets.net/dehavailland-dhc-2.html. I zoomed in on the throttle control images, and it looks like some of the Beavers have the same setup as the MilViz Beaver.

After rmuch reading of manuals, I'm guessing that maybe I was running my engine too hard for too long at the beginning of my flight. I'll pull it back to climb power sooner, 30-33.5 inch MAP, 2,000-2,200 rpm, depending upon takeoff weight. Also, I read in one of the manuals that you should only lean the mixture when the MAP is in the blue arc on the gauge. 

Also, I've got another situation: I can control the pitch with the mouse or with a couple buttons mapped via P3D on my Thrustmaster stick. If I move the throttle with the mouse, nothing happens until I touch the appropriate pitch button on the throttle; then the pitch instantly changes. 

At least I have my RXP GTN750 working in the airplane!

Thank you
ATB

20 hours ago, Paughco said:

At least I have my RXP GTN750 working in the airplane!

What version of the DHC2 is being run ?

e.g. 

• Stock
• Stock + 1.0, 
• Stock +1.0 + 1.2
• Stock +1.0 +1.2 +1.3

Cheers

I've got stock + MilViz_DHC2_Community_Update_v1.0. 

I've got a download of MilViz_DHC2_Community_Update_v1.3, but I don't have 1.2. 

Right now my Beaver is working OK, so I don't want to change anything before this Sunday. I've got N5473G with the amphib floats ready to go on our Sunday mission. The GTN750 is in the panel, and the Shift+3 popup is working. I'll be careful with the engine and it should be OK.

But I'm interested in getting v1.2 to see what it can do. 

By the way - I got an actual flight in a Kenmore Air Beaver, from Lake Washington to Friday Harbor and back. This was when I was working at Washington Department of Ecology. A guy called me up and said that he wanted to know if it was OK to burn up a ship around San Juan Island. I said no way, it'll create too much air pollution. The governor at that time was really promoting making movies in Washington. The guy said they needed to blow up that ship to make "Free Willy 2." Sorry man, not happening. The guy said they'd fly me up to look at what they were planning to do. This involved a ride in a Beaver up to Friday Harbor. Final result: They made the movie. No whales were harmed in the making of the movie. Nobody died due to air pollution. Now my wife says she wants to go up and see the bears at Brooks Falls in Alaska. This will involve a ride on a Alaska Airlines 737 to Anchorage. Then a smaller jet to King Salmon. From there a seaplane to Brooks Camp. I told her the only way we're gonna go is if the flight from King Salmon to Brooks is in an DHC-2. Not a turbo Otter. Not a Cessna 207 or 208. Only one way: Beaver Ballad.

Thank you
 ATB

I'm having a lot of fun flying the Milviz Beaver now with these updates.  Up until this patch came out, I preferred flying the old FSX default Beaver on floats and the freeware AF Scrubbs models on wheels that uses the default FSX VC.  I even thought of trying the Aerosoft Beaver X to see if I could get it to work in P3Dv5 but thank goodness this community patch turns the Milviz Beaver into a fantastic airplane.  Thank you, Rogen, for sharing your work.

I think I figured out the detonation problem. It's due to the cold weather. I need to adjust the carb heat to keep the inlet temperature in the green. Apparently the real airplane experiences that same phenomenon. 

Took the wheel version on a short test flight from Darrington Airport (1S2) to home base at Arlington (KAWO) and everything seemed to work. No popcorn sound and no flames from the exhaust. Life is good.

 

Seeya
ATB

20 hours ago, Paughco said:

I think I figured out the detonation problem. It's due to the cold weather. I need to adjust the carb heat to keep the inlet temperature in the green. Apparently the real airplane experiences that same phenomenon.

Yeah, a bit of carb heat does wonders.

On 2/8/2025 at 3:21 PM, Paughco said:

But I'm interested in getting v1.2 to see what it can do. 

As to what's in v1.2, mostly it's based on your own contribution where you mentioned you were using the F1 to RXP bezel button bridge gauge, where although I've used the gauge itself in other aircraft, for the Beaver I looked into the gauge code, resolved bugs and edited the models to enable the bezel buttons to function with a single click instead of needing to double click and now the RXP integrates as well as the original F1 GTN.

The auto pilot is also updated and is further updated in v1.3 with contributions from @gaab.

And the v1.2 update can be found in the below comment.

Cheers

Hello Rogen,
In fact, I was able to quickly install v1.2 and then v1.3. All installed as an external add-on managed by Lorby A.O.

But I didn't report to you right away because I had to deal with 2 issues installing the DHC2 update.
The first has been fixed and introduced me to a surprising feature of P3Dv4 and v5.
As for the second, I haven't found the solution, but I hope you'll be helpful.

Here's how my installation went:
DHC2-Beaver fully updated, P3Dv5.4 launched:

All Beaver models are properly available
I select the Milvix DHC2 CUXPA Base and run the scenery with this aircraft:

Yep, the same error message reported by our friend @davidk64

But fortunately for him and for me I found the fix:
Long explanation :
1-Already this error occurs only if your Add-on Milviz is in external installation as for me and @davidk64.
2-P3D requests sound files path ----\Panel\MVSounds\SND1.wav
    It's normal that it can't find them, since the Beaver's are in path \SimObjects\Airplanes\DHC-2 Beaver Milviz\DHC-2_XML_Sounds
3-The [MVSounds] directory does not exist, and even less so in the [panel] folder.
4-The explanation of this issue is simply the presence of one particular default aircraft installed  in P3DV4 and V5:
     The MilViz_P38_L whose sound files are installed in path: P3D\SimObjects\Airplanes\MilViz_P38_L\panel\MVsounds]
      So P3D loads its aircraft by default, and for externally installed Milviz Publisher aircraft, their sound files must have exactly the same installation path as 
      MilViz_P38_L.
5-The easiest fix is to drag and drop the DHC-2_XML_Sounds file into the \SimObjects\Airplanes\DHC-2 Beaver Milviz\panel and rename it MVsounds.

With this 1st issue solved, I was finally able to see the great Rogen Beaver update installed:

And finally (sorry if I've gone on a bit long) my last issue, which doesn't prevent me from flying. Nevertheless, it bothers me:
It is of course, as you may have noticed the lack of the Roland Radar v3.0.0.0 gauge. 
I strictly followed the instructions to inhibit the Milviz WX gauge and to declare the RRv3 gauge VC.
I even installed the Beaver in P3D, but the result is exactly the same as with an external add-on, and still without this gauge.
What's more, I was able to install it on my Bell UH1-C and it works fine.

Edited February 18, 20251 yr by Recciosilva

On 2/19/2025 at 5:28 AM, Recciosilva said:

Hello Rogen,
In fact, I was able to quickly install v1.2 and then v1.3. All installed as an external add-on managed by Lorby A.O.

But I didn't report to you right away because I had to deal with 2 issues installing the DHC2 update.
The first has been fixed and introduced me to a surprising feature of P3Dv4 and v5.
As for the second, I haven't found the solution, but I hope you'll be helpful.

Here's how my installation went:
DHC2-Beaver fully updated, P3Dv5.4 launched:

<SNIP PIC>

All Beaver models are properly available
I select the Milvix DHC2 CUXPA Base and run the scenery with this aircraft:

Yep, the same error message reported by our friend @davidk64

But fortunately for him and for me I found the fix:
Long explanation :
1-Already this error occurs only if your Add-on Milviz is in external installation as for me and @davidk64.
2-P3D requests sound files path ----\Panel\MVSounds\SND1.wav
    It's normal that it can't find them, since the Beaver's are in path \SimObjects\Airplanes\DHC-2 Beaver Milviz\DHC-2_XML_Sounds
3-The [MVSounds] directory does not exist, and even less so in the [panel] folder.
4-The explanation of this issue is simply the presence of one particular default aircraft installed  in P3DV4 and V5:
     The MilViz_P38_L whose sound files are installed in path: P3D\SimObjects\Airplanes\MilViz_P38_L\panel\MVsounds]
      So P3D loads its aircraft by default, and for externally installed Milviz Publisher aircraft, their sound files must have exactly the same installation path as 
      MilViz_P38_L.
5-The easiest fix is to drag and drop the DHC-2_XML_Sounds file into the \SimObjects\Airplanes\DHC-2 Beaver Milviz\panel and rename it MVsounds.

With this 1st issue solved, I was finally able to see the great Rogen Beaver update installed:

 

Interesting, yes an issue with the use of add-in pathing is the need for unique gauge naming and associated structures due to P3D running with the first item it finds.

A common one I've seen is the use of Doug Dawson's dsd_p3d_xml_sound_x64.dll where the first dll iteration found anchors the gauge & pathing relationships, unique gauge naming typically overcomes the issue though.

You should note that the DHC-2_XML_Sounds pathing is also defined in the panel.cfgs, and might need some reworking in that area as sounds like you've a situation where P3D is saying opps I couldn't find the path, lets fall back to a search type of thing.

 

On 2/19/2025 at 5:28 AM, Recciosilva said:

And finally (sorry if I've gone on a bit long) my last issue, which doesn't prevent me from flying. Nevertheless, it bothers me:
It is of course, as you may have noticed the lack of the Roland Radar v3.0.0.0 gauge. 
I strictly followed the instructions to inhibit the Milviz WX gauge and to declare the RRv3 gauge VC.
I even installed the Beaver in P3D, but the result is exactly the same as with an external add-on, and still without this gauge.
What's more, I was able to install it on my Bell UH1-C and it works fine.

 

I'm not sure I understand what processes you've been using for update and subsequent configuration.

If you've installed the Beaver and updated sequentially, the default panel will be "MilViz 530/430 GPS with no WX".

To change this one uses MVAMS to select the GTN and WX options (P3D must not be running when doing this), along with any other choices like Passenger or Cargo and type of propeller, spinner, cold cover etc.

Then when P3D is started and the DHC2 is chosen to fly, the Beaver will load with those options already pre-configured and enabled as MVAMS does the job of swapping the pre-configured panels and models in the many aircraft.cfg, so that they are all defined with the pilot's MVAMS choices, noting the cropduster is a specific config as it doesn't have a passenger cabin.

Of note is when WX is chosen in MVAMS the Roland WX radar will be automatically embedded in the original Milviz WX bezel and assuming Active Sky is properly configured and running the radar should be functioning.

The question I would ask is how are you configuring the aircraft ?

 

In this pic the Roland Radar v3 has loaded but the connection to Active Sky has not been made as I hadn't started AS, this was a test flight of the AP and is why sim vars are being displayed for review.

Here the Roland Radar v3 has loaded and connected to Active Sky and all is functioning Ok.

 

One issue I've noted (separate from WX) is the GTN will on occasion fail to start in the VC bezel (looks like an electrics startup timing issue), where the workaround is to the kill the GTN exe running under the P3D exe (in Task Manager), at that point the GTN should restart itself successfully.

Cheers

On 2/20/2025 at 12:49 AM, Rogen said:

You should note that the DHC-2_XML_Sounds pathing is also defined in the panel.cfgs, and might need some reworking in that area as sounds like you've a situation where P3D is saying opps I couldn't find the path, lets fall back to a search type of thing.

I don't think so, because I've checked this point: 

On the first error message, if you want P3D to eventually open on its startup page, scenario aircraft + scenery you'll have to click OK 55 times, because P3D requires all 55 sound files from the Beaver  (30 for MilViz_P38_L), SND1.wav to SND55.wav and how does it know there are 55 ?

Because it reads the instruction :

gauge06=..\panel\MV3DSound!MV3DS,  0,0,1,1,SimObjects\\Airplanes\\DHC-2 Beaver Milviz\\DHC-2_XML_Sounds#55

even though the path is wrong, it will load these 55 sound files, provided you apply the fix, but if you don't, you'll get  a nice but mute Beaver.

On 2/20/2025 at 12:49 AM, Rogen said:

I'm not sure I understand what processes you've been using for update and subsequent configuration.

Whether for an external installation or in the simulator, I strictly applied the process:
1-Install setup [MVDHC2 Beaver 210720.exe]
2-Install v1.0 update and cleanup process.
3-Install v1.2 update .
4-Install v1.3 update.
By the way, I noticed that it's V1.0 update that changes the default mv530_430_wx panel to mv530_430 with no weather radar.

As for the lack of my Roland Radar gauge:
Your image above shows exactly the configuration I want on my Beaver the GTN750 + Roland Radarv3 gauge running with Active Sky.

So could you please confirm that the VMAMS launched (P3D not launched) must be validated like this:

ActiveSky started, then P3D started the Beaver should display My VC  RXP750 and the VC Roland RadarV3 gauge.

And which panel should be registered in the aircraft.cfg file? :
[fltsim.0]
title=MilViz DHC2 Beaver CUXPA
sim=MilvizDHC2_Base
model=1
panel= //GNS750_WX or GTN750 ? // I think this is the essential part of my issue

Thanks again for your attention. 

 

On 2/24/2025 at 5:52 AM, Recciosilva said:

I don't think so, because I've checked this point: 

On the first error message, if you want P3D to eventually open on its startup page, scenario aircraft + scenery you'll have to click OK 55 times, because P3D requires all 55 sound files from the Beaver  (30 for MilViz_P38_L), SND1.wav to SND55.wav and how does it know there are 55 ?

Because it reads the instruction :

gauge06=..\panel\MV3DSound!MV3DS,  0,0,1,1,SimObjects\\Airplanes\\DHC-2 Beaver Milviz\\DHC-2_XML_Sounds#55

even though the path is wrong, it will load these 55 sound files, provided you apply the fix, but if you don't, you'll get  a nice but mute Beaver.

I still lean towards it being a path issue where the MV3DSound.dll cannot find the path and therefore falls back to a default, likely built into the MV3DSound.dll itself.

Do the other sounds work for you ? e.g. the tyre squeal if you apply the handbrake while moving on a hard surface, noting these are in a different pathing.

Also what about the Milviz_Lighting_Service.exe, is that running Ok too ?

 

On 2/24/2025 at 5:52 AM, Recciosilva said:

Whether for an external installation or in the simulator, I strictly applied the process:
1-Install setup [MVDHC2 Beaver 210720.exe]
2-Install v1.0 update and cleanup process.
3-Install v1.2 update .
4-Install v1.3 update.
By the way, I noticed that it's V1.0 update that changes the default mv530_430_wx panel to mv530_430 with no weather radar.

Great 🙂 all fine there then.

The purpose of not setting a default that includes weather radar is because the default MV WX gauge will result in CTD for later versions of P3D v5 as MV never updated the gauge to suit P3D v5.3+, which in turn is why the Roland's Radar option is applied.

If you're running say... P3D v4.5 you could swap back to the MV weather radar gauge which does otherwise function Ok and doesn't need Active Sky.

On 2/24/2025 at 5:52 AM, Recciosilva said:

As for the lack of my Roland Radar gauge:
Your image above shows exactly the configuration I want on my Beaver the GTN750 + Roland Radarv3 gauge running with Active Sky.

So could you please confirm that the VMAMS launched (P3D not launched) must be validated like this:

Yep, that's it, have a review of the MV & other aircraft docs, good info in them.

 

On 2/24/2025 at 5:52 AM, Recciosilva said:

ActiveSky started, then P3D started the Beaver should display My VC  RXP750 and the VC Roland RadarV3 gauge.

And which panel should be registered in the aircraft.cfg file? :
[fltsim.0]
title=MilViz DHC2 Beaver CUXPA
sim=MilvizDHC2_Base
model=1
panel= //GNS750_WX or GTN750 ? // I think this is the essential part of my issue

MVAMS should do all this for you (and it does in a std. sim based install).

Remember there are 10 aircraft.cfg to be updated with model, sound, panel, etc. It would get old really quick to have make all changes manually.

And if MVAMS is able to work successfully each aircraft.cfg will be updated and have a corresponding Aircraft_backup.cfg where both are dated the same. Given there are 10 aircraft.cfg to update I considered having a functional MVAMS to be a fairly important item as MVAMS was only partially functional in the default MilViz DHC-2 Beaver 210720.exe install.

Any panel.cfg with "_WX" in its folder name is pre-configured with WX and yeah panel=GNS750_WX is the GTN750 with Weather Radar, the name reference is the sort of bug you'd think would have been picked up in peer code review @ MV but I guess each dev mostly did their own thing unsupervised and unreviewed.

Anyway let us know how your install approach ends up.

Cheers

Sorry for my late reply I've been far away from my PC gamer for a while.

Good news the fix to my issue stems from the fact that when I installed Beaver- [setup _210720.exe], I didn't tick the Milvitz WX installation option.
At least that means that for an external installation it's mandatory.

 

After ticking this option for P3Dv5, everything is OK:

RXP-GTN750 + RR v3.0.0.0 

Night lighting OK

Of course, this also includes the other DHC2-Beaver models:
e.g. DHC-2 Beaver Milviz Straight Floats

 

So everything works, sounds, lights and so on...

 

 

Edited March 15, 20251 yr by Recciosilva
Additions