Tyler Wilding
1f6438e517
This PR updates to SDL3, and with it, adds a handful of new features. Everything seems to work but I'm going to look over the code once last time before merging, some of the API changes are hard to spot. Fixes #2773 ### Pressure sensitivity support for DS3 Controllers SDL3 adds pressure sensitivity support for DS3 controllers on windows. I have not tested on linux. The option is disabled by default. On windows you will need https://docs.nefarius.at/projects/DsHidMini/ and to be using SXS mode. ### DualSense and Xbox One Trigger Effects If enabled, Jak 2 will have certain trigger effects. They are: - xbox1: - small vibrate when collecting dark eco - big vibrate when changing to dark jak - vibrate when shooting gun, proportional to gun type - ps5: - resistance when changing to dark jak - different gun shooting effects - red (resistance) - yellow (weapon trigger) - blue (vibrates) - purple (less resistance) > **Gun Shooting effects are only enabled if the new "Swap R1 and R2" option is enabled** There are more effects that could be used in `dualsense_effects.cpp`, but I only exposed the ones I needed to OpenGOAL. If a modder wants to use some of the others and wires them up end-to-end, please consider contributing that upstream. ### New ImGUI Menu Added new imgui options for selecting the active controller, for those people that struggle to select the initial controller.  ### Testing The highlights of what I tested successfully: - display - [x] all mode switch permutations - [x] launch with all modes saved - [x] switch monitors / unplug monitor that was active, how does it handle it - [x] load with alternate monitor saved and all modes - [x] allowing hidpi doesnt break macos - controls - [x] keyboard and mouse still work - [x] pressure sensitivity on linux
2.0 KiB
Vendored
Generated
Porting
-
Porting To A New Platform
The first thing you have to do when porting to a new platform, is look at include/SDL_platform.h and create an entry there for your operating system. The standard format is "SDL_PLATFORM_X", where X is the name of the OS. Ideally SDL_platform_defines.h will be able to auto-detect the system it's building on based on C preprocessor symbols.
There are two basic ways of building SDL at the moment:
-
CMake: cmake -S . -B build && cmake --build build && cmake --install install
If you have a system that supports CMake, then you might try this. Edit CMakeLists.txt,
take a look at the large section labelled:
"Platform-specific options and settings!"
Add a section for your platform, and then re-run 'cmake -S . -B build' and build!
-
Using an IDE:
If you're using an IDE or other non-configure build system, you'll probably want to create a custom
SDL_build_config.hfor your platform. Editinclude/build_config/SDL_build_config.h, add a section for your platform, and create a customSDL_build_config_{platform}.h, based onSDL_build_config_minimal.handSDL_build_config.h.cmakeAdd the top level include directory to the header search path, and then add the following sources to the project:
src/.c src/atomic/.c src/audio/.c src/cpuinfo/.c src/events/.c src/file/.c src/haptic/.c src/joystick/.c src/power/.c src/render/.c src/render/software/.c src/stdlib/.c src/thread/.c src/timer/.c src/video/.c src/audio/disk/.c src/audio/dummy/.c src/filesystem/dummy/.c src/video/dummy/.c src/haptic/dummy/.c src/joystick/dummy/.c src/thread/generic/.c src/timer/dummy/.c src/loadso/dummy/.c
Once you have a working library without any drivers, you can go back to each of the major subsystems and start implementing drivers for your platform.
If you have any questions, don't hesitate to ask on the SDL mailing list: http://www.libsdl.org/mailing-list.php
Enjoy! Sam Lantinga (slouken@libsdl.org)