And that combined with the previous post is pretty much the current state of the engine!

My long term plan is to either have this as my main portfolio piece, or if it becomes good enough try to make it a competitive engine!

If you came this far thank you for reading and have a great day!!
(5/5)

Now this may seem like a curse but it was a blessing in disguise, thanks to it being broken I had plenty of time to iterate over how the infrastructure would look before I got it running. I also explored lots into how to get a class reflection system working.
(4/5)

But the school year was coming near its end, and I realized that I wanted to work on it from home, which wouldn't be possible due to the NDA.

So I ripped my engine in two, and once the school ended I was left with half an engine and a broken mess.
(3/5)

I came up with the name QWARP mostly due to it sounding cool and thanks to qw being next to one another, which would make an engine namespace easy.

Anyhow, I got the basics up and running and I had an ECS, event manager and rendering.
(2/5)

Currently what's missing is a wrapper for frame buffers and some sort of pipeline. After that it's rebuilding my mesh component and plenty of debugging.

As a man, same

Yeah! It was what I thought you asked with frameworks

It's made in c++23 and it's mostly based on unreal. My overall goal is usually summarized as "lightweight unreal". But I'm also taking ideas from my school's engine (lightweight and more like the good old days kind of engine) as well as unity (plugins and UI) and godot (possibly nodes and UI)

PRETTY AF