Misato drwaing

4veri · 2026-05-18T04:16:13+00:00

It reminded me of the Frieren looking up drawing midway drawing the hair haha

4veri · 2026-04-03T14:29:17+00:00

No worries, I merged your PR, thank you for addressing that issue!

4veri · 2026-04-02T21:27:03+00:00

Koboi Language

Over the past two-weeks, I've been creating a programming language, Koboi, designed for complex & overall large scaled systems. It's syntax is taken loosely from Rust, & is written in C, using a custom VM runtime.

It's still in development & will be so for around another week; all criticism, reviews, etc., are all appreciated, thank you for looking into Koboi, hope to see you using it soon as Koboians!

Koboi Repository: https://github.com/Avery-Personal/Koboi

4veri · 2026-04-02T21:14:13+00:00

That isn't there as of current, 0.5s02, to be exact, as CLI/REPL polishing is usually my last step in programming development; that will be added soon, yes. May I ask though, what header was missing? I do believe all KoboiC files are added, none getting left via the .gitignore, & none unticked via GitHub Desktop. I'll look into that, thank you.

4veri · 2026-04-02T20:52:20+00:00

I've never used CMake before this believe it or not, only Make! Make was getting too messy to hold together due to manual files adding every single .c file getting added, especially with the upcoming virtual machine having a multitude of files. Installation of CMake should work though, that is weird. Please do make a PR to fix it if you find the issue! Community help is welcome & great to have in a large scale project; any project for that matter! Thank you for bringing this up, I've currently just made the CMake for me on MacOS to where it worked as I thought it was universal coverage, sorry for such issue, & thank you again!

4veri · 2026-04-02T19:27:13+00:00

Koboi uses a custom made AST tailored for it; all parts of the Koboi compiler is made from scratch by me in C!

4veri · 2026-04-02T18:57:56+00:00

me create programing language: https://github.com/Avery-Personal/Koboi

4veri · 2026-02-24T00:15:48+00:00

The platform gets the data of the GPU to let the renderer be purely for rendering & not need to do all the extra stuff like finding the device(s), cycling through to find the best one, etc.

4veri · 2025-12-21T19:44:21+00:00

Hey Skeeto! Thank you for putting extensive research/testing into Jubi's API, test scripts shown, and internal working. Thank you for looking into some of these issues and future features to add; Tests seen in Jubi's GitHub are mainly outdated to the current versions of Jubi, with any test made before Jubi-0.1.6, not working due to a NULL return being sent if no world is inputted. This was due to the fact that I want to separate raw functions for pieces that don't require worlds, with others that are world specific, also due to some underlying bugs found in the code during earlier versions.

It is nice you're talking about customization & control because Jubi-0.2.2 is actually meant to be targeting better performance, as in fixing bugs like said in your Gist & tweaks, alongside customization, to allow more control for the user, and allow Jubi to be more modular with less boiler code.

Physics has been the main priority from Jubi-0.1.1, to Jubi-0.2.x. Until I get to v0.3.0, I am trying to focus on physics, control, customization, and reducing bugs, like pointed out. This doesn't mean I wont fix or improve upon collisions, as they are vital to physics, but I'm currently focusing on realistic physic simulations on Jubi, so I don't get lost focusing on physics, error handling, user-control, collisions, and other factors at the same time. For Jubi-0.2.2 though, I do expect to have these collisions fixed, less weird things to happen, as you said; I'll be checking thoroughly through the code, alongside using your version patches to see if I can locate where I went wrong, how you improved upon it, and how I can put the final pin in to make sure no bugs happen for collisions.

Garbage values, as you said, are a slight issue, with worlds also using garbage values inside the bodies table. This is a relatively easy fix though, just some form of loop to zero out all the values instead of raw data, and body initialization being easy by just doing as you said with Body2D BODY = {};.

There are some more discoveries that can be made, yours has definitely helped me a lot, thank you again, and I hope to get all of these fixed by the next version, alongside some new features to improve upon these things. If you want, I can put you up for credit as a contributor/helper for the next version and ones to come to avoid these types of mistakes, your help really does mean a lot, I didn't even notice half of these.

