kevinfirth

Autogen Configuration Merge by Arno Gerretson

Recommended Posts

LM have confirmed that v4, as previously, does NOT merge different specified autogen files.

However, Arno has said he will be updating ACM to support P3D4.

If you havent heard about ACM but have suffered from problems with missing autogen, conflicting sceneries or commercial developers having semi public spats about who should control autogen definitions (think OrbX, FranceVFR and Earth Simulations) then ACM can help..

It is IMHO one of the most useful yet least known addons ever, and its free...who else here has used it?

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Right up there with Pete Dawson and Tom Allensworth. Our hobby would be no where without these three

Share this post


Link to post

I know Arno for about 15 years and he is a Flightsim hero.

 

Share this post


Link to post

Kevin,

I assume that the modified version should be capable of sorting out any autogen compatibility issues between P3D v4 and the Earth Simulations scenery packages? For example, are the ES TreeScapes packs currently working in P3D v4?

Share this post


Link to post

 

11 minutes ago, Christopher Low said:

Kevin,

I assume that the modified version should be capable of sorting out any autogen compatibility issues between P3D v4 and the Earth Simulations scenery packages? For example, are the ES TreeScapes packs currently working in P3D v4?

Treescapes already works flawlessly as far as I've tested.

I just added scenery layers pointing to the same folders used in v3 and it seems to work, certainly for vols 1-3 which is what I've tested so far.

ACM is only necessary for merging additional autogen definitions.

Share this post


Link to post

FranceVFR has updated their Autogen Global X :

http://www.francevfr.com/agx_EN.htm

 

Several scenery developers have their own Autogen / descriptions entries and one can cause issues ( not seeing autogen objects ) at the other. The developers below now use 1 merged version. Their is now a P3D4 version.

This is not compatible with several Orbx scenery...

 

CONTRIBUTORS

  • French unified Freeware - Autogen available on F-BMPL (Gropied, Vogel, DomSimu, GPF, Filipo)
  • Occitania - from revision 7.0
  • LLH Créations
  • Flugwerk Design - Austria Pro HD
  • 29Palms - MykonosX
  • 29Palms - SkiathosX
  • Flylogic
  • FS Addon
  • Fly Tampa  
  • Simulation Data 
  • France VFR 
  • 3D Automation 
  • AutogenFactory 

 

Share this post


Link to post
16 minutes ago, GSalden said:

This is not compatible with several Orbx scenery...

Great. That's why I stay away form France VFR. 

FlyTampa - at least those I own - work with ORBX, LLH as well.

Kind regards, Michael

Share this post


Link to post
33 minutes ago, pmb said:

Great. That's why I stay away form France VFR. 

FlyTampa - at least those I own - work with ORBX, LLH as well.

Kind regards, Michael

As I use FTX Global and HD Trees only I can use this . Specific Orbx regions are not compatible.

But using Orbx regions can cause other developers scenery not to show up their textures...

 

Share this post


Link to post
1 hour ago, pmb said:

Great. That's why I stay away form France VFR. 

FlyTampa - at least those I own - work with ORBX, LLH as well.

Kind regards, Michael

No this is why we need ACM :)

Although it is a shame our devs cant play nicely together regarding sharing autogen definitions, instead of acting like spoiled primary school children.. *sigh*

  • Upvote 1

Share this post


Link to post

I thought Orbx stopping overriding other developers autogen these days but that is still not the case?  Also, I was under the impression ACM was for developers, not end-users?  I am not aware of how a simmer would apply ACM on their own?

Share this post


Link to post
2 minutes ago, Clutch Cargo said:

I thought Orbx stopping overriding other developers autogen these days but that is still not the case?  Also, I was under the impression ACM was for developers, not end-users?  I am not aware of how a simmer would apply ACM on their own?

just install using command prompt, as in the developers manual, then add 'autogen' folders with scenery and texture folders :)

Share this post


Link to post
On 21.6.2017 at 5:07 PM, kevinfirth said:

just install using command prompt, as in the developers manual, then add 'autogen' folders with scenery and texture folders :)

Sorry for waking up this old thread.

 

I have dozens of Orbx Scenery and lately installed Austria Professional HD and a France VFR scenery.

As far as I can see all of these kill the other's autogen descriptions so it is not possible to run them together.

 

Can the Autogen Configuration Merger help with this situation and make it possible to have all these sceneries work together without having to swap the autogen folder again and again?

And if it can, which files / folders exactly do I need to put where?

The manual provided by the ACM is quite sparse.

Thanks for your help.

Share this post


Link to post
1 hour ago, RALF9636 said:

Can the Autogen Configuration Merger help with this situation and make it possible to have all these sceneries work together without having to swap the autogen folder again and again?

Supposedly yes

1 hour ago, RALF9636 said:

And if it can, which files / folders exactly do I need to put where?

It is described in the ACM manual.  You need an additional Autogen folder alongside the traditional scenery and texture folders relating to any scenery you wish ACM to merge autogen for.  Any autogen description files containing custom autogen for that scenery go in that folder,

Share this post


Link to post

Thanks for your reply.

I read the manual but I don't understand it.

As far as I can see Orbx and the others are just changing the default autogen description files. How do I find which entries I should put in that new Autogen folder I need to create?

Or do I just copy the whole Autogen folder files (from the main P3D folder) into that new specific autogen folder? And do that again after I install any new scenery?

