[Rodo]

I got some issues to report... I was just testing this on a regular test mission I got and it seems that motion blur is always active, and some of the ships seem to get a weird texture problem on the radar window, here's a pic of that weird radar window problem:




Here are my specs:
C:\Games\FreeSpace2\FS2_PP_R.exe -mod testing,mediavps -spec -glow -env -mipmap -nomotiondebris -noscalevid -missile_lighting -normal -3dshockwave -post_process -cache_bitmaps -dualscanlines -targetinfo -orbradar -rearm_timer -ballistic_gauge -ship_choice_3d -weapon_choice_3d -3dwarp -warp_flash -snd_preload  -ambient_factor 50 -spec_exp 11 -spec_point .6 -spec_static 1 -spec_tube .5 -ogl_spec 82 -fov .88

attached the mission file if you want it to test

the problem with the textures does not happen when the post processing option is deactivated in this very same build.


[attachment deleted by Tolwyn]

[Kiloku]

How do I install it? I download the package, but don't know what to do with it..

[asyikarea51]

Wow all those overdone effect pics in pecenipicek's post on page 5 make even the simplest explosions and jumps look like a repeat of the Capellan supernova explosion... COOL!!!!

[Aardwolf]

I'd like to point out that applying bloom to the background makes it looks weird.

A solution in other games that use bloom is to use another channel (e.g. the alpha channel, if it's available) to store how much "extra" brightness stuff has... backgrounds would have no extra brightness, and glowy things (e.g. engines, or lasers, etc.) would have an alpha channel to control that...

But that might not be so easily doable in FS2.

[pecenipicek]

actually, there is an alternative... screw the texture channels. yes, it gives much more control over the effects. do you really need that actual control or would a simple table based number suffice? (a float of course)

[Colonol Dekker]

Hmmm, bloom and motion blur together appear to kill my framerate

[Kiloku]

Pleeease, someone teach me how to use it

[Colonol Dekker]

Does this not cover it?

Hi,
I thought it would be nice if fs2_open supported post-processing...

Full pack (patch, builds, demo mission, shaders)
Original pack (with some bugs): Full pack

Almost everything (but HUD and some other things) is rendered to a texture (using Frame Buffer Object) and then drawn using shaders pair "post-*.sdr". This enables huge number of new effects to use in fs2_open, I've implemented the simplest ones: (de)saturation, contrast, distort noise. Additionally, now it would be easy to implement full frame motion blur.

In order to customize post-processing effects I added three new sexps: set-saturation (0% - 100%), set-contrast (from -100% to +100%), set-distort-noise (0 - 100).

I believe this patch can be improved in the area of code reusability - I'm still not very familiar with all source code and fs2_open internal architecture doesn't help. Any feedback will be appreciated.

Post-procesing requires glsl and fbo enabled and flag -post_process set.

Example Screenshots:
Saturation: 0%
Saturation: 0%, Distort Noise: 50
Saturation: 100%, Distort Noise: 50

Demo mission after 5 seconds sets saturation to 0, then after next 10 seconds sets distort noise to 50, then after 15 seconds sets saturation back to 100% and finally after 10 seconds sets contrast to +25%.

[Kiloku]

no.. I download the pack, but don't know what to do with it

[sigtau]

Now all we need is a pixel shader for the warpout so the clipping isn't as bad.

[Rodo]

no.. I download the pack, but don't know what to do with it

here's what you need to do.

place the exe's on the root directory of FS, rename them as you like.

place the .patch on the FS root directory as well.

Create a MOD folder, name the mod folder whatever you like, add a mod.ini with all the fuzz you want (with this I mean add the mediavps and anything else you want to use the mod ini) then create the data/effects and data/missions folders in the mod one.
Now place the .sdr files on the effects folder, then place the mission on the mission folder.

Run the Launcher, select the exe, activate the post-processing option in the graphics tab, and you should be ready to go.

Note that the post processing effects are activated from SEXP's so you need a custom made mission to activate-deactivate them, pecenipicek's mission works just fine.

[Reprobator]

I'd like to point out that applying bloom to the background makes it looks weird.

A solution in other games that use bloom is to use another channel (e.g. the alpha channel, if it's available) to store how much "extra" brightness stuff has... backgrounds would have no extra brightness, and glowy things (e.g. engines, or lasers, etc.) would have an alpha channel to control that...

But that might not be so easily doable in FS2.

I'm affraid taht alpha channel's are generally already busy.
But you are right, i ve test it with a custom planet (a blue planet and it looks quite strange) but the same effectg applyed to sun and nebula looks good imo

[pecenipicek]

no.. I download the pack, but don't know what to do with it

here's what you need to do.

place the exe's on the root directory of FS, rename them as you like.

place the .patch on the FS root directory as well.

Create a MOD folder, name the mod folder whatever you like, add a mod.ini with all the fuzz you want (with this I mean add the mediavps and anything else you want to use the mod ini) then create the data/effects and data/missions folders in the mod one.
Now place the .sdr files on the effects folder, then place the mission on the mission folder.

Run the Launcher, select the exe, activate the post-processing option in the graphics tab, and you should be ready to go.

Note that the post processing effects are activated from SEXP's so you need a custom made mission to activate-deactivate them, pecenipicek's mission works just fine.

important note, the .patch file can be safely ignored, since its just the code difference file. aka, source code which is just there for the sake of convenience.


in general, if you dont know anything about modding people, please dont use it, since it most likely wont work for you.

[portej05]

in general, if you dont know anything about modding people, please dont use it, since it most likely wont work for you.

A note for modders also: Please don't rely on these changes - this really is proof of concept stuff - it may not be in this form when it ends up in trunk.
Note that this is the sort of thing that Antipodes is created for, so it will end up there first.
If you haven't tested Antipodes #2 please go and do that because Hery's unified shader patch is being staged there for a little longer before going into trunk.

[pecenipicek]

i did some minor testing. can you incorporate the most recent motion blur into the antipodes too? would be better to test it all together.

[Solatar]

I've been playing almost exclusively with this bloom build and the antipodes #2 for awhile to test. Only issue I've had with this post processing build is that if there's too much stuff on screen, the build ****s itself and just turns black. Doesn't happen too often, but some ITHOV missions caused it.

[pecenipicek]

the FBO buffer overflows itself and craps out. i believe it might be related to the number of ships on-screen or the number of textures loaded. or the overall brightness of something... in any something somewhere needs to be clamped in short.

[falcon2105]

Do normal maps have to be enabled/working for this to work? Or has anyone tested this on the famous ATI x1xxx cards that have had about a bagillion issues with fso? Cuz my normal maps don't work and i have an x1650pro and this doesn't work when i have normal maps disabled, and when i have normal maps enabled (which normally makes my game freeze) the game freaks out in a new fantastic way (sound continues to play, screen gets all garbled up).

[pecenipicek]

if you want any of these to work, use a more recent card. its extremely unoptimised code first of all, second of all IT IS NOT, and i emphasize IT IS NOT SOMETHING THAT YOU SHOULD ACTUALLY USE OTHER THAN FOR TESTING.

[Solatar]

Or if you have, like me, fallen in love with some of the bloom and decided to use it on an almost regular basis, be prepared for plenty of bugs and slowdowns.