Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Obligatory “omg, a multiplayer game for a jam, amazing!” The game itself is quite clever. You’re drawing cycles on a (motor)cycle! Everything feels buttery smooth when running the native client. Great work! I had a lot of fun playing this with my friend :) The only issue seems to me that it’s fairly hard to counter the strategy of “draw a biiig biiig circle”. I know the line length and the border slow you down, but it still felt a bit bad to see this huge line and not being able to do much about it immediately. Maybe encircling a trail could interrupt it?

Graphics-wise, I love the fact that the rotations are discrete. Very distinct vibe. Don’t know why, but it kind of reminded of Fallout 1 and 2, even though those games look quite different. Something about seeing a 3D model act in discrete poses maybe? Anyways, great aesthetic. Also: somehow, you made the engine sound of the motorcycle sound supremely calming. I quite like it :)

Thanks!
I'd really like to know why things are much smoother on the native client. Is it just that the browser is less performant?

And yes we wanted to add the rule that 'encircling a trail would break it', but this would require adding spatial indexes to efficiently find subsections of trails, and we didn't have time to do that!

(1 edit)

Consider that we got https://janhohenheim.itch.io/bike-game to run smoothly on Chrome at least, and that is a full 3D scene with lots of complicated geometry. With that in mind, I find it strange that you are running into performance issues. Maybe one of the underlying Bevy or Winit or wgpu APIs is somehow subtly broken on Wasm? I think the browser itself should definitely be performant enough for your use-case.