• 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 ACM updating AutogenDescriptions.spb despite addon deactivated

Clutch Cargo

Clutch Cargo

Messages
1,588
Country
unitedstates
Arno,

Through my testing of adding new vegetation, I just noticed that ACM is updating the AutogenDescriptions.spb file even if there are no add-on sceneries activated. The only way to prevent this is to delete the add-on from the Scenery Library. I thought this was addressed? I d/l the latest version just a few moments ago to confirm I have the latest version. The file AutogenConfigurationMerger.exe is dated 1/10/2019.
 
Let me check the source code. Do you add the scenery via the scenery.cfg or an add-on.xml file?
 
This was tested with the Scenery.cfg. I will test with the add-on.xml method.

Update Arno - Yes, using the add-on.xml method will also update the AutogenDescriptions.spb file even if the add-on is deactivated. So both methods have the issue.
 
Last edited:
OK, I'll check the code.
 
The check is not there indeed, I'll add it. For the scenery.cfg that is easy, for the add-on.xml I can't find any command to disable them.
 
Oh, that's interesting. If you cannot find a command for it I am not sure what impact this may have on a released add-on? I discovered it when I was testing/making slight changes to my custom autogen files and noticed I was losing all vegetation due to a clash with a deactivated scenery.
 
I am not sure how a clash with a deactivated scenery can give issues. Or was it a deactivated version of your own scenery?

How did you deactivate the add-on.xml based scenery btw, I think that can only be done by moving or renaming the xml file.
 
This was tested in P3Dv4.5. I have two add-ons I created. Call them addon1 and addon2. They are both installed via the Scenery Library (scenery.cfg) method. Both have the same custom autogendescriptions.xml files in their own autogen folder ready for use in ACM. I deactivated (unchecked) addon1 and I made edits edits on addon2's autogendescription.xml file for testing.

If I run P3D ACM reads both addon1 and addon2 files even if addon1 is deactivated. Now for the "clash", I cannot give an exact account and I was trying several xml edits. The result when in P3D was not vegetation at all. If I remove (delete), addon1 from the Scenery Library and run P3D again the vegetation appears again.

Of course my xml edits as I test are causing the "clash" (probably a better term since crash may be mistaken as P3D crashing which is not the case). But I would have to remove all my addon sceneries each time I test new xml scripts. I should only have to deactivate them.

With the add-on.xml in the P3D addon screen (window) you have the option to check/uncheck to make it active or not. I simply unchecked it and made sure there were no other sceneries using ACM. When I ran a fresh test ACM was still updating based on that one deactivated addon.xml scenery.

Hope that clarifies
 
For the scenery.cfg method I have changed the code now. I will get a new release out when I'm clear on the add-on.xml issue as well.
 
OK, I have found it where the active state of the add-on.xml sceneries is stored. That is in the file add-ons.cfg in the folder C:\ProgramData\Lockheed Martin\Prepar3D v4. So I'll have to modify ACM to also read that folder to check if an addon is active or not.
 
Hi,

Here is a new beta build that should read the add-ons.cfg file correctly. Can you check if it works for you?
 
I will try to check it out tonight when I get home from work. Maybe we can use my script as an example. I would need to clean it up and make it more generic like a template. That may save you some time and I would think it would help fellow developers who go through this for the first time.
 
If I can use your file as example that would be fine. I can make it more generic by changing names, etc.
 
Arno, after testing both methods I can say the new ACM version is working as expected now. I have also attached a sample of a custom AutogenDescription that I think you can use/adapt for the manual. Thanks for all your help on rectifying this.
 

Attachments

  • AutogenDescriptionsSAMPLE.zip
    647 bytes · Views: 314
Thanks for the feedback, I'll try to make an official release soon. And try to add a sample to the manual.
 
I have removed the beta build here, since I have uploaded it as official release now.

You don't have to download it again, I only changed the manual, the EXE has not changed.
 
You must log in or register to reply here.
Back
Top