I think my graphcis card should support 32p float bitmaps, because i'm using them in my own shaders (but not in this project)
Model: Radeon HD 6870

@BoH_Havoc

o.o ( <= my face right now )
sooo nice!

But I've got a little question:
If I'll use this in my projects, am I allowed to modify it?
I thought about using the bloom shader from my own HDRR-Shader pipeline instead of the standard shade-c one ( I don't like it that much )

but except this I totally love the new version!

@MasterQ32: I was talking about filtering 32bit floating point textures, not being able to use them Your HD 6870 should be more than capable to filter them though.
Can you confirm that the spotlight shadows are always soft? That would at least give me a point to start from

@Kartoffel:
Of course you are allowed to modify it. You are actually encouraged to modifiy it anyway you want. Let me know when you implemented your HDR pipeline and i might implement it into the main version if it's fast, along with a free license for you
Please keep in mind that i plan to add LogLUV encoding to the pipeline where its needed. So in the end we might get away with standard argb8 textures. It might be a good idea to wait ~7 days before you try to add your own hdr pipeline as i plan to add logluv in the next days (mainly due to the lighting buffer having some banding artifacts).
If you have a better bloom shader at hand, along with tonemapping and whatnot, please give it a try. I too am not to satisfied with the current bloom.

Here's a list of current tasks, so you know whats coming up: https://github.com/BoHHavoc/ShadeC-EVO/issues?milestone=1&sort=created&state=open

@BoH_Havoc: Honestly, do you ever see an (Finished) end for Shade-C? God, i tried the latest version yesterday and i was shocked...
Sure it looks nice and runs fast but...
i was one of the betatesters of the version right before that (where you implemented MLAA, SSAO etc) and ALMOST EVERYTHING changed again!!
now its not required anymore that models need an action assigned and all the setup commands/parameters have totaly changed.
Plus Im on A7 and had to realize i have no sunshadows anymore (yes because i dont have PSSM)
what will happen if there is A9 now with totaly different stuff in there again? You have to rewrite all again??

And when I look at the To-Do List i see alot of work ahead (im not into shaders) and by the Time thats ever finished all the other AWESOME(!!!) Stuff you implemented will be outdated again.

Now i understand why you want other users to work on Shade-C too, but i cant imagine how that will work...
I know you work close to the CSiS Guys and you probably handle all the changes better then i do, but for none-CSiS users its just best to wait for the final product.
But again BoH_Havoc, I really appreciate what you do, and I NOT say its your fault as you kept saying its all stil in Development.

If you mean those other shadows which are soft on my screenshot, yes
only the moving (i think sun-) shadows were like this, but not all the time, only at certain sun angles (i can give you more information later, when i'm at home)

@chris:
i think every piece of software in development changes like this. sometimes you just get an idea which is 10x times better than the previous version. then you change it and while you change it the same happens twice again. so yes, end users should wait for the final release or adapt their code (which isn't that hard)

sounds awesome !

BUT: Im not very experienced with shader programming so my code is probably not very clean/efficient.

Anyways, I'll do this within this or the next week (haven't got very much time at the moment)

Here's a screen of my shaders, just for you to see how the bloom actually looks like:

For my bloom I'm using alpha-blending instead of add-blending which prevents overexposure and gives it a smoother look.
It also allows me to make the bloom much more visible without looking bad.

EDIT: I just read this: So I'll wait and try to make my shader-code better

@chris_oat: there won't be any more major changes anymore as i'm tired of them myself (as well as the CSiS guys). Plus i really like the pseudo oop sytle Shade-C has now, which also makes it easier for myself to change things without changing the way to use it. I'll try to add the "old" sun-shadows again.

@Kartoffel: That bloom looks nice, i'll give alpha blending a try


Small Update:
Added Antialiasing in form of MLAA.
https://github.com/BoHHavoc/ShadeC-EVO

I did this today (the shade-c code is really good commented!)
I also added a 2nd blur-shader to make it smoother.

the result is not bad, but the lens flares which are added in the same step as the bloom is, don't look very good with alpha blending

Edit: Here are some screens for comparison. Left alpha-blending, Right add-blending.


oh and I found a bug. I'm not sure if you already know it, but if I run the application in fullscreen mode and switch to my desktop (Alt+Tab)
and switch back to the application again there aren't any pointlights or pointlight-shadows anymore, only the sun with PSSM is still there
edit: oh actually they are spotlights

I found something else, though I think it may just be me. When I try to add shade-C to my project All I get is a blue screen (Background color) once shade-C gets called. I found it has something to do with the "sc_screen_default = sc_screen_create(camera);" line. I will keep experimenting to see what the issue could be. Could there be anything I am doing wrong? Also, I get a "script error in: sc_forward_destroy" error. Any idea why?

Its setting your camera to origin. I had this bug really often.