Wintermute Engine > Feature requests, suggestions

Poll: New Scene Edit or HLSL?

(1/7) > >>

metamorphium:
So here's the deal. What would you prefer?

Jyujinkai:
I am going to have to go HLSL sharder support. The fact is that while scene edit could have a host of improvments... it dose work. HLSL dosn't. Things like theora privies in the editor would rule but ... well peoepl can already use thorea in the games as it is.

Unless there is a host of other features you are talking about that are not there at all.

Derrek3D:
Could you (or someone else) please write in a bit more detail how could each of the options help developers and their games? For example, what are shadow maps and how do they look in the final game? Or what can be achieved using HLSL?

Thanks.

FogGobbler:
I agree with Jyujinkai and also vote for HLSL things, because the scene editor works fine for me as it is. Just had a look at the new Perry Rhodan adventure and in my opinion everything can be done with WME (even the scrolling for big scenes).

But things like reflecting materials, and (sorry for repeating myself again) perpixel lighting with real shadows are vital for a modern 2.5 engine. Normal mapping for characters would also be great.

Please don´t get me wrong, Mnemonic, I think your engine is awesome, and I certainly don´t want WME to become a 3D engine, but with these features everything would be just a tick better.  ;) 

Happy Easter,
Oli

Mnemonic:
Ok, let me elaborate a little. Both the new SceneEdit and support for DirectX effect files (aka shaders support) are features that need to be done, and I'd like to see both in WME 1.9 (perhaps ending the whole WME 1.x series). But both of these are potentially quite time consuming and may take a long time to finish.

Shaders support would be nice for some additional eye candy (and perhaps some more stuff, depending on how deep would the implementation go). SceneEdit rewrite would bring better user-friendliness for scene design (i.e.  the area where developers probably spend most of their time), but mainly it would open door for new features, such as the mentioned direct Theora integration, direct placement of external entities/actors/3D actors, more comprehensive camera tweaking, the "shadow maps" (simply an image which tells the color of an actor in a given point in scene, think more advanced decoration regions), predefined scene states, and more.

So to recap, I want to do both of these, but some has to take priority for now, because my time&resources are not limitless.


While I'm at it, and as I mentioned the end of 1.x series above, some people were asking for a WME development roadmap. Well, I don't have a roadmap, and I tend to change my mind frequently (I know it's unprofessional, but please allow me this luxury at least for my pet hobby project, I have enough roadmaps and deadlines in my daily job). I can give you a rough outline of things to come:

WME 2.0 - completely replaced renderer (based on some 3rd party middleware); completely replaced script compiler/interpreter (I already have a lot of this done, but I can't merge it with WME 1.x because it will not be 100% compatible)

WME 3.0 - complet redesign of the engine/tools; I have many cool ideas, but I'm not going to talk about them just yet :)

We were even discussing the possibility of skipping WME 2.0 completely and going directly for "the new thing"(tm). Nothing is set in stone yet.


And contrary to what certain AGS users think, I AM listening to the userbase, and I AM interested in your opinions. So if you have something to say, say it now. Whew.

Navigation

[0] Message Index

[#] Next page