XAPK OHHEH

Hello all,
I'm trying to port my old-installer houdini installation workflow to new launcher, because it seem to be the only way of installing shfs (correct me if I'm wrong), and houdini seem to rely more and more on shfs existence.

The trick is that I'm limiting myself a bit, and every piece of software must be immutable, such as installation of houdini is immutable, and installation of launcher is immutable too.

And here comes the problem: it seems that launcher very much wants to write to ../data/. directory relative to the main executable, witch it fails obviously in such setup.
I cannot find any flags/env variables to change the location of the data dir, or to disable the .lock file creation.

Sure I could craft a little bind-mount safe space for launcher to be run with all the expected dirs, but I would prefer to avoid adding complexity to the setup.

Is there any way to affect launcher's data dir location, or locking mechanism?

I've been using userData to store some asset state info. UserData was chosen instead of a hidden parameter because userData can be set on a locked node, and should be saved to hip file or HDA just as a parameter.

And it all works... except it turned out that userData on locked nodes is not saved to the hip file. So an asset that consists of assets that store part of the state in userData will not store it's state to hip file, and on each scene load the userData on internal nodes of the asset instance will be reset to what it was during asset creation.

My only question is - is this the intended behavior for userData?

many thanks)