SP2 and V4 compat. USE AT YOUR OWN RISK

[JonathanBleeker]

Do you have a series of .dll files in the base aircraft panel folder , MV3Dsound , amsinterop , I am wondering if some AV program is not permitting elements to remain or install .

The Installer was run as an administrator and you were logged on as an administrator on the same account as the sim is used ? . are you using W10 by chance .
Is your sim installed on remote disks or other considerations?

It may be needed to reinstall the entire plane as an admin by right clicking on the installer , there might be o

Just to prevent confusion, the above post was directed at Bushido.

So Saitek and, in my case, CH Products throttle, are not typical?

How is the prop lever made 'custom'? Why not the throttle and mixture as well?

I believe Tomas had to do some special code to get the propeller to behave properly as part of the flight model. I have some ideas that he could use to enable controlling the prop lever animation via the prop axis command (calibrating through FSUIPC would be out though. You could assign it in FSUIPC but not calibrate as that would mask the event so we cannot see it), but no promises on that yet.

[Raptor]

I use a Saitek Yoke and Throttle quadrant. I have no issues with any of my levers either mapping from P3DV4 or FSUIPC5. And yes, in FSUIPC I mapped to PROP1. My rudders also move.

[JonathanBleeker]

Update: I just spoke to Tomas and he says it works if you map your lever to Prop 1, not to the general Prop command that will set all prop levers for a specific aircraft. This is being fixed.

[Bushido]

@ Bushido > Do you have a series of .dll files in the base aircraft panel folder , MV3Dsound , amsinterop , I am wondering if some AV program is not permitting elements to remain or install .

The Installer was run as an administrator and you were logged on as an administrator on the same account as the sim is used ? . are you using W10 by chance .
Is your sim installed on remote disks or other considerations?

It may be needed to reinstall the entire plane as an admin by right clicking on the installer and do so with the AV program off temporarily.

I have the MV3Dsound.dll and the amsinterop.dll in the panel folder.
I have run the installer as an administartor and i am loged on the only account of the computer (administrator one)
I use windows 10.
Just to be sure I have disable my antivirus (windows defender) dowload again the installer, uninstall the beaver, re-install it, have a message that the XMl toll install sucessfuly (always with antivirus off) and still no sound for the flip, the pump and so on.
I can hear the fuel boost pump and the motor when he is running (but not when it start)
And what is worse is now I can't control the Prop lever with the mouse anymore it always go back to full feather (it's something new I did not have this issue on my previous installation)

[Bushido]

Here is a copy of my "contenterrors" file related to the beaver if it may help (sorry for the long list)
There are some part that concern the sound (error 241 for example)

error=Key values exist outside of a section:
File:B:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\DHC-2 Beaver Milviz\aircraft.cfg
Key:DHC2 Milviz base FDE May 23 2017
[error.128]
error=Found Duplicate Key Name
File:B:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\DHC-2 Beaver Milviz\aircraft.cfg
Section:propeller
Key:propeller_type
[error.129]
error=Key values exist outside of a section:
File:B:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\DHC-2 Beaver Milviz Floats\aircraft.cfg
Key:Beta 23 may 2017
[error.130]
error=Found Duplicate Key Name
File:B:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\DHC-2 Beaver Milviz Floats\aircraft.cfg
Section:propeller
Key:propeller_type
[error.131]
error=Found Duplicate Key Name
File:B:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\DHC-2 Beaver Milviz Floats\aircraft.cfg
Section:contact_points
Key:gear_system_type
[error.132]
error=Found Duplicate Key Name
File:B:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\DHC-2 Beaver Milviz Floats\aircraft.cfg
Section:contact_points
Key:static_pitch
[error.133]
error=Found Duplicate Key Name
File:B:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\DHC-2 Beaver Milviz Floats\aircraft.cfg
Section:contact_points
Key:static_cg_height
[error.134]
error=Found Duplicate Key Name
File:B:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\DHC-2 Beaver Milviz Skis\aircraft.cfg
Section:propeller
Key:propeller_type
[error.135]
error=Found Duplicate Key Name
File:B:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\DHC-2 Beaver Milviz Tundra\aircraft.cfg
Section:propeller
Key:propeller_type
[error.136]
error=Duplicate Section Name
File: B:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\AI_Floatplane_DHC-2_Beaver_TFX\aircraft.cfg
Section: stall_warning
[error.214]
error=Gauge/Script Error
Type: Animation Script
Name: DHC2 Beaver N963DH
Error: Empty parentheses or closing parenthese missing: "(A:AVIONICS MASTER SWITCH,bool)! or
(A:NAV GS FLAG:1, bool) ! or
if{ 10 }
els{ 0 }
"

