No Font with MMD3 skin in latest build

[AeonicB]

So I updated WACUP to the latest public preview last night.  Left my skin as is, MMD3, before the update.

Came back to a buggy looking UI with no text displayed in the Media Library window, and Right Click context menus too thin to read or work with.

It was unstable, so I had to force quit it through Task Manager.

Backed up my settings, uninstalled, and reinstalled this morning.  Replaced my preferences, didn't replace my skin folder.

It was working with the default Big Bento Modern skin, so I tried reinstalling MMD3 again.

No text in the Media Library window, too thin text in right click menus, instability returned.

Attempting to return to return it to Big Ben Modern by accessing preferences through Ctrl + P shortcut and reloading it now gives no text and unusable menus.

Removing MMD3 restored Media Library text and Menu functionality.

For extra fun, I installed two other skins with a non-default appearance-- Peanut, and HM1 Touch.

Both worked out of the box.

Of note, this WACUP build didn't automatically associate WAL files with it after my reinstall, a problem I fixed by select WACUP as my option for opening *.WAL files.

Also, whenever I tried installing a skin, WACUP would warn me that the skin install was stopped midway through, and let me try and continue loading it.  MMD3 didn't work, Peanut and HM1 Touch did.

Regardless, reporting this as a WACUP problem as MMD3 was working fine before the latest Public build.

Attached are files showing Big Bento and its menu after attempting to load MMD3, MMD3 after its reinstall and first time loading the skin, along with its menu, the skin install error, and HM1 Touch.

[dro]

Can you provide a copy of the MMD3 skin that you're using please. As there's so many different copies of that skin out there it could be something specific to one revision especially as MMD3 is one of the ones I often use to double-check that gen_ff under wacup is behaving.

-dro

[AeonicB]

Just the version on WinampHeritage, here: https://winampheritage.com/skin/mmd3/122902

[dro]

I've quickly tried with that copy along with the selection of different ones I seem to have collected (most of them seem to be the MMD3-4-5 variant of the skin) & it all seems to be behaving correctly. Are you using Win11 by any chance?

In all honesty I'm not sure why the menus / text are getting screwed up for you as it's acting like it's not seeing there's any text to draw which shouldn't be happening. As I'm writing this, it's reminding me of some weird things I've seen reported with gaming anti-cheat software or when I had the skinned menus enabled for WINE setups (which is hard-coded to not be enabled under that use case for now).

Something to try is going to Preferences -> General -> Appearance -> un-check the use skinned menus option & see if that makes a difference (am not expecting it since the listview contents are also screwed up). If it does, then try re-enabling & using the custom menu font option to see if that still misbehaves or not.

To cover something else mentioned, WACUP doesn't setup any file associations in it's preview state (is noted during the install process) which is why WAL needed to be manually associated.

-dro

[AeonicB]

I'm using Windows 11. 

I unchecked Use Skinned Menus, reinstalled MMD3, and it looked fine.  Restarting it with the option off, no font as per my original screenshots.  Switched back to Big Bento Modern Windows 10 again, still no font.

Restarting it with Big Bento restored the font.

Forgot about the association thing.  I only use public, so it's been awhile since I've reinstalled it.

[dro]

Have had another report about this (had forgotten it had been reported on here already) so it seems like Win11's menus might be messing up custom drawing or just ignoring having the font applied which is then causing all of the menu width calculations to break (i.e. the bit that I rely on the OS to not mess up). Something else to check out once I start actively doing Win11 compatibility testing.

-dro

[Aminifu]

Hi dro,

Have you decided on when you will start the Windows 11 compatibility testing?

I'm having similar issues reported by AeonicB when trying to use the MMD3 skin. I will wait for your answer before providing my details, since what you may discover with the compatibility testing may make them unnecessary. Whatever this turns out to be may also be involved with my preferences dialog corruption issue (the ignored font and broken width calculations part).

[dro]

Not today as the full screen thing I was greeted with this morning on my win10 dev machine after it had rebooted to apply recent OS updates. Probably in the next few weeks once I've figured out the big stability issue affecting the current preview build.

-dro