/agdg/ - Amateur Game Development General

>Forgot to make the anchor post
My bad.

Consider this your ANCHOR POST.
Link your submissions here.

>>1082 (OP) 
>come participate in the thing anon!
<Sure where is it?
>trashcanyoushouldkillyourselfretardnigger.nig

What's wrong with trashchan? There's literally no drama because the site was mostly dead.

>>1088
The only thing I know about is that some people doesn't like that Chobitsu is here.

451m3MEME060323.jpg
[Hide] (207.7KB, 1200x1200)

I'm not sure if it would be helpful to you here, BO, but here's a little prototype project I made back when I was still hoping for a smol team to develop around building a robowaifu simulator:
https://gitlab.com/Chobitsu/muh-robowaifu-simulator

It covers most of the basics of creating your own OpenGL engine (and it runs really fast) based on the great training site:
https://learnopengl.com/

It uses GLFW was the windowing manager:
https://www.glfw.org/docs/latest/quick_guide.html

---

Good luck with your Game Jam this year, /agdg/ !
>

>>1089
Why do you think that, Anon?

>quickly read through
>the retardation has already been cleaned before I finish
I'm feeling rather useless.

do_your_best_anon.gif
[Hide] (2MB, 498x440)

>>1108
>>the retardation has already been cleaned before I finish
Lol, sorry, BO.

>I'm feeling rather useless.
You'll be fine, press on with your plans. Just keep moving forward, Anon!  :)

>>1111
checked and >>>/out/

0001.png
[Hide] (65.9KB, 256x256)

0001.png
[Hide] (69.9KB, 256x256)

0001.png
[Hide] (93.7KB, 256x256)

>>1082 (OP) 
Made some more assets ( >>1062 ), feel free to use. Cant exactly render explosion, so silly splashes it is. 


https://files.catbox.moe/ikxowg.7z

>>1116
I'm really digging your asteroid aesthetic. What's in them? Why are they glowing in non-natural patterns underneath?

Spoiler File
(727.3KB, 1024x512)

0001.png
[Hide] (64.9KB, 256x256)

>>1117
>Why are they glowing in non-natural patterns underneath
Picrelated HDRI. 
And I can make some more, with slightly different aestetic, more crystals. And some planets, but later.

>>1118
Your pic #2 ship is GOAT, Anon. GG.

Finally started on my idea and got some preliminary fiddle-fucking with physics libaries out of the way.  Figured I'd share my findings:

			last commit		language
Box2d		2023/02			CPP
Bullet		2023/11			CPP
Chipmunk	2023/09			C

All three built without issue.

# Chipmunk https://github.com/slembcke/Chipmunk2D
Half-assed commit logs don't inspire confidence, but it's tiny and built instantaneously.  The demo that runs is beautiful and performant, but it seems there are routines or families of routines that cause it to hang, though, so not really worth considering.

# Bullet https://github.com/bulletphysics/bullet3
Takes awhile to build, and has a smattering of warnings.  The first demo runs with nominal CPU and GPU usage.  It's 3d.  The demos all seem to work, and some are very impressive— there's a "neural network 3d walker" demo in which spiderbots figure out how to move.  It's a massive and overpowered dependency for Asteroids, but using it has the virtue of teaching you to use the basics so that you can graduate to the more advanced features later.

# Box2d https://github.com/erincatto/box2d
Seems like a sensible midway point between the complexity of Bullet, and the minimalism of Chipmunk.  Its demo reel is somewhat incomprehensible (the ray collision test relates no information about collisions to the user?) but is extensive enough that you get a good idea of how powerful it is.

>>1116
Thank you kindly, anon.

>>1080
Ballzanon, what are your thoughts on >>1120? Are you using your own physics "engine"?

>>1121
>Are you using your own physics "engine"?
Yeah I have my own simple physics with verlet integration and spatial grid to optimize checks, with 2-8 substeps per frame depending on target framerate. If you want to do your own thing and are just going to have a couple of dozen asteroids, euler integration and brute force checking everything can get you a long way. Personally I try and keep my dependencies as light as possible but if you want to do 3D or something more complex they might be the right solution for you.

