Framebuffer

@framebuffer.cl

107 Followers 57 Following

🐺, with horns. 🇨🇱 🏳️‍🌈 | 28 --- 💻 computer sorcerer + architect 🌐 https://framebuffer.cl 🏢 makes buildings with code 🐲 I play waaaaaaay too much DnD

me, looking menacing, on a three-point pose
me pointing at a screen
A battle with big bad birds, and a single (1) gigant spider in the background. Our warriors are: Strykert (dragonborn, sorcerer), Meragh (elf, artificer), Athyra (gnome, warlock), Nalten (dragonborn, barbarian), Caelus (human, paladin), Malonco (goliath, monk). Strykert is about to die (again) but Nalten is coming to save the day!
A work in progress painting my fursona, a dog (with horns) hiding on a tree.
A cardboard rendition of my fursona, with several layers of cardboard for each piece, to give it a 3D sense of depth.
Overlapping lines on a CAD file.
A Raspberry Pi 2 Zero W rotating through several tests, showing: a bitmap image, text and a QR code.
An Ender 4 3D-printer
a raspberry pi zero 2 w with a waveshare 2.13" e-ink display, running a Python demo showing a smol boi saying ba
A Macintosh PowerBook 150
The crash screen of the game RoboCop vs the Terminator for the Sega Genesis.
My profile page displays 100 followers. Epic!
Timelapse of a game being developed.
Timelapse Day 2
A timelapse of the development of a game. Graphics are being produced.
A video of a game's camera being tested.
The GitHub Desktop History tab, now with the new changes applied!
The GitHub Desktop window, now with the new project tree ready to be committed!
The Godot new project window. In here, disable Create Folder and change the renderer to Compatibility. This way, everything will be ready to go!
A folder structure containing: the Godot editor (.godot-exe), the Godot project (src) and a .gitignore file to avoid committing the editor executable to git.
To enable git-lfs, go to your repository's main page, on the top right side of your screen press "Settings" and scroll down to "Include Git LFS objects in archives".
A merged pull request window. Purple means the request has been merged, and that the new code is now present on your receiving branch. If you want, you can delete the branch that has been merged.
The screen showing an open pull request on GitHub. From top to bottom: the title of the pull request, description, changes being pushed, and a confirmation button saying if the branch is ready or not to be pushed. If all is set, the Merge pull request button will appear. Press it and done! You have a single, updated branch again!
The last part of the Pull Request window. Here, all the changes that your branch made, that will alter the receiving branch, will be shown here.
The centre portion of the Pull Request window. Here, a description and title for the request must be added. At the side, functions to manage who reviews the code, who checks out the work, and if the code is part of a milestone are displayed. You probably won't need these unless you're a much larger team than the jam allows.
The title of the Pull Request page of GitHub. Down below, the buttons to merge and compared branches are displayed. If everything is good, an "Able to merge" green checkmark will appear. If not, histories differ so much that git won't merge them without your intervention, to safeguard your code.
The main screen of a GitHub pull request.
Inside GitHub Desktop, you can create branches of your code. These branches are separate "alternate paths" to your code development. You can merge them, more on that later.
This is the "History" tab on GitHub desktop. There's a couple commits done, involving adding, deleting and modifying files. Your changes will appear here.
The publish repository menu on GitHub desktop. It shows: where to upload, the name of your repository, an optional description as mentioned before, and a checkbox to keep the project private. Make sure it's checked. Below: buttons to publish the repository or cancel out of the menu.
Top buttons: the repository you're working on, the branch you're working from, and the button to push your changes to GitHub: the cloud outside your machine. Left side: What changed between commits, and if any, a place to write what you've changed, and a button to commit those changes to main.
This is the window that appears after you click "Create a new repository on your local drive". Fill in the details as described on the post: name of your game/game jam, a description to know what it is, where it's going to be located, select Godot from the Git ignore dropdown, and, if you intend to release your game, choose a license. You can search online for each one and what they mean. Usually, MIT is very common and it's the one used by Godot. But make sure to check all of them out beforehand, to find one that suits you best.
A mock-up of two squares interacting in the style of the Sega CD BIOS for the NTSC regions, version 1.0. one square scales down to the back where another scales back up to the centre.
A video timelapse of me recreating the Sega CD/Mega CD BIOS animations on Godot.
A GitHub contribution chart, where no contributions have been made or any repositories created until mid June-early July 2024.
The word count of the post-mortem of Intuition, a game I did for the 76th Godot Wild Jam. It was a complete failure on my part. A post-mortem explaining why is coming soon.
a car floating in mid-air, and another one upside down on the ground. this does not inspire joy.