ViGEm

• 

  Update to ViGEmBus driver
  • Flarum Bot

  2
  0
  Votes
  2
  Posts
  63
  Views

  

  Originally posted by nefarius Heya, yes, I have to polish and test an added feature before I can push the next release but let's carefully assume it's going to come within the next month :slight_smile:
• 

  Installed ViGEm Bus/Drivers but how do I use it?
  • Flarum Bot

  1
  0
  Votes
  1
  Posts
  53
  Views

  No one has replied

• 

  VDX: Mapping to left or right side of DS4 touchpad
  • Flarum Bot

  2
  0
  Votes
  2
  Posts
  51
  Views

  

  Originally posted by nefarius I never planned on VDX being more than a demo and it's not really on my agenda currently, sorry.
• 

  Multiple DS3 Controllers on PC?
  • Flarum Bot

  2
  0
  Votes
  2
  Posts
  56
  Views

  

  Originally posted by nefarius It is. Well, setup is exactly the same like you did with your existing one.
• 

  Problem installing ViGem
  • Flarum Bot

  3
  0
  Votes
  3
  Posts
  66
  Views

  

  Originally posted by nefarius I think he already updated his setup as well to solve this.
• 

  Keep Both or Only One (Fireshock/ViGEm)
  • Flarum Bot

  2
  0
  Votes
  2
  Posts
  41
  Views

  

  Originally posted by nefarius @MonfGeiger#207 you don't need either of them for the DS4, except if you need support for games only reading from XInput pads.
• 

  ViGEm Installation Question
  • Flarum Bot

  3
  0
  Votes
  3
  Posts
  46
  Views

  

  Originally posted by MonfGeiger thank you nefarius, we'd be lost without you; keep up the good work
• 

  Error executing ViGem Bus
  • Flarum Bot

  5
  0
  Votes
  5
  Posts
  83
  Views

  

  Originally posted by Teejoon You have 2 different problem. The first problem with the x64 executable is that the progam can't find the ViGEm Bus Driver, I have the exact same problem when I tries to run it. I'm currently trying to figur out why the ViGEm Bud Driver doesn't seams to work. Was getting to this forum trying to get help The x86 executable seams to be dynamicly linked to the ViGEmClient.dll while the x64 executable is static linked to the ViGEmClient.lib during build time. Meaning that the x86 executable requies the dll file which you can get from compiling the source code from github and copy-pase the x86 version of ViGEmClient.dll to the folder.
• 

  UCR-xbox360ce-ViGEm pipe touchpad and guide(PS) key
  • Flarum Bot

  6
  0
  Votes
  6
  Posts
  111
  Views

  

  Originally posted by Mushroomhead_dk Its not "vigem" problem. "Vigem" is use xinput fo ps4 controller emulation and xinput you can say is xbox controller. Xbox controller has only 13 number of buttons ps4 - 14 - number 14 is touchpad click - it cannot be emulated via "x360ce" because it understands only 13 buttons. To be clear you need "vigem" can understand "vjoy" itself or can support side manufactured controllers with mapping option included. I get this way all from beginning to play Destiny via ps4 remoteplay app on my WIN10, and touchpad in this game is urgent control button - without game cannot be played, So it sad but true )))
• 

  Run-Time Check Failure #0
  • Flarum Bot

  1
  0
  Votes
  1
  Posts
  35
  Views

  No one has replied

• 

  Control PS4
  • Flarum Bot

  8
  0
  Votes
  8
  Posts
  115
  Views

  

  Originally posted by xande1337 Hello, I'm trying to setting up my notebook's keyboard and my mouse with UCR to control my ps4 through the remote play, but I'm having some problems doing that. First problem: the interception's not finding my notebook's keyboard. Second problem: after I've bind my mouse, it did not work on remote play Does anyone know a step by step solution for DS4 Emulation with UCR?
• 

  Visual Studio 2017 Support
  • Flarum Bot

  2
  0
  Votes
  2
  Posts
  42
  Views

  

  Originally posted by nefarius Thank you, indeed a valuable find! Will experiment with it a bit.
