-project_name option behavior

[Amerio.Stephane]

Hi,

Per the doc, -project_name <name> option will place all modified files inside the user profile in the <name> folder. This works well, BUT:

- console_history is still written in the app folder. Shouldn't it too be in the user folder?

- if <name> doesn't exist in the user profile or if any file is missing, then the files are created from scratch with default engine values. I'd rather it uses the default files (placed in the data/configs folder) as templates... Otherwise, it kinda defeats the purpose of manually customizing these.

=> is there any way to force Unigine to use the data/configs as a template?

=> what would happen in a migration?

Note: this problem only arises now because we are moving to read-only install folders, and we are not using the Unigine Build system (doesn't really fit our runtime constraints)

 

[silent]

Hi Stephane,

Quote

- console_history is still written in the app folder. Shouldn't it too be in the user folder?

That's interesting question. Maybe it indeed should be located in the different (or even configurable) path. I will create a feature request to the dev team regarding this behavior (but so far with a minor priority, I'm afraid).

 

Quote

- if <name> doesn't exist in the user profile or if any file is missing, then the files are created from scratch with default engine values. I'd rather it uses the default files (placed in the data/configs folder) as templates... Otherwise, it kinda defeats the purpose of manually customizing these.

Yes, this command always worked this way.

 

Quote

 is there any way to force Unigine to use the data/configs as a template?

If you have an installation / deploy scripts you can probably do a configs copy on this step on your own. That's only requires to know the final -project_name parameter.

As an alternative option, you can pass absolute paths for the configs in the engine start-up parameters. In that case, no configs from %USERPROFILE% dir will be used. Something like that: -boot_config "E:\Install_Dir\My Project\data\my_cfg\my_boot.boot". In that case you would need to know the final deploy dir prior the installation itself.

Hope that helps :)