- Messages
- 1,482
- Country
-
Arno,
I came across a repeatable instance whereby ACM will produce its GUI info window every time P3Dv4 starts (have not checked for other platforms). I am not sure if this would be considered an issue so let me explain the situation.
I have an add-on where I have my latest custom autogen default.xml file. When starting P3D it updates and I get the ACM window one time as it should and does not repeat after that. I also have an 2nd add-on with a custom autogen default.xml file almost identical to the first. However, this custom file has a few objects less listed than the first add-on. So it appears ACM is comparing and finding "less" of a match? Because the P3D default.xml file has already been updated previously.
If I use the same custom default.xml on both add-ons #1 and #2 then no ACM message. If I revert one of those add-ons back to the smaller default.xml file the ACM message appears with every P3Dv4 boot.
Here is other food-for-thought, the add-on #2 with the identical but smaller default.xml file is installed but is not activated. Not sure if ACM just checks all add-ons regardless of active status?
My concern is if I were to create a new add-on with more custom agn, this would cause older add-ons to now trigger ACM at each boot. I would have to provide updates to all older add-ons with new ones to get tham all matrched. Your thoughts?
I came across a repeatable instance whereby ACM will produce its GUI info window every time P3Dv4 starts (have not checked for other platforms). I am not sure if this would be considered an issue so let me explain the situation.
I have an add-on where I have my latest custom autogen default.xml file. When starting P3D it updates and I get the ACM window one time as it should and does not repeat after that. I also have an 2nd add-on with a custom autogen default.xml file almost identical to the first. However, this custom file has a few objects less listed than the first add-on. So it appears ACM is comparing and finding "less" of a match? Because the P3D default.xml file has already been updated previously.
If I use the same custom default.xml on both add-ons #1 and #2 then no ACM message. If I revert one of those add-ons back to the smaller default.xml file the ACM message appears with every P3Dv4 boot.
Here is other food-for-thought, the add-on #2 with the identical but smaller default.xml file is installed but is not activated. Not sure if ACM just checks all add-ons regardless of active status?
My concern is if I were to create a new add-on with more custom agn, this would cause older add-ons to now trigger ACM at each boot. I would have to provide updates to all older add-ons with new ones to get tham all matrched. Your thoughts?