u/Particular_Falcon_48

I built a free, browser-based multiplayer F1 racing game. No sign-ups, just jump in and play with friends.

Hey everyone,

I recently built a low-poly 3D multiplayer racing game that runs entirely in your browser. There are no accounts, no downloads, and no sign-ups required. You can just share the link with your friends and instantly race against them in real-time.

Play it here: https://f1-browser.vercel.app/

Tech Stack:

  • Frontend: Three.js (Handles the 3D F1 car meshes, the daylight environment, and spline-based track generation).
  • Backend: Node.js + Express with Socket.io (Handles real-time multiplayer syncing and server-side checkpoint validation).

The game has full support for both Desktop (keyboard) and Mobile (touch controls), so you can play from anywhere.

I just pushed a major overhaul to the track and physics. Please try it out with some friends, and if you find any bugs or have any feedback, let me know in the comments!

reddit.com
u/Particular_Falcon_48 — 3 days ago

I built a free, browser-based multiplayer F1 racing game. No sign-ups, just jump in and play with friends.

Game Title: Web Grand Prix (Browser-based Multiplayer F1 Racing)

Playable Link: https://f1-browser.vercel.app/

Platform: Web Browser (Desktop & Mobile)

Flair: Web

Description: Web Grand Prix is a free, instant-play, low-poly 3D multiplayer racing game built entirely for the web. I wanted to create an experience where players can instantly jump into an open-wheel Formula 1 car and race against their friends without needing to download anything or create an account. The game features a fully custom Catmull-Rom spline-based F1 circuit, complete with a long main straight, sweeping corners, red and white kerbs, and a daytime aesthetic.

The game supports cross-play between desktop (using keyboard controls) and mobile devices (using on-screen touch controls). Real-time multiplayer synchronization is handled server-side to ensure smooth racing and prevent checkpoint skipping. I am also currently experimenting with trackside billboard sponsorships (similar to real-life F1) instead of using intrusive pop-up ads. I just pushed a major physics and track geometry overhaul, so I'd love to get feedback on how the car handles, if you encounter any bugs, and how smoothly it runs on your specific device/browser!

Free to Play Status: Free to play

Involvement: Solo Developer. I built the entire frontend (Three.js for 3D rendering) and the backend (Node.js + Socket.io for multiplayer networking).

reddit.com
u/Particular_Falcon_48 — 3 days ago

I built a 3D multiplayer racing game just for fun (No sign-ups required)

I spent some time recently building a real-time 3D racing game in my browser just for the fun of it, and I wanted to share it with you all.

I really hate when web games force you to create an account before you can even see the menu, so I made this completely frictionless. You literally just click the link, and you are instantly dropped into the lobby to race against anyone else who happens to be online.

It's built using Three.js for the 3D graphics and Socket.io for the multiplayer syncing.

Link to play: https://car-game-6ajp.vercel.app/

It’s still very much a side project, so there might be a few rough edges. If you have a minute to try it out with a friend, I would really appreciate any honest feedback! Let me know how the driving feels, or if you run into any weird bugs so I can try to fix them.

Thanks for checking it out! 🏎️

reddit.com
u/Particular_Falcon_48 — 5 days ago

What if kubectl could explain why your pod is crashing instead of making you debug manually?

I’m thinking of building a CLI tool for Kubernetes debugging and wanted to validate the idea with the community.

While deploying multiple services on Kubernetes clusters, I often face crashing pods and spend a lot of time debugging issues manually. Most of the time, engineers end up copying logs and errors into ChatGPT or searching online to understand what’s actually wrong.

I initially started building this tool for myself, but then thought — why not make it something other DevOps engineers can use too?

Example:

kubectl ai debug <pod-name>

The CLI would inspect logs, pod events, restart reasons, probe failures, OOM kills, networking issues, image pull errors, and other Kubernetes signals — then explain the root cause in simple language along with possible fixes and debugging steps.

The goal is to help DevOps and platform engineers troubleshoot faster without constantly switching between the terminal, documentation, and AI tools.

Would you use something like this? What features would make it genuinely useful for your workflow?

reddit.com
u/Particular_Falcon_48 — 2 months ago

What's your process when a pod goes into CrashLoopBackOff ? How long does it usually take you to find the root cause?

Curious if person is doing like pasting the error in gpt and get the solution or any better tool avilable to use it to investigate the root cause

reddit.com
u/Particular_Falcon_48 — 2 months ago