For those using the useful Autogen Configuration Merger tool from Arno, it seems that it won´t be needed anymore in P3Dv4.4, as this latest version would come with native support to merge autogen descriptions with the main autogen files.

Does anyone knows what has to be done to make this work (natively) in P3Dv4.4?.

Cheers, Ed

 

Ed, check on the FS developer forums as there are a couple of threads there  on how to do that. There's an autogen.cfg file that must be edited in order to point to other autogen locations.

6 minutes ago, jabloomf1230 said:

Ed, check on the FS developer forums as there are a couple of threads there  on how to do that. There's an autogen.cfg file that must be edited in order to point to other autogen locations.

Thanks Jay, I´ve looked there but only found one thread that to me is mostly unclear on how to do this. I´ll look for the rest of the posts to see if I can get further clarifications.

Are you still using ACM?. In the thread I found at FS Developer forums it says it´s crashing, don´t know if it´s ACM that´s crashing or P3Dv4.4. Not clear enough.

Cheers, Ed

I promised a couple of my scenery users that I'd show a way to change from using the merger tool to the new native method. This is mainly aimed at my customers, but would work with any current developers who use the merger tool. Sorry it's quite rambling, but I wanted people to understand why as well as how....

This is posted on my own site.

It assumes an existing add-on.xml file, but of course you could just create your own with a bit of reading on FSDeveloper.com.

I've been a big supporter of the merger tool, but it is great to see the LM have recognised the need for native support for this! 

Edited December 29, 20187 yr by toprob

8 hours ago, toprob said:

I promised a couple of my scenery users that I'd show a way to change from using the merger tool to the new native method. This is mainly aimed at my customers, but would work with any current developers who use the merger tool. Sorry it's quite rambling, but I wanted people to understand why as well as how....

This is posted on my own site.

It assumes an existing add-on.xml file, but of course you could just create your own with a bit of reading on FSDeveloper.com.

I've been a big supporter of the merger tool, but it is great to see the LM have recognised the need for native support for this! 

Thanks for sharing your expertise. I have many sceneries that use the merger, including yours which are among the best for P3D, and so far I have not had any CTDs or issues.

I'm looking forward to Christchurch! PLEASE make your photo sceneries for NZ available. After seeing what you did with NZDN, I want everything you offer.

10 hours ago, toprob said:

I promised a couple of my scenery users that I'd show a way to change from using the merger tool to the new native method. This is mainly aimed at my customers, but would work with any current developers who use the merger tool. Sorry it's quite rambling, but I wanted people to understand why as well as how....

Hi, many thanks for this tutorial!. Just what I needed to know!.

It´s really impressive the amount of knowledge and quality of information that we AVSIM forum users have available!.

Thanks so much again.

Cheers, Ed

Ed,

I left the detailed answer to someone who has tried the new native autogen method. You might want to subscribe to this thread on FS Developer, though:

https://www.fsdeveloper.com/forum/index.php?threads/ACM-affected-by-P3Dv4.4-update%3F.444265/

1 hour ago, jabloomf1230 said:

Ed,

I left the detailed answer to someone who has tried the new native autogen method. You might want to subscribe to this thread on FS Developer, though:

Got it, thanks, Jay.

Cheers, Ed