- Features
- Requirements
- 3rd Party Libraries
- Getting Started
- Building Mythos
- Supported Tooling
- Common Issues
-
Native Controller Support
Controller USB Bluetooth Gyro Additional Features Amazon Luna Controller ❌ ❌ ❌ Dualsense ✅ ✅ WIP Dualsense Edge ❌ ❌ ❌ Dualshock 3 ❌ ❌ ❌ Dualshock 4 ✅ ✅ ❌ Joy-Con ❌ ❌ ❌ Nintendo Switch Pro Controller ❌ ❌ ❌ Sixaxis ❌ ❌ ❌ Stadia Controller ❌ ❌ ❌ Steam Controller ❌ ❌ ❌ Xbox 360 Controller ❌ ❌ ❌ Xbox Wireless Controller ❌ ❌ ❌
- Nativate to
Mythos/scripts
and run setup. If needed the python file can also be ran manually, however submodules should be updated and initialized beforehand. - Follow any instructions provided by the setup script. Mythos' scripts will attempt to find any required programs on your system before requesting a download. Download URLs are located in the respective
setup_**.py
file in theMythos/scripts/python
directory. - Mythos should now be ready to be built and compiled.
- Build and compile Mythos using a supported compiler and build target.
- Mythos should be ready to use!
- Run cmake and select your desired configuration. Build Mythos, if the build fails see Common Issues
- The executable will be located in
Mythos/build/bin/{configuration}
.
- MSVC
- Clang
Incorrect Controller Inputs
If you have Steam installed, it's possible Steam is hijacking the controller's data and modifying it. This can be resolved 2 ways.
Steam
->Settings
->Controller
-> setEnable Steam Input for [Xbox/Switch Pro/generic] controllers
to off, for PlayStation controllers setPlayStation Controller Support
toNot Enabled
.- End Steam as a process from task manager.
CMAKE_MT-NOTFOUND
If the build failed due to CMAKE_MT-NOTFOUND
this is because CMake could not find the manifest tool. This is likely to occur when attempting to build for Windows with Clang.
On Windows when compiling with Clang-CL and not using Visual Studio, this occurs because vcvarsall.bat
has not set up the enviroment correctly, unfortunately editors like VS-Code can't set up that enviroment provided by vcvarsall.bat
. This can be resolved by solution 3 below.
On Windows this can possibly be solved by one of the following methods;
- Adding the parent directory of the manifest tool (mt.exe) to the
PATH
system enviromental variable. This should be the easiest solution. - Running vcvarsall.bat and specifying the
platform_type
, eg: x64. - Manually setting
CMAKE_MT
in a CMakeUserPresets.json file (See below). The manifest tool should be located in"C:/Program Files (x86)/Windows Kits/10/bin/{WINDOWS SDK VERSION}/{PLATFORM TYPE}"
CMakeUserPresets.json Example File
{
"version": 8,
"cmakeMinimumRequired": {
"major": 3,
"minor": 28,
"patch": 0
},
"configurePresets": [
{
"name": "user-common",
"hidden": true,
"cacheVariables": {
"CMAKE_MT": "C:/Program Files (x86)/Windows Kits/10/bin/10.0.19041.0/x64/mt.exe"
}
},
{
"name": "override-windows-clang-release-x64",
"displayName": "Override: Windows x64 Release - Clang",
"description": "Target Windows with Clang for a x64 Release build",
"inherits": [ "windows-clang-release-x64", "user-common" ]
},
{
"name": "override-windows-clang-debug-x64",
"displayName": "Override: Windows x64 Debug - Clang",
"description": "Target Windows with Clang for a x64 debug build",
"inherits": [ "windows-clang-debug-x64", "user-common" ]
},
{
"name": "override-windows-clang-dev_release-x64",
"displayName": "Override: Windows x64 Developer Release - Clang",
"description": "Target Windows with Clang for a x64 developer release build",
"inherits": [ "windows-clang-dev_release-x64", "user-common" ]
}
]
}