tcantenot

Spherically Distorted Frustum Grid

This document describes a variant of the frustum grid that uses spherical depth shells instead of planar depth slices, while retaining the standard perspective lateral coordinates.

Planar Grid Overview

The planar frustum grid uses a piecewise depth distribution. Key parameters:

• κ = 2·tan(θ/2)/N — pixel cone slope (θ = FOV, N = pixels along one axis)
• s — voxel size (world-space units)

tcantenot

#include "precise_sleep.h"

int main()
{
    const int use_nt_set_timer_resolution = 1;
    InitPreciseSleepFunction(use_nt_set_timer_resolution);
    
    // Your app code that uses PreciseSleep(sleep_duration_s);
    
    DeinitPreciseSleepFunction();

tcantenot

// Based on: https://x.com/ptrschmdtnlsn/status/1840765584398840233

#include <stdint.h>
#include <stdio.h>
#include <string.h>

constexpr uint32_t N = 7;
constexpr uint32_t M = 1u << N;
constexpr uint32_t MaxNumStates = 6;

tcantenot

#include <assert.h>
#include <stdio.h>
#include <time.h>

#define COBJMACROS
#include <windows.h>
#include <d3d11_1.h>
#include <d3dcompiler.h>

//////////////////////////////////////////////////////////////////////////////////////////////////////////////

tcantenot

#include <stdint.h>
#include <stdlib.h>
#include <stdbool.h>
#include <windows.h>
#pragma comment( lib, "user32.lib" )
#pragma comment( lib, "gdi32.lib" )

#define SCRW 640
#define SCRH 480

tcantenot

From time to time I receive questions on the depth aware upsampling mentioned in the INSIDE-rendering presentation: https://loopit.dk/rendering_inside.pdf#page=39

The goal of this technique is to take the texture-output from a half-resolution pass, containing the results of sampling volumetric fog - and scale it up to full resolution. This presents two challenges:

• Making sure samples from the low-resolution buffer, do not spill on top of foreground objects in the high-resolution buffer
• Making sure the samples in the volumetric fog can be properly accumulated by TAA after upsampling

tcantenot

Core Coding Standard

Coding practices are a source of a lot of arguments among programmers. Coding standards, to some degree, help us to put certain questions to bed and resolve stylistic debates. No coding standard makes everyone happy. (And even their existence is sure to make some unhappy.) What follows are the standards we put together on the Core team, which have become the general coding standard for all programming teams on new code development. We’ve tried to balance the need for creating a common, recognizable and readable code base with not unduly burdening the programmer with minor code formatting concerns.

Table Of Contents

• Why we need Coding Standards
• Context is Important
• Stylistic Standards

• Namespaces

tcantenot

// Copyright (c) 2023 Tomasz Stachowiak
//
// This contribution is dual licensed under EITHER OF
// 
//     Apache License, Version 2.0, (http://www.apache.org/licenses/LICENSE-2.0)
//     MIT license (http://opensource.org/licenses/MIT)
// 
// at your option.

#include "/inc/frame_constants.hlsl"

tcantenot

import os
import bpy
import sys
import typing
import inspect
import pkgutil
import importlib
from pathlib import Path

__all__ = (

tcantenot

Shader "Unlit/MatCap Techniques"
{
    Properties
    {
        [NoScaleOffset] _MatCap ("MatCap", 2D) = "white" {}
        [KeywordEnum(ViewSpaceNormal, ViewDirectionCross, ViewDirectionAligned)] _MatCapType ("Matcap UV Type", Float) = 2
    }
    SubShader
    {
        Tags { "RenderType"="Opaque" }