I have had about the same problem and as far as I can tell it just lets you modify that Unreal clone of a game...
The "game" is just an example that uses the engine. You can build your own game from scratch. And it''s far from a clone as such, the only similarity is that it''s first person.
It seems that you need to use there interface and stuff and you have to use there weapons...
Again, the weapons are part of the example game implementing the engine. The engine doesn''t have any inherent concept of a weapon -- that''s up to the application to define what that is.
but forgot that it might need some f@#$ing documentation or sum tutorials...
Genesis has complete documentation of pretty much every function. By going through the headers, it''s rather obvious how well the API is designed and implemented -- it really is quite easy to use.
The result is that there is not a whole lotta people useing that engine.
Several known commercial games have been released, and there are several other professional licensees of the engine. Since Genesis isn''t a well known engine, the licensee''s generally choose not hype the fact they use it -- as opposed to the repeated ravings of "oh, our game uses uses the Quake engine, it''s automagically going to kick ass!".
I think it''s much easier to use Direct3DRM
As well you should. =) No offense, but by guess is you aren''t ready for realtime 3D development. You should also be advised that RM is as dead as DOS is. It hasn''t been updated or revised since DX3, afaik.
So your saying I could use genesis 3D to load a simple mesh and display it?
Genesis can do that, but it also can do so much more. Genesis can do veritably anything that Quake and Unreal can do.
just a quick Q to people of Gen3D and I think any Win32 programmer what is the diff between linking with a static lib or a dynamic lib?
Linking with a static library and a dynamic one are the same, except for one difference. Static linking pulls the library into your executable, while dynamic linking pulls only the import information into your executable, leaving the meat in a DLL that needs to be redistributed with it.