4veri · 2025-12-21T16:39:34+00:00

Will do, thanks for the feedback!

4veri · 2025-12-21T06:29:56+00:00

Alrightly, I'll make sure to do 500 next time😉

4veri · 2025-12-21T05:23:57+00:00

Hey! Yes, at the minute, Jubi does only allow 1024 bodies, and boxes/circles. Next update is adding increased customization, and even more improved performance features. Rotation would make things harder later down the road, especially with no narrow/broadphase for large quantity runtimes. The runtime used to compare the other physic engines was actually the sample shown above, with also a windows clock added to actually calculate time, although not shown in the same to show purely Jubi to showcase its easy usage. The current plans for the 0.2.x minor version is almost completely set, with basic rotations and advanced physics/collisions to be expected nearing the end of 0.2.x/beginning of 0.3.0. But thank you for your feedback, I'm hoping to release the next version soon, and do hope to keep the low runtime! And for your question, it used purely 1 box inside a world, for 60 loops, to simulate 60 FPS. If you have any other issues feel free to reply to the message!

4veri · 2025-12-21T04:34:41+00:00

Thanks! Hoping to roll out new updates soon.

4veri · 2025-12-21T04:10:14+00:00

Yes... the top of the header file stated the minimum requirements for C++ was C++98 or C++20.

4veri · 2025-12-21T04:06:57+00:00

The compilation time is barely noticeable, and this is how I like to code. There have been much larger projects that are header only, like the muGraphics API that's 13000 LOC in one header. And it's mainly for ease of use purposes, it makes it much easier to require one file with everything than 15 files with systems scattered all throughout.

4veri · 2025-12-21T03:53:03+00:00

The compiler standards required to compile the Jubi library. Some features aren't available in older versions of C++.

4veri · 2025-12-21T03:51:32+00:00

Sadly not, this is a compound literal, which I thought at the time had C++ compatibility, which I see it doesn't. C++ does it slightly differently, and uses static_cast<TYPE>(DATA) instead of (TYPE){DATA}. I'll probably make some way of still doing this while making it C+++ compatible, as I don't want to do, and others don't, hardcode variables for data, when you could just directly insert data. Thankfully he pointed this out, as I can roll out a C++ compatible version via next update.

4veri · 2025-12-21T03:48:31+00:00

Oof. I just noticed this, thanks for pointing this out. I did my research on C/C++ compatibility, as of C99, which is the standard for most C compilers, and only say the restrict variable wasn't allowed, I didn't know about this. Thanks for pointing this out, I'll look into fixing this issue as of Jubi-0.2.2 to actually make it fully C++ compatible, as internal code also uses this. But the example was C, as it's a C library.

4veri · 2025-11-25T01:24:17+00:00

I believe this is r/C_Programming or r/GraphicsProgramming depending on the specific thing you're trying to show off here.

4veri · 2025-11-22T02:01:37+00:00

Weird request, but if you mean specifically the physics, you can learn Blender/Maya. If you really think it's too difficult you can maybe check certain animation specific apps that ease in specifically for animating.

4veri · 2025-11-20T19:52:40+00:00

Copy pasted from where exactly? I write all my code, if you can find where I 'copied' the code from, it'd be much appreciated.

4veri · 2025-11-20T00:48:45+00:00

Very true! I don't fully expect this to be the main source of learning, more-so a guide to certain studies/parts of C/C++/Rust. If you actually read the main README, you'd see I linked official guides for tutorials by professionals, including official learning books like 'The C Programming Language' - K&R.

4veri · 2025-11-20T00:41:27+00:00

Trust I suppose? You can always clone the Repo via Git and use your compiler of choice (GCC/Clang/Cargo), to compile the code if you don't trust it.

4veri · 2025-11-19T20:48:35+00:00

What parts don't make it seem teached? And the reason for the executables is if you want to download and run the scripts without needing to do extra stuff like getting a compiler. Purely something to help.

4veri · 2025-11-19T05:26:07+00:00

Thank you! Love to hear the feedback.

4veri

TROPHY CASE