Some time ago I read the @lisyarus' post about his UI library. In his blog post he compares existing UI frameworks, analyses reasons why they don't work to them, and shows how he created his own library to build in-game UI.
His blog post immediately inspired me: how would I build my UI library?
| double delta_time_filtered(double dt_nanos){ | |
| // Warm start the filter by assuming 60 Hz. | |
| static double x[] = {1.6e7, 1.6e7, 1.6e7}, y[] = {1.6e7, 1.6e7, 1.6e7}; | |
| // IIR filter coefficients. 2rd order lowpass butterworth at 1/128 the sample rate. | |
| static const double b[] = {6.321391700454014e-5, 0.00012642783400908025, 6.321391700454014e-5}; | |
| static const double a[] = {1.0, -1.9681971279272976, 0.9684499835953156}; | |
| // Apply IIR filter coefficients. | |
| double value = b[0]*dt_nanos; | |
| for(uint i = 2; i > 0; i--){ |
| // | |
| // Lookup Tables for Transvoxel's Modified Marching Cubes | |
| // | |
| // Unlike the original paper (Marching Cubes: A High Resolution 3D Surface Construction Algorithm), these tables guarantee | |
| // a closed mesh "whose connected components are continuous and free of holes." | |
| // | |
| // Rotations are prioritised over inversions so that 3 of the 6 cases containing ambiguous faces are never added. 3 extra | |
| // cases are added as a post-process, overriding inverses through custom-build rotations to eliminate the rest. | |
| // | |
| // Uses the exact same co-ordinate system as https://gist.github.com/dwilliamson/c041e3454a713e58baf6e4f8e5fffecd |
| package microui_raylib | |
| import "core:fmt" | |
| import "core:unicode/utf8" | |
| import rl "vendor:raylib" | |
| import mu "vendor:microui" | |
| state := struct { | |
| mu_ctx: mu.Context, | |
| log_buf: [1<<16]byte, |
| // download glfw3 from https://www.glfw.org/download and then compile: | |
| // cl.exe -O2 q1.c -Iinclude -link opengl32.lib glu32.lib lib-vc2019\glfw3dll.lib | |
| #define _CRT_SECURE_NO_DEPRECATE | |
| #include <stdint.h> | |
| #include <string.h> | |
| #include <stdio.h> | |
| #include <math.h> | |
| #include <assert.h> |
| #include <blah.h> | |
| #include "imgui/imgui.h" | |
| #define IMGUI_DEFINE_MATH_OPERATORS | |
| #include "imgui/imgui_internal.h" | |
| using namespace Blah; | |
| namespace | |
| { | |
| MeshRef mesh; |
WARNING: Article moved to separate repo to allow users contributions: https://github.com/raysan5/custom_game_engines
A couple of weeks ago I played (and finished) A Plague Tale, a game by Asobo Studio. I was really captivated by the game, not only by the beautiful graphics but also by the story and the locations in the game. I decided to investigate a bit about the game tech and I was surprised to see it was developed with a custom engine by a relatively small studio. I know there are some companies using custom engines but it's very difficult to find a detailed market study with that kind of information curated and updated. So this article.
Nowadays lots of companies choose engines like [Unreal](https:
| CMAKE_MINIMUM_REQUIRED(VERSION 3.0.0) | |
| PROJECT(em_gl VERSION 0.1.0) | |
| LINK_DIRECTORIES( | |
| $ENV{VCPKG_ROOT}/installed/x64-windows/lib | |
| ) | |
| FILE(GLOB SRC | |
| *.cpp | |
| *.h |
| // SDL2 Hello, World! | |
| // This should display a white screen for 2 seconds | |
| // compile with: clang++ main.cpp -o hello_sdl2 -lSDL2 | |
| // run with: ./hello_sdl2 | |
| #include <SDL2/SDL.h> | |
| #include <stdio.h> | |
| #define SCREEN_WIDTH 640 | |
| #define SCREEN_HEIGHT 480 |
Find the Discord channel in which you would like to send commits and other updates
In the settings for that channel, find the Webhooks option and create a new webhook. Note: Do NOT give this URL out to the public. Anyone or service can post messages to this channel, without even needing to be in the server. Keep it safe!
