Recciosilva

Did you purchase your A330 from Aerosoft or SimMarket? If you have an Aerosoft license the paintkit for the A330 Pro for P3D is available in your Aerosoft shopaccount and since 2023, it has also been available in your SimMarket account.

I declined the V6 version as soon as LorBy_SI support announced that "Most (if not all) of the payware apps (CropDusterX, FireFighterX, CameraPositonX, AiTrackerX and WAMA) will be removed from the shops" due to incompatibility with P3DV6.x. The FireFighterX add-on is essential for me. It works perfectly with P3Dv5.4 and my awesome Canadair CL415. By the way, LORBY_SI perfectly explains the unexpected reasons for this incompatibility with P3Dv6: But now the flames are mostly black instead of red/orange

Hello @Ray Proudfoot and @deeknow, I don't think you're in the right Topic ☺️ Is Prepar3D an end of life sim?

Back to the Future https://prepar3d.com/

You're right, it's a nice view even at FL350

We know that since Wednesday 07 May 6:58 pm How can we reduce the carbon footprint of this topic? By closing it!

Drezewiecki grass runs well with P3v5.4. Its operation is very simple: Depending on the season you have chosen, it installs a [detail1.bmp] file with the same name as the default P3D path file. path ...\P3DV5\Scenery\World\texture\ This file has the same name but, as you'd expect, is not the same size. P3DV5.x default file = 11 kb Drezewiecki file = 10923 kb Summer version To install it in P3DV5.4 copy and paste the one installed in P3V4. Of course, before doing so, make a backup of the default file. Note: HIGHMEMFIX=1 fixes a memory issue in FSX that can cause out of memory errors. So especially necessary for FSX installation. Maybe you can check in your P3Dv4/ Prepar3d.cfg file if HIGHMEMFIX=1 appears in [Graphics] section. Personally, I didn't add it.

Posted May 07, 2025 so not for P3D v7

Yes, it works and produces a tire squeal on the aspalth with a smoky effect. It's the file [Sound_TyreLockupSqueal.wav] To clarify why this works, let me summarize the external installation process: This is aimed mainly at users with a minimum of experience of add-on.xml and Lorby A.O. (not recommended for novices). 1-As soon as you launch [setup _210720.exe], you need to point the installation to the desired installation directory: In this directory, you will have created the main folders used by P3D to install an aircraft e.g. SimObjects\Airplanes This applies only to installation of [setup _210720.exe] with 1st launch of VMAMS. and XMLTools64Installer.exe 2-Then the contents of the folders in this basic installation are easily rectified as the Cleanup +V1.0+V1.2+ V1.3 process progresses.1.3 3-Here are the contents of the external installation directory: One little detail: I've created a Modules folder in which I've moved the XMLTools64.dll file installed in the root of this directory. This file is automatically installed by XMLTools64Installer.exe and declared in the dll.xml path C:\Users\User\AppData\Roaming\Lockheed Martin\Prepar3D v5. I've removed these declaration lines from the dll.xml file and integrated them into my add-on.xml file (see below). In this way, we keep to the logic of the Package, which integrates all the elements required for the aircraft. 4-As you can see, DHC2-Beaver will be declared as a complete Package, i.e. its add-on.xml file will be placed directly in this installation directory. In this case, simply declare the new package in the file [add-ons.cfg] path C:\ProgramData\Lockheed Martin\Prepar3D v5 [Package.X] Path=D:\ADDONS P3DV5\P3D-ADDON-AIRCRAFTS\MILVIZ_DHC2-Beaver Title=MILVIZ_DHC2-Beaver Active=TRUE Required=FALSE Place it at the end of the list, so its numbering will be +1, and the order doesn't matter anyway. However, be careful not to change the name of the installation directory, which becomes the name of the Package, in this case [MILVIZ_DHC2-Beaver] 5-Here are the contents of my add-on.xml file which declares the components required for P3D to load the Beaver: 6-Lorby A.O. will now be required to declare this new package to the Simulator. If everything is correct when Lorby A.O. is launched, no error message should appear, and the package and its components should look like this: Package : Other_addons components : All components should appear in dark green If one or more components are displayed in dark violet, you've done a poor job and the path declared is wrong. Last point: as soon as a change is made in MVAMS, validated by [Save default], all aircraft.cfg files are modified and a backup is created. I guess this double installation option gives this nice Beaver update an extra edge, with a great flight model perfectly enhanced by you @Rogen. 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...

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

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.

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

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

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