[Plugin] PRXshot 0.4.0

[pietro025]

Do you know some place where Total_Noob posts regularly? Is easy to talk with Coldbird and report bugs but i dont even have idea in how to find TN and have the security that i am gonna get feedback from him.

He usually can be found at pspking.de but it's in german, I guess.

Advertising

[shakan09]

i love this plugin. worked great on my psp 1000 with 5.00 M33-6 and its still working on 6.38 ME keep up the good work

Advertising

[tomatofarmer]

So my theory is:

*) HEN TN-D doesn't read game.txt if this file is in the ms0 and the game is in ef0 (BUG).

That does appear to be true. It's weird that it works with pops.txt in the same situation though.

*) HEN TN-D launch plugins declared in game.txt if this file is in the ms0 and the game is in ms0 (what you have discovered).

Also true.

*) HEN TN-D probably can launch plugins declared in game.txt if this file is in the ef0 (with the plugins in ef0 too) and the game is in ef0.

Ok, I see what you're saying. This is what I did to verify that:

1. Move the seplugins folder from the M2 card to internal storage (changing ms0: to ef0: in the three text files). Restarted device, enabled HEN.
- XMB (FAIL)
- Minis (FAIL)
- PSOne classics (FAIL)
- PSN PSP games (FAIL)
(all games were launched from internal storage)

I was surprised by this. I thought at least the XMB and PSOne classics would work since they had both worked before. Then I realized that he may have done something along the lines of only enabling the plugins from the storage device that the HEN was originally launched from. So..

2. Move the entire TN-D folder from the M2 card to internal storage. Restarted the device and enabled HEN from internal flash.
- XMB (FAIL)
- Minis (FAIL)
- PSOne classics (FAIL)
- PSN PSP games (FAIL)

?! What in the heck, right?

