ScorpionInc

 Perhaps not the prettiest sprites, I don't like the white box around the joystick, but it requires no extra image files by reusing the already available images for textures.

To know the input won't be activated until it is over the threshold yes, is trivial. This would simply make it easier to play with what the deadzone threshold is...

Not sure how helpful this will be but this seems to be related to line 55 of the w_blocks.c file for OpenCL where it tries to get a file handle...

To summarizes it seems to be unable to open the GPU_ID 0. Perhaps try using -g 1 instead of -g 0 maybe that will help? If it does please share....

Hmm would recursive actually be faster? I did a quick test and it seems to be slower. Not trying to sound like a downer or rude, but maybe there is...

So looking through the code line 66 relates to setting the CUDA device by its GPU_ID this is specified by the parameter "-g 0" perhaps you have a different ID...

I've only seen this done once but if you have the resources to just throw more GPUs at the problem and your comfortable with some more advanceded stuff, using john...

Fixes some error(s) listed here: https://github.com/e-ago/bitcracker/issues/43 Primarily the following: utils.c:205:5: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘:’ token 205 | out: | ^ utils.c:207:8: error: expected declaration...