>>1120 (me)
Little follow-up: Chipmunk fails to build with GCC 13 because of some compiler arcana nobody's bothered to figure out.  It also failed to build with Clang for possibly unrelated reasons,  It does bulid with TCC.  It also turns out to be available from Void's package repo, so the point is moot.

Hoping to get some progress this weekend, been sick then work stealing time. How are anons doing so far?

>>1125
Wishing I'd either bothered to learn Godot or just used plain SDL instead of dicking around with GL texture mapping and all this pointless minutiae.

But oh well; I should have something on the screen fairly soon.

>>1125
Not too bad, just chipping away bit by bit. I haven't done any gamedev (or C/C++ for that matter) since the last jam but Raylib's docs and examples have been great for getting up to speed.
>>1126
Sounds tricky, good luck anon!

>>1126
At least you'll get extra cool points, anon!

Just about two weeks left. I think. I'm not sure how time works.
Got anything to show off, Anon?

0003.png
[Hide] (47.9KB, 256x256)

crystal_perf.png
[Hide] (69.4KB, 256x256)

0020.png
[Hide] (62.4KB, 256x256)

>>1134
Made some crystals. No code progress beyond making sdl work.

jam.png
[Hide] (521B, 640x480)

>>1134
Not much to show visually but I think I've got an underlying engine structure which will work, my hope is that the actual gameplay programming will be fairly simple by comparison.

>>1136
Writer's block?
>>1137
>engine structure
Tell me more.

ClipboardImage.png
[Hide] (140.8KB, 637x500)

ClipboardImage.png
[Hide] (84KB, 1026x1053)

>>1138
>Writer's block?
Something like that.

>>1138
>Tell me more.
Sure, at the moment there's some type structs (Game, Entity, Label) which have relevant members and their own state machines. The current Game state is the main driver of the others, running state processing functions for each type as needed. For instance, the menu in that pic is a linked list of Labels, which can act as images, text or buttons. State functions are given pointers to things like the Game object and the pointer to the current Label list, so a button can do something like changing the Game state, which will then swap out the UI during state entry/exit functions.

20240325_1.mp4
[Hide] (4MB, 960x540, 01:11)

Finally got some good time over the weekend to make progress.

Had an idea to make a proper game, with "build your own ship from blocks" mechanic, but it seems like too much work. Basically you have square parts, which can be attached to each other, but it increases size of the ship, and reduced maneuverability. I just dont think its worth it. 
>>1141
Neat.

>>1142
You could do it the way it's done in Cataclysm: Dark Days Ahead.  You have a grid (ie, an m by n matrix) and in each square there might be a "frame" that links the parts of the ship together and allows things to be put onto the frame.  Some objects care about adjacency to other objects, etc.

This may or may not be easier than thinking of it as some sort of graph of objects.

>>1143
Implementation it is not a problem, I am just lazy. It will require a lot of modelling, a lot of balancing stuff around, etc etc, and I am just not sure it will be fun, without a ton of effort put into it, compared to traditional ships. Building blocks are autisms magnets though. 

Another gimmick idea is "big fish eats smaller fish" type of game, and I think I will go with it. 
I also need to render some exhausts and explosions, and its not going well on my gpu, so simplified version will do.

>>1144
Have you tested it with placeholders? Rendering sounds like it might take quite a bit of time.

>>1145
I am using sprites so rendering in basically instant. 

Unless you talk about rendering explosions/exhausts in blender, in which case yes, practically impossible for me.

>>1141
Looking good, anon. I'm looking forward to seeing your twist.

One week left.

ClipboardImage.png
[Hide] (265.4KB, 346x346)

>>1148
Plenty of time.

36d3e21750889fcb22c1c885add3054de33d43282bff15b686e662cc25dac2aa.gif
[Hide] (714.4KB, 344x426)

After wasting 3.5 weeks procrastinating on C and GL, I decided to learn Godot, and set up the ship, and the control scheme I wanted.