[error.215]
error=Gauge/Script Error
Type: Animation Script
Name: DHC2 Beaver N963DH
Error: Empty parentheses or closing parenthese missing: "(A:AVIONICS MASTER SWITCH,bool)! or
(A:NAV HAS NAV:1, bool) ! or
if{ 10 }
els{ 0 }
"

[error.216]
error=Gauge/Script Error
Type: Animation Script
Name: DHC2 Beaver N963DH
Error: Empty parentheses or closing parenthese missing: "(A:AVIONICS MASTER SWITCH,bool)! or
(A:NAV GS FLAG:1, bool) ! or
if{ 10 }
els{ 0 }
"

[error.217]
error=Gauge/Script Error
Type: Animation Script
Name: DHC2 Beaver N963DH
Error: Empty parentheses or closing parenthese missing: "(A:AVIONICS MASTER SWITCH,bool)! or
(A:NAV HAS NAV:1, bool) ! or
if{ 10 }
els{ 0 }
"

[error.218]
error=Key values exist outside of a section:
File:B:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\DHC-2 Beaver Milviz\aircraft.cfg
Key:DHC2 Milviz base FDE May 23 2017

[error.219]
error=Found Duplicate Key Name
File:B:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\DHC-2 Beaver Milviz\aircraft.cfg
Section:propeller
Key:propeller_type

[error.220]
error=Key values exist outside of a section:
File:B:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\DHC-2 Beaver Milviz\aircraft.cfg
Key:DHC2 Milviz base FDE May 23 2017

[error.221]
error=Found Duplicate Key Name
File:B:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\DHC-2 Beaver Milviz\aircraft.cfg
Section:propeller
Key:propeller_type

[error.222]
error=Texture NONAME.BMP failed to load (FE_REQUEST_STATUS==13)

[error.223]
error=Texture BOX_002_SPECULAR.DDS failed to load (FE_REQUEST_STATUS==13)

[error.224]
error=Texture BOX_004_SPECULAR.DDS failed to load (FE_REQUEST_STATUS==13)

[error.225]
error=Texture BOX_003_SPECULAR.DDS failed to load (FE_REQUEST_STATUS==13)

[error.226]
error=Texture BOX_005_SPECULAR.DDS failed to load (FE_REQUEST_STATUS==13)

[error.227]
error=Texture BOX_001_SPECULAR.DDS failed to load (FE_REQUEST_STATUS==13)

[error.228]
error=Texture PROPS_INVFR.BMP failed to load (FE_REQUEST_STATUS==13)

[error.229]
error=Gauge/Script Error
Type: Animation Script
Name: DHC2 Beaver N963DH
Error: Empty parentheses or closing parenthese missing: "(A:AVIONICS MASTER SWITCH,bool)! or
(A:NAV GS FLAG:1, bool) ! or
if{ 10 }
els{ 0 }
"

[error.230]
error=Gauge/Script Error
Type: Animation Script
Name: DHC2 Beaver N963DH
Error: Empty parentheses or closing parenthese missing: "(A:AVIONICS MASTER SWITCH,bool)! or
(A:NAV HAS NAV:1, bool) ! or
if{ 10 }
els{ 0 }
"

[error.231]
error=Gauge/Script Error
Type: Animation Script
Name: DHC2 Beaver N963DH
Error: Empty parentheses or closing parenthese missing: "(A:AVIONICS MASTER SWITCH,bool)! or
(A:NAV GS FLAG:1, bool) ! or
if{ 10 }
els{ 0 }
"

[error.232]
error=Gauge/Script Error
Type: Animation Script
Name: DHC2 Beaver N963DH
Error: Empty parentheses or closing parenthese missing: "(A:AVIONICS MASTER SWITCH,bool)! or
(A:NAV HAS NAV:1, bool) ! or
if{ 10 }
els{ 0 }
"

[error.233]
error=Gauge/Script Error
Type: Animation Script
Name: DHC2 Beaver N963DH
Error: Empty parentheses or closing parenthese missing: "(A:AVIONICS MASTER SWITCH,bool)! or
(A:NAV GS FLAG:1, bool) ! or
if{ 10 }
els{ 0 }
"

