• 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 affected by P3Dv4.4 update?

Messages
1,533
Country
unitedstates
Having a beta-tester crashing with my installer (which includes ACM install), when trying to install for P3Dv4.4. I would not think that LM would change anything that much with regards to a point update but I just thought I would ask as I explore the issue. Also, Arno, is the version of ACM we tested (placing edits at the bottom), now a released version or not?

Thx
 
Hi,

I have not heard of differences or problems with P3D v4.4 yet, but I also have not been able to test it myself yet.

No, I did not upload the new release yet. I was still waiting for your last feedback. You did not encounter any issues?
 
We are just starting to release to the beta team. One tester installed OK into FSX:SE but the install is crashing with P3Dv4.4. Not saying ACM is the issue here but that's why I posted just to ask about any issues discovered. I'll give more feedback as I get more testers online with it.
 
OK, let me know if there are issues and else I should release this new version publicly in a few days.
 
As I understand it, P3D v4.4 now allows multiple autogen definition files, and it layers those so that one scenery's AG doesn't make global changes that affect others.

see Beau Hollis' remarks in the second post here: https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=131849

Not sure of the exact mechanism in use...I think the scenery-specific autogen is intended to be added as a new component in the add-on.xml

So the question I have--is ACM now redundant?

Regards

Bob Scott
 
Last edited:
I hope so, this is a functionality that should be part of the sim. But I haven't checked if it's implemented right in v4. 4 yet.
 
I can confirm that ACM is no longer required for P3D as of v4.4.
Simply placing an add-on component in your add-on.xml which points to the path where your Autogen files are located will allow P3D to merge them with the default autogen files.


Example:
Code:
<SimBase.Document Type="AddOnXml" version="4,0" id="add-on">
    <AddOn.Name>RS Common Files</AddOn.Name>
    <AddOn.Description>Files Common to all Richer Simulations Products. DO NOT EDIT OR REMOVE!</AddOn.Description>
 
    <AddOn.Component>
        <Category>Autogen</Category>
        <Path>RS Common\Autogen</Path>
    </AddOn.Component>
</SimBase.Document>
 
Last edited:
Very good! Much better to have native support for this.
 
Ah, yes, I had tried to get this working all day, without any success, and concluded that it didn't work. Then I realised I'd fallen for the oldest new trick in the book, forgetting to add the '_Legacy' to my filename...
This will certainly fix the issue with having to reload to see new autogen.
 
So this will work with each type of file found in the FS's root autogen folder? Your code example shows no headers or footers... not needed? Can you provide a few examples of filenames with the '_Legacy' added?

Thanks,
 
The '_Legacy' only applies to autogendescriptions, which is the vegetation types and classes. With P3Dv4, autogendescriptions.spb/xml if for the dynamic vegetation (SpeedTrees) and autogendesciptions_legacy.spb/xml is the older, legacy stuff. I tend not to use speedtrees, I prefer a mix of Orbx and my own trees.
ACMT knows to merge to both, from the one file. So for use with ACMT I only needed one autogendescriptions.xml file, but with native P3Dv4.4 support, you will need both if you want to serve those with and without speedtrees.
 
So this will work with each type of file found in the FS's root autogen folder? Your code example shows no headers or footers... not needed? Can you provide a few examples of filenames with the '_Legacy' added?

Thanks,
I have edited the code above to include headers and footers.
 
Hi Arno:
Could you please confirm is your latest release of ACM is working well with P3Dv4.4?.
I´ve just read, per the posts above, that ACM would not be needed anymore as P3Dv4.4 offers native support for autogen merging. I don´t exactly know how that would work (the native support), so I´m updating now to P3Dv4.4 from v4.3 and would like to continue using your ACM for now.
Please let me know. Thanks,
Cheers, Ed
 
Hi,
Just a question, this merge function can realized his job with autogen files provided by OrbX and France-VFR?
My question is based on the fact that OrbX autogen contains already some old GUID of France-VFR.

My thought was what this function of P3D can operate if and only if the two autogen files are completly different without common GUIDs.
I am right or no ?
 
Hi Arno:
Could you please confirm is your latest release of ACM is working well with P3Dv4.4?.
I´ve just read, per the posts above, that ACM would not be needed anymore as P3Dv4.4 offers native support for autogen merging. I don´t exactly know how that would work (the native support), so I´m updating now to P3Dv4.4 from v4.3 and would like to continue using your ACM for now.
Please let me know. Thanks,
Cheers, Ed

I haven't heard of problems, so it should work. I don't have P3Dv4.4 installed myself yet.
 
Hi,
Just a question, this merge function can realized his job with autogen files provided by OrbX and France-VFR?
My question is based on the fact that OrbX autogen contains already some old GUID of France-VFR.

My thought was what this function of P3D can operate if and only if the two autogen files are completly different without common GUIDs.
I am right or no ?

I don't know how LM implemented it. But now that the aim can merge for you, there is no need anymore for a developer to include anything else than his own definitions. It was a very bad practice to include definitions from different developers anyway.
 
We are about to test with Arno's latest un-released ACM version with several users who use P3Dv4.4 so I will post here when we feel confident in our findings.
 
Arno, so there is no way currently that ACM can detect whether a User has P3Dv4.3 or P3Dv4.4 installed correct? I may be back peddling a little here but if ACM already uses addon.xml for v4 is it just installing it the initial first time but does not check after each reboot of P3D?
 
During running it can determine the version by checking the version attribute of the P3D exe file. But just from the registry you can't see the difference.

What do you mean with installing it the initial first time? ACM is only installed during install mode. And afterwards it will run each time P3D is started.
 
We are about to test with Arno's latest un-released ACM version with several users who use P3Dv4.4 so I will post here when we feel confident in our findings.

Hi Clutch: is this still underway?. Could you pls update about your findings?.
Thanks, Ed
 
Back
Top