Good news!I just implemented save states. It was easier than I would have thought.
Is lameboy states compatible with gameyob?
Good news!I just implemented save states. It was easier than I would have thought.
I don't think he can decode a lameboy savestate without lameboy source code.Good news!
Is lameboy states compatible with gameyob?
Maybe we need to try contact with Nutki (lameboy author) for sources? His blog: http://lameboy.nutki.com/
Like Geren said, many people have tried and he simply doesn't respond...Why not? Savestate its omly ram dump (if i correctly understend it).
For example gpSP has same SS format with VBA. But i dont know is VBA opensource or not.
Maybe we need to try contact with Nutki (lameboy author) for sources? His blog: http://lameboy.nutki.com
You sure that's the real Nutki? He looks like a troll to me, you can put your name down as anything in the comments. So yeah, he seems to have completely disappeared.Like Geren said, many people have tried and he simply doesn't respond...
Except for this semi-recent post:
http://lameboy.nutki.com/?p=24&cpage=10#comment-53760
Yea, basically he's an asshole and will never release it.
Its all garbled, like an nes game that needs a blow job.How's the new T-rex FPS prototype working?
Its all garbled, like an nes game that needs a blow job.
I tried to adjust the debug settings to no avail.
I would advise any dev not to try to waste any time getting this to work, the game doesn't look like any fun at all.
At this point, it may be more fruitful to do the reverse. Because the core is mature, it would be better to get the rest of the core to behave correctly so that some esoteric* games work properly, instead of getting some esoteric* games to work properly so that the core behaves correctly. Using "corner case tests" like Gambatte's, as well as Blargg's CPU tests, would indirectly help figure out what's wrong with the games.But getting it to work would make it far more accurate in emulation besides what doesn't look fun to you doesn't mean it is no fun for anyone and myself personally I would love to see it running
Thanks for working on a DSi version, Drenn!
Just tried it out via my XL, and from a quick play Shantae ran at a steady 60fps with sound!
edit: got a guru error at the end of the first level
That's weird, Matando also said that he had sound working... he uses sudokuhax.Wait a minute......
I've got a " Sudokuhax'd " DSiXL and as of the latest build, I still don't get any sound !
How did you get the sound ? Are you running it on a flashcart in DS mode or did you run it from the SD card via sudokuhax ?
What else do you have on your card ?
It looks like dsi-mode is still rather unstable in some cases. Next time you get a guru error can you tell me the value of "pc" and the exact version number? (it should be visible from the flashcard's menu.)Thanks for working on a DSi version, Drenn!
Just tried it out via my Sudokuhax'd XL, and from a quick play Shantae ran at a steady 60fps with sound!
edit: got a guru error at the end of the first level
Hmmm...this is strange.i was using the dsi test branch via SD card. i'll try out the main one right now and give the 'pc' error I get.
edit: installed the latest build and there was no guru error at the level switch!
Nice work, i must say =D
Do you mean, that it works at all? When the bios is off, all it does for me is flash leftover tiles from the last game on the screen. It doesn't run in bgb either.Its all garbled, like an nes game that needs a blow job.
I tried to adjust the debug settings to no avail.
I would advise any dev not to try to waste any time getting this to work, the game doesn't look like any fun at all.
I can think of a more likely reason why some games have garbled sprites, mid-frame changes to tiles don't work properly. The new graphics engine will support this, if I can make it run fast enough... and I'll give it the 10-sprites-per-line limit also.At this point, it may be more fruitful to do the reverse. Because the core is mature, it would be better to get the rest of the core to behave correctly so that some esoteric* games work properly, instead of getting some esoteric* games to work properly so that the core behaves correctly. Using "corner case tests" like Gambatte's, as well as Blargg's CPU tests, would indirectly help figure out what's wrong with the games.
Gambatte's 10-sprites-per-line limit tests are failing hard on GameYob, which may indicate some form of dependency on 10-sprites-per-line in some games that currently look garbled.
_ _ _ _ _ _ _ _ _
* esoteric = using uncommon CPU/graphics/audio features
...I'm on 1.4.1 U , could it be that I need to update my DSiXL to a newer firmware ? I was afraid I was gonna lose the sudokuhax but I asked elsewhere on the forums some time ago and I've been told that by updating , you only lose the ability to install the hax, but if you already have it it should be fine.
Any thoughts ?