Underwhelming compared to OrbX preview threads.

It looks like we could have ORBX's version this weekend.

I wonder if this add-on will fix the flying buildings bug or exacerbate it.

2 minutes ago, DJJose said:

It looks like we could have ORBX's version this weekend.

I wonder if this add-on will fix the flying buildings bug or exacerbate it.

Neither.
It's a texture replacement only for the vast majority of models.
 

Just now, F737NG said:

Neither.
It's a texture replacement only for the vast majority of models.
 

Covers regions too. I'm hopeful. 😀

Почувствуйте разницу ))

Edited June 29, 20196 yr by BMW969

The developer does not know where default simulator is installed.

 

 

 

Edited June 29, 20196 yr by BMW969

1 hour ago, BMW969 said:

The developer does not know where default simulator is installed

The product shouldn't overwrite the existing P3D texture files in the first place. You can keep a texture addon separate from the sim, as an addon package (= linked by add-on.xml). This method will replace the textures without overwriting any files, and you can turn the product on or off with a mouse click in P3D Tools->Add-ons.

Best regards

11 hours ago, edpatino said:

Could you kindly comment on performance impact, if any?.

Anticipated thanks, Ed

On my PC I don't have any performance issue, the only big  issue that I have is that the textures are flickering and I had to revert to the default ones.

I adjusted the AA and didn't help, so not being able to fix this issue....................................

11 minutes ago, Lorby_SI said:

The product shouldn't overwrite the existing P3D texture files in the first place. You can keep a texture addon separate from the sim, as an addon package (= linked by add-on.xml). This method will replace the textures without overwriting any files, and you can turn the product on or off with a mouse click in P3D Tools->Add-ons.

Best regards

It's a good news. Only in the documentation it is not specified

Is it possible to learn more about  P3D Tools ?

Edited June 29, 20196 yr by BMW969

1 minute ago, Reader said:

Orbx HD Buildings:

It includes a complete overhaul of the autogen.bgl object library - Over 400 new building models for water towers, farm buildings, religious structures, and more.

That's great. How many of those appear as a percentage of your much more typical houses, apartment blocks, office blocks and factories?

The biggest impact is going to come from the building structures that I've just listed.
These are only going to have texture replacements and as I said in my earlier post are "for the vast majority of models".

1 hour ago, BMW969 said:

It's a good news. Only in the documentation it is not specified

P3D main folder -> Learning Center.chm -> SDK -> Add-ons

To do it manually, you would

1. Install the product in a folder of your choice instead of the P3D core folder, let's say F:\RDAutogenTextures
2. (I would have to take a look at the result now, but just assuming that it only replaces texture files you would do the following:)
3. Now create an autodiscovery folder for P3D: \Documents\Prepar3D v4 Add-ons\RDAutogenTextures
4. Then create an add-on.xml file in that folder (\Documents\Prepar3D v4 Add-ons\RDAutogenTextures\add-on.xml) that looks like this :

<?xml version="1.0" encoding="utf-8"?>
<SimBase.Document Type="AddOnXml" version="4,0" id="add-on">
  <AddOn.Name>RD_Autogen_Textures</AddOn.Name>
  <AddOn.Description />
  <AddOn.Component>
    <Category>Texture</Category>
    <Path>F:\RDAutogenTextures\Texture</Path>
    <Name>RD_Autogen_Textures</Name>
  </AddOn.Component>
</SimBase.Document>

Make sure that this file is encoded in UTF-8 (either user Notepad++ or, when using Windows Notepad, make sure to select Encoding UTF-8 on the "Save As" dialog).

Or you could use my P4AO tool for this purpose, that should make things easier.

Best regards

Edited June 29, 20196 yr by Lorby_SI

2 hours ago, Lorby_SI said:

The product shouldn't overwrite the existing P3D texture files in the first place. You can keep a texture addon separate from the sim, as an addon package (= linked by add-on.xml). This method will replace the textures without overwriting any files, and you can turn the product on or off with a mouse click in P3D Tools->Add-ons.

Best regards

Very good point, Oliver.

Cheers, ED

11 minutes ago, Lorby_SI said:

P3D main folder -> Learning Center.chm -> SDK -> Add-ons

To do it manually, you would

1. Install the product in a folder of your choice instead of the P3D core folder, let's say F:\RDAutogenTextures
2. (I would have to take a look at the result now, but just assuming that it only replaces texture files you would do the following:)
3. Now create an autodiscovery folder for P3D: \Documents\Prepar3D v4 Add-ons\RDAutogenTextures
4. Then create an add-on.xml file in that folder (\Documents\Prepar3D v4 Add-ons\RDAutogenTextures\add-on.xml) that looks like this :

<?xml version="1.0" encoding="utf-8"?>
<SimBase.Document Type="AddOnXml" version="4,0" id="add-on">
  <AddOn.Name>RD_Autogen_Textures</AddOn.Name>
  <AddOn.Description />
  <AddOn.Component.Disabled>
    <Category>Texture</Category>
    <Path>F:\RDAutogenTextures\Texture</Path>
    <Name>RD_Autogen_Textures</Name>
  </AddOn.Component.Disabled>
</SimBase.Document>

Make sure that this file is encoded in UTF-8 (either user Notepad++ or, when using Windows Notepad, make sure to select Encoding UTF-8 on the "Save As" dialog).

Or you could use my P4AO tool for this purpose, that should make things easier.

Best regards

Sounds like the correct way to do it, but I think that you could end up with two sets of textures installed in your simulator, the original P3D ones AND the RDAutogen new HD textures, and that could explain why some users are experimenting flickering in their setups.

By all means I think the original P3D textures will have to be replaced. The issue is that they should be able to be recovered back if you find the HD replacement textures are not of your liking, or have certain performance impact.

Cheers, Ed

8 minutes ago, edpatino said:

Sounds like the correct way to do it, but I think that you could end up with two sets of textures installed in your simulator, the original P3D ones AND the RDAutogen new HD textures, and that could explain why some users are experimenting flickering in their setups.

By all means I think the original P3D textures will have to be replaced. The issue is that they should be able to be recovered back if you find the HD replacement textures are not of your liking, or have certain performance impact.

Cheers, Ed

Hello Ed,

I copied an error into the XML in my initial post, please edit your quote!

As for the general principle, I'm afraid that your assessment is incorrect. If there are files on the discovery paths that have the same names, P3D will only use the one that is loaded last in the discovery chain. Internal files are always discovered first, so every addon package that you apply will replace them. At least that is what the spec says. And this is true for every type of content - you are not supposed to overwrite anything in the core simulator folders anymore - that is the whole point of these packages...

I have successfully applied this to Rex textures and world airports too.

Best regards

Edited June 29, 20196 yr by Lorby_SI

11 minutes ago, Lorby_SI said:

As for the general principle, I'm afraid that your assessment is incorrect. If there are files on the discovery paths that have the same names, P3D will only use the one that is loaded last in the discovery chain. Internal files are always discovered first, so every addon package that you apply will replace them. At least that is what the spec says. And this is true for every type of content - you are not supposed to overwrite anything in the core simulator folders anymore - that is the whole point of these packages...

Ah, Ok. Thanks for the information!, it really makes sense.

Cheers, Ed