First of all, I never said 'evil', that's what you make out of it. Apart from that, you've misunderstood my comment, but I doubt you'd understand anyway.

I've shown screenshots of work in progress on my website in the past. For various reasons I have not shown them here on the forums, mostly because it wasn't finished anyways. I definitely could show a few screenshots of my latest projects, but except from the fact that it proves that I am working on games, it doesn't prove A7 is on par with Unreal Tournament III, nor Torque for that matter and so on. The graphics really are okey, but no way near AAA. So, in a way it would be a waste of time showing my work in progress anyways because it would never be 'good enough'.



I never said WED blocks, I haven't made a level with blocks since the last version of A5. I in fact wondered if you tried to make a level inside WED instead of importing. You can stitch together models in WED too you know, instead of importing geometry. You should have figured that out by now.

Okay, I explain it more deeply for you:
The advantage of static meshes in Torque Constructor, WED, Lawmaker or in the Irrlicht editor is: You can compile static shadow maps on top of the geometry. Every static mesh can cast and receive shadows (at least it should work like that, if the shadow compiler works properly and it does in all of the mentioned tools except of WED).

Now try that with models! It will not work in WED.
You have to bake shadows in another application. And since MDL 7 does not support more than one uv-set you have to find external rendering helpers as well.
If you bake everything into one texture then it will have very low resolution.

I hope that makes it more clear for you.

and then the conclusion is,

GS needs a better light mapper, a better map compiler, and better editors.

radiosity lightmapper(beta),importing lightmaps from fbx(beta) ,Importing several UV coordinate sets for model textures(?)

are listed in forecast, but i think still there is alot more new things needed.

Yes Quadraxas. This is a nice summary.

But don't rely on forecast features. Sometimes they vanished from their lists and sometimes they took 2-3 years to finish in the past.

Besides that an indoor scene-management is needed that works well with shaders.

two are in beta, though. that's pretty promising. and i think there's enough demand for the second UV set that it'll almost definitely make it in.

julz

Yes, it does make it clear for me and yes this is the one point of critique I agree with. However it's not entirely true that it can't ever work with models, I've got per pixel lighting working (sort of as I'm not a shader guru) and stencil shadows work fine here, as said before though this is with A6 not A7. If the compiler is broken, it definitely needs a fix but I'm sure Conitec is working on this. As for the lighting issue, I hope they add that soon to A7, it will be a immediate reason for me to upgrade basically...

All this said and done though, as far as A6 is concerned suggesting that it's impossible to make nice games with A6 (or A7 once the compiler issues are fixed if that's a actual 'show-stopper' thing) is a bit weird,

Cheers

Yes. Absolutely. But the issue many customers have: A7 is at the market since July 2007. It has been announced in January 2007 and the beta was more than one year ago.
It still offers features that simply don't work, is still an incomplete and faulty release.
I don't blame JCL, he did not make the compiler and does not work on the tools. But it is a problem for Conitec and Gamestudio and of course a problem for customers working on real projects.

Pure forum users not working with A7 don't have to care about that. So I fully understand that users like Phemox don't have much trouble because of that. But I hope that users like him get a bit more understanding for the existing problems of A7 users with real projects that way.

Just out of curiosity, what are you always talking about that WED can not work properly with shadow maps? I am working with WED since 3 years and A7 WED since 1 year and it casts and receives shadows on top of geometry fine so far, and obviously for other people also, so what problem have you specific?

Just import a static mesh in A7 and compile shadows! I am not the only one having problems with that. Even the beta forum was full of images describing this problem. Try it yourself! It will work with simple cubes but not with static models.

We already described that in all details here and on other places in this forum.

Excuse me, I import static meshes and compile shadows all the time, and see nothing in the bug forum about this "full of images describing this problem", so I really do not know what problem you have. Does if happen with some mesh you imported? If you have a problem, have you made a bug report to Conitec?