I might still be able to pull off the concept.

>>1150
You can do it anon!

>>1150
I hear this is also how real gamedev goes.

ClipboardImage.png
[Hide] (455.1KB, 1026x892)

ClipboardImage.png
[Hide] (597.9KB, 1920x1040)

>>1150
>3 days left
A perfect time to start!

Mostly finished renderer. Doing everything in most brute and lazy way possible, no texture atlas, no buffers, no optimization, everything breaks if you delete any file, even when its not used...

Now I only need to make the game itself. Already have an idea, where you control a single ship, and collect crystals, after collecting enough you add another follower ship, basically like in snake. I wanted to make "upgrade system" but I dont think I have time for it, which is shitty, I know.

ClipboardImage.png
[Hide] (1.2MB, 1920x1040)

ClipboardImage.png
[Hide] (1MB, 1920x1040)

>>1153
Good news, stuff is mostly working like I want it to work. Bad news, I will likely miss the deadline.

ClipboardImage.png
[Hide] (1.2MB, 1920x1040)

2024-04-03_19-36-58.webm
[Hide] (7MB, 800x450, 00:03)

>>1154

>>1154
A shame. Perhaps we can pretend it isn't 4/4 until GMT 23:00 or something along those lines?

>>1155
Pretty cool looking Anon!

>>1156
Aren't we going by 00:00 UTC like last time?

>>1158
We are?

massteroids.png
[Hide] (604B, 640x480)

>>1085
Here's my entry, despite being my first C project and the first game I've written from scratch I think it's come out alright:
https://archive.org/download/19100-massteroids/massteroids.zip
I look forward to playing your entries anons!

baada6a0b7e866d6f77d6a62184c6f4226f6b7f2e9e08879d9a39036f8cbd6d1.png
[Hide] (28KB, 1153x638)

I will post tomorrow

>>1161
Very pretty, anon. How does it work?

2024-04-03_20-11-17_1.mp4
[Hide] (8.4MB, 1920x1080, 00:35)

This is my three days with Godot.

My concept was "racing through an asteroid field" or maybe Death Rally IN SPACE!  It was originally going to be part of a larger game about mining and towing.  I only figured out how to make an array of something at the last moment, so I have two polygons bounding the track instead of an asteroid field.  The polygons should probably be invisible and much farther apart.  I reckon I'd use a path or pair of paths to lay down the entire run of asteroids.

You use a twinstick controller and have the sticks each controlling a thruster to thrust forward or backward.  Pushing one and pulling the other turns you sharply.  This is awkward, but kinda fun,  A little QWOPish.  Seems like it'd get better with practice.  I scaled the thrust particles to the stick angle, which I was pretty happy about.

I was going to add a tow cable that you fire into a rock and you can drag it into the middle of the track to hinder the other racers, like a Mario Kart banana peel, or slingshot yourself around a corner.  Attempting to tow cable the other racers is bad sportsmanship and should never cross your mind, of course.

The corridor is too narrow relative to the player's turning arc and Godot's collision resolution needs some kind of tuning, because it's absolutely batshit out of the box.  The fucking walls keep eating me.  I should probably use a simpler collision shape for the ship.

Calculating impact damage seems to be its own can of worms, and implementing other racers or netplay would take indefinite time to work out.

>>1160
This is very well done!  Small, clean source.  Takes 1/5 the CPU time the browser needs to idle in this thread.  Just want you want to see in a C project.

>scan-build: Removing directory '/tmp/scan-build-2024-04-03-204012-24306-1' because it contains no reports.
*chef kiss*

>>1164
LOOKS REALLY GOOD ALREADY, ANON!

>>1166
Wow, thanks anon! Being strict about warnings and carefully considering how to structure things definitely helped me find the right mindset, C was fun to work with and I'll certainly keep using it going forward.
>scan-build
I haven't heard of this before, looks very useful!

>>1168
>Being strict about warnings and carefully considering how to structure things definitely helped me find the right mindset, 
That's the spirit Anon! Becoming an engineer is actually a very creative process. And the rewards can be immense!

