Idk exactly how true this is or how “playable” it’s claimed to be, but this is interesting nonetheless:
Yeah but PS3 (RPCS3) is no where near playable on PS4 Linux… I doubt this would be anywhere near full FPS…
Looks like 13 or 15 FPS if you look in the bottom right of the window. Too blury to tell exactly what, but I don't think it's above 20.
Frame time also supports this rough area too as it looks like maybe 83.75ms and that would be about 12 FPS.
Ah, thought it was better but I really don't have a personal interest because my laptop can handle all of those emulators as well as Switch. But just for other people to enjoy them.
what type of files do the applo save tool use for cheats? and how about the MultiTrainer II V1.1.6.0? about what file size should they be?
Two totally different and unrelated things.
Apollo does save editing. You can see the patch sources at https://github.com/bucanero/apollo-ps4/tree/main/appdata
MultiTrainer is similar to the offline application version of ps4trainer.com, so open ps4trainer.com, select any game and press the "View code" button.
Last edited by subworx,
Apollo uses/supports save wizard codes, not sure if others as well.
In the github I linked, you can find existing cheats and take an example from them.
https://playersquared.com/forums/81...12-save-wizard-custom-quick-code-formats.html contains some basic info regarding all code types.
Does anyone know if the fan control payload or lapy's temp control application survive:
1. Reboot.
2. Shut down.
3. Or plugging the AC cable completely.
I know that it survives 1 and 2. But not sure about 3.
Thanks.
1. Reboot.
2. Shut down.
3. Or plugging the AC cable completely.
I know that it survives 1 and 2. But not sure about 3.
Thanks.
No. When you remove the power cable from the PS4 the fan threshold temperature setting is reset back to its default value of 79 degrees C.
Thank you very much for the answer! It seems that I will need to run the payload every time I load the exploit.
Edit: extra question if you do not mind answering.
In Leeful v10 host the fan control payload is defined by pl_Fanthresh.js.
In psphive it is defined by 2 files, which are pl_Fanthresh.js and pl_Fanthresh2.js.
The pl_Fanthresh2.js is similar to pl_Fanthresh.js in v10 and is called first.
The pl_Fanthresh.js in psphive is called after pl_Fanthresh2.js.
May I know what is the purpose of pl_Fanthresh.js (setfantemp()) in psphive? It seems that pl_Fanthresh2.js (pl_Fanthresh.js in v10) is enough to set the temp in Leeful v10.
Thank you.
Last edited by r5xscn,
In v10 the fan threshold payload (pl_FanThresh.js) is loaded via the same miraloader payload code (exp_loaderPL.js) that all the other payloads use which gives a popup message 'Launching Payload" before the payload is loaded.
In PS-Phive! instead of using the same miraloader payload code that gives a popup message 'Launching Payload" before the payload is loaded, it uses its own modded version of the miraloader payload code that gives a popup message 'Setting Threshold" before the payload is loaded.
In v10 :
exp_loaderPL.js = The payload loader.
pl_FanThresh.js = The payload itself.
In PS-Phive! :
pl_Fanthresh.js = The payload loader.
pl_Fanthresh2.js = The payload itself.
Similar threads