• 

  Usermode DLL and API
  • Flarum Bot

  3
  0
  Votes
  3
  Posts
  42
  Views

  

  Originally posted by DarKcyde There are no alternatives that provide the abilities that Target does. Besides complex C programming for macros, it handles HID device hiding, virtual joystick driver, and LED control of TM devices. Joystick Gremlin is the closest generic solution I think. Still no where near the abilities of the TM solution. Really the only major drawback of Target is it only works with TM devices, which isn't a problem for us folks who own those devices.
• 

  Help me pls...
  • Flarum Bot

  1
  0
  Votes
  1
  Posts
  29
  Views

  No one has replied

• 

  ViGEm and DirectInput emulation
  • Flarum Bot

  13
  0
  Votes
  13
  Posts
  212
  Views

  

  Originally posted by evilC Ooh, interesting... I am currently implementing Interception for keyboard / mouse IO, I take it that vmulti is output only? Can it synthesize input coming from a specific device, or just "synthetic" input? If so, can it synthesize input coming from a device which is not present on your system?
• 

  Error Message When Using GLOsc
  • Flarum Bot

  3
  0
  Votes
  3
  Posts
  46
  Views

  

  Originally posted by svyatogor92 For all of You struggling with "Error Initializing ViGEM". All You need to do is: Uninstall GloSC. Run PowerShell x86 (not x64 or standard) as an Admin. Enable running unsigned scripts by entering: "set-executionpolicy remotesigned". Run GloSC installer as an Administrator Installer will install GloSC and ViGem script without any problem. Hope it will help.
• 

  Switch Pro X + Suggestion for HidGuardian
  • Flarum Bot

  1
  0
  Votes
  1
  Posts
  33
  Views

  No one has replied

• 

  How exactly do i use(/build?) this?
  • Flarum Bot

  28
  0
  Votes
  28
  Posts
  704
  Views

  

  Originally posted by nefarius @QuestingHero#209 on https://vigem.org is the channel link in the top menu.
• 

  Force feedback
  • Flarum Bot

  5
  0
  Votes
  5
  Posts
  77
  Views

  

  Originally posted by nefarius Yes, with vigem\_register\_xusb\_notification
