Thank you for buying the game, and I appreciate your patience with the issues that some of you are having. Launching a game when you're essentially a one man team was bound to be a bit rocky, and I really appreciate the community effort to find and resolve some of these issues until I can fix them officially.
This thread contains some common issues that people have found and fixes for them, until I get around to resolving them officially. This list will get reduced over time as updates are pushed to Steam.
Game Crashes at Unreal Logo / UDK.exe has stopped working
This is a generic UDK error that can have many causes. The following are some fixes that have worked for other members in the community.
- Updating to a later version of PhysX drivers has resolved this issue for many. Regardless of whether your graphics card is ATI or NVidia, you can install newer drivers found in your Antichamber Steam directory: *installdir*\Binaries\Redist\physx\PhysX-9.12.0613-SystemSoftware.msi. This is not installed by default, as the drivers that shipped with UDK are required for some, while these newer ones are required for others.
- Renaming *installdir*\Binaries\Win32\PhysXLoader.dll to something else (anything) has also resolved this issue for others.
- Try running the game as an administrator.
- Try changing the default resolution the game is trying to load in (see below).
If none of these fixes helps you and you cannot find a fix via the community forums, please do the following:
Right click Antichamber in your Steam Library, go to "Properties", "Set Launch Options" and add -FORCELOGFLUSH
Try running the game again, and email *installdir*/udkgame/logs/launch.log to firstname.lastname@example.org. This will give me a better idea of what your specific issue is, and how to go about resolving it.
Until the options wall in the game is redone to support more resolutions, you can get around this problem by opening *installdir*/UDKGame/Config/DefaultEngine.ini and changing the following lines, at the bottom of the file:
Change ResX (width), ResY (height) and FullScreen values to the desired resolution values. This may help anyone who tries to run the game and only sees a black screen, as the game did not originally display in a supported resolution.
In game reconfigurable controls are something I am still working on to support officially (having in-game art register the keys correctly, etc.). Until that goes in, you're free to change them manually.
Open *Installdir*/UDKGame/Config/DefaultInput.ini, search for "Antichamber Keyboard Bindings", and then change the keys to what you need. A more complete guide was written by another user here: http://steamcommunity.com/sharedfiles/filedetails/?id=124125413
It is possible to play the game with an XBox controller, but it wasn't tuned correctly so I ripped it out for the launch. I thought it would be better to have no support rather than unfinished support, but I can see that many people would still like to be able to play with a controller.
To re-enable (unofficial) support, in *Installdir*/UDKGame/Config/DefaultInput.ini, search for "Antichamber Controller Bindings" and replace what is there with the following.
; Antichamber Controller Bindings
; Secondary default bindings
; Primaray default bindings
.Bindings=(Name="XboxTypeS_Start",Command="GBA_ShowMenu | OnRelease CancelExit")
.Bindings=(Name="XboxTypeS_RightShoulder",Command="StartTriFire | OnRelease StopTriFire")
.Bindings=(Name="XboxTypeS_LeftShoulder",Command="StartTriFire | OnRelease StopTriFire")
The buttons will all work (hold B to walk), but the motion on the thumbsticks isn't tuned and accelerates too harshly. When this stuff has been resolved (in code) and tested properly, this will all be put back in officially.
Game Crashes when drawing huge loops / cubes
If you draw a very large loop or cube (e.g. trying to make a cube close in on yourself), it's likely the game will crash as an algorithm will go out of control and try to do more than one million iterations in a single frame. There is no puzzle in the game that requires this (there was an earlier issue with "Over The Edge", which has since been resolved), so for now, don't do it. I will be looking at improving this algorithm over time to resolve this issue completely.