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!
Permanent demo link as usual: http://key-race.com