btipling

A good way to think about a buffer or an image descriptor is to imagine it as a very fat pointer. This is, in fact, not too far removed from reality, as we shall see.

Taking a peek at radv, we find the uniform buffer and storage buffer descriptors to be a 4-word tuple, where the first two words make up the address, followed by length in bytes for bounds checking and an extra word, which holds format information and bounds checking behavior [^1].

Similarly, the sampled image descriptor is a 16-word tuple containing an

btipling

const needle: []const u8 = "layout(bindless_sampler)";
const needle_len: usize = needle.len;

pub fn disableBindless(
    bytes: []u8,
    locations: []const usize,
) ![]u8 {
    var buf: [50]u8 = undefined;
    var loc: usize = 0;

btipling

#include <GL/glew.h>
#include <GLFW/glfw3.h>
#include <vector>
#include <cmath>
#include <cstdio>
#include <limits>
#include <chrono>
#include <thread>
#include <mutex>

btipling

i was wondering if we should/could list common errors in the gl get started thing too, after debugcallback/renderdoc chapters or probably in some appendix, if you have more of those, let me know then we can compile those together into some comprehensive unfuck gl list

• nothing works:

  • get rid of GLCALL/GLCHECK macros, most of them use glGetError incorrectly anyway
  • setup glDebugMessageCallback see here
  • your shaders could contain errors, make sure you check compile and linking state and fix according to what the error was highlighting

• renderdoc crashes when i try to capture something from my project:

  • most likely some of your code is fucked, its rarely renderdoc being fucked in that case

• make sure to hookup glDebugMessageCallback as stated above

btipling

const std = @import("std");
const zsdl = @import("libs/zig-gamedev/libs/zsdl/build.zig");
const zopengl = @import("libs/zig-gamedev/libs/zopengl/build.zig");

pub fn build(b: *std.Build) void {
    const target = b.standardTargetOptions(.{});
    const optimize = b.standardOptimizeOption(.{});

    const exe = b.addExecutable(.{
        .name = "hellotriangle",

btipling

param ([string] $Status)

function Invoke-SlackRequest([string]$Url, [hashtable]$data, [hashtable]$headers) {
    Write-Host "Making a request to slack @ $Url"
    $Body = ConvertTo-Json -InputObject $data
    Write-Host "Sending body: $Body"
    $headers["Content-type"] = "application/json; charset=utf-8";
    $result = Invoke-RestMethod -Method 'Post' -Uri $url -Body $body -Headers $headers
    if (!$result.ok) {
        Write-Error "Not OK!"

btipling

{
  "foo": 3,
  "bar": 10
}

btipling

PS C:\Users\swart\projects\powershell_scripts> .\name_value_store.ps1

PS C:\Users\swart\projects\powershell_scripts> Add-Data -Name "Foo" -Value 2

PS C:\Users\swart\projects\powershell_scripts> Add-Data -Name "Bar" -Value 8

PS C:\Users\swart\projects\powershell_scripts> Read-Data


Name Value

btipling

param ([string] $Path)

Get-Item -Path $Path -ErrorAction SilentlyContinue -ErrorVariable test | Out-Null
if ($test.Count -eq 0) {
    Write-Host "The file at $Path exists!"
}
else {
    Write-Host "The file at $Path was not found."
}

btipling

param ([string] $name, [int] $value = 0)

$table = @{ Name = $name; Value = $value }

Write-Host "Your table is:"
Write-Output $table
Write-Host "`n"
Write-Host "It has this many items in it: " $table.Count
Write-Host "`n`n"