It seems that by cooking content for Windows, I noted that there were a few more errors past the Automation Test tool. Some of the assets have names that are too long; some just passed the test without being noticed.
Speaking of noticed...Jeez; sometimes these levels load in Automation, sometimes they don't. I've noted that errors sometimes rise, but the real errors are replaced by a "none is not a standard filename" filler statement on the output log. Helpful? Quite the opposite!
As for neurofeedback, none has been done by any of the other programmers. As a result, I was forced to do their work. Luckily it was fairly simple; visualizing a score that I already implemented and making a loading screen UI to fill in while the neurofeedback software is synchronizing with the Unity game client.
What next? Resting while the others toil to catch up...
No comments:
Post a Comment