MiSTer Nuked-MD Mega Drive Core

[Primeira_Fase]

Is anyone able to change buttons in this core? I try, however do not saves It.

[dickhardpill]

Do you scroll down and confirm on the save option in the menu?

[Primeira_Fase]

Do you scroll down and confirm on the save option in the menu?

Yes

[dickhardpill]

Which core are you using? What’s the name and date on it?

[retro]

Question:
Is this core compatible with Direct Video?
Direct Video woks between my MiSTer and RetroTink 4K for almost all cores, but this doesn't. I just wanted to confirm, since the MegaCD and 32X cores have Direct Video support.

[Retro-Nerd]

Yes, direct video works fine with the core. I'm using it via Retrotink 4K too. What's exactly the problem? Garbage, wrongly scaled image, black screen?

[retro]

Yes, direct video works fine with the core. I'm using it via Retrotink 4K too. What's exactly the problem? Garbage, wrongly scaled image, black screen?

Black screen.

I don't have all cores installed in my MiSTer, but of all the console cores I have tested this is the only one where Direct Video doesn't work.

The core in my MiSter is the latest 20240408.rbf release.

[Retro-Nerd]

Strange. Have you tried to delete the MegaDrive config files in media/fat/config ?

[retro]

Strange. Have you tried to delete the MegaDrive config files in media/fat/config ?

Thanks! Will try this and revert to you later.

[elmisterache7]

I'm having a weird issue with this core.
I have everything configured to output a composite signal to my CRTs and everything works fine but this Nuked-MD core outputs a green image, as if it is outputting component or something.

[retro]

Strange. Have you tried to delete the MegaDrive config files in media/fat/config ?

Unfortunately this did not work either.

The RetroTink 4K keeps switching between MiSTer Gen (MegaDrive) and MiSTer 240p (MegaDrive), but other than that there's no audio and video.

I guess it's progress - previously it was simply "No Signal"

[Retro-Nerd]

Yeah, this shouldn't happen at all. Mister 240p should be stable when in direct video mode over HDMI. What's your display? Usually VRR capable devices have less issues with that. You could also try to something like this in the Mister.ini:

[MegaDrive]
vsync_adjust=0

or set it to "Triple Buffer" in the Tink HDMI Ouput -> Sync Lock settings.

[retro]

Yeah, this shouldn't happen at all. Mister 240p should be stable when in direct video mode over HDMI. What's your display? Usually VRR capable devices have less issues with that. You could also try to something like this in the Mister.ini:

[MegaDrive]
vsync_adjust=0

or set it to "Triple Buffer" in the Tink HDMI Ouput -> Sync Lock settings.

I am using an LG OLED C3.

The MiSTer is connected to the Tink 4K with a HDMI swtich, and the Tink 4K outputs directly to the TV. The HDMI input at the TV has 4:4:4 enabled.

No difference whether it's Triple Buffer or Gen Lock, there's simply no signal from the MegaDrive core.

For the record, this (and the Sharp X68000 core) are the only cores where I am having problems with Direct Video.

And yes, I have the following in mister.ini.

[MegaDrive]
vsync_adjust=2

[Retro-Nerd]

The Sharp X68000 core doesn't support direct video. The C3 shoudn't have any problems with the MegaDrive core. So this could be it just an incompatiblilty with the Switch in combination with the Tink. If vsync_adjust=0 doesn't help your probably out of luck (for now at least). I guess you've tried to enable VRR (either in the mister.ini -> Freesync, or directly via Tink)?

[retro]

The Sharp X68000 core doesn't support direct video. The C3 shoudn't have any problems with the MegaDrive core. So this could be it just an incompatiblilty with the Switch in combination with the Tink. If vsync_adjust=0 doesn't help your probably out of luck (for now at least). I guess you've tried to enable VRR (either in the mister.ini -> Freesync, or directly via Tink)?

Looks like my mister.ini is quite old, as it doesn't have VRR related settings.

You're referring to https://mister-devel.github.io/MkDocs_M ... h-rate-vrr, correct?

I am adding the following settings to see if it makes a difference.

vrr_mode=2
vrr_min_framerate=0
vrr_max_framerate=0
vrr_vesa_framerate=0

[Retro-Nerd]

Yep, vrr_mode=2 is correct for "Freesync" and should work with LG OLEDs (i have the C9). You could also try to set vrr_min and max, accordingly to the VRR range the C3 supports, e.g. 40 and 120 (Hz) or something similar.

[retro]

Alas that did not work.

I am still getting the same results.

