• 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?

Another piece of information:
1. Due to the Paris City Scenery from FranceVFR being really a frame killer, I have disabled that scenery from the Scenery.CFG (is still installed the old fashion way), but the Autogen folder remains in the same location together with the respective Scenery and Texture folders of the FranceVFR scenery (which is disabled). Don't really know if for ACM it would be necessary the local scenery to be enabled or it has nothing to do with it.
2. I also have several FlyTampa sceneries that use the same autogen definitions of the FranceVFR scenery, and those definitions are only in the single local Autogen folder mentioned before under the Paris City Scenery from FranceVFR.
I hope this is clear and will not create any confusion.
Thanks again for your top-notch support.
Cheers, Ed
 
Hi Ed,

I do see those Orbx sceneries, but ACM did not find any autogen configuration files there to merge. It's only in two other sceneries that custom autogen definitions are found that are being merged.

But I understand your workflow now. Let me see how I can debug this. I don't have the Orbx or France VFR sceneries here to test with.
 
I do see those Orbx sceneries, but ACM did not find any autogen configuration files there to merge. It's only in two other sceneries that custom autogen definitions are found that are being merged.

Ok, clear. That's probably the way the ORBX's stuff works. None of the ORBX sceneries contain an Autogen with specific definitions inside. As I mentioned before, they (ORBX) work by replacing the main P3D autogen default definitions at every running of their FTX Central (as far as I know).
Please remember that I didn't notice any issues with merges while I was using ACM v1.1.xxx and the same FranceVFR/FlyTampa sceneries.
Cheers, Ed
 
Yes, so it must be something related to the changes I made for Marcus, but also related to the way that France VFR made their custom definitions that are being merged.
 
FYI - When we were testing we also tested as:

1. Installed Orbx Global
2. Installed 3rd-party add-on (in this case it was our scenery)
3. ACM updated
4. No Missing Orbx autogen

I'll check to see if any of our testers have France VFR.

Arno, when you have something to test, post it, and we will test again.
 
FYI - When we were testing we also tested as:

1. Installed Orbx Global
2. Installed 3rd-party add-on (in this case it was our scenery)
3. ACM updated
4. No Missing Orbx autogen

I'll check to see if any of our testers have France VFR.

Arno, when you have something to test, post it, and we will test again.

In my opinion something happened from ACM's version v1.1.xxx to v1.2.xxx. As I posted before, I did not notice any issue when I had v1.1.xxx installed.
Thanks for your support.
If Arno and yourself need to test something please let me know and I can test.
Cheers, Ed
 
Ed,

Could you privately send me the Orbx and France VFR files you are merging? Then I can test here what the difference is between the ACM versions for these files. Hopefully that helps to find the problem.
 
Hi Arno:
Of course I can. I supose you're talking about the autogen files for each of them, right?. Please confirm and I'll give you a link over my dropbox account.
Thanks, Ed
 
Please also don't forget that the autogen descriptions for FranceVFR are similar to those used by FlyTampa, just in case any of your beta testers have a FT product.
Cheers, Ed
 
Ed,

Yes, I meant the configuration files of the two addons. Then I can try the merge here with the different versions of ACM.
 
I was a little surprised you posted it here already. Got the files and removed the post now. Will try to see what is going on.
 
I was a little surprised you posted it here already. Got the files and removed the post now. Will try to see what is going on.

Sorry for that, Arno. Thanks for deleting the post. Hope the files could help.
Cheers, Ed
 
My testers have so far come up with no issues. We have been testing with Orbx Global, UT, GEX. No one on the team has France VFR. Ed, you said FlyTampa was similar. Can you name a particular airport? Maybe we have one of those?
 
My testers have so far come up with no issues. We have been testing with Orbx Global, UT, GEX. No one on the team has France VFR. Ed, you said FlyTampa was similar. Can you name a particular airport? Maybe we have one of those?

Amsterdam Schiphol, Saint Maarten.

Cheers, Ed
 
Hi Arno/Marcus:
Good afternoon/evening (your time?). Just want to follow-up with you if you had the opportunity test ACM with the set of autogen files I've sent some days ago?. Have you found any issues?.
Thanks, Ed
 
As mentioned, so far we have not seen the issues yet does not mean it is not there. No testers had France VFR scenery so I am checking if they have any FlyTampa as you said it has the same issue.

Let me ask Ed, you were seeing this with P3Dv4.4? Also, do you have any add-on scenery for P3Dv4.4 that uses the add-on.xml activation method?
 
As mentioned, so far we have not seen the issues yet does not mean it is not there. No testers had France VFR scenery so I am checking if they have any FlyTampa as you said it has the same issue.

Let me ask Ed, you were seeing this with P3Dv4.4? Also, do you have any add-on scenery for P3Dv4.4 that uses the add-on.xml activation method?

Ok, Marcus. Thanks.
I'm seeing this with P3Dv4.3. I have a bunch of scenery in P3Dv4.3 that uses the add-on.xml method (either installed automatically by their respective installers or by myself by moving them to my scenery addon folder, outside the P3D root). But this have been always my case, when ACM was indeed functioning properly.
I'm moving to P3Dv4.4 probably tomorrow. I need to find some free time for that.
Probably you know, but I've sent to Arno some files from my add-on autogen folder that was the one to be merged with the main autogen folder in the P3D root (for testing). Please verify if you have them.
Anyway, FranceVFR has available in its website a file named Autogen Global X that you can freely download. It contains the autogen definitions for FranceVFR products, that area the same used by FlyTampa, 29Palms and others (all they are mentioned inthe download page). Hope this information could be useful.
Thanks again, Ed
 
Got it. P3Dv4.3. I don't suspect any difference actually with regards to the agn... we haven't seen any. I will take a look at that for France VFR. Arno I'm sure is plugging away at debuggin.
 
I haven't started testing yet, was busy with some other things. Hopefully later today.
 
Back
Top