+1

Finally got my native Lite-C hashmap working (STRING*, void*).
Converted a terrible written c library into the
terrible Lite-C c like language.
Especially the variable types in Lite-c have given me a headache.
Why not supporting unsigend datatypes, why is no real short type implemented?
Why can I convert a char value to an int, but not vice versa?

shadowmapping is close to black magic, especially the variance calculations.

imo shade-c is great but will be always rewritten this is one reason why I use the old 0.91 and take out what I need. the other reason is that the new Evo is not free to use. it has great features, but also there are a lot of bugs, and lacks a flexible interface, and a lot of important things are simply missing. but definitely okay for learning purposes, and as a base to make your own shaders.

+1

thanks for the nice feedback!

however, I don't think I'll release the pipeline... It took me very long (should be more than a year by now) to get the results you saw on the screenshots I've posted.

If you contribute to shade-c evo you can use it for free.

it's a good news. probably I'll check evo in the future, I hope I can do some useful things... but currently 0.91 is complex enough for me to explore step by step, and evo lacks water and terrain shaders I badly need, which is fine in 0.91, after I partially rewrote them...

What about selling licenses?

And again: +1

Nobody succeeds in developing a working shader framework in GS and those who can won't give it away

I'd also pay for it if it works fine!

Me too.

me2