MiSTer FPGA Forum

I seem to be running into an issue getting WiFi working on mine as well. I ordered the "Ovker" Bluetooth+WiFi one on Amazon, and Windows identifies it as a RTL8821CU as others have gotten working here. Using a USB 2.1 hub (just installed) but only the stock power supply. However, I've only got the dongle hooked up right now, and Bluetooth...

Mine is the same way. I think it's normal.

Yes, I'm getting it, too. I was thinking maybe it was the "GBC-on-GBA" sound issue from other games like Vigilante 8, but I didn't get the sound issues on a GBA with an EverDrive X3.

Headers contain a fair amount of info, but the most important is that it identifies which mapper chip the game uses, since the mapper isn't part of the ROM dump.

I think it is - I just grabbed the single file in the 2020-04-16 set from the usual source and it seems to work fine.

I have a ROM that did the same thing - I think it's either from an older No-Intro or EverDrive pack. Check out the one in a newer EverDrive pack. CRC32 is FC97FC14 for the one that works for me.

No sense getting upset over what is supposed to be an entry-level look at the MiSTer Multisystem. Yes, there's lots of stuff that could have been covered, but doing so gets heavily into the weeds and doesn't help the lay user at all. The video was fine.

I'm seeing this too. Everything downloaded via the update-all script. Not sure if it's a core issue or a ROM issue.

Can confirm that I'm having the same issue with FM sound enabled.

Okay, thanks. I meant to check when I got home yesterday, but got sucked into other stuff.

Anyone check the issue with Zed Blade yet?

A bad ROM dump could certainly cause unintended behavior, but I don't think that's the case here. I'm using a no-intro version on both the MiSTer and SD2SNES, and also tested the same ROM in bsnes just for sanity's sake while getting the checksum.

sha256: d45e26eb10c323ecd480e5f2326b223e29264c3adde67f48f0d2791128e519e8

Bummer. Well, I'm sure as the core gets more accurate, it will all get sorted out. Thanks to everyone that works on these cores!

Can confirm that through an original model SD2SNES, enemies shoot at you a ton on the highest level in Episode 3. They do virtually nothing on MiSTer. Definitely some sort of edge case broken in there.

Exciting times to be sure. Rooting for both of these to be amazing!

Might want to bring it up as an issue in the repository.

https://github.com/MiSTer-devel/Intv_MiSTer/issues

I'm going to take a look at this core for sure. It's the one system that I haven't reobtained from my childhood yet, and I probably should.

Or if you're comfortable with command line stuff, you can just do a "rename *.srm *.sav" in a Windows command prompt from the save directory. Preferably on a copy just in case something goes wrong.

Definitely appreciate the info from an FPGA guru.

I suspect "complex" in this case mostly refers to using pretty much all the logic elements available in the FPGA. And as that quoted statement says, when timings are really tight, heat can potentially affect said timings enough to cause undesirable behavior. While it may be rated for those high temps, heat still often reduces the lifespan...

I like the functionality, and yeah, the options to disable the download are there. From a legal standpoint it's not great, but I didn't realize that the MAME-GETTER stuff is also a separate script that's part of it, like Jotego's stuff. Good to know in the future. So basically, yeah, if you use the update_all script, just be aware of what you're ge...

Definitely something strange going on - I forgot to mention that mine was via component as well, and no issues with colors that I could see.

Someone correct me if I'm wrong, but Jotego's updater doesn't actually grab the ROMs, right? It's the update_all script, which integrates his updater.

As nice as the update_all script grabbing the arcade ROMs is, I do think it's problematic that it does so. Much like emulators, the scripts should only be distributing the cores.

It looks fine on my Trinitron. Hard to make out that last band, but it's still the right colors. I got my I/O board from MisterAddons.

Ha, missed a bunch of responses. Still, I'll leave this up. The input lag is additive. You'll get display lag coupled with emulation lag. The MiSTer will still have a small amount of lag from an LCD (although this highly depends on if this is a TV or monitor and the brand), but it'll be less than what you'd get with emulation + LCD. Basically, thin...

Yeah, I'd assume to avoid accidental saves. On the EverDrive, you can map to two buttons, and there have been a few occasions where I've accidentally saved or loaded when I didn't want to.

Oh, nice. Thanks for that tidbit!

It looks like Rastan uses some pretty standard chips: MC68000 and Z80, and a YM2151. Don't know anything about the OKI MSM5205 ADPCM chip, but I suspect Rastan would be quite doable.

*coughbattletoadscough*

Seriously, though, I practiced using save states before making my legit runs. Great that this core is getting save states, because even if you're not using it for practice, it's nice to be able to leave off anywhere you need to.

I thought it was normal. I always get that audio pop running from the analog IO board out to a CRT. It's also something I hear on my NES that has been modded for expansion audio.

In most games, the lag isn't even noticeable. Only in the worst case scenarios like Punch-Out!! can you really feel the few frames makes a massive difference. I have really been enjoying the MiSTer project. But there are still advantages to emulation as well, and I liberally use both. And PS1 emulation is definitely better on PC, although for most ...