#key-race

While working on the new version of Keyboard Racing website I totally forgot about the current one... Shame of me! And what happened? Right! The current website became like an old house. The roof with holes, downspout is detached and overgrown garden. By translating to the technical language: broken login with Facebook or Google, non-parsable content for search-robots, bad makeup for tablets and mobile phones: YESYESYES, you actually can play with mobile phone ;)

Google said: At some point of time I got an email from Google, like “Hey body! Do you see? Your customers trust you, you have your traffic grows! And yeah, your site is sh..t, but I also trust you, Google said.”

I realised, that I must spend some time to fix all this small issues and make my old house clean and neat! Because I love this project and I hope you love it too.

Fix it!: So I spent my time to restore what were broken: Single sign-on page: Google and Facebook, I had a long negotiation between me and Google/Facebook, because now they require huuuuuge amount of checks and validations. They want to be sure that they can trust me and you can trust me. Now you can ;) I proved it :)

Also (I don’t know why) I updated my design and made it responsible! (still do not know why ¯\_(ツ)_/¯    

Finally, I can continue working on the new project and I hope I will launch it as MVP very soon! Cross the fingers :)

KeyRace GUI and Scenes

This day ended with the new demo! http://key-race.com/demo

After spending a few days of researching different GUIs and interfaces I realised, that I cannot find the best one, the one I want to have for the KeyRace project. So I decided to create my own layout :) Simple, right?

You can find the MainMenu prototype (follow the demo link), ah and yeah, I create a HomePage scene. This scene now will welcome you and will guide you through the game process. Of cource now it's just a prototype, but I promise, it will be the most interactive "Main menu" you ever seen ;)

Optimization problems

Hello everyone! 

I decided to publish a development  progress of the Key-Race v2, like a dev blog. So after a first demo I realised one thing: BROWSERS ARE SLOW!

Not all of them, Chrome works pretty well, but others, like Safari - not. And chrome is also not perfect on slow machines (macbook 13''). As you can see, I added some tech info about mem usage and FPS. And yeah.... it's not perfect. And the problems are - amount of polygons to be rendered and the realtime light.

After 2 days of researching I was able to reduce amount of polygons from 3.3 million to 1.1 million. I optimized a car by dropping amount of poligons from 330 000 to 96 000. And even tried to use LowPoly AudiTT car. And of course I baked all the possible lights.

After all the total amount of polygons were dropped to 700k only! It allows me to run the mac-compiled app with the stable 120 FPS. But browsers... Safari shows 60 FPS but even though it renders the image too slow and not smooth. Chrome + Mac 13'' showed better performance, but also has some smoothing performance issues.

By testing this I realised that the max affordable num of polygons is about 200-300k max, so it means, that I need to change the concept to some LowPoly ideas. Because even the low-poly AudiTT generates ~70k polygons (+realtime light adds *3 multiplier) and yeah, it will be very hard to render the race with 10+ participants. Will see. 

Stay connected, subscribe to this page and check the development state! Stay health!