Difference between revisions of "Dragon"
Jump to navigation
Jump to search
Larger Image (may take a bit to load)
(put the dragon to sleep) |
m (→What is it, post April 1st: typo) |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 3: | Line 3: | ||
=== What is it, post April 1st === | === What is it, post April 1st === | ||
Dragon was our April Fools for April 1st, 2005. Nobody really | Dragon was our April Fools for April 1st, 2005. Nobody really bought it. :) | ||
It was however conducted with a certain amount of internal help at Revolution (woo, spywork!) and the filenames and source code visible are indeed real. Even the screenshot is a real internal screenshot, albeit the only one we could locate with a graphical glitch, which turned into a bogus cover-story about clipping bugs to make things a little more authentic. | It was however conducted with a certain amount of internal help at Revolution (woo, spywork!) and the filenames and source code visible are indeed real. Even the screenshot is a real internal screenshot, albeit the only one we could locate with a graphical glitch, which turned into a bogus cover-story about clipping bugs to make things a little more authentic. | ||
[[user:ender|Ender]] was behind the text and posts, but [[user: | |||
[[user:ender|Ender]] was behind the text and posts, but [[user:joostP|Joost]] came up with the idea and did all the hard work. | |||
===Screenshots=== | ===Screenshots=== |
Latest revision as of 07:11, 19 August 2007
What is it
Dragon is a renderware-compatible engine framework, for easy porting of some titles such as Broken Sword: The Sleeping Dragon. Much thanks to Revolution for the game source. (this is all a lie)
What is it, post April 1st
Dragon was our April Fools for April 1st, 2005. Nobody really bought it. :)
It was however conducted with a certain amount of internal help at Revolution (woo, spywork!) and the filenames and source code visible are indeed real. Even the screenshot is a real internal screenshot, albeit the only one we could locate with a graphical glitch, which turned into a bogus cover-story about clipping bugs to make things a little more authentic.
Ender was behind the text and posts, but Joost came up with the idea and did all the hard work.
Screenshots
Larger Image (may take a bit to load)
Todo
- Music Manager
- Fix memory leak in renderer
- Software Renderware-compatible renderer?
- Fix near clipping issue (artifacts behind
- Clean up makefile
- Lots lots more