Assassin's Creed (ÇIKTI) (195. sayfa)

quote:

Orjinalden alıntı: benanantalya

arkadaşlar cıkacak olan orjinal oyunda türkçe secenekte varmış diye bi yerlerde okumustum ama bidaha bu bilginin izine raslamadım :)
bilgisi olan varmı acaba. eger oyun tamamen türkçe olursa orjinalini satın alır baştan tekrar oynarım çünkü oyundaki dialogları çok merak ediyorum :)

quote:

Orjinalden alıntı: kobem

kudüs ile ilgili bişey buldum OKUYUN!

For people wondering why the files can't be copied over:

"OK... so it is as I feared. As we all know, the PC version is the Director's Cut, and it has several new mission types. I was hoping the guys at Ubisoft added these NOT in the specific .forge level files, but in an external file that is accessed for mission generation.

It is not so.

The programmers at Ubisoft, in their infinite wisdom, have decided that this is not the way they want to code their engine. They do not want to reuse code and resources or, God forbid, make it easier for themselves when the time comes to support this game and patch it. They refuse to design their engine along industry lines and have universal resource packs and only changing assemblies for platform deployment (the way UE3.0, Viscous Engine and Vision Engine do it). No. they lump it all together and make life harder for themselves for absolutely no reason. As a side effect, it screws our idea of replacing the two faulty files (the Jerusalem and Arsuf .forge files) with the ones from the X360 version.

The whole .forge format is ridiculously stupid. I've been reading most of them during the last several hours, and they just throw everything they're fraking able into it. Get a hex editor and open, for instance, the Damascus .forge file. The format is pretty simple:

1. scimitar string
2. zeroed bytes
3. hashed header
4. zeroed bytes
5. real header (contains a list of resources in the file)
6. zeroed bytes
7+ definitions of the resources separated by zeroed bytes

The point is, they put everything in these .forge files. The Damascus file alone has diffuse textures, alpha maps, cube maps, code blocks, material properties, mocap data, _foliage_ entity descriptors... you name it, they've put it in there. The format is basically a wrapper for anything they desire, which goes contrary to pretty much every game engine design concept I know of.

This also means that the mission subroutines are also in the .forge files (search for "quest" in the Damascus .forge file and you'll see the datablocks that hold the code). And so the PC-specific missions are also in there. And the X360 .forge files do not have these extra missions, so when we try replace the corrupt files with them, the exe basically crashes with "unresolved external symbol" errors (you can't see these without a debugger) because it can't find those code blocks.

Point being, our lovely idea of swapping the corrupted files with the X360 ones fails. It really should have worked, and it would have had the Scimitar Engine been designed like every other modern engine today.

In case you're wondering, this poor design is also the cause of the 2GB RAM minimum requirements, and 3GB for the recommended: the WHOLE .forge file needs to be loaded into memory if they want to use anything in it, they can't just load the parts they need (which is the sensible, rational and common way of doing it) because it's all one big file. You need the DataPC file in memory (200MB), the sounds .forge files (600 MB combined), and whatever level file you are in currently (usually around 700MB). For instance, wherever you are in the game, the game has loaded ALL of the sounds from ALL of the levels, even if you're in the main menu.

That's the single most retarded idea I have ever seen in engine design. "

quote:

Orjinalden alıntı: Pinky_Demon

İngilizce bilmek için Oxford mezunu mu olmak gerekiyor?

quote:

Orjinalden alıntı: command_4

quote: Orjinalden alıntı: kobem kudüs ile ilgili bişey buldum OKUYUN! For people wondering why the files can't be copied over: "OK... so it is as I feared. As we all know, the PC version is the Director's Cut, and it has several new mission types. I was hoping the guys at Ubisoft added these NOT in the specific .forge level files, but in an external file that is accessed for mission generation. It is not so. The programmers at Ubisoft, in their infinite wisdom, have decided that this is not the way they want to code their engine. They do not want to reuse code and resources or, God forbid, make it easier for themselves when the time comes to support this game and patch it. They refuse to design their engine along industry lines and have universal resource packs and only changing assemblies for platform deployment (the way UE3.0, Viscous Engine and Vision Engine do it). No. they lump it all together and make life harder for themselves for absolutely no reason. As a side effect, it screws our idea of replacing the two faulty files (the Jerusalem and Arsuf .forge files) with the ones from the X360 version. The whole .forge format is ridiculously stupid. I've been reading most of them during the last several hours, and they just throw everything they're fraking able into it. Get a hex editor and open, for instance, the Damascus .forge file. The format is pretty simple: 1. scimitar string 2. zeroed bytes 3. hashed header 4. zeroed bytes 5. real header (contains a list of resources in the file) 6. zeroed bytes 7+ definitions of the resources separated by zeroed bytes The point is, they put everything in these .forge files. The Damascus file alone has diffuse textures, alpha maps, cube maps, code blocks, material properties, mocap data, _foliage_ entity descriptors... you name it, they've put it in there. The format is basically a wrapper for anything they desire, which goes contrary to pretty much every game engine design concept I know of. This also means that the mission subroutines are also in the .forge files (search for "quest" in the Damascus .forge file and you'll see the datablocks that hold the code). And so the PC-specific missions are also in there. And the X360 .forge files do not have these extra missions, so when we try replace the corrupt files with them, the exe basically crashes with "unresolved external symbol" errors (you can't see these without a debugger) because it can't find those code blocks. Point being, our lovely idea of swapping the corrupted files with the X360 ones fails. It really should have worked, and it would have had the Scimitar Engine been designed like every other modern engine today. In case you're wondering, this poor design is also the cause of the 2GB RAM minimum requirements, and 3GB for the recommended: the WHOLE .forge file needs to be loaded into memory if they want to use anything in it, they can't just load the parts they need (which is the sensible, rational and common way of doing it) because it's all one big file. You need the DataPC file in memory (200MB), the sounds .forge files (600 MB combined), and whatever level file you are in currently (usually around 700MB). For instance, wherever you are in the game, the game has loaded ALL of the sounds from ALL of the levels, even if you're in the main menu. That's the single most retarded idea I have ever seen in engine design. "

Herkes Oxford mezunu değil. Bir bilgi paylaşıyorsanız bunu herkesin anlayabileceği bir şekilde sunmalısınız.

quote:

Orjinalden alıntı: devilcnr

Bunun oyundan atmayan versiyonu çıkmadımı hala..

quote:

Orjinalden alıntı: egomanyak.

jerusademe giriyoda 1-2 dk sonra gene atıyo oyundan ya!
çözüm varmı

quote:

Orjinalden alıntı: xxxlarge

atın yol tutusu cok guzel şaka bi yana ata binmeyi guzel yapmışlar evet

quote:

Orjinalden alıntı: Sage Dj@vul

Arkadaslar oyunda Türkler var diye sevinmeyin keske hic olmasaydı diyorsunuz oyun sırasında cünkü Türkler resmen yol kesen eskiyalar tarzında olmus.


Oyunda güldügüm bir nokta ise adamın isini bitirince son nefesini verirken Allah Belanı Versin diye bagırıp ölmesiydi