Hopkins on 26/5/2003 at 19:02
I seem to be affected by a rather annoying bug. I was forced to reinstall my OS and Arx Fatalis with it. Previously I was running W2K and now I am running WinXP. I have a saved game in the Akbaa temple after I dispelled the field into the golem/switch area and I have played with two of the switches but not the switch behind the double doors where you have to shut one door to open the second. Before I reinstalled the OS I had pulled this third switch to release the bridge and then defeated the demon. However I did not keep a saved game at this point because I had troubles with the sound. Now, on reloading the saved game, I cannot release the bridge no matter how much I fiddle with the switches!
I have tried different combinations of game and patch but to no avail... Does anyone have any suggestions? I will leave this for a few days and if I have no luck then I will e-mail the bug to the Arx support team.
Cheers!
twisty on 27/5/2003 at 10:16
Unfortunately, this is a bug that hasn't been addressed in any of the patches. I sent Raf a list of suggestions and bug fixes quite some time ago but it looks like they missed that one.
Hopkins on 27/5/2003 at 13:27
Thanks for the reply! I'm glad that you have been able to confirm that it has been recognised before. Is there any any way around it (my last backed up save was about 10 hours ealier :() or shall I give Morrowind a go until they fix it?
twisty on 27/5/2003 at 23:19
I doubt that they are going to fix it as they have released two patches since I first mentioned it to them. I highly recommend that you email Arkane Studios about it as they might be able to send you a small fix.
Hopkins on 27/5/2003 at 23:44
Will do. Thanks for your help!
Hopkins on 3/12/2003 at 16:32
Misery, I am to play Arx no more. One of their guys said he'd fix this for me months ago, but he never did. He'd ask me for a save game, then loose it, and I'd ask him a couple of months later, and he'd ask for it again, and I'd send it, and this just repeated. Now they've released another patch and it's still not fixed. I'm pretty god damn disappointed, especially as this problem has clearly been found and ignored. :tsktsk:
