• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

P3D v4 No Autogen using ACM

Messages
152
Country
france
Hello all,

Having installed AGX 64 from France VFR (I am a strong user of FVFR sceneries) and willing to also keep P3D definitions I tested ACM in its last release.

Here is what I did: I maintained the original Autogen definitions in the P3D V4.1 Autogen folder and put AGX 64 definitions in an autogen folder in a scenery as required (I think this is the correct procedure)

ACM did work, recognized the two different Autogen folders (my log file is attached) and did the merging job.

However after the above I restarted P3D but I have completely lost the FVFR Autogen above France (not a single tree or building).

I reinstalled FVFR Autogen definitions in the P3D Autogen folder and I then recovered all the autogen as normal. I had that issue in the recent pas using a developmental version of ACM so I thought the issue was gone but - at least for me - it is not solved.

Can someone tell me if I did something wrong here ?

Thanks a lot for the help

Philippe
 

Attachments

  • AutogenConfigurationMerger.txt
    25.7 KB · Views: 546

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,859
Country
netherlands
In which scenery folder did you put the AGX autogen files? Because I'm not sure I see them in the log.

However it is not advised to consider a complex set as the AGX autogen files as the input for the merge. Because the merging will also try to insert the definition at the right order within the default ones. If the definitions to be merged already include the default ones as well that becomes tricky. So it is best to have in a scenery only the new definitions used by that scenery.

That's also way I think an initiative like AGX to combine definitions from various developers in one set is not a good idea. It makes it even harder to maintain the autogen definitions.
 
Messages
152
Country
france
I Arno

The AGX autogen files ahave been put in the following folder as identified by ACM :)Found config: f:\prepar3d addon\addon scenery\occitania_vfr\autogen\Materials.spb is the first line)

So in your mind it is not recommended to try to merge the original P3D autogen definitions set and the FVFR AGX one ?
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,859
Country
netherlands
No, I would not try so. Why you think the default ones are not part of AGX?
 
Messages
152
Country
france
ok understood. Regarding your question I never found a clear assessment that the default ones were part of AGX.
 
Messages
118
Country
france
Hello, I'm almost sure that default P3D definitions are part of AGX. I'm using AGX and FVFR scenery since many years and never had to merge autogen definitions, whatever the FSX or P3D version.
 
Messages
203
Country
unitedkingdom
Merging AGX definitions and those distributed by Orbx (which contain legacy definitions from Earth Simulations for example) is a very common requirement I see on forums....
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,859
Country
netherlands
I understand the need to merge them, I'm just saying that merging two complete definitions, that each contain sets from many developers is hard and more likely to give conflicts and issues.
 
Messages
41
Country
unitedstates
I understand the need to merge them, I'm just saying that merging two complete definitions, that each contain sets from many developers is hard and more likely to give conflicts and issues.
Do you recommend not using your program with Orbx? I have no autogen if Orbx and other scenery autogen entries are merged.
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,859
Country
netherlands
I know people are using ACM with the Orbx definitions successfully, but I would not advice to try to put the Orbx definitions in an autogen folder with the scenery and let ACM merge them into the global definitions. That works best with sceneries that have been prepared for ACM.
 
Messages
41
Country
unitedstates
Orbx edit the main Autogen files when I run the FTX Central program. The problem of missing autogen starts when the ACM detects Orbx changed the autogen files and attempts to add the Autogen entries from some other scenery.
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,859
Country
netherlands
And those other sceneries have been prepared for ACM by the developer?
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
32,859
Country
netherlands
And which other sceneries you have with a local autogen folder? Do they contain default definitions or only their local ones?
 
Messages
41
Country
unitedstates
The default.xml in one scenery (SBGR2017)

<?xml version="1.0" encoding="utf-8"?>
<AUTOGEN>
<REGION>
<CODE>D</CODE>
<CLASS>
<NAME>tsim3dyellowlight</NAME>
<GUID>9532982a47c8a6fbd75853a2e282f851</GUID>
<WIDTH>3</WIDTH>
<DEPTH>3</DEPTH>
<LIBRARYOBJECT>
<NAME>tsim3dyellowlight</NAME>
<GUID>9f692eaa49c1b4c9583dad8219e1271e</GUID>
</LIBRARYOBJECT>
</CLASS>
</REGION>
</AUTOGEN>
 
Top