To quote from the embedded tweet: "Today I got something very special for you. I ported a pc dev menu for dying light to ps4. It is packed into an update file."
Check out a demonstration video below alongside some other tweets making rounds on Twitter today!
AW 1.00 / PS4 5.05 MEME Dying Light 1.00 PS4 Dev/Cheat Menu
Note: For those on lower PS4 Firmware it's recommendedNOT to update your PS4 console for this method, as $ony is likely to patch it very soon and then you'll be stuck with a PlayStation 4 console that can't run backup games, emulators, exploits and homebrew with no way of downgrading the PS4 once the 'temporary' method is patched.
Update: The method is now confirmed to be patched as expected!
Check out the PS4 6.20 method demo video below, and here are the tutorial steps from the description guide as follows to quote:
Add your account with games to PS4 and activated
After changing your user for see all games is unlocked
After going to account with games and wait in deactivate menu
For those unaware, here's a bit more on RetroArch (Twitter) from the official site at RetroArch.com to quote: "RetroArch is a frontend for emulators, game engines and media players.
It enables you to run classic games on a wide range of computers and consoles through its slick graphical interface. Settings are also unified so configuration is done once and for all.
RetroArch has advanced features like shaders, netplay, rewinding, next-frame response times, and more!"
...
Earlier this year we got a first look at PlayStation 4 Virtualization by @AlexAltea, and recently he shared on Twitter an experiments in PS4 emulation video from his YouTube Channel demonstrating the Orbital PS4 emulator currently in development.
He also tweeted he'll be present at this year's 35C3 event stating the following, to quote: "Flying to #35C3. I'll be around the emulation assembly, otherwise reachable @ 8180 (GSM): mostly CTFing, having tschunks and working on Orbital, my LLE PS4 emulator (sneak peek below). Happy holidays!"
And from the video's description: Experiments in PS4 emulation. Current status:
All drivers initialize correctly.
VFS is successfully loaded.
First userland application, /mini-syscore.elf, is decrypted and launched successfully.
Shortly after /SceSysAvControl.elf is launched which successfully handles system events.
Simultaneously, mini-syscore detects an issue with the HDD, which is to be expected during first-time boots, and launches /safemode.elf.
The system enters Safe Mode successfully, but gets frozen while rendering the safe mode menu.
Orbital #1: User Interface
Orbital #2: Graphical Output
Experiments in PS4 emulation. Current status: After last update, we have reimplemented large parts of the PS4 GPU graphics pipeline using Vulkan and recompiling AMD GCN bytecode into SPIR-V. This finally allows us to "see" the Safe Mode menu, booted from a PS4 5.xx kernel.
At the moment, we receive a CE-343* issue which indicates a PS4 HDD failure. This error is to be expected since we have booted the PS4 kernel without a valid HDD image.
In the future Safe Mode menu will have an important role when booting...
'Twas the night before Christmas... and following the OpenGL ES for PS4 release PlayStation 4 developer BigBoss shared OrbisGlPerf which is an OpenGL ES 2.0 Perf Sample for PS4 developers to utilize in homebrew applications and games.
git clone https://github.com/orbisdev/orbisGlPerf
cd orbisGlPerf
make
copy bin/homebrew.elf to ps4sh/bin folder or where you are executing ps4sh binary
You will need ps4sh because all is loaded from host using the last orbislinkgl.pkg look for it or make your own using code published by flatz or me
Copy content of folder assets where your homebrew.elf was copied
Before execute homebrew.elf you need ps4sh running on folder where your homebrew.elf was copied. Load orbislinkgl pkg and you will see logs in your ps4sh tool
After you see orbislink splash screen execute connect command on ps4sh
Code:
[PS4][INFO]: debugnet initialized
[PS4][INFO]: ready to have a lot of fun...
[PS4][INFO]: [PS4LINK] Server request thread UID: 0x80F4C9C0
[PS4][DEBUG]: [PS4LINK] Created ps4link_requests_sock: 7
[PS4][INFO]: [PS4LINK] Server command thread UID: 0x80F4CE40
[PS4][DEBUG]: [PS4LINK] bind to ps4link_requests_sock done
[PS4][DEBUG]: [PS4LINK]...