Re: Game Boy Interface
Posted: Sun Feb 11, 2018 5:33 am
For low latency version:
- Reverted audio latency reduction.
Gamecube/Wii support & news forums
http://www.gc-forever.com/forums/
Swiss has its own ISO, use that with an SD gecko and the boot.dol feature.polybius22 wrote:I installed a xenogc and can't for the life of me figure out how to get this on disc. I get that its not recommended by the guy in charge, but how hard can this really be? I tried the homebrew_disc pack by infact, and wound up with a PAL disc which appears to have at least booted swiss in 50hz lol. So close but so far.. who's had success here?
Code: Select all
truncate -s +1024 <file>
What hex editor would you suggest I use? Where you have <file>, do I input the exact file location? Sorry, I just don't know much at all about scripting language or any of that stuff. If I could post my ISO on here, would you care to add the null bytes for me? I really like GBI, and would just like to have it in the medium that I want it, as if it were the original GB Player Boot Disc. I don't like the sight of going through Swiss. I just want immediate boot up to GBI, and I'm willing to take the trouble, but just need the extra help.Streetwalker wrote:I think the easiest way to do it on windows would be to open the file in a hex editor and add 1024 bytes at the end of it with the value 0. Or on any unixy OS:Code: Select all
truncate -s +1024 <file>
Try this.claywilson95 wrote:What hex editor would you suggest I use? Where you have <file>, do I input the exact file location? Sorry, I just don't know much at all about scripting language or any of that stuff. If I could post my ISO on here, would you care to add the null bytes for me? I really like GBI, and would just like to have it in the medium that I want it, as if it were the original GB Player Boot Disc. I don't like the sight of going through Swiss. I just want immediate boot up to GBI, and I'm willing to take the trouble, but just need the extra help.Streetwalker wrote:I think the easiest way to do it on windows would be to open the file in a hex editor and add 1024 bytes at the end of it with the value 0. Or on any unixy OS:Code: Select all
truncate -s +1024 <file>
Streetwalker wrote:Try this.claywilson95 wrote:What hex editor would you suggest I use? Where you have <file>, do I input the exact file location? Sorry, I just don't know much at all about scripting language or any of that stuff. If I could post my ISO on here, would you care to add the null bytes for me? I really like GBI, and would just like to have it in the medium that I want it, as if it were the original GB Player Boot Disc. I don't like the sight of going through Swiss. I just want immediate boot up to GBI, and I'm willing to take the trouble, but just need the extra help.Streetwalker wrote:I think the easiest way to do it on windows would be to open the file in a hex editor and add 1024 bytes at the end of it with the value 0. Or on any unixy OS:Code: Select all
truncate -s +1024 <file>
Extrems wrote:You added them to the ISO and not the DOL.
If you mean the on-screen display, you need to pass --no-osdclaywilson95 wrote:Is there any way to turn off the preset options from showing up on the screen upon bootup? I just turn them off every time it boots, but would like for them to not show as soon as it starts, but when I decide to use them rather.
I don't understand. The power up is instant for me.claywilson95 wrote:Also, just being picky again, but when GBI first boots up, it doesn't boot at the start of the GBA sound playing, but a second or two after. I'd love to see that get fixed, if possible.
Ah, that's a shame, it seemed to work alright for me. But I only tested for a little while.Extrems wrote:For low latency version:
- Reverted audio latency reduction.
Could you give a brief explanation on how to pass "--no-osd"?Extrems wrote:If you mean the on-screen display, you need to pass --no-osdclaywilson95 wrote:Is there any way to turn off the preset options from showing up on the screen upon bootup? I just turn them off every time it boots, but would like for them to not show as soon as it starts, but when I decide to use them rather.I don't understand. The power up is instant for me.claywilson95 wrote:Also, just being picky again, but when GBI first boots up, it doesn't boot at the start of the GBA sound playing, but a second or two after. I'd love to see that get fixed, if possible.
Make a CLI file and append it to the DOL (before the padding).claywilson95 wrote:Could you give a brief explanation on how to pass "--no-osd"?
It sounds like a problem with your display chain resynchronizing (from 480i to 480p?). I can't help you with that.claywilson95 wrote:And when I first start GBI, every time it always boots up a second or two after the splash screen starts. So I don't hear and see the full thing as soon as I load it, not unless I press the reset button and let it boot again and then it shows the entire splash opening.
Make a CLI file and append it to the DOL (before the padding).Extrems wrote:claywilson95 wrote:Could you give a brief explanation on how to pass "--no-osd"?
I also have had no problems with GC rumble or GBA rumble. When you start the dol from swiss select rumble, hit left to select yes and make sure the rumble option is checked and hit start.Stremon wrote:Hi guys,
I wanted to know if there is any problem recently with the rumble function on GBP enhanced games or any special parameter to change to make it work? (beside the --enhance option)
I have the original Drill Dozer and Mario&Luigi Superstar games, in both I can activate the Rumble, but in game the rumble doesn't work at all...![]()
The problem is the same in Normal LL or ULL versions. Only rumble doesn't work the rest of the functions work great.
I boot GBI from Swiss on SD Gecko, and I tried changing the parameters both at startup or with a cli file, but no matter what I tried I still get no rumble sadly.
Is there anything I might be missing? Any idea of what I could try to make it work?
Edit: I forgot to mention, the rumble is working perfectly in normal GC games, so it's obviously not a controller problem.
Did I do this correctly? I added the command to the end of the DOL, then added the 1024 null bytes.Streetwalker wrote:A CLI file is just a regular text file, you put one argument on each line. Then pad that file to be 1024 bytes long and append it to the DOL, still using your hex editor.