The only plugin that was enabled in the three text files in the seplugins directory of ef0: was PRXshot. (I don't have any isos on there so I removed aLoader). However if there *was* something wrong with PRXshot (and internal storage on the Go) then these results shouldn't be surprising. I looked around for a small plugin that was confirmed to work 100% with TN 6.20. The one I chose was the spoofer (changes the MAC and version number under system info). I added that to vsh.txt in the seplugins directory on ef0:. Rebooted the device, enabled HEN from internal storage and IT WORKED.

So. This means that (at the very least) vsh.txt plugins *should* work if they are placed in ef0: and HEN launched from ef0:. It also means that since we know PRXshot worked (in XMB mode) from ms0: that it *should* also work from ef0: when added to vsh.txt in the seplugins directory of internal storage. (Especially since it was the only plugin listed in vsh.txt at the time) But it didn't. This doesn't rule out the possibility that there actually is a bug with TN (and game.txt) but the XMB screenshot should have worked right? If true then that means that the problem has to be related to PRXshot?

Don't be discouraged. You are really doing great work with this plugin! I already have some future requests to help make it better but I'll wait until this issue is ironed out because I know it's probably not easy. Of course, the silver lining is that if this was easy then someone else already would have done it, so if you're up to the challenge you can claim the first 100% compatible screen shot plugin.

Do you know some place where Total_Noob posts regularly? Is easy to talk with Coldbird and report bugs but i dont even have idea in how to find TN and have the security that i am gonna get feedback from him.

Just the German site that @pietro025 mentioned. Wololo did that great interview with him and I'm sure he's familiar with the Go from the testing that went into HBL. Maybe you can help you contact him or at least pass along a few questions? Might be worth a try?

[tomatofarmer]

Hi, I'm back again with test results from TN-E Fix. One of the bugs listed in the 'Fix' release was:

Fixed loading of game/pops plugins.

I thought maybe that might apply to us so I re-did the testing for the new version.

Environment & Info:

PSP GO 6.20 TN-E Fix
Games used: Mini (Angry Birds), PSOne classic (Vagrant Story), PSP PSN game (Sega Rally)

Contents of prxshot.ini:

# To comment a line (or part of it) place a # before the text

[General]
CreatePic1 = 0
PSPGoUseMS0 = 1
XMBClearCache = 1
ScreenshotKey = 0x800000 # NOTE
ScreenshotName = %s/pic_%04d.bmp

Test 1 (log attached as prxshot-m2.zip)
plugins located at memory stick, TN-E Fix launched from memory stick

- XMB (Success)
- Mini launched from ms0: (Success)
- PSOne classic launched from ms0: (Success)
- PSP PSN game launched from ms0: (Success)
- Mini launched from ef0: (Fail)
- PSOne classic launched from ef0: (Success)
- PSP PSN game launched from ef0: (Fail)

ALL IMAGES WERE SAVED TO M2 CARD (correct behavior - honors settings in prxshot.ini)

Test 2 (log attached as prxshot-internal.zip)
plugins located at internal storage, TN-E Fix launched from internal storage

- XMB (Success)
- Mini launched from ms0: (Success)
- PSOne classic launched from ms0: (Success)
- PSP PSN game launched from ms0: (Success)
- Mini launched from ef0: (Success)
- PSOne classic launched from ef0: (Success)
- PSP PSN game launched from ef0: (Success)

ALL IMAGES WERE SAVED TO INTERNAL STORAGE (Incorrect behavior - ignores settings in prxshot.ini)

Results this time were the best so far! Only two issues remain:

Issue 1:
Cannot capture screenshots with Minis and PSN PSP games when launched from internal storage (when HEN is loaded from M2 and plugins located on M2).

Issue 2:
Screenshots were all successful when HEN is loaded from internal storage (and plugins located on internal storage) BUT the screenshots were saved in the wrong place. Setting PSPGoUseMS0 should force the creation of all screenshots onto the M2 card regardless of where the game is launched or HEN/plugins are loaded.

[thecobra]

i like this plugin, it work perfectly for my psp and it helping me take screen shot of my own project Thank you and keep on working it. maybe add a function to save the image as a png or jpeg instead of only bmp. that would be nice

[leojava]

really cool plugin!

i like this plugin, it work perfectly for my psp and it helping me take screen shot of my own project Thank you and keep on working it. maybe add a function to save the image as a png or jpeg instead of only bmp. that would be nice

really!
so we can save a bit of memory on our memorystick!

sorry for my bad english.

[codestation]

really cool plugin!

i like this plugin, it work perfectly for my psp and it helping me take screen shot of my own project Thank you and keep on working it. maybe add a function to save the image as a png or jpeg instead of only bmp. that would be nice

really!
so we can save a bit of memory on our memorystick!

sorry for my bad english.

Currently working on gif support (the encoder is very small). Not sure if i can deliver png/jpeg support seeing that the encoder is like 100-150KiB of size (+ memory allocations) because the free kernel memory is so small (less than 500KiB with zero plugins active).

[Yuin]

how to use this plugin if i want take screenshot with square + Triangle and saved images to internal memory.
pspgo 6.20 Prob5/Tn E user.thanks

[codestation]

how to use this plugin if i want take screenshot with square + Triangle and saved images to internal memory.
pspgo 6.20 Prob5/Tn E user.thanks

Try setting ScreenshotKey to 0x009000 (square + triangle). PRXshot by default saves the images to the internal memory in PSPGo so you dont have to do anything (PSPGoUseMS0 = 0).

@tomatofarmer the problem with thescreenshot location is tied to a problem in OFW. Looks like if the game/plugin is started from ef0 then the psp remaps ms0 to ef0 to its impossible to access the M2 at all in that case. I am investigating the issue to see if something can be done about that because this isn't a problem with the plugin or the CFW, its a OFW issue.

[Strangelove]

Currently working on gif support (the encoder is very small). Not sure if i can deliver png/jpeg support seeing that the encoder is like 100-150KiB of size (+ memory allocations) because the free kernel memory is so small (less than 500KiB with zero plugins active).

can't you load the module to a different kernel mem partition? and why does it need kernel mode anyway?

and if that doesn't work for some reason, there's other possibilities. i recently managed to call kernel code from user mode (needs HEN), you could go the other way too by letting a user mode module handle converting pictures. haven't tried the latter but it could be fun...