Lil' nitpick with Genplus-GX - Overclocking?

[Blackgrowl]

Hello. I have read from here that Genplus-GX is capable of overclocking: https://docs.libretro.com/library/genesis_plus_gx/#emulation-hacks

Namely "CPU Speed", it can change from 100 to 500%.

But I can't seem to find such an option in Bizhawk itself, is there any way I can request to add this feature, then?

[Morilli]

I believe we don't usually expose overclocking options and there's a number of cores that could theoretically expose this option.

[YoshiRulz]

(This is distinct from #3440.)

What title(s) do you need the setting for?

[Blackgrowl]

I believe we don't usually expose overclocking options and there's a number of cores that could theoretically expose this option.

Why not? I understand BizHawk is meant to be for Speedrunning, but...It does have some options that reduces emulation accuracy, so why not emulating overclocking too?

(This is distinct from #3440.)

What title(s) do you need the setting for?

For one, Ranger-X. In that game there's moments where destroying one of the massive silos that spawn enemies would make the game get a slowdown, almost to a crawl even.

For two, Soldiers of Fortune, which is the USA release of the venerable "The Chaos Engine". That one suffers slowdowns by a constant, just having 5 character sprites makes it slowdown.

For three, there's Urban Strike, it suffers from constant slowdowns but these aren't as severe until later where there's more tiny people and vehicle sprites on the screen.

Not sure if it will help but in Sparkster, when you hit the moving vehicle, it "stutters", I really do wonder if emulating CPU overclock would fix that.

[CasualPokePlayer]

Options we end up exposing that reduce emulation accuracy would be ones which don't have a general risk of causing game crashes and such. That would be a key difference between overclocking and say disabling the sprite limit. This is also why we don't also end up exposing options to remove CD latency emulation.

[Blackgrowl]

Options we end up exposing that reduce emulation accuracy would be ones which don't have a general risk of causing game crashes and such. That would be a key difference between overclocking and say disabling the sprite limit. This is also why we don't also end up exposing options to remove CD latency emulation.

Can't a compromise be made? For example, you can add the options but you also make them "unique", like give them a reddish (or perhaps orange to make it easy for the eyes) background so it indicates that this option is not recommended to deal with since it may cause crashing. Or make a pop-up appear that details such. And that it also disqualifies you from the speedrun, after all it's a very inaccurate hack.

Since you mentioned it, I would actually like an option to remove simulation of the "CD access time" too, though I haven't played much Sega CD games so I can't really say which ones would it benefit from.

[YoshiRulz]

I'm in favour of either exposing the setting, or adding a gamedb flag for those titles (which would also be available to power users).

[Blackgrowl]

I'm in favour of "exposing the setting" myself, you never know when you might need to overclock Genesis' CPU, on whichever title.

[Blackgrowl]

Hello, are there any news about this? And if I were to expand the suggestion further with all other cores, including Mupen64, should I ask in here or make another thread?

[YoshiRulz]

Bruh it's been not even a month.

You can open a new issue for each core, but the feature needs to exist in upstream (not sure what you're referring to w/ Mupen64Plus) and it needs to be justified with a list of titles that have lag problems on real hardware.