Typo fixes

This commit is contained in:
Benjamin Höglinger
2018-06-30 21:22:23 +02:00
committed by GitHub
parent f1c668c7bc
commit 3576a5517f

View File

@@ -6,7 +6,7 @@ Windows kernel-mode driver emulating well-known USB game controllers.
)](https://ci.appveyor.com/project/nefarius/indicium-supra) [![Discord](https://img.shields.io/discord/346756263763378176.svg)](https://discord.gg/QTJpBX5) [![Website](https://img.shields.io/website-up-down-green-red/https/vigem.org.svg?label=ViGEm.org)](https://vigem.org/) [![PayPal Donate](https://img.shields.io/badge/paypal-donate-blue.svg)](<https://paypal.me/NefariusMaximus>) [![Support on Patreon](https://img.shields.io/badge/patreon-donate-orange.svg)](<https://www.patreon.com/nefarius>) [![GitHub followers](https://img.shields.io/github/followers/nefarius.svg?style=social&label=Follow)](https://github.com/nefarius) [![Twitter Follow](https://img.shields.io/twitter/follow/nefariusmaximus.svg?style=social&label=Follow)](https://twitter.com/nefariusmaximus)
## About
The `ViGEmBus` driver and `ViGEmClient` libraries represent the core of the Virtual Gamepad Emulation Framework (or `ViGEm` , in short). `ViGEm` aims for a 100% accurate [emulation](<https://en.wikipedia.org/wiki/Emulator>) of well-known gaming peripherals as pure software-based devices at kernel level. As it mimics "the real thing" games and other processes require no additional modification whatsoever to detect `ViGEm`-based devices (no Proxy-DLLs or API-Hooking) and simply work out of the box. The spiritual father of `ViGEm` is the (now obsolete) [Scarlett.Crush Productions Virtual Bus Driver](<https://github.com/nefarius/ScpVBus>) while it has been completely redesigned and rewritten from the ground up utilizing Microsoft`s [Kernel-Mode Driver Framework
The `ViGEmBus` driver and `ViGEmClient` libraries represent the core of the Virtual Gamepad Emulation Framework (or `ViGEm` , for short). `ViGEm` aims for a 100% accurate [emulation](<https://en.wikipedia.org/wiki/Emulator>) of well-known gaming peripherals as pure software-based devices at kernel level. As it mimics "the real thing" games and other processes require no additional modification whatsoever to detect `ViGEm`-based devices (no Proxy-DLLs or API-Hooking) and simply work out of the box. The spiritual father of `ViGEm` is the (now obsolete) [Scarlett.Crush Productions Virtual Bus Driver](<https://github.com/nefarius/ScpVBus>) while it has been completely redesigned and rewritten from the ground up utilizing Microsoft's [Kernel-Mode Driver Framework
](https://en.wikipedia.org/wiki/Kernel-Mode_Driver_Framework).
### Emulated devices
@@ -19,7 +19,7 @@ A few examples of the most common use cases for `ViGEm` are:
* You have an unsupported input device you'd like to use within games without modifying said game.
* You want the freedom to use a different controller of your choice in [PS4 Remote Play](<https://remoteplay.dl.playstation.net/remoteplay/>).
* You encountered a game not compatible with [x360ce](<https://www.x360ce.com/>).
* You want to extend the the reach of your input device (like send traffic to a different machine over a network).
* You want to extend the reach of your input device (like send traffic to a different machine over a network).
* You want to test/benchmark your game and need a replay mechanism for your user inputs.
* You want to work around player slot assignment order issues in `XInput`.
@@ -50,4 +50,4 @@ Before installing the bus driver on Windows 7 (x86 or x64) the following 3rd par
- [InputMapper](https://inputmapper.com/)
- [Oculus VR, LLC.](https://www.oculus.com/)
- [Rainway, Inc](https://rainway.io/)
- [WiimoteHook](https://forum.cemu.info/showthread.php/140-WiimoteHook-Nintendo-Wii-Remote-with-Motion-Rumble-and-Nunchuk-support)-
- [WiimoteHook](https://forum.cemu.info/showthread.php/140-WiimoteHook-Nintendo-Wii-Remote-with-Motion-Rumble-and-Nunchuk-support)