ig_config.xml out of data folder not working

[Lales.Charles]

Hi,

I do have an issue trying a simple task: starting the app (2.16.1 based) with args specifying ig_config.xml path out of data folder..
Typically I try to use it from C:\Users\<user>\AppData\Roaming\<tool>\tmp\ig_config.xml
It is simply ignored, with complain "can't load.."
It is working fine if we put the file in data folder, or sub folder, accessing by relative or absolute path, but anywhere above or out of data.. not working.

Would you reproduce the issue?
Any workaround?

Regards,
Charles

[cash-metall]

Hello!

Yes, indeed, this is a bug - we reproduced it and added it to the tracker.

To workaround the bug, you need to delete the default ig_config.xml from the data folder, and also clear guids.db

Thankyou!

[Lales.Charles]

Hi,

Thanks for feedback.
Removing default ig_config.xml from data folder is not ideal.. also user have only read access to the app directory.
Creating chained directory links under data folder seems to make the job.. but if it can fixed at one point, that would be greatly welcome.

Regards,

[silent]

Hi Charles,

Yes, the proposed solution is not optimal, but the fastest one that we could find for 2.16. Proper fix will require a bit more time and probably will require some filesystem changes to proper resolve external paths.

We plan to fix this properly in the upcoming 2.18.1 or 2.19 update.

Please let us know if you need a patched engine version for 2.16.x as well or you can temporarily delete ig_config.xml from data as a workaround?

Thanks!

[Lales.Charles]

Hi,

Thanks for proposal, but no it is fine.

As explained, I get it work with double link directories to current user files.. from inside data directory, and it is properly taken into account.

If it can be solved in 2.18.1, that would be great.
From tests, it seems also that you use a data structure equiv to dictionary with filename as key and path to it.. and refuse any update if key already exists.
If so, this part could be updated as well.. or?

Regards,
Charles

[silent]

Quote

From tests, it seems also that you use a data structure equiv to dictionary with filename as key and path to it.. and refuse any update if key already exists.
If so, this part could be updated as well.. or?

Sort of. When resolving file paths we used a wrong comparison method, as a result wrong file was selected (from data instead of provided path).