• 

  x360ce2ViGEm
  • Flarum Bot

  7
  0
  Votes
  7
  Posts
  97
  Views

  

  Originally posted by spacelime I've made a tweak to x360ce2vigem in order to auto-calibrate game controllers upon connecting. In case anyone has any use for it here's the code: int LXOffset[] = { 0,0,0,0 }; int LYOffset[] = { 0,0,0,0 }; int RXOffset[] = { 0,0,0,0 }; int RYOffset[] = { 0,0,0,0 }; bool calibrated[] = { false,false,false,false }; printf("Starting translation, close window to exit...\n"); while (true) { auto begin = high_resolution_clock::now(); for (int i = 0; i < XUSER_MAX_COUNT; i++) { ZeroMemory(&state, sizeof(XINPUT_STATE)); // The Mayflash WiiUPro adapter assigns the first connected controller to bus 4, the second to bus 0 etc.. This is to sort them properly. if (i == 0) result = XInputGetState(3, &state); if (i == 1) result = XInputGetState(0, &state); if (i == 2) result = XInputGetState(1, &state); if (i == 3) result = XInputGetState(2, &state); if (result == ERROR_SUCCESS) { vigem_target_set_vid(&targets[i], 0x1234); vigem_target_set_pid(&targets[i], 0x0001); if (VIGEM_SUCCESS(vigem_target_plugin(Xbox360Wired, &targets[i]))) { printf("Plugged in controller %d\t\t\t\t\n", targets[i].SerialNo); } // Calibrate controller if (state.Gamepad.sThumbRX != 0 && state.Gamepad.sThumbRX != 1 && !calibrated[i]) { LXOffset[i] = state.Gamepad.sThumbLX; LYOffset[i] = state.Gamepad.sThumbLY; RXOffset[i] = state.Gamepad.sThumbRX; RYOffset[i] = state.Gamepad.sThumbRY; calibrated[i] = true; } if (state.Gamepad.sThumbRX == 0 && state.Gamepad.sThumbRY == -1) calibrated[i] = false; // Assign the proper offsets if (calibrated[i]) { //LX if (LXOffset[i] < 0) { if (state.Gamepad.sThumbLX - LXOffset[i] < 32767 + LXOffset[i]) state.Gamepad.sThumbLX = state.Gamepad.sThumbLX - LXOffset[i]; else state.Gamepad.sThumbLX = 32767 + LXOffset[i]; state.Gamepad.sThumbLX = state.Gamepad.sThumbLX * (32767.0f / (32767.0f + LXOffset[i])); } if (LXOffset[i] > 0) { if (state.Gamepad.sThumbLX - LXOffset[i] > -32767 + LXOffset[i]) state.Gamepad.sThumbLX = state.Gamepad.sThumbLX - LXOffset[i]; else state.Gamepad.sThumbLX = -32767 + LXOffset[i]; state.Gamepad.sThumbLX = state.Gamepad.sThumbLX * (32767.0f / (32767.0f - LXOffset[i])); } //LY if (LYOffset[i] < 0) { if (state.Gamepad.sThumbLY - LYOffset[i] < 32767 + LYOffset[i]) state.Gamepad.sThumbLY = state.Gamepad.sThumbLY - LYOffset[i]; else state.Gamepad.sThumbLY = 32767 + LYOffset[i]; state.Gamepad.sThumbLY = state.Gamepad.sThumbLY * (32767.0f / (32767.0f + LYOffset[i])); } if (LYOffset[i] > 0) { if (state.Gamepad.sThumbLY - LYOffset[i] > -32767 + LYOffset[i]) state.Gamepad.sThumbLY = state.Gamepad.sThumbLY - LYOffset[i]; else state.Gamepad.sThumbLY = -32767 + LYOffset[i]; state.Gamepad.sThumbLY = state.Gamepad.sThumbLY * (32767.0f / (32767.0f - LYOffset[i])); } //RX if (RXOffset[i] < 0) { if (state.Gamepad.sThumbRX - RXOffset[i] < 32767 + RXOffset[i]) state.Gamepad.sThumbRX = state.Gamepad.sThumbRX - RXOffset[i]; else state.Gamepad.sThumbRX = 32767 + RXOffset[i]; state.Gamepad.sThumbRX = state.Gamepad.sThumbRX * (32767.0f / (32767.0f + RXOffset[i])); } if (RXOffset[i] > 0) { if (state.Gamepad.sThumbRX - RXOffset[i] > -32767 + RXOffset[i]) state.Gamepad.sThumbRX = state.Gamepad.sThumbRX - RXOffset[i]; else state.Gamepad.sThumbRX = -32767 + RXOffset[i]; state.Gamepad.sThumbRX = state.Gamepad.sThumbRX * (32767.0f / (32767.0f - RXOffset[i])); } //RY if (RYOffset[i] < 0) { if (state.Gamepad.sThumbRY - RYOffset[i] < 32767 + RYOffset[i]) state.Gamepad.sThumbRY = state.Gamepad.sThumbRY - RYOffset[i]; else state.Gamepad.sThumbRY = 32767 + RYOffset[i]; state.Gamepad.sThumbRY = state.Gamepad.sThumbRY * (32767.0f / (32767.0f + RYOffset[i])); } if (RYOffset[i] > 0) { if (state.Gamepad.sThumbRY - RYOffset[i] > -32767 + RYOffset[i]) state.Gamepad.sThumbRY = state.Gamepad.sThumbRY - RYOffset[i]; else state.Gamepad.sThumbRY = -32767 + RYOffset[i]; state.Gamepad.sThumbRY = state.Gamepad.sThumbRY * (32767.0f / (32767.0f - RYOffset[i])); } } vigem_xusb_submit_report(targets[i], *reinterpret_cast<XUSB_REPORT*>(&state.Gamepad)); } else { if (VIGEM_SUCCESS(vigem_target_unplug(&targets[i]))) { printf("Unplugged controller %d\t\t\t\t\n", targets[i].SerialNo); } } }`