HonestFlames

You don't have to hurt your wrist, you just have to develop a technique to mash buttons quickly. I played on PC using an Xbox 360 pad and the button mashing difficulty was just enough to make it a challenge.

I've played past this and got caught by the guards on my first attempt and then I got past them on the second attempt. I did not run into the bug being mentioned here. 1. I walked up to the guards and they told me to get lost. 2. I walked near to them but not close enough to trigger the cutscene. 3. I distracted the left guard with a sneaky squeaker to the left (he moved down and to the left). 4. Similarly with the right guard distracting to the right. 5. The left guard had begun to walk back to his post whilst I was still approaching the gate, but I was not caught.

How do you know what happens when a machine uses an Nvidia device that is not listed within video_autodetect.xml? For instance, the device ID for the GPU in my laptop is 0x11a3, which is not listed in video_autodetect.xml and yet the game runs at highest quality for me. It would seem logical that the game does: 1. Match device ID or SearchKey. 2. Set graphic detail based on search result. 3. If search result is not found, set highest detail. It would make sense that every missing device ID is a higher number and thus probably a higher performing GPU because of being newer. Anything beyond a GTX480 (you did see device ID 0x06C0 in there, which is a GTX480?) can easily run the game at highest settings. Legacy and slightly older Device ID lists are easy to download. Newer ones are not. Nvidia provide a device ID list current only to Jan 2013 (they obviously have a newer list somewhere, but Googling reveals only the Jan 2013 list as readily accessible). If a new GPU comes out that isn't listed in video_autodetect.xml that doesn't have the necessary performance to cope with highest quality, it's a very simple process for Obsidian to release a patch, or even a quick forum post of "add this line to the config file".