Patch for crisis 3 direct 10

We work on a "rigid" scheme

Downloading the program PAK Manager (Pak Manager Tool), it is needed to unpack encrypted *.PAK game files, from the official site CryTek supplied with Crysis 2 Mod SDK

Crysis 3 DX9 Project

Updated 22.03.2013 !
After exhausting digging into Cry Engine 2 And Cry Engine 3 it was found that in the latter (from the game), there are important settings.
Among them it should be noted - r_Driver(CE3) accepts the values: DX11, AUTO and NULL.
Quote from crysis3.exe "Sets the renderer driver (DX11/AUTO/NULL)". And also the line helped a lot: Specify in system.cfg like this: r_Driver = "DX11". Specifies index of the preferred video adapter to be used for rendering (-1=off, loops until first suitable adapter is found). Setting r_Driver="DX9" led to the disappearance of some of the objects on the maps and the lack of drawing of characters (only the head and weapons were visible).

Checking r_ShadersExport (0 off, 1 allow shader export during shader cache generation - Currently 360 only.), that is, we export the processed effects to files (Crysis3\USER\Shaders\Cache).
And again, failure, as scientific research has revealed, most of the commands that were available in C2 are either fixed here, or the engine does not react in any way to their change, although the settings for PS3 and Xbox 360 are often viewed in the code, in particular: r_ShadersPS3 And r_ShadersXenon. Generally speaking, the file itself crysis3.exe contains a lot of garbage and unnecessary information, for example, you can find compiler calls and parameters, but what you need to find was not possible, on this note, the study Cry Engine 3 was stopped. It is worth noting that in the C3 code, the expression skips D3D9, so it's possible, initially, CE3 was created for DX9 as well, apparently the developers encountered some inexplicable problem and decided not to strain themselves, bungling up a "new" engine quickly.

What has been achieved

Empirically, it was found that C3 responds to a command in system.cfg, sys_spec(0-6), with a value of 5 for Xbox 360 and a value of 6 for PS3! (sys_spec=5). I should note that in this case, the game starts to use all your N-core processor without stopping, loading it at 99%! The video below demonstrates the main problem, there are no low resolution textures in the CE3 engine, at least for the characters. In addition, we found the possibility of recompiling textures. See screenshots below and watch the video.

At the moment, a team of enthusiasts HardWare Masters working on it, as soon as we finish and test it - we'll post it!

Crysis 2 MOD SDK

To install the developer package from the Germans, you need C2 version 1.9, if you have a pirate installed and SDK not installed, crashing with the following error: "requires a full installation of the game Crysis 2, updated to Patch 1.9", then you need to do the following:
- check registry key (for 32-bit systems) HKEY_LOCAL_MACHINE\SOFTWARE\Crytek\Crysis 2 string type key Install Dir, if there is no such entry in the registry or the path is incorrect, then create and register the required one!
- for x64 systems, the registry key is located at: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Crytek\Crysis 2 , the actions are similar to the previous paragraph.

useful links

DirectX 11 Hook/Hack/Patch

After spending a lot of time learning the engine from the Crysis 2 game, the idea of ​​emulating/bypassing DirectX 11 API calls came to mind. Actually, the idea is not new, if you remember the old utility from a German author called 3D Analyze, which made it possible to emulate the version of shaders and configure each application for almost any video card, then this solution method is faster and more reliable. We sent Thomas"have a message, but they themselves have already begun to work in this direction. Patch / Hack / Utility will present itself as either a direct patch (.dll) or a universal one (modify the process memory).

As a result of researching the EXE file, it was decided to make a "own" library d3d11.dll, so that the functions in the library would return the required parameters without the participation of drivers. Also in the process of researching technology DirectX a very interesting number of details were found, for example, that any model with DX11 effects can be rendered on almost any video card. Actually, there was a suspicion that all the "goodies" of DX10 / 11, etc., are add-ons over DX9, and support for the corresponding API lies only in drivers. After all, what's the difference what to send to the chip? In the end, all the same, the machine code is sent to the chip, for example, Tessellation - in fact, adds a few more wireframes to the existing model. As a result, we see with our own eyes all modern marketing, that is, new chips were invented to sell new chips, which can also be recreated on earlier models (8600GT / Radeon 4000 series...). For example, if in DX9 the bulge can be built with 9 commands, then in DX11 only 3, this is just an example, at the output the graphics chip will still be loaded in the same way). Another point, even if you make a model for only version 11 shaders, you still have to set the "bumps and lighting" by hand. That is why in Crysis 3 shaders for models are already in the game itself). In fact, all blocks are in drivers and libraries (thanks to MS, NV and AMD - all monopolists). Below is a video that demonstrates in which direction you need to dig, and also clearly shows the correctness of my statement.
What do we want to do? Replace the DX11 libraries with analogues, that is, every call to the 11.0/11.1 API function will always be successful;).
Remembering the history a little... For example, how long people sat on XP, and everyone was happy with everything, as well as the failure of Vista (the main feature of the pseudo DX10), and then the slow transition to Seven (the climbed out Vista and the pseudo-new DX11), once again proves the loyalty statements.

Preparing for the hack

Alternative DirectX 11 library - concept

After a cursory examination of the game for calling DirectX functions, before loading the menu, two were found: D3D11CreateDevice And . Having opened the Microsoft Knowledge Base (MSDN), it was found that there are not so many discrepancies, with the exception of the number of arguments.

This code is on the site. MSDN so anyone can check. In particular, the function D3D11CreateDeviceAndSwapChain is called only twice in the game before loading the main menu, in fact, most likely the test for checking the chips of the 11th version of DirectX is based on this, it was decided to replace the d3d11.dll library (placed in the folder with crysis3.exe), writing it "clone" which, first of all, will intercept all function calls from the game and write it to the LOG file, and secondly, it will always be possible to return the values ​​we need!

The screenshot below does not show the differences between DX9 and DX11 (Dragon Age 2), DX is just a software API for the video driver, the driver in turn creates a set of commands (instructions) for the GPU. DirectX 11 features are just additional effects for DX9, DX10/DX11 - just marketing to sell Windows Vista and other operating systems from Microsoft, as well as to change the video card more often because of the "new" features, which are essentially nothing more than just a program. If you had documentation for a video adapter (we tried to get it, but we were refused), for example GeForce 6600, you could easily make the necessary driver for any API that could create a command stream to apply the same DX11 effects on a simple 6600 or on any other chip and adapter!

Files

Important: to unpack the archive, you need to use an archiver that supports the 7z format, for example, 7zip(7-zip.org) or WinRAR(rarlab.com).