Talk:Assassin's Creed

Seems like not all retail releases make use of Safe disc. Got a copy through the Ubisoft 25 Years collection that seems to be running without any sort of disc check.

Not just that. Apparently the one from the "Assassin's Creed I & II: Ultimate Collection" also doesn't have any protection.

If you can, please upload that release's details on redump.org. It seems to be missing.

Never heard of that site so sure.

interesting fact too is that its not labelled as "Directors cut" (though pretty sure it is) and seems to have the 1.2 patch pre applied.

Actually got a lot of rare PC games laying around. Gonna check if any of those are present

Yea, quite a few are missing.

This can make searching easier, for example to look only for PC releases: http://wiki.redump.org/index.php?title=Redump_Search_Parameters

They're also on the VGPC discord server: https://discord.com/invite/AHTfxQV

NEW UPDATE: So, I got the GOG version of Assassin's Creed 1 and it seems that it works very well on Windows 10. So, I guess the crashes was present only in other version, but they were fixed in the GOG version 1.02.

Hi everyone! So, I decided to replay Assassin's Creed 1 after so many years again and... there was a lot of crashes. First, the game crashed on me in very strange way. I was on the quest of killing the first guy in the first big city, and so when I screwed up and he killed me instead, game froze and then there were black screen but my monitor shut down. But I could still hear the sounds of the game, all tho they were of in-game NPC's talking. Then I rebooted PC and launched the game via launcher, instead of DX9 or DX10 exe file. And it worked well for few hours, until I got to the next quest in Jerusalem.

In there, when I beat up this one guy to get some information from him and then got to the nearby tower to climb up and look around to open new areas, there were guards on the roofs, and one started to attack me. I kicked him off of the roof and the game crashed right after that. But this time it only froze for a few seconds and closed, without any black screen. There was even no error messages or anything like that. Thus I stopped playing it and started to wondering, if there is solution to my problem. I googled every possible word to try to find the solution, but those that I found were very banal, like reinstalling your video card drivers, or updating them, or checking on your video card and stuff like that. But I know that everything works fine with other games, as far as my hardware goes. It's the games that keeps screwing up with me because of, it looks like, Windows 10.

Thus, here is my question: is there any solution to this? Like, I set compatibility with Windows XP SP3 and run as administrator for this game on DX9 exe file, but I didn't tested it yet. But the thing is that, in the past, like in 2013 maybe, when I last time played this game, there were no crashes at all. But I played on Windows XP back then. But now, on Windows 10 this game keeps crashing and I keep wondering, why it happens. Why it continues to crash. So, is there any solution to this? Because, I really want to replay very first Assassin's Creed game and I can't because of those crashes. So if anyone could help, it will be really cool.

UPD: So I tested compatibility for this game on Windows 10 with Windows XP SP3 and I also run it as administrator and... it still crashes. Heck, it does not even launch. Like, I launch the game and after loading screen, it stops on 70% and crashes back to desktop without any error. I disabled "run as administrator" but it didn't helped. So I had to disable compatibility and only then it worked but keeps crashing in random moments. Like, I was doing quests in Jerusalem after visiting every single tower available, and there is a quest where you have to go inside the church to find out the information from two guys talking. And after that, when I got out and guards attacked me, I climbed up on the roof to hide from them, and game froze and then crashed. I will later try to run it via DX10 exe and see if it helps.

UPD 2: So I just tested Assassin's Creed 1 by launching it via DX10 exe file and it still crashes, when I get killed. And symptoms are the same. Game freezes, then black screen shows up and there is yellow light on the monitor's ON button glowing instead of green. But I still hear the sounds of the game like nothing happened. I tried to press Alt+Ctrl+Delete to launch task manager, but nothing shows up. Then, I tried to press Alt+F4 and still nothing helps. And so yeah, the only thing that helps is fast PC reboot by the press of the button.

Thus, in conclusion I would say that Assassin's Creed 1 does not work properly on Windows 10. And there is no ordinary solution to this problem. And it will crash no matter what in random situations. By the way, I'am playing on Windows 10 Pro X64 22H2 version.

I'll have to do more tests, but tried using x360ce for the first time ever, choosing v4 and it's really easy.

I read about v3 and thought it was a little bit too complicated for me... v4 is really easy even though it's in Beta.

I'll edit the wiki if I have the time and knowledge.

I realise I'm late to the party but could you elaborate at all? I'd be very interested to know if V4 changes anything.

It seems like it's no longer DRM-free on Uplay as of September 2019. Can anyone else confirm this? If I replace the EXE, it launches without Uplay

Hello everyone,

I investigated the crashes on launch a bit further recently and I found something that seems to be causing them - and it's not the network connection (even though disabling the network adapter still helps).

On my system, the game consistently crashes on launch when I have Comodo Internet Security (or just the Firewall) installed and enabled. However, it's not the basic antivirus or firewall components but one of the advanced features that detects shellcode injections that seems to be the cause of the crashes on my system.

I'd appreciate it if someone could check this out to confirm this. Follow these steps:

1. Download and install Comodo Firewall / Comodo Internet Security

2. Disable all components except for the Firewall and set the Firewall to "Custom Ruleset". Leave other settings as-is.

3. Launch Assassin's Creed and observe if it crashes on launch.

4. If it does: Open Comodo, then: Settings -> Advanced Protection -> Miscellaneous

5. Make sure "Don't detect shellcode injections in these applications" is **checked**

6. Click on "these applications" and add all your hard drives as folders to the exceptions. Click Ok, close settings by clicking Ok again.

7. Launch Assassin's Creed again and observe if it doesn't crash anymore.

Thanks for your help!

Running the game in DX9 should solve the issue. There are no differences in graphics between the two DX options anyway in this game.

Nope, in my case it doesn't. Only putting these settings in place in Comodo fixes the crashes on my system. But sure, it's specific to Comodo users.

Can you try "checking" with Process monitor if the dlls the game loads are always the same in the two situations?

I did just now and the only difference is that guard32.dll (a COMODO component) is loaded when the drive where AC is installed is not added to the exceptions.

As a Comodo Firewall user I can confirm that adding the exception for detecting shell code injection does prevent the crash on startup. No other workarounds necessary in my system. This info should be added to the main page.

W10-x64pro, Ryzen 3700x, RTX 2060.

As far as I can see, the game doesn't have designated controller prompts for the Xbox 360 controller.

Although, it does have prompts that correspond to the proper letters.

http://pcgamingwiki.com/wiki/Assassin%27s_Creed#Get_DX10_Working_For_versions_of_Windows_after_Vista

Instantly crashes on launch.

Missed patch changelog, if true: http://pcgamingwiki.com/wiki/Assassin%27s_Creed#Patches

The game is claimed to use a simple Generic Keycode as DRM...
Though, the first run had to be done with administrator rights to let the game install TAGES drivers..
Of course I received the usual TAGES error which always happens with windows 7, but as always you just need to install updated drivers first