Please excuse my ignorance. ;-)

Share this post


Link to post
6 minutes ago, RALF9636 said:

As far as I can see Orbx and the others are just changing the default autogen description files

There are several relevant autogen description files.  The main ones are:

default.xml - Contains the name and GUIDs of all library objects used as autogen

RoofDescriptions.spb - Contains the names and GUIDs of all roof models used for autogen

AutogenDescriptions.spb - Contains the names and GUIDs of all vegetation models used for autogen

Orbx distribute a set of files with their sceneries that include some but not all of other scenery developers custom autogen descriptions.  The ones they don't include will obviously not show in the sim because they aren't known to it as they aren't in the files.  Same for FVFR etc...  

 

15 minutes ago, RALF9636 said:

Or do I just copy the whole Autogen folder files (from the main P3D folder) into that new specific autogen folder?

Only the ones where the time/date stamp shows it has changed

 

16 minutes ago, RALF9636 said:

And do that again after I install any new scenery?

Yes

 

I would suggest that a workable solution could be as follows for example, for example with an Orbx and FVFR scenery.

1. Install one of the sceneries

2. Create an Autogen folder alongside the Scenery and Texture folders for that scenery

3. Copy the 3 files above from C:\Prepar3D v4\Autogen to the Autogen folder you created in (2)

4. Install the second scenery

5. Install ACM using the command prompt (described in the developers manual)

6. Fly...

The second installation should overwrite the first scenery's autogen descriptions.  However, you've copied them to the new Autogen folder you made so they aren't lost.  When you start the sim after installing ACM, ACM should merge those 2 sets of files and the sim will use the merged ones, theoretically allowing you to use both sceneries fully as intended with each other, as opposed to having to make a choice between one of the other.

Hope that made sense :)

 

Share this post


Link to post

Thanks a lot for that explanation. Now it makes sense to me.

 

But - in your example if I first install an Orbx scenery and then an FVFR scenery - don't I have to do the steps 1-3 again also for the FVFR scenery to be safe?

If I don't do it I will loose the FVFR autogen again as soon as I open Orbx's FTX Central the next time, because it will overwrite the files again with its own. Or is there still something I am missing?

Share this post


Link to post
14 minutes ago, RALF9636 said:

But - in your example if I first install an Orbx scenery and then an FVFR scenery - don't I have to do the steps 1-3 again also for the FVFR scenery to be safe?

If I don't do it I will loose the FVFR autogen again as soon as I open Orbx's FTX Central the next time, because it will overwrite the files again with its own. Or is there still something I am missing?

I thought ACM would just reinsert the missing entries (and ask you to restart the simulator)? 

Kind regards, Michael

Share this post


Link to post
1 minute ago, pmb said:

I thought ACM would just reinsert the missing entries (and ask you to restart the simulator)? 

Kind regards, Michael

But ACM could only do that if I create a specific autogen folder in both the Orbx and the FVFR folder (?)

And btw do I have to do that with every Orbx scenery?

Share this post


Link to post
17 minutes ago, RALF9636 said:

But ACM could only do that if I create a specific autogen folder in both the Orbx and the FVFR folder (?)

And btw do I have to do that with every Orbx scenery?

To be honest: I was hesitant to do that myself so far for France VFR. However, I have been using ACM with some other sceneries (e.g. Godzone) already.

I don't think it is required to make autogen folders for the ORBX sceneries as FTXC 3 inserts the entries every time it is called. However, the France VFR entries are overwritten this way. ACM leaves the ORBX entries in their place but adds the France FVR entries which it finds in the named autogen folder (besides scenery and texture).

At least that's my understanding, I would be grateful if Kevin could confirm (or falsify) this.

Kind regards, Michael

Share this post


Link to post

AFAIK the only dev that has a utility that continually overwrites autogen files is Orbx, so it would probably be best to put any other custom autogen files in Autogen folders and let FTX central overwrite the sim files with the orbx ones.

If you do that you dont need to create any autogen folders for any Orbx scenery.

ACM reads and merges the autogen files at run time, every time, so you wont need to go through the whole process every time :)

  • Upvote 1

Share this post


Link to post
2 hours ago, RALF9636 said:

ut - in your example if I first install an Orbx scenery and then an FVFR scenery - don't I have to do the steps 1-3 again also for the FVFR scenery to be safe?

No.  You only need one set of files for each scenery with custom autogen.  In our example the P3D autogen folder is the one holding the Orbx ones.

Arno has coded ACM to filter out duplicate entries in files, but it is recommended for devs using ACM to only include THEIR custom autogen in additional files, not duplicate other devs stuff.  If you wanted to be purist about it you could download spb2xml, convert the autogen spb files to xml then edit out any duplicate entries in files so you didnt rely on ACM doing it for you, but I suspect most people wouldnt be up for that!

Share this post


Link to post
17 minutes ago, kevinfirth said:

AFAIK the only dev that has a utility that continually overwrites autogen files is Orbx, so it would probably be best to put any other custom autogen files in Autogen folders and let FTX central overwrite the sim files with the orbx ones.

But doesn't the France VFR's "Autogen Global" Tool the same, just in the opposite direection? They may not overwrite autogen entries of those associated (29Palms etc.) but those form ORBX - or not?

Kind regards, Michael

Share this post


Link to post

I thought the autogen category in the addon xml method dealt with the issue, does it not work by merging autogen definitions?

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now