Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SNES9x needs a System Bus memory domain #943

Closed
Trivial-Man opened this issue Jul 27, 2017 · 4 comments

Comments

Projects
None yet
4 participants
@Trivial-Man
Copy link
Contributor

commented Jul 27, 2017

...or at least some sort of memory domain that allows access to the ROM itself and not just the RAM.

@zeromus

This comment has been minimized.

Copy link
Contributor

commented Jul 28, 2017

Do you think you're going to edit the ROM? That won't work right now. The ROM is read only. File On Disk should work. You probably wouldnt be able to edit the ROM through the sysbus memdomain anyway, it would certainly be read-only mounted through there.

@zeromus zeromus added the Core-Snes9x label Jul 28, 2017

@Trivial-Man

This comment has been minimized.

Copy link
Contributor Author

commented Jul 28, 2017

Not for editing, no. This would allow me to read values with the RAM search tool and lua's memory.readbyte function (and readfloat, readbyterange, etc). If File on Disk is a valid option for those I wasn't aware.

Specifically, the reason I want this is so I can have a script that (among other things) looks up the initial carrying capacity for bombs and arrows in randomized LttP ROMs. It's at location 0x308034 using the system bus with the bsnes core, or 0x180034 using the cartROM.

@vadosnaprimer

This comment has been minimized.

Copy link
Contributor

commented Jul 28, 2017

System bus for scripts makes sense, because the game can indeed read from rom in its algos one might want to simulate. The only question is, why not bsnes core itself? snes9x core is for casual gaming.

@Trivial-Man

This comment has been minimized.

Copy link
Contributor Author

commented Jul 28, 2017

Essentially because the script I'm writing is for casual gaming. It's just a visual tracker for certain items/events. Helpful for a novice (like myself) or a streamer's audience but useless for an advanced speedrunner or TASer.

For the record I do use bsnes, but this one instance of reading values from the ROM is the only part of the code that behaves differently between the 2 cores. And since a system bus or a similar domain is present in at least a good number of the emulation cores I tested, I thought this was more of a standard feature that just hadn't been implemented yet and wanted to make the devs aware that it was wanted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.