In development. Does it run ...? No!
Runtime and rendering part is private currently. Target is to have a standalone framework for shader reconstruction, command buffer translation and managing the GPU memory, for others to use. This project uses it to run "Linux" binaries on windows.
Yet another compatibility layer! I solely focused on the rendering part and recently started to implement the system functions to run some binaries.
It renders decently fast, the planned changes will make it almost perfect. Had to reverse engineer and try out a lot, before.
It currently doesn't support:
- multiple command buffer submits
- for loops in shader
- missing opcodes
- missing symbols
I’m happy for any help. Just hop in, system part isn't complicated.
I don't serve spaghetti only bugs.
- Vulkan SDK 1.3.268.0, minimum
- Up to date graphic drivers
(May add the Vulkan libs in Future Releases, if needed.)
For development:
- Ninja
- CMake 3.24+
- Visual Studio 2022, it's just for the build environment (uses clang-cl,c++20)
- Windows SDK 10.0.22621.0 or newer
For testing, just download the latest release and install the Vulkan SDK.
.\emulator.exe --h
.\emulator.exe --file="C:/****/eboot.bin"
If no --root is defined, it uses the folder from --file
For testing/benchmark, use --vsync=0
Update (app1): --update
.\emulator.exe --file="C:/****/eboot.bin" --update="C:/FolderWithUpdate"
It expects the undecrypted Target to be in the following format:
sce_module
sce_sys
eboot.bin
Try out input_ps4 to see if the emulator and your controller work correctly
Use boosts thread, mutex and conditions. The waits have to be alertable in order to receive fake signals from "kernel".
Project uses p7 for tracing -> Baical server.
- modules: the ps4 libraries
- core: kernel, memory etc.
- emulator.exe: (From Releases) contains the runtime and rendering
I'm using vscode, '.vscode\tasks.json' contains the config & build tasks.