Accepted: V-Sekai Roadmap and Goals 2023-06-18

Metadata

  • Status: superseded
  • Deciders: V-Sekai, fire, guillefix
  • Tags: V-Sekai, chatgpt4 summary,

Context and Problem Statement

What is the V-Sekai Roadmap and Goals?

Describe the proposed option and how it helps to overcome the problem or limitation

The roadmap presented here is short-term.

Describe how your proposal will work with code, pseudo-code, mock-ups, or diagrams

By avoiding work on User Generated Content (UGC) and world building, we can prioritize the three main states in the roadmap: “World / Avatar Performance” (WAP), “Networking” (NET), and “UI/UX”. This allows the team to focus on the core aspects of V-Sekai and achieve the goals more efficiently.

Goals

World / Avatar Performance (WAP)

  • Timeline: Q2-Q3
  • Implement light assets and asynchronous loading to reduce load time by 30%
  • Utilize modern rendering techniques and high-performance libraries to achieve 60 FPS on mid-range devices
  • Apply network optimization and low latency protocols for better performance, reducing latency by 50%

Networking (NET)

  • Timeline: Q2-Q3
  • Use efficient data formats and optimized compression algorithms to reduce file size by 40%
  • Ensure accurate IK points are respected, achieving 95% accuracy
  • Explore multiple technologies and alternative solutions for continuous improvement, evaluating 3 new technologies per quarter

First Time User Experience (FTUX)

  • Timeline: Q3-Q4
  • Optimize first-time user experience by improving the loading process, increasing user retention by 20%

Diagram

sequenceDiagram
    participant V-Sekai
    participant Player
    participant Creator
    participant Lyuma as "Lyuma (VRM1 - WAP)"

    Note over Lyuma: WAP: World / Avatar Performance
    Note over Lyuma: Timeline: Q2-Q3

    Creator->>V-Sekai: Implement light assets and asynchronous loading (reduce load time by 30%)
    V-Sekai->>Player: Utilize modern rendering techniques and high-performance libraries (achieve 60 FPS on mid-range devices)
    Player->>Creator: Apply network optimization and low latency protocols for better performance (reduce latency by 50%)

    Note over Player, Creator: NET: Network Optimization Techniques
    Note over Player, Creator: Timeline: Q2-Q3

    Creator->>V-Sekai: Use efficient data formats and optimized compression algorithms (reduce file size by 40%)
    V-Sekai->>Player: Ensure accurate IK points are respected (achieve 95% accuracy)
    V-Sekai->>Player: Explore multiple technologies and alternative solutions for continuous improvement (evaluate 3 new technologies per quarter)

    %% Metrics
    Note over Player, Creator: Metrics:
    Player->>Player: File size reduction
    Player->>Player: IK accuracy
    Player->>Player: Technologies evaluated

sequenceDiagram
    participant Fire
    participant Creator

    Fire->>Creator: Optimize first-time user experience by improving the loading process (increase user retention by 20%)

    Note over Fire, Creator: FTUX: First Time User Experience
    Note over Fire, Creator: Timeline: Q3-Q4

    %% Metrics
    Note over Fire, Creator: Metrics:
    Fire->>Fire: Load time reduction
    Fire->>Fire: Frame rate (FPS) for flat desktop
    Fire->>Fire: Frame rate (FPS) for VR desktop
    Fire->>Fire: Latency reduction
    Fire->>Fire: User retention rate

Positive Consequences

  • Easier creation of V-Sekai.
  • Focused development on core aspects.

Negative Consequences

  • Potential overhead challenges.

Option graveyard

  • Waiting for Godot Engine 4.2 instead of assisting with 4.1 features.

If this enhancement will be used infrequently, can it be worked around with a few lines of script?

No. This is a process.

Is there a reason why this should be core and done by us?

This is a core process for V-Sekai.

References