>C was fun to work with and I'll certainly keep using it going forward.
EXCELLENT. C is the technical foundation of the modern era, systems-software wise. Smol & Efficient. Those are the guiding keywords to econcomical high-performance.

>>1161
>>1164
I'll wait for (You).

>>1085
>>1170
>>1163
It's asteroid but in 3D with 6dof, I used godot 4.2, gdscript, the code is a mess and the rotation is kind wonky, fortunately it looks fine in the middle of the void, there is windows build, a linux build and the project itself.
https://pixeldrain.com/u/oXDUUr9E
MD5:1f005a4dc58e09732b1bd573b2e573df

>>1171
Nice.  I didn't have any trouble with rotation.  Took me a bit to realize I'd get rocked if I sat still.

>>1171
Cool concept anon, the star field was a bit distracting and it would be nice to have an Elite-style radar but I hope you keep working on it!

8dd9dfb434660b15075d8060f8cef6f915cc2110afaff88bdb105f35c4497820.png
[Hide] (183.6KB, 500x357)

It's nice to see that /agdg/ isn't dead.

>>1174
This.

Thank you for participating, everyone.
Remember that demo day is planned for 8/8.

>>1164
That background parallax is inverted. The further away something is, the less it needs to move. Those stars(?) are moving faster than the rocks in front.

>>1177
Yeah, I had to spend another 20 minutes investigating, but I figured out why it was like that.

ClipboardImage.png
[Hide] (4.9MB, 1920x1040)

ClipboardImage.png
[Hide] (777.9KB, 1920x1040)

ClipboardImage.png
[Hide] (282.1KB, 550x283)

Testing why offset for the center of the tiles weren't working properly. 

And I completely forgot how sine and cosine work. Especially since they apparently take radians instead of degrees, so I have to visualize that fucking shit, only to realize that Y axis is inverted for some fucking reason. I have no idea why, but I dont really care at this point.

>>1186
Don't let it bring you down, anon. Unrust on your math skills a bit and you'll be capable of pretty awesome complexity.

>>1194
It just I did everything alright the first time, but it didnt work, so I have to redo it over and over, until I learned that I simply used radians instead of degrees. Not the first time angles fuck me up, its like every fucker invented his own measurement system for them. Yeah, I should have known that this thing uses fucking quaternions, and not degrees, and I am totally heard of them before.  
I spend few hours trying to figure out why textures dont work, and it turns out directX cannot keep textures in memory, if you resize the window. Do you know how hard it is to fix a problem, if you did everything right, but something slightly related has some weird quirk? 
But the good news is, its basically done, and I needed that stuff anyway.

>>1194
>Unrust on your math skills a bit and you'll be capable of pretty awesome complexity.
That reminds me, does anyone have some relevant math resources they'd recommend? I ended up using a function for circle-line distance in >>1160 that I don't understand and I figure developing a stronger foundation will be important.
>>1195
>Do you know how hard it is to fix a problem, if you did everything right, but something slightly related has some weird quirk? 
The last missing piece of the puzzle always seems to take the longest to find! Looking forward to playing your game anon.

ClipboardImage.png
[Hide] (30.7KB, 683x610)

ClipboardImage.png
[Hide] (5.1KB, 378x206)

ClipboardImage.png
[Hide] (8.5KB, 303x238)

>>1196
>maths distance
Its always the basic geometry and right triangles. 

//lazy square distance
if (abs((int) _a1.posX - (int)_a2.posX) <= 2 ) {
	if (abs((int) _a1.posY - (int) _a2.posY) <= 2) {

You basically check x1-x2 first (and mod it to get positive values), if its below threshold("radius") it collides. And than do it for Y too, because its faster to separate them. 

//advanced distance
/*	if (sqrt(pow(TargetX - posX, 2) + pow(TargetY - posY, 2) * 1.0) <= 5) {
It just works.

ClipboardImage.png
[Hide] (27.5KB, 673x601)

>>1197
In case first image is 100% transparent for you too.

>>1197
>>1198
Ah, thanks for the explanation.