Warzone 2100 Forums

I think he's not talking about the config dir of the game, but the whole game during the setup, maybe.

I assumed he was talking about the config dir, (which, as Purple Monkey kindly pointed out is all ready implemented), as doesn't the windows installer already let you decide on an install dir? as for running warzone from a usb stick under Linux, well you'd have to include the dependencies (QuesoGLC) on the stick as well as add them to ldconfig so WZ can find them ,which would requires admin rights.

Anyway all of this is very nice, but has very little to do with this thread or the 2.1 beta test..

All hail the Wise and knowledgeable DevUrandom!

see you learn something new every day here at the WZforums.

Ummmm, how do you use the --configdir option? i've been typing it into the Traget area (along with --noshadows and all the other options im using) yet i cant seem to get it to work. everytime i start the game a new folder is made in the my documents folder.

--configdir DIR

how exactl do you type the directory name? I've tried:

--configdir F:\Junk\Warzone 2100\WZ2100ConfigFiles
--configdir WZ2100ConfigFiles
--configdir Warzone 2100\WZ2100ConfigFiles

and so on, but i cant seem to get it to work. Any ideas?

well first off relative paths (your last 2) should start with .\

second it seems to be completely ignoring the --configdir option and not simply getting the dir wrong, if it was then wz wouldn't run at all, so first question is... it it actually taking notice of your other options?

second, could you copy/paste the full command line  exactly as it appears in the shortcut so we can see just what exactly your trying to get it to do?

Well, the address is as follows:

Target:
"G:\Junk\Warzone 2100\warzone2100.exe" --window --resolution 640x480 --cheat --noshadows --configdir .\WZ2100ConfigFiles

Start In:
"G:\Junk\Warzone 2100"

--window --resolution 640x480 --cheat an --noshadows all workfine, but everytime i try WZ out, i can't stop it forming a Warzone Folder in My Documents.

I've tried the relative path thing and it still wont work.

Any ideas?

BTW, warzone works perfectly fine in everyother way, but --configdir doesn't work. Oh, and i'm using version .... 2.07? WTF? Give me a minute, ill try this with 2.0.10 (D'Oh!)

2.0.10 will not support that either... (Though it might give you an error "unsupported commandline option" instead. )
--configdir is only present in 2.1_beta1 and above.

I thought it was a recent addition but i wasn't sure when it was added, as I couldn't find it in the ChangeLog.

Bugger, well, when 2.1.0 gets more stable, ill download it then. Until then, i guess i'll just delete any extranuous files

actually I've found the last few svn build from trunk & 2.1 branch to be fairly stable, at least on my machine. Even debug builds  which seem pre-disposed to crashing on a whim (like when loading the next level in the campaign). last night i managed to play the entire Alpha campaign in one sitting with out any crashes or weird stuff happening, at least nothing i noticed.

Verminus wrote: actually I've found the last few svn build from trunk & 2.1 branch to be fairly stable, at least on my machine. Even debug builds  which seem pre-disposed to crashing on a whim (like when loading the next level in the campaign). last night i managed to play the entire Alpha campaign in one sitting with out any crashes or weird stuff happening, at nothing i noticed.

Those "crashes" which appear only in debug mode are actually assertions, which occur because some values are not what we expected them to be. Would be nice if you could add informations about that to the bugtracker. The info will be:
- in the gdmp
- in the logfile, if you told WZ to create one via --debugfile
- on the console if you started WZ from there
- in stdout.txt / stderr.txt if you are on Windows
Best is if you submit any information possible, so we can track that down.

Will do, but in the last few builds I've found they only tend to happen if I've been messing around with the cheats