This is a video of what I am getting from the RT4K's stats.

https://imgur.com/4rq9c5G

[Retro-Nerd]

You get the same issue when you connect the Mister directly to the Tink, without the HDMI switch in between?

[retro]

You get the same issue when you connect the Mister directly to the Tink, without the HDMI switch in between?

Not possible to test because of cable management in my shelf.

I asked around the RetroTink Discord and several people were getting the exact same results as I am.

Looks like it's back to the old Genesis core for me

Many thanks for all your help!

[sacredbanana]

Is anyone able to change buttons in this core? I try, however do not saves It.

I am getting the exact same issue. No matter what I try, even deleting the config file and even the whole core and starting afresh, the buttons are all wrong on my DualShock 4 controller and it won't let me set them. It works fine in the old genesis core

[JayRockets]

I'm not sure I can get on board with that definition of 'accuracy'...fidelity, perhaps.

I have never been able to play a single game on software emulation without one of the following: Audio Glitches, V-Tearing, or Stutter. Getting rid of two always leaves one. For years I played with the stutter you get from sync issues thinking it was slowdown that was present on real hardware. It's not. It's noticeable. And it's inaccurate.

[rhester72]

I have never been able to play a single game on software emulation without one of the following: Audio Glitches, V-Tearing, or Stutter. Getting rid of two always leaves one. For years I played with the stutter you get from sync issues thinking it was slowdown that was present on real hardware. It's not. It's noticeable. And it's inaccurate.

On what emulator(s)? What you're describing really hasn't been a thing in the past decade on virtually all software emulation (except possibly playing NTSC on PAL displays).

[JayRockets]

On what emulator(s)? What you're describing really hasn't been a thing in the past decade on virtually all software emulation (except possibly playing NTSC on PAL displays).

Higan, Bsnes, Mesen, Mame. You want to see what I am talking about? Load up Chrono Trigger, go to the Millenial Fair, and then sprint back and forth at the widest part of the fair for like 30 seconds.

[Retro-Nerd]

With VRR capable displays tearing and stutter shouldn't happen anymore in most emulators (if they have VRR support of course).

[FPGA64]

Also running the Emulator on something other than a Potato helps.

[vanfanel]

I have never been able to play a single game on software emulation without one of the following: Audio Glitches, V-Tearing, or Stutter. Getting rid of two always leaves one. For years I played with the stutter you get from sync issues thinking it was slowdown that was present on real hardware. It's not. It's noticeable. And it's inaccurate.

That's not the case at all with well-configured emulation. With the RetroArch frontend, you get the emulation cores synchronized to video refresh rate and audio resampled to cope for that, which fixes those defects like the ones you describe. It's not magic, it's simple maths.
Standalone emulators however will show those defects no matter what.

[FPGA64]

I have never been able to play a single game on software emulation without one of the following: Audio Glitches, V-Tearing, or Stutter. Getting rid of two always leaves one. For years I played with the stutter you get from sync issues thinking it was slowdown that was present on real hardware. It's not. It's noticeable. And it's inaccurate.

That's not the case at all with well-configured emulation. With the RetroArch frontend, you get the emulation cores synchronized to video refresh rate and audio resampled to cope for that, which fixes those defects like the ones you describe. It's not magic, it's simple maths.
Standalone emulators however will show those defects no matter what.

No its got nothing to do with retroarch. A good standalone emulator will be fine, you need to use an accurate one like Ares on a decent machine.

[niallquinn]

Also running the Emulator on something other than a Potato helps.

To be fair, stick a multimeter into it, on low voltage, and it does create some millivolts!

[vanfanel]

No its got nothing to do with retroarch. A good standalone emulator will be fine, you need to use an accurate one like Ares on a decent machine.

Ok, I'll bite: How do you solve the problem that, if you sync to host machine refresh rate (which is imperative to get no stuttering at all), the amount of generated audio frames must be altered to a matching value?
That can be done manually on some emulators, but RetroArch does it for you on every core as part if it's API.

Also, parting API and emulation core is simply the perfect way to port and manage emulators, which also RetroArch does.
There was some stupid woke hate towards the project, a maneuver that came from this shit often comes from: corporations that sell emulation solutions which are not happy about RetroArch impossible to beat portability and features being free+opensource.

[FPGA64]

No retroarch has a history of ignoring emulators developers wishes. Duckstation for example. Retroarch should never be supported. I use Ares and never see any issue, sound and picture are perfectly in sync. You do know that under the hood retroarch is just a collection of standalone emulators.