First of all, I'm not professional such as Valve guys... Should that mean that there is no way for me to make cool and fast FPS game?
I've made really fast movement and weapons (did everything I could do to make it fast!), but placed grass models and 20-40 fps?!

LUA is interpreted and thus by definition slower than Lite-C. Given a good compiler, C is one of the fastest languages available. Here is a nice comparison:
http://shootout.alioth.debian.org/u32/wh...&calc=chart
(I'm not saying that the Lite-C compiler produces equal fast output as GCC, plus I'm also pretty sure that Clang-LLVM can produce even faster code).



No, I'm not saying that you can't do it. I just wanted to point out that everyone has to put some thoughts into performance.
Plus, your problem was already pointed out by Nils, the problem is the heavy alphablending. A task which isn't done by the engine but by your graphic card so blame it if you want to blame something

I have never seen a good looking big 3d shooter running fast with this engine, nor done by myself or any other person around in this forum. Show me, then i believe.

I've already said that I've tested compiled version of my project with my other PC, and it has NVIDIA GeForce GT 430.
I've played a lot of great games with high settings on it, games which require tough PC, and I'm getting 20-40 fps with 80 bushes?

Afair it was you who accused A8 to be slow so actually its your task to prove it
Beside that, why should I put time and effort in something that doesn't even remotely interest me? Like I said, its not easy but its doable.

Making good games needs a lot of time, knowledge and experience. If you lack one of those things, you won´t be able to create good/complex/big games. There are endless tricks to make things fast and if you start with doing the worst thing possible performance wise, which is alphablending with lots of pixels, you do something wrong.

About the 6 Zombie example, what shaders do you use, how are the zombies animated, are you using stencil shadows?
99.99% of the shaders around are extremely slow, because they where never really optimized in any way and just thrown together by beginners, as for example me 5 years ago. Bone animations on the CPU are also very slow, because it needs your vertex data on the gpu to be updated every frame, while doing it in a shader is a lot faster, especially in combination with tangents, depending of your models, this can speed things up like 10 times and a best case scenario. Stencil shadows in gamestudio are really slow. Don´t use, or use very lowpoly meshes for them.

Edit: There usually is a reason if things are slow and most of the time, there is a solution, which has nothing to do with the engine.

I did everything I know (what I got from the manual) to make things fast...
Ok, framerate problem is my bad, not only mine but my old outdated graphic cards...

I dont use any kind of shadows cause then is everything over ^^

I used the std. mtl_specBump shader and animated them via ent_animate (bones). The model itself had +-4.000polys. 512x512 dds texture.thats it.

But i dont want to talk much about it, i just wanted to say i have fps probs too (nearly always).

That shader needs tangents, if you would do the animations in a shader it could very well be a LOT faster.

How can i do that ? As u know iam a shader noob. U have an example of that ?