Відео

Sounds great. Maybe someday I'll do the same for my game.

Glad, that I could help.

yey you did it good job

It's zig + SDL2 + SDL_image + freetype for font rasterization. Everything else is homemade.

Yes, thats true. But that would assume I will support non latin based alphabets (if thats correct term) which I won't do due to lack od resources. If game happens to be success and I can afford proper localiztion, then I will probably also have resources to rework text rendering.

Thanks!

Thanks for the insight. I usually try to keep videos not too technical, so it's not only targeting other game devs. But here I probably get carried out, but on the other hand knowking how allocation works explain some of decision I made in this video, which may be a bit unclear without this knowledge. Maybe this video would work better as fully technical explanation/presentation but I'm explicitly avoiding making such videos.

@@undermountain_dev it's all good, it really depends what you want to get out of your channel, I'm a dev I like the content because of the deep dive stuff but this video felt like it was trying to cater to both sides of the opposite coin

@undermountain_dev For me *personally,* this video is great _because_ of its depth. Surface level videos are already dime a dozen, after all.

@@ultimaxkom8728 I agree, so many dev's just play with engines and don't really get into the weeds of problem solving that we all face, especially when building things without the common engines. I want more of the complex problems and less of the surface level stuff.

Indeed

Thanks!

Thanks!

Yeah, maybe in future I'll improve my approach too, but right now - anything that works. About instancing - that's from my understanding how SDL works, maybe there are ways to easily costumize it and improve performance, but I'm quite certain it won't be neccessary for my game.

That's interesting. I'm not sure if managing all game's graphic in single .aseprite file would be convenient after some time. But that's helpful knowledge. Thanks :)

@@undermountain_dev yeah yours is definitely way more flexible and all kinds of cool features. Still some of the aseprite export options might be helpful for you at the beginning of your process. And most of it works with cli. Like I'm using the trim frames options since my characters have hundreds of frames of all different sizes.

1. Kind of like that. I my code I've list of sprites. Sprite have 3 different properties: reference to texture atlas, indices (xtop etc.) - I call this 'clip', and pivot 2. I don't know details about minecraft, but most likely it's true. Also it's simplest solution if there's not that much graphic content in the game. Just load single texture and that's all what's needed.

Understandable. Personally this doesn't bother me so I allow this in my game.

Yes, layers are unfortunately lost. About updating, right now I have to click 'refresh' or 'f5'. Engine will go through the directory and if the modification timestamp was updated since the last refresh, the new sprite sheet will be exported and loaded into memory. But it's possible to detect those changes in separate thread and update sprite sheets without the need to click anything. Idea with with having access to layers is nice, and maybe Aseprite already have export option to keep layers separated.

Yeah, it would be nice. Right now I'm planning to edit animations inside my engine using those sprite sheets, but definitely, I could load them directly from .aseprite.

Thanks and sorry to disappoint ;) maybe someday I'll write a pareser, but right now that's all I need.

Postaram się mniej więcej wyjaśnić, ale jest tutaj kilka mechanizmów. Nie jest też to idealne rozwiązanie, ale takie, które uznałem, że jest wystarczające. Najpewniej istnieją inne lepsze, ale wolałem też zostać przy takim, które w miarę rozumiem, a nie brać gotowy shader, którego nie mam pojęcia jak mogę zmodyfikować. 1. Kod shadera tutaj: gist.github.com/jakubpodgorniak/f27e90d1706ff0504d7b18175b378142 2. Do shadera przekazuje kolor, który nadaje barwę całej scenie (ambientColor) 3. Przekazywana jest też tablica świateł (max 48), dla każdego ze świateł określana jest pozycja, promień, barwa oraz intensywność. 4. Przekazywana jest też tekstura, na której wyrenderowane są rozmyte inne źródła światła (np. efekty cząsteczkowe) 5. Przekazywana jest kolejna tekstura, na której wyrenderowane jest rozmyte światło z tych widocznych na thumbnail-u zielonych ścianek. 6. Barwy te są kombinowane w jedną (punkt 3 działa dość słabo na zintegrowanych kartach, więc można wyłączyć tą opcję, wtedy wszystkie światła w grze są robione za pomocą pkt 4) Trochę chaotycznie opisane, ale też nie czuję się super mocny jeżeli chodzi o shader-y i to jest jeden z obszarów, w których chcę się mocniej podszkolić.

Dzięki!

Thanks! Yeah, it's a topic I was also scratching my head over for quite some time. But after releasing one game I can grasp it pretty well, but still learned I learned a lot just by making this video.

Thanks. That's the idea, I hated adding new sprites till the end of Pumpkinman development, so this time I change approach : )

Thanks! I hope so.

Explain how that would help here please because i just googled what a texture packer is and off the top of my head i'm sure it doesn't solve the issue but i might be wrong just from my quick understanding.

@@ApexJnr This approach is just fine btw, For my workflow use the export function save all selections and frames as pngs, add the texture packer code to my gradle file then in my launch configurations I can choose which folders to include and whether to use the texture packer and that builds the atlas file and loads it in as it boots the game

When working on Pumpkinman I just wasn't planning for the game to grow as it did. So I was doing everything manually, and then didn't want to do revolution in codebase. That's why I wasn't using texture packer, but yes it would save time. For this game I will actually write my own simple texture packer (probably with some naive algorithm - but for my needs it's fine). It will be actually a topic of one of upcoming videos!

Nothing wrong with that, I did whole game this way. I just tought this is a cool feature to have.

Thank You Very Much!

who are you to decide how words are pronounced? let him say engine whichever way he pleases!

Speaks the smooth brained American that only speaks 1 language

I’m sorry brother, I love commenters on indie dev videos so much, but please for the love of god research how to write the word “losing”, I’m losing my mind xD

Thanks!

Thanks! I guess it will take some time to gain momentum.

@@undermountain_dev I saw this vid and subbed! So thats 1 more ^_^

Thanks :)

Thank You! Glad to hear that.

Thank You!

Thank You Very Much! And good luck with Your dream game!

@@undermountain_dev thank you!

Thank You Very Much!

Hmm, haven't seen that, but looking at formula it should work nicely, no conversions needed. Maybe I will find chance to test it. Thanks!

Thanks!. It's much easier implementation wise, but I don't have any data about performance, unfortunately. The entities movement wasn't bottleneck at any point, so I didn't bother improving it's performance. This change was only driven by how painful it was to work with previous solution. From my experience, I would say second solution is more performant, but without proper tests it's hard to say.