Thanks for the heads up. :)

I've briefly tested the latest version (0.1_ff17c.z) and I haven't seen the issues you mentioned; there are some subtle differences but it mostly plays very closely and a couple of minor issues seem to have been sorted out already. It's already looking stable enough for me to give this a proper try the next time I play.

The wiki mentions migrating features like bump mapping and EAX to their modern equivalents which should be very interesting.

EDIT: note that permissions haven't been fixed for Vista and newer so as with the official version you'll need to run the game as an administrator for saving and so forth to work correctly, but unlike the GOG release it isn't set up to request this by default.

Did you use the 32 or 64-bit exe? I'm on XP so I could only use the former and as I'm on XP there should not be permission issues as I am the administrator. So for you the intro narrative (and other conversations) worked fine and rocks hit floor and not something in midair?

It's odd that some conversations work and others not. It's almost like it isn't finding the sound files (but there's no errors in log file). The sound and music both in game and intro work just fine, just the speech is missing.

How's it working for you? Did you encounter the clitches I mentioned above or am I the only one?

I am not currently playing the game. I was only obsessed with getting it to run. My backlog of games is huge but it doesn't stop me from continuing to purchase games that I know I will like at great price reductions! :)

The tutorial says that the symbols don't disappear immediately if you click them. Is this really a bug?

My bad, that changelog sentence is misleading.

If you click on a spell, the corresponding runes sequence will appear in the top right corner of your screen, and they stay there after you close the spell book. As the tutorial points out.
However, if you click on a rune, its shape will be drawn on the left page of the spellbook, and if you closed the book fast enough it would continue animating "in the air". That's what I modified (if I'm not mistaken! That was a while back ;)).

Those are total lies! Well, ok, they are not ;-) - the first Windows binaries did have those issues. They were not meant to be stable versions though, just snapshots of the source code (the five letters/digits corresponded to the source version).

Since this thread is stickied I feel the need to add that we have since released version 1.0, 1.0.1 and 1.0.2 of Arx Libertatis. These should have none of the bugs mentioned above. If they do, the best way to get them fixed is to file a report on our bug tracker.

I'd also like to point out that AL 1.0+ includes most of the changes from Nuky's version.
(edit: looks like we got everything up to v0.02 but are missing some things from v0.03 - I'll look into importing the remaining fixes)

We still have a bug report open for that and I can't remember a fix specifically for that, but it's been a long time since I encountered that bug. Maybe it just happens when the game runs too slow though - Arx uses non-continuous collision detection so there will be glitches if a frame takes significantly longer than it should. Can you (or anyone) still reproduce this bug?

That's unfortunately still there, but possibly less severe/frequent. I don't think this will be easy to fix, but we'll get there eventually.

do you know how to get this game working on my computer? ive tried all the stupid downloads and patches and NOTHING works. it feels as though gog sold me a broken product and despritely tried to hide it.

my specs
win xp
1 gig o ram
intel family chipset

I'm using an I7 Intel 8-core computer with Win7 64bit.
If it works on 64 bit, it must be working surely on 32 bit (XP).

Because this is an older game. You are using 1 gig ram ?
Is that enough for this game (minimum required) ??
I have many more ram, than you.

Hence, I use my ram to play older games, instead of my GTX video card.
Because most older games don't recognize it.

What about your soundcard & videocard ? Are they compatible with the game ?
Maybe they are old or need an update ??

Look at me, the game works, but crashes a lot with my computer.
I need to "save game" every 2 minutes.
The update/patch gives me a small screen like:
320x100 or something like that.

I accept bugs & crashes without the update.
At least I can play ........ bit by bit .... hahahah

Jack

SYSTEM REQUIREMENTS
MINIMUM PC REQUIREMENTS
MINIMUM
Windows 98/ME/2000/XP
Intel Pentium II 500 MHz
64MB RAM
750MB Hard Drive Space
16MB DirectX 8.0-compatible Video Card
4X CD-ROM
DirectX 8.0-compatible Sound Card
RECOMMENDED
Intel Pentium III 900 MHz
256MB RAM
32MB DirectX 8.0-compatible Video Card

If you are crashing all the time in Win7 64bit, set it to Win XP (SP3) compatibility mode (Right-click launch icon, select Properties, select Compatibility, then select compatibility mode of Windows XP (Service Pack 3). It was crashing constantly for me too, but haven't had it crash even once since I changed it.

I can safely say this patch is imperfect. I noticed some of the animations in cutscenes are broken, am shagar warps foward in game on ocashion, audio cuts out and a fleshtone flash ocashionaly pops up for a second or 2. But with that said I'd take that over the crashing of vanilla arx any day

As this thread is sticky, I'll just mention that the changes from version 0.3 of Nuky's excellent patch (which is the latest version at the time of writing) appear to have been merged into Arx Libertatis (judging by the closed status of the relevant issue, as mentioned by dscharrer).

As such, if anyone is confused about which third-party patch to use, I would suggest that Arx Libertatis should definitely be your first port of call.

I plan on embarking on a new Arx Fatalis adventure after I finish Planescape.
But all this talk about patches and whatnot makes me wonder: is the vanilla game truly unplayable? Does it have so many game-breaking bugs?

In my last play-through I got until temple of Akba, and didn't encounter any bugs that affected my gameplay.