itch.io

My non-programmer friend was able to build for Mac well enough. He did have some issues and I added some notes on the readme regarding some of his pain points. He was not, however, able to reproduce your exact issue. I’m not sure why Bash is looking in your home directory and not it’s own file directory.

The build system is written in Bash. It’s a very useful scripting language to know/learn. If you’re still having issues, you can read it and see if you can find the cause. You can also try to export to Mac using the manual steps listen on GodotRust.

I’ve spent some hours on debugging your issue now and that’s time not spent on my own projects. No one else can seem to reproduce it. Let me know if you figure out what’s happening so we can add it to the readme to prevent other people from having this issue.

If it’s not working still, then I think I should drop Mac support all together. Trying to figure out what’s happening on your system is becoming time consuming. I don’t own any Mac hardware so I cannot debug locally. I’m going to ask a friend to try to see if they can build it with the instructions provided.

It looks like you are running that script from your /Users/max/Library folder, not the repo copy. You need to pulled the repo into a clean folder and run ./buildSystem.sh --allMac from inside that folder. I’m not sure how you’re doing this, but if you are doing this all correct and still having this error, then Mac support is broken and I don’t have hardware or time to fix it. I will have to delete the Mac instructions from the repo.

You could try to read the build script itself and figure out how it works to see why it’s failing. It’s build on these instructions, so you could could try running them for yourself: Export to macOS and iOS.

You shouldn’t need to do that if you’re using the template. But if you’re compiling it yourself you’ll need to read buildSystem.sh

I don’t know why it’s not detecting your OS. I use this line to detect Mac. But I don’t own a Mac so this isn’t an important feature for me.

    elif [[ $OSTYPE == "darwin"* ]]; then
        export TARGET="macos"

Try building with ./buildSystem.sh --allMac. Please start a new, clean folder and pull the project into that. Don’t run it out of another folder like /Users/max/Library. That’s a recipe for mess and disaster.

Clone or download the repo and run the builder in the cloned copy.

Did you do a git clone of the whole repo or just download the single files? You need the whole repo.

I’m getting pretty good frame-rate on at least one of your games. Did you use the version from this website? Did you compile it yourself, and if you did, did you use the --release flags? Do you mind sharing a ROM that has more immediate problems? I’d really like to figure out what is causing these kinds of issue for you in case it’s happening to other people or end-users.

Ooo, I’ve been thinking about doing some touchscreen controls for mobile exports. That could be useful.

I haven’t looked into it lately. I have a lot of plates spinning right now. Day job nearing major release.

I’d love to get back to improving GodotBoy, but it’s hard to justify spending time on it right now.

I can usually run dozens of instances before multithreading and often hundreds once I do multithread with Godot.

I’m curious about your project if you’re having issues. Does it have similar issues in other emulators? Have you tried on real hardware?

I would love a wood wall and a fireplace.

Also: Your Twitter link seems down and I can’t find you on BlueSky or elsewhere. If you are open for commissions, I’d like a character as well.

The asset lib version is old. It will always be old. Godot AssetLib is not a good platform for automating updates. It says as much in the AssetLib listing.

If you can find a legal homebrew ROM that can replicate this error, I will look into it. But I cannot spend time on a fix for an ripped cartridge ROM, even if it’s for personal use copied from a legit cartage that you own. This emulator is intended for publishing homebrew games on modern hardware.

I suspect that game doesn’t quite follow the spec and that’s what’s causing this error. I would be curious to see if it causes other emulators to crash. Regardless, investing that is outside of the scope of this project. Sorry.

I’d love to see what else is in your 3d emulation system. But I’d also like to see what causes that error. Do you have a ROM that will reliably reproduce it? Does the error result in a ROM crash or does it continue normally after the error?

Blib_buf is used for sound. I find it strange that it would error like that. It does lots of checks before hitting that line to insure it won’t read out of bounds.

If you’d like to file a bug on gitlab that would probably be easier to talk about code with.

I don’t think it’ll make a difference but: did you download an old version or do you have the latest version here.

What part of it was “inscrutable”? It’s outlined very simply: install rust and run the build script. Not sure what part your caught on.

How has it been going?

Try the instructions as written on the repo and tell me if you have any trouble. I’ve written buildSystem.sh, refined, and reused it for quite a few projects at this point. And others hasn’t had any problems. One person didn’t install the prerequisites, but they figured it out. It’s pretty battle-tested at this point. But please try it for yourself and let me know how it goes! If you have any trouble, it’ll be worth learning what happened to further refine the buildSystem.

Really, anyone trying to use this tool is likely trying to publish on Steam or similar. They’re gunna NEED to codesign for themselves.

I apprentice the offer to build it for me, but I have no way of knowing if what you built was really what I sent. This itch build is compiled on GitLab. Anyone could audit the log (I should install install checksums if anyone was concerned). Ultimately though the project does get updates pretty regularly and I don’t think people will want to have to call someone else to get them builds.

I could pay for GitLab to use one of their Mac build machines, but this project already makes less then nothing, so I can’t invest in a Mac build pipeline when I get Windows, Linux, and Android for free.

