MAMEHub
MAMEHub copied to clipboard
dip mirroring doesn't work at the start of a game
if the host changes his dip settings in the middle of a game, the peers will get the changes. However if the host had the changes before the start of the game, i.e. his config file the clients well not get the changes to the dip switches
Does this cause a checksum error when the clients with different dip switches try to connect?
some times it seems too, but other times not, i can try to replicate a checksum
ok tested in mario bros us revision unknown. had peer set his dips to 6 lives before joining, i had mine set to 3. got checksum error host log https://gist.github.com/Prinygod/31567af23036c9497cac peer log https://gist.github.com/anonymous/d46bf487ed41bc8b19d5
how do you change your dip settings before the game starts? Is it a cfg or ini?
On Mon, Aug 11, 2014 at 10:10 AM, Prinygod [email protected] wrote:
ok tested in mario bros us revision unknown. had peer set his dips to 6 lives before joining, i had mine set to 3. got checksum error host log https://gist.github.com/Prinygod/31567af23036c9497cac peer log https://gist.github.com/anonymous/d46bf487ed41bc8b19d5
— Reply to this email directly or view it on GitHub https://github.com/MisterTea/MAMEHub/issues/249#issuecomment-51809734.
well there is, how i did it was to go into a game, set the dips and then leave, it saved it into the .cfg file i don't know if your able to change the dip switches in config file witll out changing the other settings, but if you could, and make it some how universal that might be one fix. remember that gamepad settings and more are also in the .cfg file
Yeah we need to pick and choose what items from the cfg & ini file need to be sent to clients, and then on the client-side we need to merge those items with the client's cfg/ini files.
I got another one on the GBA with another player. I had to delete the nvram to get it to work:
http://pastebin.com/uGj74FMQ
Although it doesn't have anything to do with DIP settings I suspect it is the same problem. It's like settings/saves aren't being transfered properly (or checksum validation happens before transfer).
ill look into it, but nvram sending is currently supported so if its not working thats a bug, and is a separate issue