[7DRL-2016] Some Dogs Go To Hell (Sucks a-I mean, success!)

[Hrakanku]

How slow is really, really slow? 'Cos it's ~ .25 - .50s on the average turn (and the first turn takes a couple times that since all the AI routines are kicking in at once) on my machine, which is a straight-up gaming laptop... I tried doing some optimizations but the result turned out to be super buggy and 10 times slower anyway and it mangled the repo on top of all that...

But yeah, I've got a migraine right now so I can't do much of anything, but once that goes down I'll zip up the required libraries and send 'em to you.

Actually... hmm. This probably won't work, but try sticking the .py files into the same directory as the executable in the win32 distribution and launching from there. Maybe also try replacing all the "import <bla>" statements with "from library import <bla>".

It's something like 0.8 - 1.2s / turn, which actually still is playable, if only just. And yeah, didn't work, tdl.py seems to be the problem. And whatever stuff that depends upon of course. Also: I kind of love the name, even if it is a bit long.

[TOASTEngineer]

Oh crap. I just now noticed I left in a debug print that's now screwing up the whole status window. That's great.

[TOASTEngineer]

Oh, I should probably actually link to the finished product, huh?

https://schilcote.itch.io/7drl2016

[Avagart]

***ok, everything is ok, my bad***

[kipar]

I thought i've seen all about optimization after 7DRLs on Unity with ugly ascii chars being shown using modern shaders. But I was wrong. Now i've seen a 7DRL that takes more then 1 second per turn on (relatively old but still) core i7.
So while the name of the game and battle mechanics (and possibly squad mechanics, but i haven't got to it) are great, ii is impossible to have fun from it.
Any plans about post-7drl version which will work, like, 10 times faster?

[TOASTEngineer]

Yup! I spent the entirety of the last day re-doing the slowest part, in fact... only to find the "accelerated" version was five times slower. I just have to take a different approach to fixing it.

[KhaoTom]

Getting an easily reproducible crash: press A to attack and then immediately hit Enter without inputting anything else.

[TOASTEngineer]

Yup, that's a known issue. It'll happen with any text input, in fact. It's actually a wierd thing Python does, I never figured out how to get around it...

The game also crashes if something eats your corpse after you die.

[KhaoTom]

You can avoid the crash by catching the exception in a try: except (EOFError) block.

Code: [Select]

try:
      command = raw_input('Input command:')
except (EOFError):
      break  # break out of handling the command


[TOASTEngineer]

Right, but that means wrapping EVERY input() in a try...except, which isn't exactly elegant. I'd much rather have it replicate the same behavior as reading an empty line from stdin...

[KhaoTom]

Elegance has no place in 7DRL 

[TOASTEngineer]

Actually, I think working out elegant architecture early on helped me later. I notice that while I was making progress a bit slower than average early on, I was getting stuff done way faster in the last three days.

[TOASTEngineer]

Providing what Hrakanu asked for was significantly harder than I expected.

However, I have released a fixed version of SDGTH that runs about an order of magnitude faster, fixes a few annoying bugs, and also includes stairs to other floors (which never end). It's available on itch.io alongside the competition version.