- C++ 58.4%
- C 36.7%
- Rust 2.2%
- HLSL 0.7%
- GLSL 0.6%
- Other 1.2%
Symmetry pass for the D3D11 backend matching the D3D12 / Vulkan
fixes. The same Lazy-mode lockup pattern was reproducible: the
worker held m_batch_shader_mutex across the slow D3DCompile, and
the main thread's first DrawBatchVertices stalled on the mutex
for the duration of one shader compile - in practice locking up
the runloop before the BIOS screen as the worker walked the
144-entry batch matrix on its first run.
# What changed
* common/d3d11/shader_cache: D3D11::ShaderCache is now thread-
safe. One internal mutex (m_shader_cache_mutex) covers the
DXBC index (unordered_map), the blob file, and the index
file. NOT held across ShaderCompiler::CompileShader, so two
threads compiling different shaders run truly in parallel.
Two threads racing to compile the same shader is harmless:
D3DCompile is deterministic on identical source so both
produce identical DXBC; the double-check under the lock
picks whichever publishes first and the loser's DXBC is
discarded.
Unlike D3D12 / Vulkan, no pipeline-cache analog is needed -
D3D11 binds individual state objects rather than monolithic
PSOs, and ID3D11Device::CreatePixelShader is documented
free-threaded by Microsoft.
* core/gpu_hw_d3d11: GetBatchPixelShader restructured. Shadergen
+ m_shader_cache.GetPixelShader (D3DCompile HLSL -> DXBC +
CreatePixelShader) now run WITHOUT m_batch_shader_mutex held.
The mutex is taken BRIEFLY at the end for the publish step -
a slot.store + race-loser detection under double-check.
Window measured in microseconds instead of the previous
50-200 ms per compile.
Race-loser handling: two threads racing to compile the same
slot both produce equivalent ID3D11PixelShader objects. The
loser's ComPtr falls out of scope at function exit and
releases its COM reference automatically; the winner's
canonical_slot ownership is the one published.
# Behaviour summary
Same shape as the D3D12 / Vulkan commits:
* Disabled: CompileShaders builds the ~20 non-batch shaders
upfront (D3D11 has no lazy non-batch path). Batch
matrix stays empty; faulted on first draw. ~200 KB
cache footprint after a session.
* Lazy: CompileShaders builds the ~20 non-batch shaders
upfront, spawns the worker to walk the 144-entry
batch matrix in the background. Gameplay starts
instantly; worker fills slots opportunistically.
~5 MB cache footprint when worker finishes.
Pre-fix this mode locked up before BIOS as the
worker held the compile mutex across each ~50-200 ms
D3DCompile call and the runloop starved on its first
DrawBatchVertices.
* Enabled: CompileShaders builds every shader upfront. ~60 s
first-run cold compile (D3DCompile is slow on the
heavier shaders); near-instant warm-cache runs
afterward. ~5 MB cache footprint immediately.
# Files touched
* src/common/d3d11/shader_cache.h: include <mutex>, add
m_shader_cache_mutex.
* src/common/d3d11/shader_cache.cpp: scope-narrow
m_shader_cache_mutex around index + file I/O in GetShaderBlob;
add the double-check + publish pattern to
CompileAndAddShaderBlob.
* src/core/gpu_hw_d3d11.cpp: move shadergen + compile out
before the publish-only m_batch_shader_mutex window in
GetBatchPixelShader; update worker-entrypoint comment to
reflect the new mutex semantics.
* src/core/gpu_hw_d3d11.h: update the two-level-sync comment on
GetBatchPixelShader and the storage-mutex comment on
m_batch_pixel_shaders to describe the publish-only window.
|
||
|---|---|---|
| CMakeModules | ||
| dep | ||
| src | ||
| .clang-format | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| CMakeLists.txt | ||
| libretro.osx.def | ||
| LICENSE | ||
| link.T | ||
| Makefile.libretro | ||
| README.md | ||
| TODO | ||
SwanStation - PlayStation 1, aka. PSX Emulator
Features | System Requirements | Disclaimers
SwanStation is a hard fork and open-source Libretro core implementation of DuckStation, which is an emulator of the Sony PlayStation(TM) console, focusing on playability, speed, and long-term maintainability. The goal is to be as accurate as possible while maintaining performance suitable for low-end devices. "Hack" options are discouraged, the default configuration should support all playable games with only some of the enhancements having compatibility issues.
A "BIOS" ROM image can be used, but is not required. You can use an image from any hardware version or region, although mismatching game regions and BIOS regions may have compatibility issues. A ROM image is not provided with the emulator for legal reasons, you should dump this from your own console using Caetla or other means. If no ROM image is provided, OpenBIOS will be used instead.
Features
SwanStation features include:
- CPU Recompiler/JIT (x86-64, armv7/AArch32 and AArch64)
- Hardware (D3D11, OpenGL, Vulkan) and software rendering
- Upscaling, texture filtering, and true colour (24-bit) in hardware renderers
- PGXP for geometry precision, texture correction, and depth buffer emulation
- Adaptive downsampling filter
- Post processing shader chains
- "Fast boot" for skipping BIOS splash/intro
- Save state support
- Supports bin/cue images, raw bin/img files, MAME CHD, single-track ECM, MDS/MDF, and unencrypted PBP formats.
- Direct booting of homebrew executables
- Direct loading of Portable Sound Format (psf) files
- Digital and analog controllers for input (rumble is forwarded to host)
- Namco GunCon lightgun support (simulated with mouse)
- NeGcon support
- Emulated CPU overclocking
- Multitap controllers (up to 8 devices)
- RetroAchievements
- Automatic loading/applying of PPF patches
System Requirements
- A CPU faster than a potato. But it needs to be x86_64, AArch32/armv7, or AArch64/ARMv8, otherwise you won't get a recompiler and it'll be slow.
- For the hardware renderers, a GPU capable of OpenGL 3.1/OpenGL ES 3.0/Direct3D 11 Feature Level 10.0 (or Vulkan 1.0) and above. So, basically anything made in 2013 or later.
Region detection and BIOS images
By default, SwanStation will emulate the region check present in the CD-ROM controller of the console. This means that when the region of the console does not match the disc, it will refuse to boot, giving a "Please insert PlayStation CD-ROM" message. SwanStation supports automatic detection disc regions, and if you set the console region to auto-detect as well, this should never be a problem.
The region checking can be disabled in the console options tab. This is the only way to play unlicensed games or homebrew which does not supply a correct region string on the disc, aside from using fastboot which skips the check entirely.
Mismatching the disc and console regions with the check disabled is supported, but may break games if they are patching the BIOS and expecting specific content.
LibCrypt protection and SBI files
A number of PAL region games use LibCrypt protection, requiring additional CD subchannel information to run properly. libcrypt not functioning usually manifests as hanging or crashing, but can sometimes affect gameplay too, depending on how the game implemented it.
For these games, make sure that the CD image and its corresponding SBI (.sbi) file have the same name and are placed in the same directory. SwanStation will automatically load the SBI file when it is found next to the CD image.
For example, if your disc image was named Spyro3.cue, you would place the SBI file in the same directory, and name it Spyro3.sbi.
Tests
- Passes amidog's CPU and GTE tests in both interpreter and recompiler modes, partial passing of CPX tests
Disclaimers
"PlayStation" and "PSX" are registered trademarks of Sony Interactive Entertainment Europe Limited. This project is not affiliated in any way with Sony Interactive Entertainment.