[Terrain texture blending]

Vertex blending is much worse. Think vertex shading vs per-pixel shading. Also since the heightmap and texture max seem to have the same resolution, it would basically have the same affect.

I doubt that. See this page for example before and after shots. The 'before' shot looks essentially identical to our current terrain blending.

[Terrain texture blending]

Have any of you heard of something called 'vertex blending' or 'vertex color blending'? I can't find any really concise information about it, but it sounds like a way to do it without any masks.

[Terrain texture blending]

Blending of two different terrain textures currently look quite bad:

Any ideas for how we might solve this?

(Relevant ticket.)

[Post-processing effects test (SSAO/HDR/Bloom)]

For a slight diversion I thought it would be interesting to look at some fancier waves. I found this webpage provided an efficient approximation. Perhaps we could use it to create a wake around boats? I don't think it would work very well for ocean waves since it needs artificial damping or reflections off the coast will make it go wild.

http://freespace.vir...ics/x_water.htm

I turned it into a javascript+canvas demo so you can see what it looks like.

http://dl.dropbox.co...sion/waves.html

I doubt this would scale to a full lake or river, because we can't tile it like the current water shader. You would need to run a full simulation of the entire body of water at all times or you would get weird artifacts where the ripples would cut off when you move the camera.

Cool demo, though.

[Post-processing effects test (SSAO/HDR/Bloom)]

I've committed the fix for the waterShader branch, it should work but there might be a place I forgot.

It's working (save for a minor fix)! Water has never looked so pretty on this crummy netbook.

Well done.

[Post-processing effects test (SSAO/HDR/Bloom)]

I did this:

TEMP temporary;
MOV temporary, 0.8;
POW fresnel, fresnel.x, temporary.x;

Which seemed to work, because now the error has moved to another line:

ERROR: Failed to compile fragment program 'shaders/arb/water_high.fp' (line 93): line 90, char 45: error: expected scalar suffix
ERROR: CRenderer::EndFrame: GL errors occurred

If you can fix all errors of this type and push to Github, I'll pull and try again.

[Post-processing effects test (SSAO/HDR/Bloom)]

Actually, since it's two inputs, but one output, it should work.

I see.

The thing is that it seems to consider that "1.0" is not a scalar, for some reason... On my computer, there's no issue, which further baffles me.

Yeah, I'm using an Intel card so all bets are off Could it be that it has a problem with literals and you'd need to MOV the values into variables first?

[Post-processing effects test (SSAO/HDR/Bloom)]

According to this spec, the POW instruction takes 2 inputs while you seem to give it 3:

	  Instruction	Inputs  Output   Description
	  -----------	------  ------   --------------------------------
	  POW            s,s	 ssss	 exponentiate

[Post-processing effects test (SSAO/HDR/Bloom)]

That's strange... There is no reason for it to crash at this particular point. You're sure you haven't changed anything?

I'm positive. I even did a 'git reset' and recompiled to be certain.

Does it work it you replace the line 76 with something like:

POW fresnel, 0.5, 0.8;

If I do that, the error 'moves' to char 14:

ERROR: Failed to compile fragment program 'shaders/arb/water_high.fp' (line 82): line 76, char 14: error: expected scalar suffix
ERROR: CRenderer::EndFrame: GL errors occurred

[Post-processing effects test (SSAO/HDR/Bloom)]

If preferGLSL is false and you're using the Shader path, you're definitely using ARB shaders. Mess up the GLSL shaders, run the game, if you don't get an error...

Ah, yes. I deleted shaders/glsl. The result is the same.

Also, I get this error:

ERROR: Failed to compile fragment program 'shaders/arb/water_high.fp' (line 82): line 76, char 25: error: expected scalar suffix
ERROR: CRenderer::EndFrame: GL errors occurred

[Post-processing effects test (SSAO/HDR/Bloom)]

This is what I get with the waterShader branch:

Also, the surface is static (unanimated).

By the way, does anyone know of a way to ascertain that I am using the ARB shader?

[Post-processing effects test (SSAO/HDR/Bloom)]

Woah, careful. Why is your diff looking like this? Did you mangle the line endings?

Seems like it:

$ file source/renderer/TerrainRenderer.cpp
source/renderer/TerrainRenderer.cpp: ASCII English text, with CRLF line terminators

historic_bruno seemed to have issues with this too - maybe he can chime in with a solution...

[Hoplite animations]

I just found this on 0 A.D.'s Facebook wall: motion captured Hoplite animations

(Didn't remember seeing it posted elsewhere on the forum, sorry if duplicate.)

[Post-processing effects test (SSAO/HDR/Bloom)]

You may want to keep the water-related and model-related code changes separate, so see if you can create a new branch (from the master branch) for the water.

And if you don't know how to do branches just yet, I can even do them for you. Such is the glory of Git. Main thing is that you get the code up so we can begin tinkering with it.

[Post-processing effects test (SSAO/HDR/Bloom)]

Github is the ideal solution if you want feedback on your code so you can clean it up prior to it being submitted to Trac. They have many good tutorials themselves, starting here. You will want to fork myconid's repo once you're set up. It should all be quite simple and even enjoyable once you get started.

[Bug in actor editor under Linux]

I see. I'll try building again with that flag on.

Okay, now I don't get any errors in Atlas, but the original issue has reappeared Not sure what happened, since it is not likely to have anything to do with GL being enabled. Maybe I misinterpreted the result of my first test of 2.9 and the issue was never fixed in the first place.

[Post-processing effects test (SSAO/HDR/Bloom)]

I'll try to see if I can port your glsl shaders to arb, which seems to work.

If you manage to convert all the modelmapping shaders to ARB, that should increase the chance of getting them into A11 considerably (because it would remove the need for an unwieldy GLSL compatibility database).

If you feel like pushing any of your work to Github, I'd be happy to help test/debug.

[Post-processing effects test (SSAO/HDR/Bloom)]

We could easily, once we fix http://trac.wildfire...om/ticket/1514. The problem is pulling in possibly untrusted code from third party sources, compiling and distributing that EXE, especially if it's some kind of automated process.

True. Maybe if you all become more keen on using Git one day, someone trusted could maintain a more liberal 'experimental' branch separate from the main trunk - a lot of OS projects seem to do that.

And there's a few different branches, I'm not sure which one would be best for demonstration.

Personally, I would use 'modelmapping' since the normal/parallax stuff seem to have the greatest near-term impact for artists.

[0 A.D. on YouTube]

Here's a video I did for my channel, Lazy Game Reviews. Love the game!

Nice video. I'd like to know the story behind the palm obelisk too

[Terrain erosion]

Cool!

[Terrain erosion]

Nice, but I am wondering what was autogenerated and what was authored? The heightmap was generated randomly and then 'flooded' to some height level? To which degree can the layout be controlled?

[Random Map Script: Corsica vs Sardinia]

It needs this.

On a general note, if #1493 is accepted, we can do opacity map type of things, so we can blend grass and sand textures, for instance, like this:

[Post-processing effects test (SSAO/HDR/Bloom)]

As an aside - For guys who have been around a while (like me) I think there is a level of irony that a windows .exe of your patch hasn't been readily available for testing purposes.

We should make the autobuilder capable of working off Github branches so all these kinds of features can be developed in cooperation with the artists who should use them.

[Dynamic Water]

That is actually intentional (unless you can give examples where it is not due to the viewing angle, of course).

[Bug in actor editor under Linux]

I see. I'll try building again with that flag on.