Code center > Darwinbots Program Source Code
Re-writing DB in JAVA
Numsgil:
Clicky.
Just saying... don't let that stop you.
ikke:
OT (but that hasn't ever stopped me or anyone else on this forum): eta for db3?
Ammeh:
Alright, I'm convinced. Working on DB3 would be better than wasting my time in java.
I reckon we should set a deadline and really get it going though. like, 6 months tops to get everything together and have a working version to show...
Numsgil:
--- Quote from: ikke on January 07, 2011, 05:53:30 AM ---OT (but that hasn't ever stopped me or anyone else on this forum): eta for db3?
--- End quote ---
I'm a few weeks (IRL time, assuming my current pace) from finishing what I need to finish with the Math stuff ('Azimuth'). Then I can start on the physics engine ('Lodestone'), which has some stuff already. I've written a few physics engines in my time, so I could probably pump out a working version in maybe 50 man hours (say, 2 months real time). Then graphics still needs work. I don't have a good handle on how much work is left, but certainly a few weeks at least. Then we can start on Darwinbots proper and tie it all together and get bots moving on screen. I didn't really do any work on Darwinbots between like last February and October, so there's still a fair amount of work to be done.
--- Quote from: Sammeh on January 07, 2011, 08:44:11 AM ---I reckon we should set a deadline and really get it going though. like, 6 months tops to get everything together and have a working version to show...
--- End quote ---
Problem is that it's hard to judge in terms of 'real time' since I usually can only work on Darwinbots on weekends (it's really hard to come home after staring at code at work and stare at code some more :P), and even then sometimes I'm just not in to it and play games instead :P
If people are getting to a point where they have time/effort to spare for DB3, though, I can start delegating some tasks. But fair warning: I'm not sure any of it is very fun or interesting. Or the parts that are fun and interesting are also extremely technical so you have to be dedicated enough to probably go way outside your comfort zone and read dozens or hundreds of pages of stuff before you even touch the code (I'm thinking specifically shader work in graphics. It's not hard, but if you have no idea how a graphics card actually works and how data gets pipelined it's easy to get lost).
Anyway, I'll see if I can't put together a roadmap and log some issues in Mantis and then I can start posting tasks and interested people can take them and run with it.
Panda:
I can help, that'll get it out quicker, maybe... :p
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version