[error.234]
error=Gauge/Script Error
Type: Animation Script
Name: DHC2 Beaver N963DH
Error: Empty parentheses or closing parenthese missing: "(A:AVIONICS MASTER SWITCH,bool)! or
(A:NAV HAS NAV:1, bool) ! or
if{ 10 }
els{ 0 }
"

[error.235]
error=Gauge/Script Error
Type: Animation Script
Name: DHC2 Beaver N963DH
Error: Empty parentheses or closing parenthese missing: "(A:AVIONICS MASTER SWITCH,bool)! or
(A:NAV GS FLAG:1, bool) ! or
if{ 10 }
els{ 0 }
"

[error.236]
error=Gauge/Script Error
Type: Animation Script
Name: DHC2 Beaver N963DH
Error: Empty parentheses or closing parenthese missing: "(A:AVIONICS MASTER SWITCH,bool)! or
(A:NAV HAS NAV:1, bool) ! or
if{ 10 }
els{ 0 }
"

[error.237]
error=Gauge file not found: MV_WX!WX2D

[error.238]
error=Gauge file not found: MV_WX!WX

[error.239]
error=Gauge/Script Error
Type: Gauge
Name: passenger
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): "SP1" in: SP1

[error.240]
error=Gauge/Script Error
Type: Gauge
Name: DHC2_SysEvents
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): "SP1" in: SP1

[error.241]
error=Gauge file not found: MV3DSound!MV3DS

[error.242]
error=Gauge/Script Error
Type: Unknown
Name: Unknown
Error: Panel Background bitmap not found: "B:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\DHC-2 Beaver Milviz\panel.mv530_430\C310_VC_05.bmp"

[error.243]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.244]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.245]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.246]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.247]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.248]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.249]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.250]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.251]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.252]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.253]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.254]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.255]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.256]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.257]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.258]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.259]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.260]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.261]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.262]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.263]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GTX330
Error: Boolean does not evaluate to TRUE or FALSE

[error.264]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS530_1
Error: Missing gauge image file: ..\panel\Milviz_GPS\GNS530_Off.bmp

[error.265]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Boolean does not evaluate to TRUE or FALSE

[error.266]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Boolean does not evaluate to TRUE or FALSE

[error.267]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Boolean does not evaluate to TRUE or FALSE

[error.268]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): ")" in: )

[error.269]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Boolean does not evaluate to TRUE or FALSE

[error.270]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Invalid script (command not found - perhaps a space is missing or there's an extra space?): ")" in: )

[error.271]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Boolean does not evaluate to TRUE or FALSE

[error.272]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Boolean does not evaluate to TRUE or FALSE

[error.273]
error=Gauge/Script Error
Type: Gauge
Name: FBS_GNS430_2
Error: Missing gauge image file: ..\panel\Milviz_GPS\GNS430_Off.bmp

[error.274]
error=file "void(.wav|.ogg)" not found

[error.275]
error=file "void(.wav|.ogg)" not found

[error.276]
error=file "void(.wav|.ogg)" not found

[error.277]
error=Gauge file not found: MV3DSound!MV3DS

[error.278]
error=Texture NONAME.BMP failed to load (FE_REQUEST_STATUS==13)

[error.279]
error=Texture BOX_002_SPECULAR.DDS failed to load (FE_REQUEST_STATUS==13)

[error.280]
error=Texture BOX_004_SPECULAR.DDS failed to load (FE_REQUEST_STATUS==13)

[error.281]
error=Texture BOX_003_SPECULAR.DDS failed to load (FE_REQUEST_STATUS==13)

[error.282]
error=Texture BOX_005_SPECULAR.DDS failed to load (FE_REQUEST_STATUS==13)

[error.283]
error=Texture BOX_001_SPECULAR.DDS failed to load (FE_REQUEST_STATUS==13)

[error.284]
error=Texture PROPS_INVFR.BMP failed to load (FE_REQUEST_STATUS==13)

[boez]

Unfortunately, we don't use these hardware addons and therefore can't support them. If Fsupic isn't helping not much we can do though I will leave the final decision on that with Tomas and Chuck.

Outstanding bugs seem to be MP gauge not working, toes brake animations missing and floating beacon light.

Edit. (Unnecessary bleating removed!). I found that before I successfully installed xmltools64 that the MP gauge did not work (indicator lights permanent lit too) but once the DLL was installed these two issues disappeared.

[Chuck Jodry]

Bushido, 241 MV3DSound!MV3DS is in the panel folder so we are seeing a permissions or directory issue , and from the indications there is a likelihood a systems dll isn't being read as well.
Just to be sure this is a gauge load issue please let us know if its in the base version with none as the panel option .

Please post your system specifications , gpu type and addons operating at the same time if any as well as if there are out of the ordinary installation options like P3D on secondary drives.
I had noted earlier when you installed XMLtools as an admin it went through where it failed first time , there is a clue there as to what the problem is and with some further information we will be in a better position to determine where the problem is and how to rectify it

Best CJ

@ Bushido > Do you have a series of .dll files in the base aircraft panel folder , MV3Dsound , amsinterop , I am wondering if some AV program is not permitting elements to remain or install .

The Installer was run as an administrator and you were logged on as an administrator on the same account as the sim is used ? . are you using W10 by chance .
Is your sim installed on remote disks or other considerations?

It may be needed to reinstall the entire plane as an admin by right clicking on the installer and do so with the AV program off temporarily.

I have the MV3Dsound.dll and the amsinterop.dll in the panel folder.
I have run the installer as an administartor and i am loged on the only account of the computer (administrator one)
I use windows 10.
Just to be sure I have disable my antivirus (windows defender) dowload again the installer, uninstall the beaver, re-install it, have a message that the XMl toll install sucessfuly (always with antivirus off) and still no sound for the flip, the pump and so on.
I can hear the fuel boost pump and the motor when he is running (but not when it start)
And what is worse is now I can't control the Prop lever with the mouse anymore it always go back to full feather (it's something new I did not have this issue on my previous installation)

