The plan is to create a large narrative driven game using a self made engine with Vulkan…
- User
The plan is to create a large narrative driven game using a self made engine with Vulkan and C++
Assistant
Based on this plan alone, feasibility is extremely low (1/10). Here's why:
- Vulkan's Complexity: Vulkan is a low-level, explicit API. Building a stable, feature-complete engine (renderer, physics, audio, networking, asset pipeline, tools, etc.) requires immense expertise and time.
- "Large Narrative-Driven Game": This implies vast amounts of content (art, writing, voice acting, animation, level design, music) and complex systems (dialogue trees, branching narratives, quest logic, scripting). This is a massive production burden on top of engine development.
- The Engine Trap: Building the engine becomes the project. Performance optimization, platform support (PC, consoles?), bug fixing, and tool creation will consume years before significant game content is built.
- Resource Intensity: This plan requires a rare combination of deep C++/Vulkan expertise, game design skill, narrative design talent, and massive amounts of time/funding. It's typically the domain of large, experienced studios (and even they often use established engines).
- Scope Creep: Engine development naturally leads to scope creep as you chase the "perfect" feature set instead of shipping a game.
Key Risks: Burnout, project abandonment, engine limitations hindering the game's vision, never finishing the game itself.
Starting Rating: 1/10 (Highly Impractical)
Let's see how technical achievements change this rating. Provide the first achievement!
- User
The plan is to create a large narrative driven game using a self made engine with Vulkan and C++
Assistant
Based on your plan to create a large narrative-driven game using a self-made Vulkan/C++ engine, here's my initial feasibility assessment:
Initial Feasibility Rating:
1%
(Extremely High Risk / Borderline Impossible for a Solo/Small Team)Key Challenges:
- Engine Complexity:
- Vulkan is a low-level, explicit API requiring deep GPU/rendering expertise.
- Core systems needed: Renderer, physics, audio, animation, asset pipeline, scripting, UI, etc.
- Scope of "Large Narrative Game":
- Expect 100k+ lines of code for the engine alone.
- Content creation (writing, art, sound, levels) for a "large" game often requires 10,000+ hours.
- Team/Time Constraints:
- AAA studios with 100+ engineers take 3–5 years for such projects.
- Solo development could easily exceed 10 years.
- Maintenance Overhead:
- Debugging a custom engine is exponentially harder than using Unreal/Unity.
Now, provide your first "technical achievement." I'll reassess feasibility after each one.
(Example achievements: "Implemented Vulkan renderer with PBR," "Built a working scene editor," "Integrated Lua scripting," etc.)
Current Progress:
- 🔴 Engine: 0%
- 🔴 Game: 0%
- 🔴 Feasibility: 1%
Waiting for your first achievement...
- Engine Complexity:
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.