For SpecialK I think you get what the patch sets for the mini-games so 30 FPS, it works especially after the game got patched and with the framerate limit disabled you should be able to use the SpecialK framerate limiter as a full replacement for a overall smoother experience as it's not going to have any issues with how the developers utilized the sleep command as it can be problematic or at least imprecise in responsiveness.
(It's set to 1ms but it can be up to 16ms.)

Alternatively the games framerate cap and then combined with the sleepless render thread option flipped to enabled in SpecialK but I think the framerate limiter is more robust than the games own is so I'd probably go with that entirely and skip the game one other than the patch hard coding the mini-game framerate for timing reasons. :)

These games are going to be a bit weird when ported to PC or the underlying tech at least is going to run back and forth between new and old.


Yakuza Like a Dragon as the newest game and the Dragon engine hopefully with this fixed but then the listed but unreleased Yakuza 6 as the first Dragon engine game and then there's Yakuza 3 - 5 re-released and updated but running on I think it's the Binary Domain engine?
(Actually might have been Yakuza 4 and 5 only.)

Judgement if that ever gets ported slots in between Yakuza Kiwami 2 and Like a Dragon and then I believe the North Star game is back to the Yakuza 0 and Kiwami 1 engine.


Back and forth a bit but perhaps the two studios that have so far done the ports can improve and we'll have this fixed from now on, stuff got fixed via patches as well but not all of it including this issue.



EDIT: Yakuza Kiwami 2 also has the Cookie "Silent" patch come to think of it.
https://cookieplmonster.github.io/2020/01/18/silentpatch-yakuza-kiwami-2/

Frame pacing improvements same as I believe you get from SpecialK alternatively the sleepless render thread checkbox to disallow the sleep command here.


Toylets capped to 30 but other mini-games can do 60 FPS.

Is that a downside of the original Github repository going down?

Although by this point I suppose the changes since what version of SpecialK these were built around would be so significantly out of date it would almost need to be rebuilt again against the latest core and code adding a lot of work to the existing 0.12.x list which if that's ever in the plans for these separate earlier stand-alone projects would probably work best once the new version is released.

Suppose some of these older games also using DirectX 9 hampers some of the later developments a bit compared to D3D11, wrapping through Vulkan like what Proton or DXVK is doing likely also doesn't offer any immediate improvements through SpecialK.


EDIT: Upcoming Tales of Arise (I think it was called that?) should be on UE4 so at least it should "only" have the typical UE4 issues.

Not that it helps here, doubt there's much of a chance for further updates for Symphonia, Zestiria or Berseria although if Koei/Gust can port some of the earlier PS3 Atelier games Namco could perhaps have some re-releases of the earlier Tales games although considering their popularity some of those should have already happened or so it feels like.

Sometimes stuff just happens though, not sure about the earlier ones due to even older code but it's not like it's impossible or anything just more work.

Could be a Wine issue.
https://www.winehq.org/pipermail/wine-bugs/2018-December/504555.html

I don't use Linux at all so I can't be of much help though, a lot of these functions and features have been added through Wine, Proton and such including wrapping D3D to Vulkan and more but there could still be the occasional feature or newer Windows OS or Windows application functionality that might not be all supported yet.

Visual C++ 2015 also has updates through 2017 and the latest 2019 runtime so that might complicate matters a bit depending on what part is required although Tales of Symphonia or rather this utility here for it should be mostly running through the earlier versions of SpecialK so the later runtime features aren't a concern.

wmn5r.exe seems to be Wangan Midnight Maximum Tune 5 but from there and searching on the exe name it moves to Tekno Parrot and various loaders so I can't find that much more.

http://www.emuline.org/topic/1449-tuto-wangan-midnight-maximum-tune-5-including-versus-play-lan-setup-extra-car-livery/

The non-backer version should be up on Steam on the 19th I think so a bit over a week, using DirectX 9 probably removes a good amount of the D3D features in SpecialK though and the issues around scaling and the way this game does it's 60 FPS framerate limit would probably need a patch but I don't know what the plans for the game is once it's released in full.

I've seen the mechanics working really well with the Steam gamepad but there are some issues that hopefully the developers will be investigating and resolving although I do not know how some of this could be missed in testing in the first place but it happens.


Wonder what else is going on in the game, suppose if you do pick it up that might get some answers.

Shouldn't be the most troublesome port although from WiiU to other platforms is a bit different than XBox or Playstation but as long as the devs read issue reports such as from the Steam forums or Kickstarter backer updates and discussions there's always a possibility for getting these patched properly.

19th should also unlock the game fully and then through Steam DB it would also show if there's any newer work in progress branches for a patch in progress. :)
(There's no publisher issues here I believe so Platinum shouldn't be hindered like with Nier Automata or whatever happened there so that's something at least.)

There was a SpecialK guide on Resetera for some of the fixes that could be used.
https://www.resetera.com/threads/the-wonderful-101-remastered-goes-up-on-kickstarter.168248/page-107#post-33416568

https://gtm.steamproxy.vip/app/1190400/discussions/0/2248929785822802198/

it runs at 59 fps instead of 60, that's why. A partial solution that worked for me in MGR For 2 hours every time I ran it, is to use the global injector of Special K, and then enable Sleepless Window Thread and Sleepless Render Thread. So far (played for an hour strait just to check it) it remained at 60 at all times, without ever dropping below. But still, in MGR after 2 hours or so of play I had to exit and relaunch the game, and I can only assume it will be the same here. Platinum need to fix it.

There's also some camera issue particularly due to going above that resolution and it's scaling problem.

https://www.resetera.com/threads/the-wonderful-101-remastered-goes-up-on-kickstarter.168248/page-108#post-33435996


Though why is it using D3D9 it should be using D3D11 you'd get a lot more out of it and it wouldn't be a single threaded API with all sorts of limits so why even use that these days.

That's going to be a problem, DXVK wrapping or similar might be a thing but that's a weird choice for the port but nothing to be done about it now unless they somehow patch that which I would expect to be extremely unlikely.


EDIT: Ah but it's the same issue it seems in where it only works for about a hour or two using SpecialK to try and mitigate the way the game is managing the framerate.

Wonder if wrapping it and some settings for DXVK would be a thing then if it's compatible with this game.

https://github.com/doitsujin/dxvk/releases

https://git.froggi.es/doitsujin/dxvk/-/jobs
(Main project and the latest compiled code.)

I'll forever wonder what happened to Last Remnant, PC specific improvements, fully unlocked framerate and resolution support, mouse and keyboard supported well plus gamepad of course and it ran really well only missing two smaller DLC from memory.


Then that got pulled from Steam some year back and the UE4 powered remaster got released but only on console, what?

Engine wise and for all their ports and studios even some of the western acquisitions via Eidos and outsourced PC porting they've never really hit that standard again, UE3 is or was really good but it too is very open to being modified and can see even basic functionality broken or messed up.


Final Fantasy 15 got close only hindered by the struggles of the development team and effort behind this leading to a too early pause of support and pretty much termination of content updates finalizing one of the three year 2 DLC with the others wrapped up through a short novel story instead.
(Bit more polish and a bit less executive pressure for the online bit being focused on and that could have been a really good port too.)


The Dragon Quest XI team (Armor Project?) didn't do a bad job or anything, would be nice if the Switch version improvements would be patched in around September / October (Standard year length exclusivity.) but that's a pretty big if since Nintendo were more directly involved in these enhancements.

It's Unreal Engine 4 they can't have broken it that badly could they?
https://framedsc.github.io/GeneralGuides/universal_ue4_consoleunlocker.htm

Pop that in use ~ (Tilde) or Tab and this command specifically.

r.PostProcessAAQuality

0 to 6

0 is off, 1 I believe is FXAA and 2 being higher-quality FXAA

3 to 5 being TAA with 4 as the usual game value

6 as a sort of very high quality temporal AA method mostly for non-realtime usage but it does work although it's a good idea to monitor framerate and maybe reduce it down to 5 if it takes too much of a toll on the GPU and starts causing framerate drops and stuttering. :)


There's other commands for fine tuning it from TAA sharpening, number of samples or just invoking max quality mode overall but for TAA itself that should be good.

r.MotionBlurQuality

0 to 4

0 would disable it 4 would be the highest quality, if there are issues with motion blur this will disable it. :)


Scalability or the user config option could work but this works as well, multiple cvars are also possible via the | divider.

r.PostProcessAAQuality 6|r.MotionBlurQuality 0

Like so.



EDIT: Or the full everything.

sg.ResolutionQuality 100|sg.ShadingQuality 4|sg.AntiAliasingQuality 4|sg.ShadowQuality 4|sg.FoliageQuality 4|sg.ViewDistanceQuality 4|sg.PostProcessQuality 4|sg.EffectsQuality 4|sg.TextureQuality 4|r.Shadow.DistanceScale 2|r.Streaming.LimitPoolSizeToVRAM 0|r.Streaming.PoolSize 4096|r.Streaming.MaxTempMemoryAllowed 256|r.SSR.Quality 4|r.ViewDistanceScale 2|r.StaticMeshLODDistanceScale 0.01|r.MaxQualityMode 1|r.ScreenPercentage 100


Commands can just be copy pasted.

Careful with the R.SSR.Quality setting, it's a whole lot better than the grainy noisy normal value of 3 but it also costs upwards of 40% extra all on it's own.

Shading quality is a newer preset group in 4.22 or more recent, mostly used for I believe some of the advanced hair rendering effects introduced to the engine.

Screen percentage can be used for super-sampling, also incredibly demanding but it really counters the TAA blurriness and general aliasing improvements.

Back on the actual topic though I suppose the Ubisoft situation also still hinders things for support for these games and others if their idea of third party mods or utilities is that they're malicious and won't even bother with trying to get that resolved, unfortunate but it is what it is.

EDIT: Especially if Steam is doing it's +1 score tally for running bans and that situation again. Yay.