[CHANGES MADE] CPro MMD3 won't load

[Resident_Stevil]

The new beta that just went up should resolve problems with that option being enabled. The fix is based on looking at the skin.xml which also caught one cpro skin for me that didn't have the cpro prefix along with showing that the Skins page list wasn't working correctly with it also enabled. With the option off then it's just going to be looking at the file / folder name & files it can see if not already extracted.

So this fix will come with the next public release?  I don't have access to beta versions.

[dro]

The loading failure & skin type detection fixes will be in the next preview build once other beta build issues have been resolved (no eta other than when it's done).

[Resident_Stevil]

Still not 100% perfect but at least it's not freezing anymore.

[Aminifu]

What's wrong with it? If you want the tab labels to be spelled all the way out, make the skin a little wider. Point to the bottom right corner and when the mouse pointer turns into a double headed arrow, click and drag to the right.

I suggest you turn on a custom beat vis. Right-click on the Cpro label at the top, select the show beat vis command at top of the dialog that opens and select one of the beat vis listed. I like the dancing queens.

[dro]

It'll be the 2 elements that are bright pink as part of the player control section. I can't get my 5.666 install to complete loading with the skin but for the brief time where I'm seeing the main window it doesn't seem to have those elements messing up so most likely there's something going on with the images involved that aren't handled the same as what 5.666 was doing (i.e. due to almost a decade of libpng related changes since then based on some problems that have been seen when trying to use modern skins in wacup).

[Aminifu]

It'll be the 2 elements that are bright pink as part of the player control section. ...

Oh that. They won't be as bright when choosing a different color theme. One of our Skinner members can probably provide a better solution.

[dro]

Its something that's wrong my handling to try to fudge gen_ff to work outside of winamp due to there not being a 'color' value specified in the skin for the "$solid" part used to generate the background of those led elements. Afaict that's meant to be treated as color="0,0,0" & adding that into the appropriate line in the groups.xml file in the skin seems to fix it (the pink seems like it might be an error colour to help identify possible problems but gen_ff seemed to gracefully handle this). There'll be change in the next build which should do all of that without having to edit the skin which isn't imho the right fix even it's the quick way to do it.

[Aminifu]

Hi dro,

IMO, it is mighty big of you to have your code turn those leds on/off for that 1 skin, since it is popular. Thank you!

[dro]

It's not a skin specific fix & is a flaw with my handling around getting gen_ff to work outside of winamp. I'd seen it from the first test once I got the skin loading but didn't know if that was correct or not since I'm not going to mess around with trying to get the 5.666 test install loading cpro skins (I want to uninstall it but keeping it for the odd bit of comparison testing still makes sense for now) but thankfully it was simpler to fix purely due to seeing what the related element in the skin related to which is often not the case with other skin rendering issues.

[Aminifu]

It'll be the 2 elements that are bright pink as part of the player control section. ...

That is fixed in build #22186 (x86). Thank you dro.