I'm trying to finish the last textures of the 1st Act of the game.
I have a big problem: I need a lot of time to surf the web, to look for pictures, textures, ... that i need to create the new HD textures.
Several guys have asked me about the release time of the 1st act.
Well, if you are not good with photo edit, maybe you still can help me, by sending me good pictures, textures, ... it will save me a lot of time, and i could do things faster this way.
I need pictures of materials like marble, wood, rocks, sand, asphalt, glass, bricks, ornaments, fabrics, metals, windows, doors, chairs, leafs, bark, ... if you have played the game, you should know the sort of pictures that i need.
The pictures must be for free use (do not use copyrighted pictures).
Once i finish the textures, i'll need more time to finish some details of the new version of the patch.
Still the new AA method does not fix the problems with the videos.
Under Vista x64, i have this problem with the videos, but, under XP32, they work flawlessly.
So, as final solution, i have coded a new cutscene.dll, that will replace the original dll used in the game. With this trick, the videos do work under Vista x64.
In this new version, the 'useOldFSAAmethod' & 'fsaaCompatibility' options are deprecated, due to some major changes in the AA code. Sorry, but i cannot mantain the backwards compatibility. The users who needed these options can use the new cutscene.dll to keep enjoying the videos. The new AA code is faster than ever & it's compatible with all the AA modes (it also uses less video memory).
I plan to release the demo of the HD textures this weekend.
I need to finish the configuration tool, and create the final packages for the demo.
You'll need the last version of the patch (1.5+) to use the HD textures.
There will be 2 packages with the HD textures this weekend.
The base package (400MB), and the extended package (900MB).
For each texture, there are 3 versions: low quality (DXT1 compressed), medium quality (DXT5 compressed) & high quality (uncompressed).
The base package contains the textures that you will need to play the ACT1. It's a very well balanced configuration between quality & speed. It uses DXT1 for the color & gloss maps, and uncompressed normal maps. This version works ultra fast in the 8800GTX at 1920x1200 MSAA 4x, max quality effects (the GTX280 should work fine with SSAA 2x).
The extended package contains the other 2 versions of each texture, not used in the base package. Ex: If the base package contains the 'medium' quality version of the texture 'wall01', the extended package will contain the 'low' & 'high' quality versions of 'wall01'.
This means that if you want to enjoy everything, and configure it manually, you'll need BOTH packages. But if you trust in my criteria, you'll only need the base package.
Someday, there will be a gfx card to run the game with the uncompressed textures. Something with 2GB, and 300GB/s should be enough. Meanwhile, a gfx card with 512MB and 60-100GB/s will work.
I feel a bit depressed lately, because nobody is interested in joining to the textures project.
Anyway, i keep working in the textures of the ACT2 (SD/HD):
I was planning to release ACT by ACT, but, after the experience with the ACT1 demo, i think that i won't release anything.
Therefore, i have returned to the work in the shaders of the game, and i eventually will work a little in the textures.
I started to work in a new shader for the blood pools. This is an early test, while i was trying to reverse engineering the original shader of the game:
Of course, this is just a test. I discovered that the game uses projective texturing to draw the blood pools, but, not with the standard texture matrix. It was hard & tricky, but, i finally found the coefficients.
After this discovery, i started to play with some perlin effects for the blood pools, trying to make it look more 'gore' (default/+gore):
As you can see, in the pic on the right, with the perlin noise fake bump map, the blood pool looks more 'gore'.
This is another test with other values:
Here, it looks more 'flat', but still with a lot of noise.
The effects have 'motion', so, you will see some sort of waves, moving around. The motion is slow, because the blood is a fluid with higher viscosity than the water.
I was planning to write another sort of shader, using the luminance of the surface below the blood pool. I could use that value, to add more relief to the blood pool.
Time will tell, but, i must write something spectacular for this shader, because 'blood' is in the name of the game ('BloodRayne').
Again, if you like what i do, and if you love the game, please, join to the textures project.
Another screenshot of the blood pools (Original / New):
Like i said, the new effect uses the luminance of the floor. It's a more realistic effect. Some users may prefer a red color with higher intensity, but, there is no problem, you can adjust the intensity of the red color in the shader, to match your personal 'gore' taste .
A friend started to work into a true Rayne HD skin.
He just started to work in her face, but, the result is truly impressive:
Btw, i keep working in the blood shader, among other things.
I'm also learning to optimize for CF/SLI, and i hope to double the speed of the patch in multi GPU systems in the future. The problem is that i do not own a SLI mobo, or several ATI cards to run on my X48. So, it will be hard to test the results.
Unrar, exec 'run_tests.bat', and you should see something like this:
The best time of my GTX285 in the 256x256 test was 0.024s, and the best time of my 3.6 GHz Xeon 3350 Quad was 0.65s (using the old tool that comes with my br2 patch). So, my GPU is running around 27x times faster than my CPU in this test. Finally, good results.
There is still a lot of room for optimizations, so, this is going really well.
There are some problems with the FP 'precision'. The ALUs in the GPU do not follow the IEEE FP standards, and there are some errors in the 1024x1024 test.
Unluckily, i was doing something bad, and the results of the benchmark are erroneous.
I have fixed them, and now the code is only 2.5x times faster than on the CPU.
Sucks, because this is with my GTX 285, and i was planning to use my old 8800GTX for the CUDA code, but, it won't end running much faster than my quad, and i know that my SSE3 Perlin code runs really good on those new Core i7.
Running Benchmarks ...
TF [128, 512] Total Time: 0.192191s
SM [128, 512] Total Time: 0.107221s
TF [256, 256] Total Time: 0.191223s
SM [256, 256] Total Time: 0.103024s
TF [512, 128] Total Time: 0.190813s
SM [512, 128] Total Time: 0.126796s
TF [1024, 64] Total Time: 0.189704s
SM [1024, 64] Total Time: 0.189470s
TF [2048, 32] Total Time: 0.189634s
SM [2048, 32] Total Time: 0.390741s
TF [4096, 16] Total Time: 0.198291s
SM [4096, 16] Total Time: 0.942939s
TF [8192, 8] Total Time: 0.255677s
SM [8192, 8] Total Time: 2.238887s
TF [16384, 4] Total Time: 0.435167s
SM [16384, 4] Total Time: 6.500768s
TF [32768, 2] Total Time: 0.856746s
SM [32768, 2] Total Time: 22.913676s
Best Config (Shared Memory) [256, 256]: 0.103024s
Running Verification Test at (Shared Memory) [256, 256] ...
Running Benchmarks ...
TF [512, 512] Total Time: 0.697142s
SM [512, 512] Total Time: 0.370065s
TF [1024, 256] Total Time: 0.692771s
SM [1024, 256] Total Time: 0.374493s
TF [2048, 128] Total Time: 0.690623s
SM [2048, 128] Total Time: 0.464357s
TF [4096, 64] Total Time: 0.688960s
SM [4096, 64] Total Time: 0.712639s
TF [8192, 32] Total Time: 0.690871s
SM [8192, 32] Total Time: 1.504626s
TF [16384, 16] Total Time: 0.702908s
SM [16384, 16] Total Time: 3.673776s
TF [32768, 8] Total Time: 0.974903s
SM [32768, 8] Total Time: 8.863379s
Best Config (Shared Memory) [512, 512]: 0.370065s
Running Verification Test at (Shared Memory) [512, 512] ...
Running Benchmarks ...
TF [2048, 512] Total Time: 2.361321s
SM [2048, 512] Total Time: 1.282897s
TF [4096, 256] Total Time: 2.369100s
SM [4096, 256] Total Time: 1.336673s
TF [8192, 128] Total Time: 2.361914s
SM [8192, 128] Total Time: 1.677807s
TF [16384, 64] Total Time: 2.360700s
SM [16384, 64] Total Time: 2.639611s
TF [32768, 32] Total Time: 2.360139s
SM [32768, 32] Total Time: 5.692210s
Best Config (Shared Memory) [2048, 512]: 1.282897s
Running Verification Test at (Shared Memory) [2048, 512] ...
It's 6.5x times faster than the CPU. It will be hard to make it faster.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum