FOSS gamedev and creative worlds

An idea for cutting back on the tiled look:
Create multiple (like 5) extra textures for each node.
The nodes would, at runtime, be randomly assigned a texture from their node type.


A stone example with only one extra texture, and a poor one at that:

Sounds like the "repeating" or "random" textures of MCPatcher. I would like to see those too, ideally without having to edit any Lua code so that texture packs can implement it by themselves.

I'll just leave this here:

http://wiki.flightgear.org/Procedural_Texturing

It could be done like soundfiles: Texturepacks can provide <texture_name>.n.png, where n is 1 - 9.

PilzAdam wrote:It could be done like soundfiles: Texturepacks can provide <texture_name>.n.png, where n is 1 - 9.

That is a good idea.

PilzAdam wrote:It could be done like soundfiles: Texturepacks can provide <texture_name>.n.png, where n is 1 - 9.

thats a realy good idea

PilzAdam wrote:It could be done like soundfiles: Texturepacks can provide <texture_name>.n.png, where n is 1 - 9.

+1 I like this idea too, however, doing this like sound files (ie randomly) could result in different tiling each time a scene is rendered.
Perhaps using the node coords as a seed would ensure the same texture will always be used at any given location.

stu wrote:+1 I like this idea too, however, doing this like sound files (ie randomly) could result in different tiling each time a scene is rendered.
Perhaps using the node coords as a seed would ensure the same texture will always be used at any given location.

I don't see why this would be a problem, the textures should be similar enough to not make any sort of noticable difference.

John1 wrote:

stu wrote:+1 I like this idea too, however, doing this like sound files (ie randomly) could result in different tiling each time a scene is rendered.
Perhaps using the node coords as a seed would ensure the same texture will always be used at any given location.

I don't see why this would be a problem, the textures should be similar enough to not make any sort of noticable difference.

True, but it would still be best to do what stu said.

PilzAdam wrote:It could be done like soundfiles: Texturepacks can provide <texture_name>.n.png, where n is 1 - 9.

One further possibility might be to use additive or alpha-blitting (such as is done with minerals) to obtain exponentally many permutations from a few, canned textures. By inserting a local method call into "tiles=" and using maybe using something quick-and-dirty for pseudo-random generation, it could all be done quite "cheaply" in Lua.