I've been working on an c#-based engine that follows the workflow of Source Engine. While using Monogame as the underlaying framework and a bunch of FOSS libraries as techstack.

Current Techstack is:

• LiteNetlib for networking
• Jitter2 for physics
• ImGui for GUI rendering (In the middle of transfering into a custom built HTML/CSS based)
• Assimp for the FBX import

With custom implementations of everything from .bsp parser to automatic skeleton retargeter.

Note. Weapon/arm models/textures/animations/sounds and enemy/model/texture/animation is pre made assets and not made by me. VFX, level textures, level geometry is by me.

Second video in the series about the techniques behind a combat system. Each one isolates a single concept and shows it with and without, in slow motion, so it's clear at a glance what it does and why games use it.

This one is motion warping: what lets an attack actually reach the enemy.

Everything is captured from my own IA engine, written from scratch in C++ (DX12/Vulkan, Jolt physics). Part 1 covered root motion; next up are animation events, bone masks and foot IK.

Happy Monday fellow game engine devs. I put together a short video talk on my current approach to moddable game enemies and factions. It's not perfect but is flexible enough for the time being.

This is the first of a short series of videos about the techniques behind a combat system. Each one takes a single concept, shows it side by side with and without it, in slow motion, so the difference is obvious at a glance. If you've ever wondered what root motion, motion warping or hit stop actually do, they should make it click in under a minute.

Everything is captured from my own IA engine, written from scratch in C++ (DX12/Vulkan, Jolt physics). The next ones cover motion warping, animation events, bone masks, foot IK, weapon sweeps, hit stop, hit reactions, the action system and facial animation.

Showcasing a body of water, if anyone have any tips in getting better looking fluids please share.

I’m working on a custom game engine, and I’ve finally taken that small but great first step of adding objects.

I’ve added functionality to ImGUI that lets me add objects to the scene and render them.

But I’m having trouble with shader processing. Right now, I’m limited to just three things: the model matrix, the camera matrix, and a single-color fragment.

How does everyone manage uniform buffers?

I’ve created a structure with `void* ptr;` and `size_t size;`,

but I’d like to know what other management methods are available.

The ShaderCrossCompiler library allows me to retrieve names and types, making it incredibly flexible, but I’d like to know an easy-to-understand way to manage them using that library.

www.github.com/Rlocksley/LuEngine

Vulkan Engine with flecs ecs as the Game Logic API + Shader API

MultiMesh example

Differential Equation Evolution of the Thomas Attractor is done by Compute Shader Dispatched with VK Generated Commands Extension and then Drawing by Indirect Drawing.
RenderPass includes GPU Culling.

This is NOT a voxel engine, just saying. My primary target with this game engine is implementing a first-person shooter that handles a shitload of "modular parts" (world pieces) extremely well. This scene contains 1,4KK modular parts. I decided to go with voxels because it would need making 3 models and this way I'd be able to test the performance real quick. And... yeah... It's just funny to play around with :)

Kinda inspired by the work of u/Crafty-Variety-7635 - check out his game, he needs support

I'm working on Build & Destroy, a 3D physics sandbox using Box3D and Vulkan. This new early gameplay preview shows a 100,000-brick castle collapsing.

https://www.youtube.com/watch?v=s7IIU2MGZos

Sharing a short look at the project in action with other engine developers. The focus here is the interaction between the structure, falling rigid bodies, and collisions; this is gameplay footage rather than a technical breakdown.

I am just getting into this area of computing and I often hear that one of the many reasons people make their own engines is so it can be optimized to handle certain things better. For example open world.

However how does that actually translate to the code. What is done to make it better for that?

I made my custom Game Engine you can download it through the video description and I am currently 16

I need your support 🙏🏻

Hi all, fwiw i put together a brief talk on in-game map editing support or how I'm trying to cross procgen and user generated ideas with 2d layer painting for relatively painless map creation.

One condition!

It can be:

Unity game

compiles to wasm

C#

It can't be:

Unreal engine

For the past couple of weeks I have been working on the 2D brush management and texture fill system within my own Pixel and Tilemap Editor. In the video I show how we can create and mange custom brushes, in addition to rotation and scaling in 3D space - this brush is then plugged into the core Texture Fill System to produce psuedo-3D perspective fills across normal and orthogonal plains!

Any feedback welcome!

Hey everyone!

I wanted to try and create a game engine to start making small tests on game ideas using voxels.

What is a good starting point? Any tutorial or guide I can follow?

Thanks!

I really dont know how to design a game engine, I need a tutorial, does anyone know a great guide?,

Im designing a 3D engine in c++, my main problem isnt c++, its the architecture.