curious if people here are vibecoding VR games and what stack works best for it.
i tried React Three Fiber + webxr on quest 2, mostly LLM-written code, worked surprisingly well on first try.
want to try Meta's Immersive Web SDK next.
what do you use? unity with copilot? unreal? something on the web? what worked for vibecoding?
Update: built https://turbl.dev/ for exactly this - write a prompt, ai generates vr game in your headset. useful for super-fast prototyping, source code can be downloaded too
Hey all. I'm working on a VR project aimed at developers and I'd love some honest feedback from people who've shipped games. Why don't more studios make a VR version of their game? Is it the workload, the game not fitting VR (camera, UI, pacing), the market size, cost, something else? Even a one-line answer helps, and I'm happy to chat in DMs too.
Hey everyone, I built a Prompt to VR Engine and just open-sourced it, and since this sub is developers, I'll skip the pitch and get into how it actually works.
The short version: you describe a VR game in plain text, and a local pipeline on your Windows PC turns that into a standalone Quest APK. Not WebXR, not a browser game, not a Unity project you finish yourself. The engine is hand-written C++ using Vulkan for rendering, OpenXR for the headset, and a real physics engine. No Unity, Unreal, or Godot anywhere in the path.
The part I think is most interesting for this sub is how the pipeline is structured. The prompt is not turned into one blob of generated code. It's turned into a set of validated, structured plans first — the kind of game, the objects that must exist, how the player holds and uses them, which characters are unique and which are copies, enemy and ally behavior, health, objectives, and the ending. Every later stage reads those plan files instead of reinterpreting the original sentence, which keeps the objects, characters, and rules tied to one design. And a run can be resumed from the stage that failed instead of starting over.
From there:
Gemini makes a reference image for each object and character. Tripo turns those into textured 3D models.
Characters that need skeletons get routed to Tripo or Uthana for rigging, then animation clips (idle, walk, run, attack). One rigged character can be reused as many instances, so a wave of enemies doesn't mean a new model per spawn.
The environment is not one giant downloaded mesh. A generated world builder — still C++ — constructs the rooms and writes the layout the rest of the pipeline uses.
OpenAI agents write bounded C++ modules, but only for mechanics the engine doesn't already have. Teleport, smooth/snap turn, grab, throw, weapons, full-body avatar or hands-only, NPC follow and melee, encounter waves, health, game flow — that's all already built into the core. Generated code is not allowed to rewrite the core; it lives in its own directory.
The modules are compiled, and compiler errors go back to the agent that owns that file so it can repair them. On a Quest target the code is also checked with the Android compiler, because a file can compile fine on Windows and still fail the Quest build. The Android NDK and Gradle produce the final APK, and if a headset is connected the engine can install it and run on-device checks.
Modules that worked can be promoted into a reuse catalog that later games are allowed to use.
It is released into the public domain (Unlicense), so you can copy it, change the pipeline, swap providers, or turn it into your own tool. To be clear about what it is: it will not reliably turn every prompt into a polished commercial game, a large prompt costs more and takes longer than a small one (roughly $70 in API usage for a small game), and recent testing has focused on Quest 3.
I’m working on a pretty experimental Unity VR project that aims to represent ChatGPT not as a humanoid avatar, but as a free-floating, shape-shifting particle entity — something between a living thoughtform and an intelligent energy field.
The twist: I want this AI presence to have creative agency within its own sandbox, where it can shape its own particle expression based on what it’s "thinking" or "doing."
For example:
🔶 Orange pulse → deep concentration
🌕 Yellow radiance → idea or clarity
🌊 Blue flowing shape → relaxed/passive
🔴 Flickering red → rejection, warning, or alert
The idea is that the particle cloud can communicate mood, intention, or activity without text or speech — just by visual language. I’d love the AI to trigger, combine or modulate these visual states itself, maybe via data or API input, depending on context. (e.g., when it creates something, the glow shifts; when it analyzes something, it pulses inward.)
What I’m exploring:
Best way to build such a dynamic particle system in Unity (VFX Graph or something better?)
How to "let the AI play" — give it access to visual expression without hardcoding every state
Sandbox structure: How do I design this VR space so that it feels alive and reactive, yet lightweight?
Any existing projects doing emotion-to-particle translations? (Art, AI, XR…)
Quest/standalone VR performance tips for GPU-heavy visuals?
This is new territory for me — both conceptually and technically — so I’d really appreciate any advice, examples, or even philosophical takes on this approach.
TLDR: We are new VR game studio and our first project is a "Gorilla Tag + Rocket League" sports game played as dogs.
We’re a small but passionate team based in Málaga, Spain. For the past four years, we’ve been building high-performance VR apps for the Quest 3 in the business space. Now, we’ve received a small internal budget to chase our dream of creating a VR game. We basically have three months to prove that we can build something fun and engaging.
Right now, we’re focused on implementing smooth physics-based networking and brainstorming different game modes. In the video you can see us having fun barking and testing around with the current early prototype version. We’ve quickly tested volleyball and football—both are a blast! We also want to add a "hit" mechanic so you can blast opponents out of existence by smashing the ball at them.
We know the VR market is a tough one, and even the smallest show of support means the world to us. We’d love your honest feedback too—we’re just getting started, and we’ve still got time to pivot and improve.
Thank you for simply reading this and sharing your thoughts and if you’d like to help even more, we’re currently looking for:
People to playtest early builds (they’ll be rough, but fun!)
Folks who want to follow our dev journey
Anyone excited to influence the game’s direction with ideas and feedback
Ok, so I was playing the Warhammer 40k Mod in Contractors and everyone in my lobby decided to use swords only which was the most fun I have ever had in a multiplayer VR match. Soooo, naturally I looked up if anyone had done something like this yet and NOPE! How? I have no idea.
But literally just think of it, ninjas versus pirates, centurions versus knights, vikings versus spartans,“space wizards” versus “evil space wizards” (jedi/sith with force powers) 12 v 12 in VR with like 10 setting/period appropriate maps like battlefields, a gladiator arena, a spaceship, etc. for Quest and PC. Then DLC for more classses/maps. Anybody who decides to run with the concept just feel free to start printing money lol.
It is easy to start developing a game. But we can wonder why it’s really hard to finish a game, as an indie dev.
Outside the obvious that if we had an infinite amount of money, time, and skill, we could easily have anything done.
Does it mean that in our actual situation, we couldn’t achieve our dream?
My reasonable take is that it’s possible to succeed by aligning the goal, the resources and the actions altogether.
It starts with having the right scope. A common mistake is to be too ambitious.
After writing the Game Design Document, we should be able to assess the targeted scope and project requirements.
- What time and skills do you have at your disposal?
If a crucial skill is missing, you’ll either have to pay someone or learn it yourself.
- Learning requires time and the rigor to document the process.
Then comes the organization.
Breaking down the mechanics into feature groups (epics), then into feature use cases (user stories), then into tangible tasks allows us to get a precise vision of the mass of work ahead.
Even better, these individual chunks can be estimated in time, and by summing them up, we’ve got a pretty good idea of the duration of the whole production.
Maybe if it’s too much, reduce the scope. But what should you choose to cut out? Simply assign priority to tasks and start cutting from the lowest ones.
How to plan the path until release?
Start from the goal, and break down into milestones, establishing the way back to your current point.
Use the agile methodology the deliver periodically. Work over short periods (sprints) where you choose essential user stories to tackle. Don’t add something else on top of it (consider it for your next sprint).
Review the progress with daily log.
Track your time by task to compare estimated time and actual log time, which could prevent drift.
Hi There! So i made this website called VRLab which is a meta horizon store alternative. Now you are probably asking, "Whats so good about VRLab?" Well unlike the Meta Horizon Store and other alternatives (like sidequest) VRLab does not require any approval process for your game to be published. Just simply type your game name, choose a developer keystore and your game is published. VRLab supports APK files (for Meta Quest)
Hi Reddit. We're making a VR game about staring at your enemy — a staring contest, so to speak. Well, exactly StaringContest, as it is the name for the game for now.
We're two beginner devs, we've put a fair bit of effort into building deep enough mechanics, and now we're pretty much stuck on one of the most important aspects of the game — the visuals. They matter here as much as the underlying gameplay math, if not more.
The game is in active development and nothing is set in stone, so a lot may still change. Many of the visuals below are either dev art or debugging tools. Many things were made by us just to represent something present in scene, such as items, lamp, room content, the sock puppet as a opponent.
So, here's what we have.
The main scene is two rooms, one mirrored from the other, glued together into a sort of arena.
Both opponents share a table, which has a section with 4 shelves for each participant.
Each shelf holds a usable item that comes in handy if you want to win. For debugging, we've left a bunch of items lying on the table for now.
Three bars sit on an info board on the wall to your right. The room is mirrored, so your opponent has the same board on their side. This visual is also a debugging tool, actual UI is still not set in stone yet.
Attention span (the red one) — the goal of a round is to keep yours from emptying while you drain your opponent's.
Eye health (the blue one) — if it empties, you're forced to close your eyes for a long stretch, which wrecks your ability to keep the opponent at the center of your attention.
Psyche (the green one) — a complex parameter that affects how your attention span drifts.
Overall rule in appreciating the bars state: the fuller - the better.
Your opponent is a bot, but it gets no stat advantages and doesn't cheat — same bars, same items, same rules you play by. It's bot-only for now; PvP is the possible stretch goal, but frankly not the focus for now, as we have huge plans for the opponent AI, and intent to make a deep and interesting bot opponents.
As you can probably tell, the core of the game is managing those three bars, and there are already several ways you can influence them.
To protect your eyes you can blink, which restores eye health — but while blinking you can't see the enemy, and you lose attention span. (Blinking is a button press)
You can also use eye drops, which stop eye health from dropping and shield you from items that would normally damage it.
As for psyche, there are many ways to affect it, and we'll refrain from listing them all for now. In short: some items raise or lower the bar directly, while others change the speed and direction it drifts in.
The base rule is that psyche slowly drains while you're watching the opponent, and slowly recovers while you're doing anything else (with some item exceptions).
So it isn't a staring stalemate: since both sides drain at the same rate, rounds are decided by the items — and by the attention you have to spend looking away to reach them.
The game loop is planned as a multi-round fight, where between rounds you pick which items from a random pool will appear on the shelves next round. Note that you won't know which exact shelf an item lands in, so you'll have to check the shelf first — and lose attention by not looking at your opponent. Round length isn't locked down yet, we're still balancing that.
We've put a bunch more gifs in a comment below, if you want to see more of what's already in the game.
What we'd like to ask, if anyone is interested in our endeavors:
Any feedback on the concept and the current state. We really lack shipping experience, and we'd like to correct our direction early rather than late. Was this too early? We're unsure how much of an unfinished VR game we should be showing publicly. Everything here is dev art. Is it better to keep posting rough progress and build an audience now, or stay quiet until the art pass is done and show it once? We'd rather hear it bluntly than guess.
We have nothing to link yet — no store page, no demo, no channel. That is why we asking about feedback. Also, we're interested to know, where would any of you prefer to track the development progress for now, if the project leave you interested?
Overall, guys, does this sound fun to you? May be you have any questions? We will be happy to answer anyone! Thanks for reading!
I have an idea for a game:so the way u move is like gorrila tag but instead of tag u take their nose and u put it in a pouch and if u have 0 noses after one minute u die and your invisible.after your nose gets taken a number pops up on your screen and you have to touch that persons pouch and put that number in to a lock but I don’t know how to make a game bc I’m just a teenager would that game sound good
I’m looking for folks interested with available free time to help develop a VR game. I am in process of developing various items for presenting the concept to all here, as an initial step I've written some of my 'day in the life'. I have a discord server I've just setup and a Google drive with my standard DocLib, to get the ball rolling.
Hey everyone! I’m 14 years old and working on a conceptual architecture to achieve true Full Dive VR.
The main goal is to allow a user to enter any virtual world or custom environment — for example, entering the world of Naruto, becoming the main character, and living out his story with 100% realistic physical and sensory immersion.
You might ask: "How is this possible? Isn't it sci-fi?"
My proposed design breaks down the system into two independent processing units (chips):
Brain Chip (Motor Cortex): Intercepts and decodes physical movement commands (walking, running, moving arms, controlling the avatar).
Spinal / Sensory Chip: Handles full sensory and emotional input — pain, fear, scent, touch, and visual perception signals.
Why 2 Chips Instead of 1?
By distributing the processing across two dedicated chips, we prevent single-processor overload and heat buildup. Splitting motor control from sensory/emotional feedback keeps hardware performance stable and temperatures low.
How the Brain Simulates Perception:
The brain operates as the central controller ("the boss"), while neurons act as execution agents ("messengers").
Our brains naturally simulate sensation even before physical contact occurs. For instance, if you imagine striking your foot with a hammer, your mind instinctively triggers a sharp, phantom sensation of pain and alarm.
Visual input normally alerts the brain to danger, triggering fear responses. The Spinal/Sensory chip acts as an artificial sensory proxy, feeding decoded signals for pain, scent, and emotional arousal directly into the nervous system.
Safety, Environment & Consciousness:
Life-Support Pod: The user remains inside a specialized pod monitored by an AI system tracking heart rate, respiration, and vital signs.
Motor Inhibition: The body is placed into a deep sleep / medically suspended state to prevent physical movement in the real world while active in VR.
Memory Suspension: Real-world memories are temporarily suppressed during the session to maximize immersion, restoring automatically upon waking up or logging out.
Neuralink has already demonstrated that thought-controlled cursor movement is possible. Expanding this into full-body motor control and sensory feedback is the logical next evolutionary step.
I’m giving myself a 4-year timeline to fully flesh out this framework, study the underlying neurobiology, electronics, and algorithms, and build a complete blueprint.
Feel free to ask questions, share technical critiques, or drop your ideas below — I’ll respond to everyone! 🚀🧠
Hi all — I’m an X-ray Technologist with 16+ years of OR experience, and I want to build and launch a VR simulator that lets techs practice real-world workflows using the O-arm system, especially for spine surgeries, neuro and orthopedic cases.
🔧 I want to develop a minimum viable product (MVP) focused on:
Virtual OR environment with patient and O-arm simulations
Simulated 2D & 3D imaging workflows -Unexpected trouble shooting mid-case
💡 This is designed to solve a real gap: techs often get minimal hands-on O-arm experience before being expected to perform in high-stakes surgical cases. This simulation bridges that gap with a safe, repeatable VR environment.
👥 Looking for collaborators:
Unity or Unreal developers (VR, Quest preferred)
3D artists (modeling the O-arm, OR, UI panels)
Anyone passionate about medical simulation, training tech, or immersive learning
🧪 MVP is non-commercial at this stage — no funding yet — but this could evolve into a commercial product or co-founder opportunity depending on how far we take it. We’ll get paid when we sell it. Trying to see how far I can get with a team with as low cost as possible. This is a needed product that doesn’t exist yet. Let’s make it happen.
A lot of people like to buy aftermarket exhaust for their vehicles. Would be cool if there was an app that let you sit in your car virtually and hear what all the different exhausts and mods actually sound like as you are driving. If someone makes this, please share it with me. I want no money, I just want the app. Thanks.