• Introduction
  • Setting Up Your Workspace
  • Development Pipeline
  • Product Overview
  • Writing Proposals
  • Coding Standards
  • Planning
  • Profiling Plan
  • Documentation Standard
  • Quality Assurance
  • Build Server
  • Risk Assessment
  • Production Roles
  • The Team
  • Configuration Management
  • Credits
  • Wiki Contributions


    • Renderer

  • Architecture
  • How To Use Fallback
  • Detailed Feature List
  • Research

    • Writing Proposals

    The Goal

    The goal is to set clear research guidelines and allow any team member to implement a proposal. The format below is written to force the author to truely think about how the feature would work and would be implemented into the renderer.

    The Format

    # Proposal

**Date:** [Day/Month/Year]
**Author:** [Author]

## Introduction

What is the task and how does it work.

## Approaches

Discuss different approaches and compare them. Than propose what we should do.

## Result

The expected end result when the entire proposal has been implemented.

## Workload

### Subtask 1

What is this subtask? How does it work?
A subtask could be a optimization technique like reprojection
or maybe its something like rendering a texture.

#### How long will it take

How long with this take and why.

#### What is the resut of this subtask

expected performance impact?
expected visual changes?

#### Proposed Implementation

Here go into a bit more detail on how we should implement it. Add some code snippets and some pseudo code for example.

#### What files need to be modified.

* d3d12_xxx.cpp
* demo.hpp

### Subtask 2

// ... etc

### References