Hi,
it is not possible to assigne a outside spot for the RealAir Lagacy and Duke. It always jumps back into the cockpit.

I know this was already discussed back in Aug 2017. Any solution by now?

Regards
Raller

 

 

We have not had reports of issues with the Duke... Can you generate a Report file from the Preferences after observing the issue and send the file to us?

Ok, report is sent.

This is the view (in either one, RealAir Legacy and Duke) it always jumps back when i switch to Outside-View.
In this view it is also NOT possible, to move the sight with the joystick pan switch nor with the CP camera sliders!

 

The same thing happens to me, but it is because of the new installers for version 4 of Prepar3d.

Installing by hand with the old ones, if there were external views.
Greetings.

I do not have that issue. Can you guys generate a Report file and send it to us via email? We will analyse the files to find the issue.

I already sent a Report, but i send it again...

Edited May 7, 20188 yr by Raller

1 minute ago, Raller said:

I already sent a Report, but i send it again...

Where did you send it? Because I have not received it.

I am in communication with @Quasar07 right now, we're trying to figure it out. So far, I have noticed that the install process you guys went through is not the same as the one I have with the P3Dv4 installer for those aircraft.

Have both of you guys tried to reinstall the aircraft with the latest installers?

I send it to "support@***.com" like it is told in the report-file.

The installers for the Duke and the Legacy are the latest, dated 2017-11-22, especialy for P3Dv4.

The aircrafts are installed in a extra folder and a add-on.xml is pointing to it:

<?xml version="1.0" encoding="utf-8"?>
<SimBase.Document Type="AddOnXml" version="4,0" id="add-on">
  <AddOn.Name>RealAir</AddOn.Name>
  <AddOn.Description>Aircrafts by RealAir</AddOn.Description>
  <AddOn.Component>
    <Category>Effects</Category>
    <Path>P:\MyP3Dv4AddOns\RealAir\Effects</Path>
    <Type>GLOBAL</Type>
  </AddOn.Component>
  <AddOn.Component>
    <Category>SimObjects</Category>
    <Path>P:\MyP3Dv4AddOns\RealAir\SimObjects\Airplanes</Path>
  </AddOn.Component>
</SimBase.Document>

 

Edited May 7, 20188 yr by Keven Menard
Censor Email addr.

Where is that add-on.xml located?

"C:\Users\Ralf\Documents\Prepar3D v4 Add-ons\RealAir\add-on.xml"

So when I run the installer, by default it would install in \Documents\Prepar3D v4 Add-ons\Turbine Duke V2 P3D4

If I redirect it to a custom folder, say D:\FS\Addons\aircraft\Turbine Duke V2 P3D4 it will install in that folder and nothing will be placed in the Prepar3D v4 Add-ons folder. The add-on is referenced in the effects.cfg and simobjects.cfg in ProgramData...

Can you confirm that reinstalling the aircraft follows that structure?

Ok, inspired by A2A (these Aircrafts are also installed in my extra folder "P:\MyP3Dv4Addons\A2A") i did the following things:

1. Removed the folder "C:\Users\Ralf\Documents\Prepar3D v4 Add-ons\RealAir\" with the add-on.xml
    
2. Add a further entry (5) in the "C:\ProgramData\Lockheed Martin\Prepar3D v4\add-ons.cfg":

   [Package.4]
   Path=P:\MyP3Dv4Addons\A2A
   Title=A2A P3D Add-Ons
   Active=True
   Required=FALSE

   [Package.5]
   Path=P:\MyP3Dv4Addons\RealAir
   Title=RealAir P3D Add-Ons
   Active=True
   Required=FALSE
    

3. Put the add-on.xml directly into the folder "P:\MyP3Dv4Addons\RealAir\add-on.xml" with this modified entries:
   
   <?xml version="1.0" encoding="utf-8"?>
   <SimBase.Document Type="AddOnXml" version="4,0" id="add-on">
     <AddOn.Name>RealAir</AddOn.Name>
     <AddOn.Description>Aircrafts by RealAir</AddOn.Description>
     <AddOn.Component>
       <Category>Effects</Category>
       <Path>Effects</Path>
       <Type>GLOBAL</Type>
     </AddOn.Component>
     <AddOn.Component>
       <Category>SimObjects</Category>
       <Path>SimObjects\Airplanes</Path>
     </AddOn.Component>
   </SimBase.Document>

Now the Outside-View in ChasePlane works fine with the RealAir Airplanes!

I don't know why Lockheed Martin offers this two different ways to provide add-ons in an extra folder. It's a little confusing...

 

Awesome, glad you got it to work!

Thank you for taking care of this problem.

Many greetings from Germany
Raller