Quote:

---

Yes Bloom if not optimised can kills FPS on some engines.
Some blooms do not require pixel shaders like in Blitz3D (DX7 engine) demos.
I think you could have a faster bloom if you would use BLitz3D trick.

---

You're right, there are a lot of great tricks to get bloom without pixelshaders... A6 just isn't well set up to do a lot of them without additional render code in a DLL....

And this is why I'm writing my own renderer now .

Quote:

---

For A6? Meaning we get more fancy shmancy effects??
Btw I like the bloom, but its a little hard to get the effect to blossom more.

---

No, Ben (Wizrealms) and I are developing a new engine, called CRUTCH3D. Pretty early in development yet.

I tinkered some with it in the WACAI "dust" style demo, and added a tinting ability to it to make it so it can be tinted red when you get injured, it looks bloody awesome (literally ). Reminds me some of the hit effect in Call of Duty 2. The demo still runs at 60fps on my system too.

Might post a demo and screens sometime.

Quote:

---

Humm ya using box blur for bloom or gaussian blur? Your blur look pretty different compared to our blur. (check the Rabbit Engine thread at Tools forum) When we use bloom in our engine the fps goes down almost by half. Our bloom is pretty simple:
Render to texture (with FBO)
Down sample 1/4 of the screen
Horizonal blur pass
Vertical blur pass
Combine

Creates pretty nice and strong bloom... Though box blur aint the best for bloom...

---

Quote:

---

@Rhuarc
Okay . Humm the reason for the big fps cut in our bloom is probably because the scene is very simple so even the littlest additions affect the fps pretty much. If it would be bigger, then the fps would be more stable I guess. But good luck on your engine .

---

Yeah. that will do it .

It helps to use a per-poly/textel framerate calculation in your framerate "performance" factoring to figure what your actual performance hit is. Usually more work than it's worth though . It does make for an "ok" benchmark though.