Change log - feature additions and bug fixes in active development

[Chris]

I have an exam and a major deadline on Friday. After that, I hope to take a weekend break and get some Inventive Dingo work of some kind done. This is my Honours year, so I'm not going to be truly free until sometime in November, but I'll try and squeeze little bits in when I get sick of iterating on my Honours project.

[Jp]

I have an exam and a major deadline on Friday. After that, I hope to take a weekend break and get some Inventive Dingo work of some kind done. This is my Honours year, so I'm not going to be truly free until sometime in November, but I'll try and squeeze little bits in when I get sick of iterating on my Honours project.

I know that pain all too well. In the middle of exams at the moment, too.

It'd be nice to get some MI gaming in at some point.

[Minus]

Still got the game installed! Never left my hard drive.

[Chris]

Cheers guys. I'm glad that my temporary hiatus hasn't completely turned you off.

[Chris]

I have an exam and a major deadline on Friday. After that, I hope to take a weekend break and get some Inventive Dingo work of some kind done.

My deadline got postponed by a week (phew), which means I also need to postpone my weekend of Inventive Dingo work until next weekend.   It will happen though!

This is my Honours year, so I'm not going to be truly free until sometime in November, but I'll try and squeeze little bits in when I get sick of iterating on my Honours project.

Speaking of my Honours project - in case anyone's interested, my project is basically entering this contest, and the above deadline is for its qualifying round. I'll either do OK or crash and burn, depending on whether the technique I'm investigating turns out to be a good one or not. (I had to try something new enough to be Deemed Worthy of Academia, rather than picking something tried-and-tested.) I'm hopeful, but getting the bot's aiming behaviour right is proving tricky; and the turnaround time for tweaks is about a day (thanks to having to recompute a ton of data), so it's hard to iterate on! On the plus side, I can use the computation time to e.g. write this post.

Hmm, maybe I can use Psyco to speed up the turnaround time... (Edit: Psyco doesn't seem to do much for this case, but I managed to speed the code by a factor of x2 with a really simple optimisation, so that helps!)

[Kumlekar]

That contest sounds awesome! I would think the hardest part would be the pathing and aiming for the ultra-accurate guns.  You've gotta reduce the accuracy somehow, and pure randomization will give it away in a second.  Whats your method?  Also, will you let the bot go for shock combos?

[Chris]

I'm keeping my methods secret for now, since I have a novel approach which I hope will be fairly successful. I'll tell you after the competition.   (Or after this qualifying round, if I don't qualify... I'm reasonably confident I will though.)

[Chris]

OK, so I did end up spending the weekend on Mayhem Intergalactic stuff, and bits of Monday and Tuesday, but didn't get much code work done. Mostly ended up spending the time on accounting and business development stuff. Which is good, just not very exciting.

I did review what I've done so far towards the next version, and then half-fixed a bug. I would have completely fixed it but I got a little distracted with some much-needed refactoring. I will finish fixing it soon.

[Kumlekar]

Ok, but you can't at least answer the shock combo part?   

[Chris]

No, it doesn't deliberately go for shock combos.

[Chris]

Oh, and I forgot to mention - I qualified.   I came first by a reasonably healthy margin, too; so evidently my method is indeed worth keeping secret, for now. I look forward to divulging it after the finals in September!