This is not the place to spam your channel or stream. No screenshots of websites or Twitter.įollow the rules of promotion. No general URL shorteners (bitly, tinyurl, etc). Submit only the original source of the content. No Giveaways / Trades / Contests / Items for sale / Donation Requests / Crypto anything Cosplay posts from content creators who focus primarily is adult content will be removed. Mark your spoilers and NSFW submissions, comments and links. No bandwagon/raid/"pass it on" or direct reply posts. Discussion prompts must be made as text posts. Note that we do not allow non-gaming meme templates as submissions. Submissions must be directly gaming-related, not just a "forced" connection via the title or a caption added to the content. Directly messaging individual moderators may result in a temporary ban. Only message the team via the link above. Simply message the moderators and ask us to look into it.ĭo NOT private message or use reddit chat to contact moderators about moderator actions. For an added bonus though, this 4KiB is aligned to the emulator's memory alignment in the host system, not the emulated system, so may or may not correspond to any interesting alignment in the emulated ROM.If your submission does not appear, do not delete it. In fact, an entire 4KiB block around any poke you made will come from the old ROM and not the new ROM. The implementation details of waterbox make this one really interesting: If you poke the ROM with memory domains and then save a state, and then later load the same state but with a different ROM (barging down any hash checks in your way), the pokes you made override the new ROM. In general this is wildly unsafe but in certain cases it is practical.
Sms plus game genie free#
I'd say this is fixed good enough, but if there are any remaining problems feel free to reopen.Ī more serious problem is that there may be some homebrewers or hackers who want to load a state and test a modified rom. But if you don't have them initially enabled, and then turn them on later, they do seem to work. The exact codes given crash the game if they're present from startup.I can't locate technical details on the innards of mega drive game genie design, but given that it sat between the cart and the system, I think MD CART is the domain that makes sense. By default, the game genie decoder puts these cheats on the M68K BUS, but that doesn't allow writing to the ROM as it's still obeying the rules the CPU normally would use.I tested the game in question with the cheats in question, and noticed two problems: With fbee96c I allow writes to the required memory domain. So I vote for allowing rom pokes and savestating it. If it was truly absolutely necessary this could be made into an option or a command line option. It can be re-added if anyone actually demands it by a function (conceptually, at least, I'm not saying it's clean in our UI paradigms right now) to clobber the rom from a given file. If the user now changes that data, that's his business.Ī more serious problem is that there may be some homebrewers or hackers who want to load a state and test a modified rom. The way I see it, at t=0 the user has a workbench of equipment, one of which is a ROM whose data has been set from an indicated file. I am totally okay with the changes being in the savestate. It's there, it's visible: they want to tweak it. That it's technically read only is not something that ANY SINGLE USER cares about. I think I might even go as far as to say the ideal behavior is to be able to poke roms. I don't like that cheats are implemented by actually poking ROM, but independently of that (if for no other reason than for DEVELOPING cheats) users want to poke roms. I'm okay with there being a discrepancy between cores in this area. This does seem to be an issue of preventing writing for integrity purposes (as it won't change back if disabled as it's changing the actual value rather than patching it on the fly like a real cheat device would), but it is annoying for the end user to say the least.ġ.x seemed to only protect memory through the Read-Only flag when creating the domain (which is why poking the bus directly worked), but it looks like Waterbox actually protects the memory from being written from what I can tell? Rom domain is flagged as read-only, you can manipulate it through the bus in 1.x, you can't manipulate it through the bus in 2.x In 2.x, the MD Cart domain is flagged as read-only and manipulating it through the bus doesn't work. In 1.x, the MD Cart domain is actually flagged as read-only but you can still manipulate the rom through the bus and since this is a genie code, it's applying to the bus. The cheat is applied to the M68k bus, Appears to be within the rom section. I just verified the cheat does work in 1,x
0 kommentar(er)
