Posts for CLChambers00

Experienced Forum User
Joined: 7/21/2017
Posts: 54
I have also confirmed that resetting the game does not retain RNG values so it is not required to power cycle the NES in order to do RNG manipulation.
Chambers_N
Experienced Forum User
Joined: 7/21/2017
Posts: 54
So I have confirmed that changing the core in Bizhawk from QuickNES to NesHawk gives yet another set of values. So FCEUX(Old PPU), FCEUX(New PPU), Bizhawk(QuickNES), and Bizhawk(NesHawk) all yield different results, so four different outcomes. Once again changing the initial RAM State either in Bizhawk or FCEUX does not modify outcomes since the Rom initializes its own values. What changes this? Why such a difference between emulator outcomes? And yet none of these outcomes match original cart with Front Loader, or with Top Loader, nor use of Everdrive with Front/Top Loader. There must be a way to know why and have the ability to sync some of this. Any thoughts?
Chambers_N
Experienced Forum User
Joined: 7/21/2017
Posts: 54
All the details are in the link. I had stated that changing the initial RAM state did not result in different outcomes. What is causing different outcomes is whether I use Bizhawk, FCEUX (Old PPU), or FCEUX (New PPU). These three all yield different results and I want to know why. And how I many adjust something in these emulators or modify a memory address or two that would be causing it so that I can get one of these three outcomes to correlate with original hardware. This game initializes its memory so that is not the problem.
Chambers_N
Post subject: Who Framed Roger Rabbit
Experienced Forum User
Joined: 7/21/2017
Posts: 54
I had originally created this thread in NESDEV to address this issue I am having. https://forums.nesdev.com/viewtopic.php?f=2&t=16226 I have been trying to get either Bizhawk or FCEUX (Old or New PPU) to correlate to original hardware. Bizhawk populates different values than FCUEX, and even the values differ between Old and New PPU in FCUEX. So I have three differently functioning emulators producing different outcomes despite exact same inputs, etc. Changing the Initial RAM State in FCEUX to FF, or 00, or keeping the default 00 FF, does not alter the results since these addresses are initialized by the Rom to 00. I have also observed the same results when I use my Everdrive with both the Front Loader and the Top Loader, probably since the Everdrive works the same despite the hardware. As of yet, I have not been able to correlate either Everdrive with Top or Front Loader, or original cart with either Front or Top Loader with any of these three emulator conditions. For speedrun purposes it is preferred to TAS out 1000's of variations, then mere trial and error. For TASing purposes what emulator would be acceptable since actual hardware conditions don't appear to be met. And which would be used for such a project, what would be allowed. I assume that using a Lua Script in order to write specific values into the addresses of the item spawns is not allowed for TAS projects. Any thoughts or reflections would be greatly appreciated. As mentioned there is a lot more detail in the link to NESDEV that would also be helpful to bringing you up to speed on this project. Corey
Chambers_N