in my mind the only way would be to use different passes with transparency and slightly different positioning to get the blur (just like the furshader works, but another way of positioning).
i dont think that a blur can be done in a single pass using blurformulas as u dont get the values of the neighbour-pixels

but how would you do it in a multipass-technique? that won't be possible, neither.
how do the rendermonkey-examples work, and how many passes do they use?

A small test map would be nice for us graphic noobs! Whats 2 or 3 mb's...

Here's a new Gamasutra article on realtime glow/blur using DirectX 7, 8, and 9:

http://www.gamasutra.com/features/20040526/james_01.shtml

NICE! theres hope...

Based on the Gamasutra article I got blur working in 3DGS. It uses render to texture so it will probably only work in commerical and pro. You need a 320x240 white pcx named 320x240.pcx in the path. You need to be running at 1024x768.

If you want to increase the blur you need to use a smaller image like 160x120 or 80x60. You also need to change the blurcam size_x and size_y to the same size as the image. Additionally you need to change the blurmap.x to fit the blurmap perfectly on the screen. 277 is perfect for 320x240. 69 is perfect for 80x60. Other resolutions (like 800x600) require a different blurmap.x.

As stated in the Gamasutra article there are artifacts but these can be mitigated by increasing the alpha of the blurmap. Making the blurmap less transparent also increases the blur. There will probably be less artifacts the more you blur too (less at 80x60).

---

Explaination of how it works:

You have Camera and Blurcam. Blurcam takes the exact same picture that Camera does except that it does NOT include blurmap in the picture. Camera has a view entity on layer 1 named Blurmap. Blurmap is a sprite (basically a panel) that is 320x240. Blurmap is transparent. Blurcam renders itself to Blurmap (render to texture). Blurmap (a 320x240 texture) is stretched across the 1024x78 view causing it be "blury" except that blurmap is also transparent and therefore you have the regular view and then the blury view superimposed on top.

Frame rate: The only frame rate hit you take is from the extra 320x240 render per view that Blurcam has to render. The blurrier the less of a frame rate hit you take (because the Blurcam render is smaller).

The frame rate hit I noted was LITTLE to NONE.

---

entity blurmap
{
type = <320x240.pcx>;
layer = 2; // display above view entities with layer 1
flags = visible,transparent;// visible on screen from the start
view = CAMERA; // same camera parameters as the default view
albedo = 0; // gouraud shading from sun position
x = 277; // place 277 quants ahead of the view
y = 0; // center horizontally
z = 0; // center vertically
}

view blurcam
{
layer = 0;
pos_x = 0;
pos_y = 0;
size_x = 320;
size_y = 240;
offset_x = 0;
offset_y = 0;
flags = visible;
}

function main()
{
blurmap.alpha=50;
blurcam.bmap=bmap_for_entity(blurmap,0);
cameramove();
}

function cameramove() {
proc_late();
while(1) {
vec_set(blurcam.pos,camera.pos);
vec_set(blurcam.pan,camera.pan);
wait(1);
}
}

---
No blur:



Blur (320x240):



Blur (80x60):

cool how do ya get the stretch part working? and where did 277 calculation come from?

i Have A6 Pro 6.22 i can see the blur map but it stays at 320 x 240 with the code above