Developer - Lead Artist
Joined: Wed Apr 14, 2010 6:36 pm
Location: Melbourne, Australia
Cars: 1994 Mazda MX5 with big cams - 101RWKW
Thank you very much for your applications! We have considered all of them until this point. Unfortunately,
we cannot consider any further applications as the final beta run before demo release comes very close.
There is an additional round of selection for the potential new beta testers. If you were selected, you will
receive a PM from me (Killrob) asking two questions which we would like to have answered. If you are
chosen to partake in beta testing after this, you will be notified via email soon!
Thank you all for the great response! There are a lot of good offers in here and many of you will be accepted
into the beta... probably already at the end of this week. You will be the first to test the newly implemented
scenarios. Also: no need to put in hours upon hours of testing. It is well-structured and focused testing that
is worth much more than many hours. One to two well-documented testing hours a week are worth a lot to
us already - and if you do that, we don't care how much you play around in the beta with the rest of your time.
Although, more good feedback is always appreciated!
Keep the posts coming until Wednesday Feb 29, this will be our cut-off for this wave.
New Testers Needed
The devs are making great progress on the engine designer currently, moving ever closer to a demo release.
The proposed inclusion of scenarios has started and their in-game mechanics are now fully functional.
Of course you will be able to sandbox-it-up in the demo too!
The good news:
At this pace the demo will be released within about a month, if all goes well and no major problems surface.
The not so good news:
Currently the engine designer demo is in its true beta-phase, meaning there are bugs, but it is basically
feature complete. So what is bad about that you ask? Well, we do not have enough (wo-)manpower willing
to test and fine-tune certain aspects of the demo. More specifically there is a specific task we had in mind:
precisely model existing engines in Automation and compare their performance figures to their real-life
counterparts. One major question mark right now is how accurately the fuel octane rating is modeled in
Automation. And we need help with that!
So here's the deal:
- Have preordered Automation
- Are willing to test the demo
- Are willing to document your findings in a detailed fashion in the tools provided (Pivotal Tracker & Engine Spreadsheet)
- Know that "testing" does not mean "just playing around"
- Are able to give detailed feedback to assist in making Automation more polished and fun
- Write here in this thread how much time you are willing to put in
- be accepted into the beta if we deem your offered effort both reasonable and sincere.
If you like the sound of this, you are most welcome to post down below! Also, be honest. We don't need more
people not doing any testing and playing around. Your help would be greatly appreciated, and will make the
Automation Demo a better product in the end - and the consequences of that should be to everyone's
/Killrob (Lead Beta Tester)
Edit: Now with proper Killrob-esque formatting!