PyWeek - GD - feedback
PyTM30
Tee
Sorry, this looked like a lot of fun but I had to give up on this. I first had the issue described in Tip 1, which was solved with headphones. But then it was too hard to make the game understand my voice perfectly, so I gave up. I wish you had implemented a text-based version just so I could play the game.
Cosmologicon
Really innovative idea for an interface, but unfortunately I couldn't get it to correctly understand more than a few words no matter how much I tried. I'm on version 1.2.
mit-mit
I love the idea of using speech to text in a pyweek game: awesome job for exploring this new ground (haven't seen thi before in any past entries :) ) ... unfortunately I had a few issues getting the game to work properly: I could load it up and the speech to text was working, I could see in the bottom corner it understood what I was saying but it did not respond to any of my voice commands at all. I tried scouring the readme, but the game didn't seem to be responding to anything I actually said. Running on osx 10.15, python 3.8.4, all packages versions as specified and no error messages.
yanigisawa
I got the game screen to load using Python 3.9, but the mic was not detected.
I rebuilt my venv using 3.7, and got the below logged to the console:
(venv3.7) $ python run.py
objc[27692]: +[NSPlaceholderString initialize] may have been in progress in another thread when fork() was called.
objc[27692]: +[NSPlaceholderString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
objc[27693]: +[NSApplication initialize] may have been in progress in another thread when fork() was called.
objc[27693]: +[NSApplication initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
objc[27691]: +[NSNumber initialize] may have been in progress in another thread when fork() was called.
objc[27691]: +[NSNumber initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
^C% (venv3.7) $
fireclaw
Well, this was something special. Only working with speech control is definitely new, but keeping this the only source of input even to close the game definitely isn't the best. Which also made it impossible to play for people that don't have mics available. That's also why I can only rate the innovation part.
Chard
Error during `pip install -r requirements.txt`:
```
Could not find a version that satisfies the requirement vosk==0.3.21 (from -r requirements.txt (line 31)) (from versions: )
```
Impressive and frustrating