American McGee's Alice is a third-person puzzle/shooter computer game, which takes place in the Alice's Adventures in Wonderland universe. It was developed by Rogue Entertainment and published, distributed and marketed by Electronic Arts, and under the Sold-Out Software label as well. Alice was designed by American McGee, and featured music composed by former Nine Inch Nails drummer Chris Vrenna.
My system has resisted all attempts to force 1360x768 mode. AFAIK the game works just fine with it, provided your system supports it, but mine doesn't.
Hey guys I just installed Alice on my Windows 7 pc and it works just fine! I want to make the game go widescreen though. I saw on this sight that you're supposed to mess with the config.cfg file in the base folder of the game directory. My problem is I don't have that file! I would post a pic of my base folder but I don't know how to. The only files I have in the base folder are: cgamex86.dll, fgamex86.dll, pak0.pk3, pak1_large.pk3, pak2.pk3, pak3.pk3, and pak4_english.pk3. What am I supposed to do? HELP PLZ!
I changed it to the highest the game will allow, then I started playing it and thought, I want to play this in widescreen. So i looked it up here, saw that that I'm supposed to mess with the config.cfg. Didn't see it in the base file, then came here.
I thought I'd post some insight on running this with Windows 7. I am on Win7 (Build 7600), so this may not apply to SP1, but it probably still does.
I do think Neuromancer is generally correct in his point that VirtualStore is the location of .cfg files, but this is not the case for my installation of Windows7. My .cfg file is located in GameBase as anticipated. However, the file's contents are a bit unexpected. Note first that I did check the VirtualStore, in which no such file exists or any files related to Alice.
All the general Quake settings are there, auto-generated no doubt, but they are un-lined (no soft "enter" between cvars), so they appear simply as "//Comment Desciption//cvar1 cvar2 cvar3//Comment//cvar"...etc... in a single line, so it's not exactly easy to deal with. I tried reformatting it, assuming the engine would read past the soft enters without a hitch. It did, of course, and configured according to my additions in the file (more specifically, it succeeded in changing the bind of "m" to edit the FOV variable on the fly), however it reformatted the file back to the initial illegible format.
It also completely removed the lines dealing with setting the custom resolution ("seta r_customwidth/height" and "seta r_mode -1") and did not successfully load my requested resolution (1360x768), yet loaded what seemed to be a 640x480 overlayed on a black screen of 1360x768 (black columns on horizontal AND vertical). Basically this meant to me that it did not accept the resolution as a valid game resolution and therefore didn't stretch it properly... or something like that.
So to FIX this I simply loaded the console in game and used the following lines to change the .cfg from inside:
seta r_customwidth "#"
seta r_customheight "#"
seta r_mode "-1"
to which the console would (sometimes) report that changes would happen whenever the game restarted. Upon restarting the game, as long as I DON'T CHANGE OTHER VIDEO OR SOUND SETTINGS IN THE GAME, it retains my custom resolution stretched properly, or as properly as the report above shows.
Long story short, change all graphics settings and sound settings before you try to go to a custom resolution, then do it in game. It should only take once. This is of course IF the OP method does not work for you. I trust that OP's method will work for most everyone; I am probably an exception.
I just thought I'd share in case people have additional difficulties. Command line globals might actually fix this problem, but I haven't looked into it. Post on that if you'd like.
I have since my last post learned that the game was merely behind by one "game-loading" on the resolution changes. When I used my reported method the game would not stick at the resolution after another reloading of the game itself. This leads me to believe that r_mode is set back to 8 after the game successfully loads in r_mode -1, for whatever reason, probably due to compatibility. My theory is that if I set the r_mode every time I load the game, each concurrent loading of the game will be in r_mode -1 because I will have overridden the r_mode 8 change done automatically by the console.
Long story short, I have to bind "m" to the FOV, then bind "n" to the "seta r_mode -1" and press them every time the game loads in order to retain the settings. Hope this helps someone.
