There is a bug when running castlevania legends in SGB mode
There's an issue with the controls when starting the a and b buttons replace left and right on the d pad but after a about a minute the controls go back to normal. The colors are also scrambled. The game plays normal with SGB off
There's an issue with the controls when starting the a and b buttons replace left and right on the d pad but after a about a minute the controls go back to normal. The colors are also scrambled. The game plays normal with SGB off
My DS Lite + Acekard has been seeing very little battery consumption with GameYob... can't really compare to LameBoy, but it's absurdly small. With illumination set to 2 or 3 I think you can easily cross the 12 hours barrier.
It would also depend on the game you're playing. Shantae consumes all of the DS's horsepower, whereas most non-gbc games have many spare cycles.
Yeah I've noticed this. Sgb support is... definitely unfinished.
Indeed. I actually finished implementing this a little over an hour ago. Much like Goomba Color, it briefly starts the game in SGB mode to retrieve the SGB border, then it restarts in GBC mode.
Thus it means you could remove initClockIRQ() from your ARM7 code and place a call to resyncClock() in your VBlank handler (always in your ARM7 code I mean).
BTW I really had a lot of fun playing the good old GameBoy Tetris yesterday eve, so thank you!
Thanks for this one. Just got a question though. How do you magnify the screen? I would like to run games at full screen like Lameboy does.
Thank again!
Thank again!
You don't... there's an experimental build in the first post which has the ability to scale, but it's not very usable yet. Corrupted graphics are common. In the meantime I'm working on custom borders to hopefully compensate for that.
But there's something interesting I've noticed, which may allow for scaling without the graphics engine rewrite. For the technically inclined, take a look at this. I'm wondering, maybe it would be possible to use this capture the backgrounds into a bitmap image, which can then be scaled? There would probably be an additional frame of input lag, but other than that... is it possible?
I see. Thanks for the quick reply, though. I'll just have to wait then and stick with Lameboy for a while until GameYob might support full screen scaling. Cheers!
The DS capture unit does a 'snapshot' of what the 2D/3D main core is generating and stores it in a 15bpp bitmap in VRAM... for instance this is used to generate 3D images for the 'other' screen.
I don't get what you would like to obtain using it. What you get on that screen capture it's the same you can get directly...
I have 2 branches now. "master" and "newgfx". Master uses a goomba-style graphics engine: it uses the ds's tile-based background layers and sprites to emulate video. This is efficient but it was (I thought) impossible to scale. Then I started the "newgfx" branch, where the entire screen is drawn onto a single image. This image can be scaled. Newgfx has numerous problems and will never be quite as fast. But in the master branch, if I can capture each frame into a single bitmap image, then that image can be scaled... I'm going to start experimenting with this now.The DS capture unit does a 'snapshot' of what the 2D/3D main core is generating and stores it in a 15bpp bitmap in VRAM... for instance this is used to generate 3D images for the 'other' screen.
I don't get what you would like to obtain using it. What you get on that screen capture it's the same you can get directly...
You need to do the following on both handhelds:
- go to the settings menu
- switch NiFi on
- return to the game (press B)
- go to the pokemon centre
- speak to the person at the desk, near the computer
The question did have some merit: Usually, in DS-to-DS transfers, a receiver needs to choose which sender they'd like to link with, like in DS Download Play and game lobbies. You need to have a host and a client; in some games, the distinction is minimal (like in New Super Mario Bros. where the distinction is the character you use), but you still need to look up your sender.
The question may have asked whether you needed to choose your sender. If GameYob accepts packets from any sender, then that could become a bit of a problem if there are two pairs of games going on.
Personally, I'd like an answer from Drenn about this.
I've had some success with scaling on branch master:
Having the second, unscaled image there is kind of necessary, since it needs to be captured. On my dsi the bottom backlight is disabled, rendering the bottom screen invisible. There may be other tricks to make it disappear, however console output won't work with scaling enabled, which means no FPS counter or time.
Also, just producing the scaled image each frame requires vram banks C and D. That's 256 kilobytes, and that doesn't include all the resources required to make the original image. Oh well. I think I can manage.
But thankfully, speed appears unchanged. A large amount of copying needs to be done, which I was able to offload to arm7, since vram banks C and D are accessible from there. So arm9 is free of that burden.
Having the second, unscaled image there is kind of necessary, since it needs to be captured. On my dsi the bottom backlight is disabled, rendering the bottom screen invisible. There may be other tricks to make it disappear, however console output won't work with scaling enabled, which means no FPS counter or time.
Also, just producing the scaled image each frame requires vram banks C and D. That's 256 kilobytes, and that doesn't include all the resources required to make the original image. Oh well. I think I can manage.
But thankfully, speed appears unchanged. A large amount of copying needs to be done, which I was able to offload to arm7, since vram banks C and D are accessible from there. So arm9 is free of that burden.
The nifi code is rather basic. GameYob will just send its packet out for any other GameYob in range to receive. This obviously won't work if more than 1 pair of people want to play multiplayer at once in the same place. Any "host/client" stuff is handled by the game itself.
I'll fix this momentarily... I changed something about bios loading behaviour in a stupid way and I don't even know why.
Similar threads
