Oolite Bulletins

Smivs wrote:

The illumination map (white ellipses on a black background) also seems very bright, even when the ship is facing the sun. How do I reduce the effect? Do I just make the White Grey or is it not that simple.
TIA for any help/advice.

[materialTest.runTest]: Running test full:6 (diffuse_map + emission_map + illumination_map). 
[materialTest.runTest]: Running test full:7 (diffuse_map + emission_and_illumination_map).

Smivs wrote:

I've got emission maps OK (and have successfully used them) but my problem now is that I want to use an emission map and an illumination map on the same model (I am trying to give ships lit cockpits and portholes (emission map) and hull spotlighting (illumination map).

• Oolite does all the necessary processing when you use illumination and emission maps in non-shader mode, but to make it save the new emission map you need to build it yourself and change “#define DUMP_COMBINER 0” to “#define DUMP_COMBINER 1” in OOCombinedEmissionMapGenerator.m. I appreciate that this is a tad inconvenient.
• In a layer-based editor such as Photoshop, Acorn or GIMP: put the diffuse map in the bottommost layer, then the illumination map in Multiply mode, then the emission map in Lighten mode.

Smivs wrote:

I've got both working independently, but when I try to use both, only the emission map seems to work, or just the illumination map if I reverse the order they appear in the code.

Smivs wrote:

Code: Select all

materials = 
{ 
    "python_redux.png" =
    {
        diffuse_map = "python_SS.png";
        emission_map = "python_em-map_SS.png";
        illumination_map = "python_illum-map_SS.png";
    };
};

Smivs wrote:

The illumination map (white ellipses on a black background) also seems very bright, even when the ship is facing the sun. How do I reduce the effect? Do I just make the White Grey or is it not that simple.

Eric Walch wrote:

Smivs wrote:

The illumination map (white ellipses on a black background) also seems very bright, even when the ship is facing the sun. How do I reduce the effect? Do I just make the White Grey or is it not that simple.
TIA for any help/advice.

According to this you can add a multiplier for the emission map but not for the illumination map. But making white a bit more gray will reduce the effect.

Displaying both maps at the same time is possible and is also used in the material test suite on cube 6. And this test runs okay with me.

Code: Select all

[materialTest.runTest]: Running test full:6 (diffuse_map + emission_map + illumination_map). 
[materialTest.runTest]: Running test full:7 (diffuse_map + emission_and_illumination_map).

And you can merge both maps by putting the illumination data in the alpha channel of the emission map as shown on cube 7.

Ahruman wrote:

The suggested approach is to convert the maps into a single emission map. This can be done in two ways:

• Oolite does all the necessary processing when you use illumination and emission maps in non-shader mode, but to make it save the new emission map you need to build it yourself and change “#define DUMP_COMBINER 0” to “#define DUMP_COMBINER 1” in OOCombinedEmissionMapGenerator.m. I appreciate that this is a tad inconvenient.
• In a layer-based editor such as Photoshop, Acorn or GIMP: put the diffuse map in the bottommost layer, then the illumination map in Multiply mode, then the emission map in Lighten mode.

Ahruman wrote:

Smivs wrote:

I've got both working independently, but when I try to use both, only the emission map seems to work, or just the illumination map if I reverse the order they appear in the code.

This is highly unlikely. The order things appear in a dictionary should have no effect whatsoever. It’s more likely that you’re seeing a pattern that isn’t there. (are you holding down shift while restarting Oolite?)

Ahruman wrote:

The only reason I can think of for something like that would be if you were using a graphics card with only two texture image units. You can get your texture image unit count by running the material test suite, or with console.glFragmentShaderTextureUnitCount in the debug console.

Ahruman wrote:

Smivs wrote:

Code: Select all

materials = 
{ 
    "python_redux.png" =
    {
        diffuse_map = "python_SS.png";
        emission_map = "python_em-map_SS.png";
        illumination_map = "python_illum-map_SS.png";
    };
};

There’s nothing obviously wrong with that (except the lack of a namespace prefix on the texture names), but I can’t really say more without the files.

Ahruman wrote:

Smivs wrote:

The illumination map (white ellipses on a black background) also seems very bright, even when the ship is facing the sun. How do I reduce the effect? Do I just make the White Grey or is it not that simple.

That’s generally the best way. Using a modulate colour as Eric alluded to might preserve subtle detail better on some hardware in shader mode, at a very small performance penalty.

The material documentation is currently outdated. The modulate colour for emission maps is now emission_modulate_color, and for illumination maps illumination_modulate_color.

The best, most up-to-date example of this stuff is the material test suite.

Smivs wrote:

I really haven't got a clue what the first bit means but the second method looks like something I could try. I use Gimp. Do I save the resulting image as a .png or will it have to be a .xcf to preserve the layers?

Smivs wrote:

Sorry to be dim, what's a namespace prefix?

Ahruman wrote:

Save it as PNG. Oolite has no use for layers – the point is to do the compositing work in advance, not provide a different way to tell Oolite to do it.

 emission_map = "whatever-its-called.png";

Ahruman wrote:

Smivs wrote:

Sorry to be dim, what's a namespace prefix?

When looking up files by name, Oolite doesn’t distinguish between different OXPs (or the game itself) – all names are in the same category, or “namespace”. If two OXPs have identically-named files, they will collide and only one will be used.

The way to avoid this is to prefix each name with something intended to be unique, such as your own name, thus establishing your own “namespace”.

In other words, your textures should have names like “smivs_python_em-map_SS.png”. The same applies to models, AIs, and global script identifiers like script names and mission variables.

Smivs wrote:

Ahruman wrote:

Save it as PNG. Oolite has no use for layers – the point is to do the compositing work in advance, not provide a different way to tell Oolite to do it.

OK, thanks, so how do I reference it in the code...an emission map is

Code: Select all

 emission_map = "whatever-its-called.png";

what should I call this multi-layered composite thing?

DaddyHoggy wrote:

Thing is smiv in years to come - tracing a dodgy something-or-other in an OXP - will anybody (including you) remember SS stands for smiv's ships - at least with your name at the front we'll be able to hunt you down...

Smivs wrote:

Is this because the backgrounds to the emission and illumination images are black?

Ahruman wrote:

Any messages in the log?