Really the best way is to refine buildSystem as much as possible. If you find any pain points, I’d love to hear about them.

I don’t own any Apple hardware and I don’t have a subscription to Apple’s developer program, so I can’t deliver Mac binaries for codesign reasons. BUT if you check out the repo, there are instructions on how to compile it for yourself and those instructions work for Mac. You’ll have to figure out codesigning for yourself too.

That’s also mentioned in the text above.

If you’re having trouble playing it, here is a video: https://youtu.be/Li4AvQnlrxo?si=9GV3Ro5JjPO87nqZ

I think it’s actually more CPU bound generating meshes. Does the framerate recover if you stand still for a bit?

I did most of the development on mobile integrated framework and I get pretty okay framerate on my phone. So I’m wondering if something else is wrong?

In Godot Editor, press F1, search GodotBoy. The memory functions aren’t well documented yet, but they’re pretty self explanatory. The next release of GBStudio includes some files to help figure out script variable bindings.

https://github.com/chrismaltby/gb-studio/issues/1750

Cool, if you can do a Merge Request on GitLab, I can merge that. Otherwise, I’m out of town and can’t review/fix it properly for a bit.

But thank you for bug+fix!

Godot 4 came out in 2023. This shader is from 2021. I wouldn’t expect it to run out of the box, but you might be able to fix the 3.x->4.x changes.

Nope. DLLs must be separate files for security reasons. Windows gets upset when you break that paradigm. In theory, someone could make a GameBoy emulator that compiles with Godot. But I’m not working on that.

There are tools to change the Icon of Godot at export time. It’s documented in their docs. Since most people are using this project for Steam distribution though, the DLL usually fine; most games have LOTS of ancillary files.

GBA was a rough prototype that has had a lot of problems. I was working on another tool for GBA and other emulators, but it’s a bigger project than I’m able to do on my own.

I heard from someone about the Stream Tearing issue. They said they fixed it by changing the renderer to Compatiblity, instead of Forward+. Can you see if that helps you?

Yeah, not sure what the best way to deal with that is yet. The game is updating the screen out of sync with emulator updates. I think this might happen if you have high refresh rate monitor, but maybe without high refresh rate too.

Godot4.4 issues are outside the scope of this project. This template was built for 4.3. It should work in 4.4, but if it doesn’t, it’s likely this is a 4.4 issue, not a GodotBoyTemplete issue. Read their docs for more. Try deleting your .godot folder first though. That forces projects to reimport assets and sometimes fixes issues.

The template here was behind the Git repo a bit. Looks like there are some old bugs with the export that were fixed on the main branch. I updated the build here. Try your export again.

RcEdit is a tool for changing your games icon. If it’s missing, the export will still work, but it will have the Godot logo. Nothing wrong with that, but if you want to change that, you can install that.

Read Godot’s docs for more.

Well, it looks like it’s not loading your ROM. Did you put it in the right place? Does it have a matching file extension?

Hrm. Did you copy the exe to a new folder on it’s own? It needs the dll and (if you didn’t bundle it with the exe) the pck files.

Try running it from command line and seeing what the error messages are.

Yeah! I’ve chatted with him. I think there are a couple of edits I would make: debug checkbox in the export screen should be off for releases and PLEASE save it to a new folder, not just on your desktop. It creates a DLL file that you need for export.

I love these materials, but I do wish they were higher resolution, like 128+. Not more detail, just 4x the scale with 4x the noise. Like for the brick texture have 4x as many bricks per side without just tiling.

I’ve been tempted to downscale some of your higher resolution materials to get that effect.

yeah, I think it’s a controller issue. even if you don’t have a controller, I think it’s reading something weird. or is web issues.

I just did an update with a proper win condition if you wanna try it again.

I just did an update with a proper win condition if you wanna try it again.

Controller input should work fine, but it’s not well tested. Right trigger should shoot.

I just did an update with a proper win condition if you wanna try it again.

Well Damn, that’s news to me. I guess this is dead then. That’s a shame. It was completely dependent on Gotm’s multiplayer. I might publish the P2P UDP version or a hot-seat play version. But I’m not going to put effort into it any time soon.

I made a VERY similar project recently, but I took a different approach to it. I made a game about mining, instead of road tripping.

I turned it into a desktop widget. It sits as a semi-transparent window that lets you see and interact with text behind it. Instead of taking a whole screen, it’s a small floating window that you work around, but can always see.

My next steps are adding session notes, for when you launch the app, and iteration notes, to say what you did for each 25 minute sessions.

I planned on gamifing it with reward every time you “complete” an iteration that lets you do “number go up” style idle game unlocks.

I haven’t published any of this, but I’m curious what you think.

BTW, you have to be careful using “pomodoro” or “tomato” timer in productivity. It is trademarked. And the owner is kinda litigious.

At one point there was a hint there that you’re supposed to hold the jump button and hover (not glide) between the pillers. It’s intentionally very difficult to jump across, but if you run through while holding the space, There is a hover mechanic. I think I forgot or ran out of time to put hint and NPC back in.

Me too.