PATH=C:\Users\Biker57\Documents\Prepar3D v4 Add-ons\Real Air Turbine Duke v2 I use my F:/ drive with a folder called /Prepar3D v4 Add-ons for the aircraft files An absolute Path must be stated in the add=on.xml fileĪn add-on.cfg file in %USERPROFILE%\Appdata\Roaming\Lockheed Martin\Prepar3D v4 is automatically populated by the sim code if it finds an add-on.xml fileĮxample - add-om.xml in %USERPROFILE%\Documents\Prepar3D v4 Add-onsĮxample - associated add-on.cfg entry added by Prepar3d The add-on.xml files read by the Add-on.cfg are very small, they do not take up a lot of space in %USERPROFILE%\Documents\Prepar3D v4 Add-ons I place ONLY the add-on.xml files in this location for each aircraft. I do not follow LM recommendation to install the full aircraft package content in location %USERPROFILE%\Documents\Prepar3D v4 Add-ons distribute an Add-on Package and place it in a directory where Prepar3D can automatically discover it. I use the Method recommended by LM as it is the most stable - but with a small modification The following is MY personal understanding of the external install and add-on process and how I use it at the moment Simple solution to the problem with this profile, set the zoom broken camera manually with the "+" and update cameras set. Most likely you have a problem with the Camera set profile of the aircraft created in an earlier version EZCA2. This happened sometimes in earlier versions EZCA2, in the latter, we no longer observe.
Loading "non-profiled" 777 all is fine and I can create cameras.Īny way to use the older profile, what is happening when the view starts going backwards, why is it happening?Īs you describe occurs if the camera zoom is reset to 0 - "quickly runs back and turns into a black screen or a black dot". If I load the older profile I have, which I think is from v1 initially, then adapted and probably resaved in v2, the view starts to go backwards quite fast, until I have a black screen.
I hoped that I can run EZCA with PMDG777 and/or 747, but I still get the black screen on load - has this been fixed, am I doing something wrong?
0 kommentar(er)
