Albert on 2/2/2010 at 17:06
I stand firm on my 2012 estimate... Er, mebbe 2013. :sweat:
But progress is progress, and very good process by the looks of it. Now, is there any possibility of making a widescreen menu? Y'know, in case any FM maker decides to make the menu fancy and such?
242 on 3/2/2010 at 11:21
Quote Posted by Albert
I stand firm on my 2012 estimate... Er, mebbe 2013. :sweat:
You'll be disappointed ;)
That MAY be possible only if you (or anybody else) will gather like 3-5 experienced programmers working full-time. Because you know, it's harder than creating a new engine.
Volca on 3/2/2010 at 11:39
Agreed. Add to that that there is low interest in helping. It is somewhat rewarding but only later on, first there is a slow, long learning curve ahead for everyone joining the project (Understanding the original Dark as much as possible, orientation around the codebase). I tried to improve this by writing a dev. manual (an older version is still online here: (
http://opde.sourceforge.net/manual/)) - but I'd love to have a dedicated documentation maintainer - I suck at this pretty much :)
bikerdude on 3/2/2010 at 17:37
Quote Posted by Volca
but I'd love to have a dedicated documentation maintainer - I suck at this pretty much :)
Have you put a request in for this in the editors guild.. - (
http://www.ttlg.com/forums/forumdisplay.php?f=85)
Albert on 3/2/2010 at 17:48
Eh, I think this is goin' pretty well, though. In contrast to other proprietary engine reduxes.
MaxDZ8 on 8/2/2010 at 07:31
Quote Posted by Volca
some resource management improvements (we still need a better system for this though - I'd love to add some threading at least to this part of the engine, we may be lucky as Ogre 1.7 introduces a generally usable worker thread and work queue concepts that may fit without us needing to add another library dependency).
Could you elaborate on this? Why are those improvements needed? What problem are you trying to solve here? While I can understand the "I'd love to..." rationale, I'm not completely sure of what you mean.
Quote Posted by Volca
There are some large unknowns in the PHYS_SYSTEM tag still, mainly how contacts are stored. Some rough path ahead :)
This sounds tough.
Volca on 8/2/2010 at 07:49
Not yet - I suppose TEG people come to this forum as well. I might consider it though.
Quote Posted by MaxDZ8
Could you elaborate on this? Why are those improvements needed? What problem are you trying to solve here? While I can understand the "I'd love to..." rationale, I'm not completely sure of what you mean.
This sounds tough.
Sure. The resource management is a bit messy right now. There is no responsibility assignment and the usage of Ogre resource system does not really simplify things. We need a piece of code to assign resource management to. Threaded loading is needed for sound handling later on (sounds need to be loaded on the fly as needed) and thus there is no reason to not do the resource handling threaded as whole. It should simplify loading displays as a side effect too. This responsibility should end up being summoned as a new service (probably), which would get a set of methods to work with the asynchronous loading of individual types of data, to check whether those are already loaded or not, etc. I have the details still a bit blurry, but it is slowly coming together.
Serpentine on 12/2/2010 at 13:02
Why hello there sexy.
Good work guys :)
TheCapedPillager on 12/2/2010 at 18:08
Quote Posted by clearing
I see AI
Is this OPDE? If so, well done, the shadows look very good! Looks just like Dark.:thumb:
