New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not fully portable (on Windows?) #158
Comments
I find this a bit annoying myself but have gotten used to it. |
I'll have a look at it. We'll likely fix the baseq2-case and provide a mechanism to disable the usage of the users home directory altogether. |
This is the first step to fix issue #158, consistent behavior for all cases. This problem was also reported by @lonkamikaze through IRC.
Normally Q2 writes all persistent data (the configurations, saves, etc.) into a subdirectory in the users $HOME. That can be a problem when the game is installed onto an thumb drive or something like that. Therefor provide a cvar fs_portable. When set to 1 the games uses it binary dir as it's persistent storage location. Examples: ./quake2 +set fs_portable 1 ./quake2 +set basedir ~/games/quake2 +set fs_portable 1 fs_portable is _not_ saved into the config file. It must be set at every start! This closed issue #158.
Okay, I've just pushed the fix. When fs_portable is set to 1 the game writes it's configuration data, the savegames, etc. into the binary dir. An example: The game is installed to D:\quake2 and started with |
I'll compile and test it. |
@Yamagi It's work, but not all. |
I totally forgot about that files. I've just pushed a fix. |
It's called 'portalable', now. And no longer 'fs_portable'. |
@Yamagi It's still creates dir YamagiQ2 and std*.txt files in it. I'm using |
That's very nice to know. Thank you! |
Latest client still creates and uses files from Documents directory only (C:\Users%USER%\Documents\YamagiQ2).
How I can set it fully portable? If I start Quake 2 with "+set game baseq2" parameters, it uses saves and config form game dir, but still creates YamagiQ2 dir in Documents and saves logs there.
The text was updated successfully, but these errors were encountered: