I'm sorry for the late reply, thanks for all the detailed bug reports.
Hey, would like to say thanks for the update.
I have a problem, I'm using a CTF theme titled "sony black" originally for 5.00 m33, but I updated it to 5.50 so I can use it on my 5.50 GEN-B2 slim. Everything is working correctly but when I use the content browser mode it freezes when I select the memstick Icon. I tried it without cxmb enabled and it worked; just doesn't work with my theme.
I wasn't able to find a copy of this theme for 5.50 GEN and thus was unable to reproduce it, though recent changes to the code may have helped in fixing it. Give the new update a try.
When I use the Content Browser mode, and ONLY when I use the Content Browser mode, 2 "Unsupported Data" icons appear in my "Applications" category and 1 "Unsupported Data" icon appears in my "Games" category(see below). I think it has to do with the __SCE__ and %__SCE__ prefix namng of two application icons that the 1.5 kernel apps create-One becomes the one to launch the program and the other becomes an "Unsupported Data" icon(In the two other modes and when not using the plugin, I do not see these "Unsupported Data" icons since "Hide Corrupt icons" is enabled in the recovery menu.) Also notice that the "Unsupported data" icons always appear after the 1.5 kernel app with the __SCE__/%__SCE__ naming scheme.
Therefore, I decided to try to change the names from __SCE__Appname and %__SCE__Appname to Appname and Appname% since I saw gpSP had this alternate Appname/Appname% naming scheme and there was only ONE "Unsupported Data" icon in CAT_Games, not two.
It worked for me, but I'd just like to let you know this can happen. The solution for now is to rename all the __SCE__Appname/%__SCE__Appname 1.5 kernel apps to Appname/Appname% or use the 5XX version.
My suggestion is to either include this information into the Readme or add support for the naming scheme without showing the "Unsupported Data" icons.
Bug reports like that one is what gets things done, thanks.
It's caused by the fact that a lot of homebrew and the custom firmware make use of the fact that homebrew can be hid by prefixing them by __SCE. When coding Content Browser mode, I didn't take this in to account. It should be fixed now.
A very small bug I've noticed: This plugin seems to disable the preview icons for the "color" section of the Theme menu. I'm running 5.03 GEN-B (Full) on a PSP 2000. This happens regardless of what settings I choose for the plugin. This seems to be the only bug I've encountered that I haven't seen reported yet; excellent work on the plugin so far.
If you need any more details from me, I'll be happy to try and provide them.
Small bug, it's been fixed.
I've been having quite a bit of trouble specifically with emulators with this plugin, the DoomWAD (whatever the app is actually called) can't find its WAD file because its prog to read in the game folder, SNEStxyl sorta works, but the minute I start it it says can't read mem card and no rom folder will show up, NES works 100% (just have to reroute rom folder) homer's rin loses its save states, and I believe that's it, but those bugs actually relate more to the apps themselves I'm not sure how bubbletune might be able to fix them
EDIT: I'm not sure why this didn't occur to me before, but in theory you should just be able to put the roms in the GAME folder under whatever the emu's name folder is, but I have yet to test it
Are you using version 11? Version 10 had a major bug regarding this matter. If you're using v11, it's likely that it's caused by them using absolute paths.
there is one bug id like to let know about
if using the cxmb plug-in the network update gets disabled for both 5.00 m33-6 and update for GC 11 on a large amount of the themes
and the previews for the colors are still not showing up
It's probably caused by the fact that some themes swap Network Update for Reboot PSP. Could you tell me in more specific on which themes it happens?
there's 2 bugs i've found:
1. as of version 10 or 11, the psp crashes while booting up after entering the password in Lockdown XMB Style (slim only)
2. if you highlight the memory stick in the game column, enter sleep mode (to simulate the conditions one would have done before experiencing the bug), then turn system back on and hit X on the memory stick as soon as the XMB loads up (free space calculation will have a dash). result: infinite loop "busy icon"
1) Fixed.
2) I wasn't able to reproduce it, but try the new version nonetheless, a number of internal changes might have contributed to solving it.
Hmm, gameboot flash video still not working under context browser option...
Mind you fix this on the next update? looking forward to it.
As said in the readme, this isn't a bug. It's because I have to make my own call to LoadExec, which doesn't play the gameboot.
This version doesn't work with Lockdown. Even when loading plugins after mediasync.prx (not the load after password for extra security method). v9 worked fine.
I was patching sctrlHENPatchSyscall to intercept VshControl's patches done with it, which was interfering with IOP.prx. In order to fix it, I've disabled the patches if the return address points to IoPrivileged.
