UT99.org | Unreal Tournament Community

papercoffee wrote:What maybe work on concrete and metal parts don't quite fit at the crates. It looks too grainy.
If we could use displacement mapping ...this would be a huge improvement.
But bump-mapping looked ugly even when it was new and nearly every game used it.

FraGnBraG wrote:before you go any further you should go and play wootbulous from extreme woot ...

bump mapping plain old UT99 maps is wasting time imo - there's only a tiny audience left for UT99, and not many ppl will likely even care...

better yet, if you are new to UT mapping and want learn skills, why not just go learn how to make maps for UT4 ... ?

it is far more graphically rewarding (all aspects of the tech are just crushing UT99, sorry, sadly, but true) and get this, it takes far less
actual effort to do some crazy things than it does in UT99...

anyways, go find extreme woot - it's way better looking, with or without a bump-mapping driver.

Dr.Flay wrote:Rough as it may be, but I am glad to see someone try and take advantage of the newer features we have to play with.
1 playable proof of concept is better than none.
The size and quality of the textures you are adding bumpmaps to, will be the biggest issue.

Currently it looks like the crates belong in a cartoon or cell-shaded game.

var(Texture) texture BumpMap;    // Bump map to illuminate this texture with.

PrinceOfFunky wrote:

Dr.Flay wrote:Rough as it may be, but I am glad to see someone try and take advantage of the newer features we have to play with.
1 playable proof of concept is better than none.
The size and quality of the textures you are adding bumpmaps to, will be the biggest issue.

Currently it looks like the crates belong in a cartoon or cell-shaded game.

No eheh, 923KB of Textures with BumpMaps, Bump maps are made on purpose to avoid big sizes(for textures and maps), that's the cool thing, instead of adding 30 bricks and increase the map size, you make a bumpmap that makes the CPU calculates lightmass like that surface is made of 30 bricks, and the cool is that you can use that bumpmap on every texture, making any texture you want looks like having 30 bricks(This means, you don't need 20 wall bumpmaps for 20 wall textures, you need only 1 bumpmap for 20 wall textures ).

Problem on Unreal is, that if you set a standard texture to own a bumpmap, the texture package will be different, so you better export the standard texture, reimport it into another package and, then, let it owns a bumpmap. [Probably this could be fixed with a script, hoping the bumpmap is not a constant].

EDIT:

Code: Select all

var(Texture) texture BumpMap;    // Bump map to illuminate this texture with.

Rly good, BumpMap variable is not a constant, I will provide to create a script that changes bumpmaps at runtime, so there will be no need to create another package for the standard textures.

sn260591 wrote:

PrinceOfFunky wrote:

Dr.Flay wrote:Rough as it may be, but I am glad to see someone try and take advantage of the newer features we have to play with.
1 playable proof of concept is better than none.
The size and quality of the textures you are adding bumpmaps to, will be the biggest issue.

Currently it looks like the crates belong in a cartoon or cell-shaded game.

No eheh, 923KB of Textures with BumpMaps, Bump maps are made on purpose to avoid big sizes(for textures and maps), that's the cool thing, instead of adding 30 bricks and increase the map size, you make a bumpmap that makes the CPU calculates lightmass like that surface is made of 30 bricks, and the cool is that you can use that bumpmap on every texture, making any texture you want looks like having 30 bricks(This means, you don't need 20 wall bumpmaps for 20 wall textures, you need only 1 bumpmap for 20 wall textures ).

Problem on Unreal is, that if you set a standard texture to own a bumpmap, the texture package will be different, so you better export the standard texture, reimport it into another package and, then, let it owns a bumpmap. [Probably this could be fixed with a script, hoping the bumpmap is not a constant].

EDIT:

Code: Select all

var(Texture) texture BumpMap;    // Bump map to illuminate this texture with.

Rly good, BumpMap variable is not a constant, I will provide to create a script that changes bumpmaps at runtime, so there will be no need to create another package for the standard textures.

Not necessary to edit packages. D3d10 can use external textures http://kentie.net/article/d3d10drv/page2.htm#overrides
Example:

d3d10_test.zip

sn260591 wrote:Paint.NET has supported dds.