34 minutes ago, Akila said:

i would love to have such tool and even willing to pay for such (payware).

A tool that knows about all issues that can arise is bascially impossible to make. That is what the simulators' content error log is for, turn it on and see what transpires.

An estimate: to cover even the most common and some exotic errors would be an effort of maybe 200 hours. My hourly rate as a developer is 100€. From experience, sales figures for such a tool will be around 1500€ per year. It would take solid sales for 14 years to even recover the development cost.

Best regards

6 minutes ago, Akila said:

so if i add manually (additional entry) a reference to an XML (add-on.xml is located outside the default P3D autodiscover folder, e.g. "d:\P3D_Addons\xxx") in the add-on.cfg at APPDATA, is there a risk of it being deleted/removed by the autodiscover process?

This is not a "risk", it will definitely happen. P3D will remove all entries that it cannot find in \Documents\Prepar3D V4 Addons\.

If you want your entry to be persisted, it must be added to the add-ons.cfg in ProgramData. But you don't do this manually, you use the P3D command line tools for that. Learning Center -> SDK -> Add-ons -> Add-on Configuration Files

An advice: stay away from the config files (all of them), don't ever edit them manually.

Best regards

Hey Oliver,

 

Thanks for going that extra mile.

 

Cheers,