Hi....
...this is what I was babbling on about somewhere else -- the crosstie
here (also the demo version) ... and many c4p/crosstie profiles done for
games before <steamappid> existed, (and where such games are also available
on Steam) , have possibly been created with bottlewide dlloverrides to
service the game in question. So... in example....if you used the crosstie
here as it stands on a Steam bottle, such has the potential to break other
steamapps installed in that bottle, because all the DllOverrides apply to
all apps in the bottle, and some apps may fail to run. It also creates a
situation wherein a steamapp would have an override applied to it that is
not required, and this will/could veil regressions in wine wrt the app, or
otherwise occlude wine's direction... ergo....
...when doing a crosstie for a steamapp that requires dll overrides, or, when
adding steamappid to an already existing crosstie (for a standalone version),
you really must check Installation Profile -> Advanced Installation Steps ->
Pre-Install Registry, and make sure everything is 'sane'.... so...
HKEY_CURRENT_USER\Software\Wine\DllOverrides
...becomes...
HKEY_CURRENT_USER\Software\Wine\AppDefaults\recettear.exe\DllOverrides
...and....
HKEY_CURRENT_USER\Software\Wine\Direct3D
...becomes...
HKEY_CURRENT_USER\Software\Wine\AppDefaults\recettear.exe\Direct3D
..and so on and so forth. This leads to the construct of one install profile
being able to service multiple distributor releases in a single crosstie, without
the need for multiple install profiles. It won't always work -- I can think of
some exceptions..ie; many games created with RPGMaker seem to release with the
main executable being named 'game.exe' and so every instance of 'game.exe' in
the same bottle would inherit the settings... but ... I'm not aware of an actual
incidence of same within Steam -- I just know of at least a dozen RPGM games where
the game binaries are all named 'game.exe' ... and I'm unsure if you can work around
that one..(let's face it, the games' creators should be a tad more imaginative
wrt naming conventions =) ...
...I think, however, one may need more than a single appprofile ...ie; at present, if
you use installed detection on a steamappid in a crosstie, it will invariably fail,
however you need installed detection for non-steam releases, because it is cxinstaller,
not steam.exe, marshaling the actual install process -- both appprofiles would use
(or could use) the same installprofile if it's staged as I describe above...
Cheers!
