MiSTer FPGA Forum

There just aren't a lot of complex components on that board to fail, but if you're sure you've got +5V on the board...it's dead, Jim. :/

It may look like it's connecting well, but if that power is lost, the ports shut down...I saw exactly the same on mine, and you could 'bump' the MiSTer and everything would come back. My solution to ensure a very solid connection was to solder a wire between the connection point on the bottom of the board and the "finger".

What form does that bridge take on yours? More specifically, where did you obtain it? (That bridge can occasionally get finicky if it's a metal "finger" that extends up to the DE-10 versus a plug.)

Which USB board and how does it receive power?

Curious - did they have a black or blue plastic piece in the plug? USB 3.0 is always blue.

Touche! =)

No accessory for Hoth Luke? Sacrilege! =)

@Syntax Error What makes you think the core won't run EF carts?

Problem with Keyrah is that one of the lines on port 2 is shared with port 1, so you can end up with crossover in less-than-ideal circumstances.

I did this:

https://github.com/rhester72/c64_universal_usb_kb

(with a real C64 breadbin that had a very much broken motherboard)

Underwater sound appears to be fixed in Tomb Raider, and known play issues in Sega AGES appear to be resolved.

SegaMan wrote: ↑Mon Mar 11, 2024 10:53 am

Crackle Sound on Exhumed and Panzer Dragon 2.

Where in Exhumed? The menu crackle is definitely fixed.

One thing I have noticed for the first time is how broken audio is underwater in Tomb Raider. Still, every few days, there's improvement!

Chris23235 wrote: ↑Fri Mar 08, 2024 12:11 pm

Not fully fixed for me, but much improved. I still get some cracking whenever the sound is inititalised (e.g. after loading). It's very short, but audible (only tried DualSDRAM now).

I was referring to the menu sounds...never heard it on load, but wasn't listening for it, either.

Crackle in Exhumed is fixed!

Does it work on VICE?

MadDog wrote: ↑Wed Mar 06, 2024 1:45 am

Hmm... You can find the output on the build and associate it to the commit. For instance, this commit is associated to this build.

Perfect, this is exactly what I was looking for! Thank you!

I still can't tell the difference between unstable cores from here:

https://github.com/MiSTer-devel/Saturn_ ... mits/main/

I know the hex at the end of the filename corresponds to a github commit, but when I look at the shortnames for the commits, none of the IDs ever seem to match. What am I missing?

segamemister wrote: ↑Tue Feb 27, 2024 9:55 pm

the unstable release is not needed anymore?

is this true?

Are you talking about MiSTer Main? If so, no, unstable is not needed any longer.

mrchrister wrote: ↑Mon Feb 26, 2024 12:36 am

It will be overwritten. If you want to exclude games, follow instructions from the GitHub page :

Thank you!

Chris23235 wrote: ↑Fri Feb 23, 2024 11:18 pm

Just tried Exhumed on the 20240222 nightly and sadly it's not fixed in the DualRam or the SingleRam core.

Very interesting - confirmed. That means whatever is causing that click is something different.

Cool game, too. =)

If <core>_blacklist.txt files are (deliberately) altered, will the changes 'stick' after updates or be overwritten?

The clicking may be fixed now:

https://github.com/MiSTer-devel/Saturn_ ... mits/main/

EDIT: OutRun also works properly again.

Stuttering sound isn't fixable by code, it's your RAM.

I let Daytona USA run through the demo loop twice and didn't hear any audio abnormalities.

It is indeed louder by intention (see "fix output levels"):

https://github.com/MiSTer-devel/Saturn_ ... fc640b901a