[Rongor]

Honestly I just don't get why so many people mess around setting up their controls via FSUIPC. This is entirely not necessary.
P3D's controls settings are very much capable to achieve such a basic task like setting up the desired axis for some control.
Regarding the prop lever some people reported problems with, I just set my (not-supported ) TM HOTAS Warthog right throttle axis to work as the prop lever and it works just totally fine.

If you have problems with your prop levers, don't blame Milviz.

In my understanding, for matters like these, it is not at all a question whether Milviz supports your controls hardware. P3D has to support them. And if P3D can work with your hardware, it should very well work with the Milviz Beaver.
If you setup all your controls via FSUIPC, you should look there for anything not working as desired.

[Ron Attwood]

Update: I just spoke to Tomas and he says it works if you map your lever to Prop 1, not to the general Prop command that will set all prop levers for a specific aircraft. This is being fixed.

Thank you Jonathon, an answer that makes sense! And of course it works. I'm tempted to lay on some heavy sarcasm at this point, but I'll stifle myself. I confess I was losing faith with Milviz, but I think this Beaver will eventually be an all time 'must have'.

[Ron Attwood]

Honestly I just don't get why so many people mess around setting up their controls via FSUIPC. This is entirely not necessary.
P3D's controls settings are very much capable to achieve such a basic task like setting up the desired axis for some control.
Regarding the prop lever some people reported problems with, I just set my (not-supported ) TM HOTAS Warthog right throttle axis to work as the prop lever and it works just totally fine.

If you have problems with your prop levers, don't blame Milviz.

In my understanding, for matters like these, it is not at all a question whether Milviz supports your controls hardware. P3D has to support them. And if P3D can work with your hardware, it should very well work with the Milviz Beaver.
If you setup all your controls via FSUIPC, you should look there for anything not working as desired.

Aah, so that's how it's done.

[Bushido]

@ Chuck
I have choose the milviz 530 gps in the panel option I haven't try the none option (and I'm away from the computer for a week so can't test I'm afraid)
I have an i7 6600k an nvidia 1060 and 32gb ram. I run as16, some orbx region, tongass fjord, and the aerosoft twin otter.
I have a c drive for my os and a b drive for my program where p3d is installed, nothing too fancy.
I don't think the xml tools fails the first time actually I have try to reinstall it as you propose but I always have a message stating that the xml tools install properly.
Thanks for your support !

[JirkaK]

Thank you for this beta. Installed with easy and from first view, all works fine, just... do you plan install plane outside sim folders as add-on library?

[Krazycolin]

We're not sure we can and make everything work properly.

We are looking into this but, for now, it must go into the same place...

[JirkaK]

Thanks for answer and we will see