P3D v4 No Autogen using ACM

#1
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

arno

Administrator
Staff member
FSDevConf team
Resource contributor
#2
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.
 
#3
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
#4
No, I would not try so. Why you think the default ones are not part of AGX?
 
#6
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.
 
#8
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
#9
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.
 
#10
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
#11
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.
 
#12
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
#13
And those other sceneries have been prepared for ACM by the developer?
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
#15
And which other sceneries you have with a local autogen folder? Do they contain default definitions or only their local ones?
 
#16
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