Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
mastodon.gamedev.place is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server focused on game development and related topics.

Administered by:

Server stats:

5.1K
active users

mastodon.gamedev.place: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#rgbds

1 post1 participant0 posts today
Public *
bbbbbr

New release of dev tool:
- Choose which bytes treated as empty for binary ROM files (improve usefulness for roughly finding empty space when patching ROMs)
- Allow filename to be any order in option arguments
- Added macOS ARM binaries

It's a small console app for Windows/Linux/macOS that measures free ROM & RAM space for games. Works with , , and plain ROM files.

github.com/bbbbbr/romusage/rel

Screenshot of romusage running on a rom showing tabular output with colored text graphs as follows: $ romusage -g -sRp -b:ff:00 infinity_2024-08-30_demo_1.gbc Bank Range Size Used Used% Free Free% -------- ---------------- ------- ------- ----- ------- ----- ROM_0 0x0000 -> 0x3FFF 16384 12998 79% 3386 21% |-#####################......| ROM_1 0x4000 -> 0x7FFF 16384 10796 66% 5588 34% |##################-.........| ROM_2 0x4000 -> 0x7FFF 16384 5941 36% 10443 64% |##########..................| ROM_3 0x4000 -> 0x7FFF 16384 14549 89% 1835 11% |###---###################-..| ROM_4 0x4000 -> 0x7FFF 16384 12538 77% 3846 23% |##########--##########-.....| ROM_5 0x4000 -> 0x7FFF 16384 11903 73% 4481 27% |####################-.......| ROM_6 0x4000 -> 0x7FFF 16384 11283 69% 5101 31% |###################-........| ROM_7 0x4000 -> 0x7FFF 16384 11657 71% 4727 29% |###################-........| ROM_8 0x4000 -> 0x7FFF 16384 10419 64% 5965 36% |#################-..........| ROM_9 0x4000 -> 0x7FFF 16384 9280 57% 7104 43% |###############-............| ROM_10 0x4000 -> 0x7FFF 16384 10164 62% 6220 38% |#################-..........|
Public
Damian Yerrick

I am officially bisectual.

I used #git bisect for the first time today when tracking down a breaking change in #RGBDS, a #GameBoy assembly language toolchain. I first caught it incorrectly overlapping ROM sections when building #240pTestSuite, and then I added tooling to another project (Libbet and the Magic Floor) that I could bisect more quickly.

Log at github.com/gbdev/rgbds/issues/
#gbdev

GitHubCheck .sym file reported addresses and sorting · Issue #1350 · gbdev/rgbdsBy Rangi42
Public
bbbbbr

Poll time!

What is the main way you play / Color games? (longer plays)

Curious for (unscientific) sense of what people use, since supporting blur and faded colors of OEM screens does take more effort for devs.

· 95 people · Closed
#gbdev#retrogaming#gameboycolor
Public
gbdev

Happy New Year! And to kick it off... a new RGBDS update! 🎉
github.com/gbdev/rgbds/release

Version 0.7.0 introduces many bugfixes and incremental improvements to make it more enjoyable to use.
Thank you to everyone who contributed and aided with testing!

GitHubRelease v0.7.0 · gbdev/rgbdsStarting with this release, we now publish statically-linked Linux binaries! We also provide a Dockerfile to build RGBDS. Deprecated: Defining symbols without using DEF (use {interpolation} if you...
#GBDev#RGBDS#RetroDev
Continued thread
Public
Ben Bradley

Steady progress on my assembly Gameboy game. It looks just the same in a screenshot, but the d-pad controls give the super smooth rotation animations I've been hoping for. Now working on movement. It's taken a lot of "unit tests" to get here but they're taking lots of the guesswork out.

Emulicious gameboy emulator showing 24 tick box icons, all ticked.
A grey grid on a black background with a single spaceship player sprite.
#gameboy#rgbds#assembly
Continued thread
Public
Ben Bradley

While I feel like I'm getting the hang of #RGBDS assembly and the limitations of the hardware, I am also not used to holding this kind of logic in my mind and my confidence that the code is going to do what I want is quite low.

Couple this with having a large chunk of maths to get working before I get the player moving in the way I want. I don't want to write all that maths, find the game doesn't behave as expected and try to break down why.

The tests do look scarily like "normal" unit tests:

Screenshot of RGBDS "unit test" code: ;4 ld d, 24 call GetDirectionInBounds ld a, 0 cp a, d call AssertZero ;5 ld d, 12 call GetDirectionInBounds ld a, 12 cp a, d call AssertZero ; Absolute ;6 ld a, 0 call Absolute cp a, 0 call AssertZero
ExploreLive feeds
About