XIM Community

XIM APEX => XIM APEX Discussions => XIM Link => Topic started by: W11cE on 11:32 AM - 10/01/18

Title: XIM Link 1.3 is out
Post by: W11cE on 11:32 AM - 10/01/18
Download: https://github.com/W11cE/XIM-Link/blob/master/Official%20Releases/XIM%20Link%201.3%20Setup.msi

Changelog since 1.2:
- Rebuild profile UI bindings.
- Removed blank area on main window.
- Moved "Activation Key" and "XIM Profile Key" to main window.
- Internal changes on script handling.
- Added default profile.
- Last profile is loaded on startup.
- Window size is remembered from the last session.
- Added button to send current profile XIM Profile Key to XIM.
- Multiple scripts can be selected when assigning scripts to profiles.
- Profiles are now ordered in an alphabetical order, except default profile.
- Numlock state and shift do not affect numpad keys. The behavior is as if numlock would be on.
- Ctrl+Alt+Del combination breaks passthrough mode.
- Added startup arguments -noJoystick and -LLMovement
- Added activation processes.


I was going to do a video explaining all the changes, but thought it would take too long. I want to get the release out of the way, so I can focus on new features instead.

This one took a long time to make, the changes might not look like a lot, but the amount of code changed is much more than in any of the earlier versions. This should be so far the most stable version. v1.2 was completely broken.

Activation Processes
The big new feature is the thing I call "Activation Processes". This is supposed to emulate the way mouse and keyboard profiles are bound to PC games.

You can turn on the feature from options in inside "Profile activation processes". In most cases you would use only the "Start", but for more exotic drivers like Roccat Swarm, you also need to use the "Exit".

The modes work like this:
- "Off": completely off.
- "On, Visible": Will open the process with window visible. Meant mostly only for debugging purposes.
- "On, Hidden": Will open the process with window hidden. However the window is still brought to the foreground if Link has the foreground focus while activating the passthrough.

The executables for binding are located in the folder called ProfileProcesses in the XIM Link documents folder. "Default" is the name of the starting executable and "Exit" is the name of the exiting executable. Note that these only exist if the mode is On in the settings.

For example, for logitech you would bind you profile to "Default.exe" and you should also check box "Lock profile while game is running". Now the profile is activated every time the passthrough is enabled.

For drivers like logitech, where the profile is locked while the process is alive, this works even on the backround. This is not the case for drivers that track only the foreground focus.

Also NOTE: Some antivirus software might trigger on the executables with a warning of something like "Machine Learning". This is because these executables are automatically created, opened and closed.


Lastly, some words of the next steps I am going to work on:
- Internal rebuilding of the core features (something might break), this includes hotswap support for apex connection (this is actually already 90% done, will be in the next weekly.)
- Tray mode, this will not support any deep sleep 0% CPU mode yet, but along with the hotswap support, you can start Link automatically on PC startup and it should "just work".
- Joystick rebinding, I have a plan of the editor UI already. Have not decided yet where to put the bindings, I was thinking of the putting those in the same listbox with the scripts.
Title: Re: XIM Link 1.3 is out
Post by: Bookuvapes on 02:06 PM - 10/02/18
Got so excited seeing this update. Fixes 2 things that I had a issues with. Had to install it twice but I probably did something wrong but works now. It had my profiles still there with the key mappings still there which I found a bit odd but happy with. Will be trying it out and will give update if any issues come up. Thanks for the update and hard work.
Title: Re: XIM Link 1.3 is out
Post by: MrBrutalFrosty on 12:29 PM - 10/05/18
I had to delete the old XIM link folder unistall 1.2  but now its all running smoothly now thanks for the hard work W11cE appreaciate it.looking forward to trying out this update now! :D
Title: Re: XIM Link 1.3 is out
Post by: Tosa on 06:43 PM - 10/08/18
It was my understanding that xim was never to have macro support.
This puts you in the same boat as cronusmax
Since it's already released I'd change the name from xim link to something not xim related
That way if it does become an issue you can better distance yourself.
Title: Re: XIM Link 1.3 is out
Post by: Bookuvapes on 11:00 PM - 10/08/18
It was my understanding that xim was never to have macro support.
This puts you in the same boat as cronusmax
Since it's already released I'd change the name from xim link to something not xim related
That way if it does become an issue you can better distance yourself.

Really don't understand your post but okay.
Title: Re: XIM Link 1.3 is out
Post by: MrBrutalFrosty on 11:19 AM - 10/09/18
It was my understanding that xim was never to have macro support.
This puts you in the same boat as cronusmax
Since it's already released I'd change the name from xim link to something not xim related
That way if it does become an issue you can better distance yourself.


Itl never be a issue only people that make it one i use it for a simple fast switch between PC and console works great :D
Title: Re: XIM Link 1.3 is out
Post by: martintheninja on 03:34 PM - 10/18/18
this build doesnt crash  :D :D :D
Title: Re: XIM Link 1.3 is out
Post by: SwipeFPS on 08:19 AM - 10/21/18
Will there ever be a version that doesnít have to be connected to your pc where XIM link and XIM apex is all done through the app? Donít have a pc besides me at all times
Title: Re: XIM Link 1.3 is out
Post by: Arceye on 05:50 AM - 10/26/18
W11cE
Do you have an idea of time before the ability to use the G13 analog stick will be usable via Xim Link ?
Title: Re: XIM Link 1.3 is out
Post by: W11cE on 02:47 PM - 10/26/18
Will there ever be a version that doesnít have to be connected to your pc where XIM link and XIM apex is all done through the app? Donít have a pc besides me at all times
Could you clarify? Where would you connect your devices instead?

W11cE
Do you have an idea of time before the ability to use the G13 analog stick will be usable via Xim Link ?
It should be already usable, if you configure it to work as a joystick on the driver settings?
Title: Re: XIM Link 1.3 is out
Post by: SwipeFPS on 04:36 AM - 10/29/18
Will there ever be a version that doesnít have to be connected to your pc where XIM link and XIM apex is all done through the app? Donít have a pc besides me at all times
Could you clarify? Where would you connect your devices instead?

W11cE
Do you have an idea of time before the ability to use the G13 analog stick will be usable via Xim Link ?
It should be already usable, if you configure it to work as a joystick on the driver settings?

I know link isnít intended for scripts but would here be a version to run scripts without having your device connected to your pc just to your console through XIM manager? Sorry if what Iím saying makes no sense never messed with scripts before just looking for something new learn and play with.
Title: Re: XIM Link 1.3 is out
Post by: Arceye on 11:55 AM - 10/29/18
W11cE
Do you have an idea of time before the ability to use the G13 analog stick will be usable via Xim Link ?
Quote
It should be already usable, if you configure it to work as a joystick on the driver settings?

Nope..  I tried that before posting. It acts as if the joystick it constantly inputting when it is rested and when the joystick is pushed to the extreme it stops as if in rest position.

There is no problem with the joystick when playing a pc game, or when using directly connected to the apex.

I will put a video together if needed to show what I am probably explaining terribly.
Title: Re: XIM Link 1.3 is out
Post by: havoxxx on 12:06 PM - 10/30/18

Problem signature:
P1: XIM Link.exe
P2: 1.3.1810.428
P3: 5bd61fd0
P4: PresentationFramework
P5: 4.7.3221.0
P6: 5b886121
P7: 2b6
P8: 1f
P9: System.MissingMethodException
P10:
Title: Re: XIM Link 1.3 is out
Post by: W11cE on 08:22 PM - 10/31/18

Problem signature:
P1: XIM Link.exe
P2: 1.3.1810.428
P3: 5bd61fd0
P4: PresentationFramework
P5: 4.7.3221.0
P6: 5b886121
P7: 2b6
P8: 1f
P9: System.MissingMethodException
P10:

Could you find this from event viewer and get the full stack trace? This exception has not come on anyone else yet and can come from anywhere.
Title: Re: XIM Link 1.3 is out
Post by: Y2K on 05:02 AM - 11/01/18
getting error with the weekly build,it was running fine for past couple day .. 
(https://i.imgur.com/l6G2ow3.png)



just reformatted my pc and all working ok
Title: Re: XIM Link 1.3 is out
Post by: havoxxx on 12:26 PM - 11/03/18
full list of errors. im working on a fix.

Code: [Select]
Application: XIM Link.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.MissingMethodException
   at XIMLink.App.Application_Startup(System.Object, System.Windows.StartupEventArgs)
   at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
   at System.Windows.Application.<.ctor>b__1_0(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Application.RunDispatcher(System.Object)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at XIMLink.App.Main()
Code: [Select]

Faulting application name: XIM Link.exe, version: 1.3.1810.428, time stamp: 0x5bd61fd0
Faulting module name: KERNELBASE.dll, version: 10.0.17134.319, time stamp: 0x1e206b26
Exception code: 0xe0434352
Fault offset: 0x000000000003a388
Faulting process id: 0x6f8
Faulting application start time: 0x01d473a1711331f6
Faulting application path: C:\Program Files (x86)\W11cE\XIM Link\XIM Link.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 8c9713ff-bb22-441c-b4fa-dcc56a7f8a82
Faulting package full name:
Code: [Select]
Fault bucket 1514820950869662321, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: XIM Link.exe
P2: 1.3.1810.428
P3: 5bd61fd0
P4: PresentationFramework
P5: 4.7.3221.0
P6: 5b886121
P7: 2b6
P8: 1f
P9: System.MissingMethodException
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAD3.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER17B5.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1871.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER187F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER18CE.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_XIM Link.exe_3e16f1964cd48e30df82c16d6cdc8a3a4462841_c746be97_28f11ee7

Analysis symbol:
Rechecking for solution: 0
Report Id: 8c9713ff-bb22-441c-b4fa-dcc56a7f8a82
Report Status: 268435456
Hashed bucket: cbd7b7689373b39c1505b9a102e7da71



Code: [Select]

Version=1
EventType=CLR20r3
EventTime=131857426415925439
ReportType=2
Consent=1
UploadTime=131857426452175360
ReportStatus=268435456
ReportIdentifier=e13104cd-1604-4efc-877b-59e3c6e51863
IntegratorReportIdentifier=8c9713ff-bb22-441c-b4fa-dcc56a7f8a82
Wow64Host=34404
NsAppName=XIM Link.exe
OriginalFilename=XIM Link.exe
AppSessionGuid=000006f8-0001-000b-f631-1371a173d401
TargetAppId=W:0006b16be1af041f908377a58dabbe107daf00000000!00007f0b2ba94068de4fc12ff69e335b184353e78fde!XIM Link.exe
TargetAppVer=2018//10//28:20:45:04!0!XIM Link.exe
BootId=4294967295
TargetAsId=2069
IsFatal=1
Response.BucketId=cbd7b7689373b39c1505b9a102e7da71
Response.BucketTable=5
Response.LegacyBucketId=1514820950869662321
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=XIM Link.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=1.3.1810.428
Sig[2].Name=Problem Signature 03
Sig[2].Value=5bd61fd0
Sig[3].Name=Problem Signature 04
Sig[3].Value=PresentationFramework
Sig[4].Name=Problem Signature 05
Sig[4].Value=4.7.3221.0
Sig[5].Name=Problem Signature 06
Sig[5].Value=5b886121
Sig[6].Name=Problem Signature 07
Sig[6].Value=2b6
Sig[7].Name=Problem Signature 08
Sig[7].Value=1f
Sig[8].Name=Problem Signature 09
Sig[8].Value=System.MissingMethodException
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.17134.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=0139
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=013983862af63a23cdd2459ca623f15a
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=dc99
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=dc994145133c69e07ffa292bd9035d64
UI[2]=C:\Program Files (x86)\W11cE\XIM Link\XIM Link.exe
LoadedModule[0]=C:\Program Files (x86)\W11cE\XIM Link\XIM Link.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\Program Files\AVAST Software\Avast\x64\aswhooka.dll
LoadedModule[4]=C:\WINDOWS\System32\KERNEL32.dll
LoadedModule[5]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[6]=C:\WINDOWS\System32\ADVAPI32.dll
LoadedModule[7]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[8]=C:\WINDOWS\System32\sechost.dll
LoadedModule[9]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[10]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[11]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[12]=C:\WINDOWS\System32\combase.dll
LoadedModule[13]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[14]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[15]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[16]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[17]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[18]=C:\WINDOWS\System32\USER32.dll
LoadedModule[19]=C:\WINDOWS\System32\win32u.dll
LoadedModule[20]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[21]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[22]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[23]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
LoadedModule[24]=C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll
LoadedModule[25]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\mscorlib\a6021ef6892ab519b334a17992542017\mscorlib.ni.dll
LoadedModule[26]=C:\WINDOWS\System32\ole32.dll
LoadedModule[27]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[28]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System\8ff4bf965a60a85a0598226bf67e993a\System.ni.dll
LoadedModule[29]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Core\a21329f2cc141b0dfb57579c81b7ff38\System.Core.ni.dll
LoadedModule[30]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\WindowsBase\ce34e2f759dd46cc2fa7190f5e60724a\WindowsBase.ni.dll
LoadedModule[31]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
LoadedModule[32]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[33]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[34]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
LoadedModule[35]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\PresentationCore\464b8a3771ce7066c6d74761c5e1ea45\PresentationCore.ni.dll
LoadedModule[36]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Presentatio5ae0f00f#\a69f66e313eb69f0b6f2630aa3db7f31\PresentationFramework.ni.dll
LoadedModule[37]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Xaml\cdfeba4bfc8c7fd52fbbeb81ecb25989\System.Xaml.ni.dll
LoadedModule[38]=C:\WINDOWS\SYSTEM32\dwrite.dll
LoadedModule[39]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\wpfgfx_v0400.dll
LoadedModule[40]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[41]=C:\WINDOWS\SYSTEM32\MSVCP120_CLR0400.dll
LoadedModule[42]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\PresentationNative_v0400.dll
LoadedModule[43]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
LoadedModule[44]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Configuration\1de24cba7acec99f3c5cbdc3102f3a0d\System.Configuration.ni.dll
LoadedModule[45]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Xml\96b052a0815a6699986712bec8659f0f\System.Xml.ni.dll
LoadedModule[46]=C:\WINDOWS\System32\shell32.dll
LoadedModule[47]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[48]=C:\WINDOWS\System32\shcore.dll
LoadedModule[49]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[50]=C:\WINDOWS\System32\profapi.dll
LoadedModule[51]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[52]=C:\WINDOWS\System32\FLTLIB.DLL
LoadedModule[53]=C:\WINDOWS\system32\dwmapi.dll
LoadedModule[54]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[55]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\diasymreader.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=17134
OsInfo[3].Key=ubr
OsInfo[3].Value=376
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=244
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=9901
OsInfo[15].Key=osinsty
OsInfo[15].Value=3
OsInfo[16].Key=iever
OsInfo[16].Value=11.345.17134.0-11.0.90
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=4061
OsInfo[19].Key=svolsz
OsInfo[19].Value=464
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=180410
OsInfo[22].Key=bldtm
OsInfo[22].Value=1804
OsInfo[23].Key=bldbrch
OsInfo[23].Value=rs4_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.17134.376.amd64fre.rs4_release.180410-1804
OsInfo[30].Key=buildflightid
OsInfo[30].Value=caa372d7-ead9-4320-a97d-b237d2a5906c
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=XIMLink
AppPath=C:\Program Files (x86)\W11cE\XIM Link\XIM Link.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=DD3134D42D1453D4E555F77F82CED6B8
MetadataHash=202397364

Code: [Select]

Microsoft Windows [Version 10.0.17134.376]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>DISM.exe /Online /Cleanup-image /Restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.376

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>

Title: Re: XIM Link 1.3 is out
Post by: havoxxx on 01:33 PM - 11/03/18
fixed this. writing a tutorial.
Title: Re: XIM Link 1.3 is out
Post by: Arceye on 01:52 PM - 11/14/18
W11cE
Do you have an idea of time before the ability to use the G13 analog stick will be usable via Xim Link ?
Quote
It should be already usable, if you configure it to work as a joystick on the driver settings?

Nope..  I tried that before posting. It acts as if the joystick it constantly inputting when it is rested and when the joystick is pushed to the extreme it stops as if in rest position.

There is no problem with the joystick when playing a pc game, or when using directly connected to the apex.

I will put a video together if needed to show what I am probably explaining terribly.

W11CE:
2 video links as promised.
Video 1 Xim4 Using SandhawC G13 analog stick works correctly.
Video 1: https://photos.google.com/photo/AF1QipPv76dF2ORmdsBf0tiPuHQrI96xWSFT6dmIbjFR

Video 2 Xim Apex Using Xim Link G13 analog stick is not working, it is inside out and reversed.
Video 2: https://photos.google.com/photo/AF1QipOrQHP77xTdwhAfslfoNawC8Q_EyFzvgtzlBX8n


Edit: video deletion date.
Videos will be deleted Monday 19th November 2018
Title: Re: XIM Link 1.3 is out
Post by: W11cE on 03:27 PM - 11/15/18
The videos are deleted already, but I have G13 too, so I can check this with that.
Title: Re: XIM Link 1.3 is out
Post by: solenrus on 07:25 AM - 11/18/18
Yo, W11ce, could you bring back the ability to see what keys are being pressed in the future builds, please.
It was super helpful. Thanks!
Title: Re: XIM Link 1.3 is out
Post by: W11cE on 07:07 PM - 11/22/18
Yeah, that broke temporarily. Dont worry, it will come back.
Title: Re: XIM Link 1.3 is out
Post by: Snabel on 11:07 PM - 01/05/19
Does the xim link work with xim4? Or only with the Apex?
Title: Re: XIM Link 1.3 is out
Post by: W11cE on 12:45 PM - 01/14/19
Does the xim link work with xim4? Or only with the Apex?
Sorry no, only with the Apex.
Title: Can't launch Xim Link
Post by: Check Six on 04:27 PM - 01/18/19
 :( :( :( :(
I get an application Error when I try to start Xim 1.3. for use with my XIM Apex on my PS4
I tried to uninstall and re-install, same result.
I'm using the Plugable USB 3.0 Windows transfer cable
I've installed .NET Framework 4.7.1 and both versions of Microsoft Visual C++ Redistributable for Visual Studio 2017 on my Windows 10 (64bit).

Here is the text I get in the Windows error box:

"System. Invalid OperationException:
Sequence contains no elements at System.Linq.Enumerable.First[TSource](|Enumerable'1 source)
at XimThreading.XimWinUSB.Connect()
at XimLink.MainWindow.Window_SourceInitialized(Object sender, EventArgs e)"



From the Log Viewer:
Log Name:      Application
Source:        Application Error
Date:          18-Jan-19 17:05:01
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Ryzen-7
Description:
Faulting application name: XIM Link.exe, version: 1.3.1809.103, time stamp: 0x5ba16202
Faulting module name: KERNELBASE.dll, version: 10.0.17134.441, time stamp: 0x428de48c
Exception code: 0xe0434352
Fault offset: 0x000000000003a388
Faulting process id: 0x3fdc
Faulting application start time: 0x01d4af79d50d34ba
Faulting application path: C:\Program Files (x86)\W11cE\XIM Link\XIM Link.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 8cc17968-41f2-4987-a468-4d64f199cea4
Faulting package full name:
Faulting package-relative application ID:
Title: Applicaton error
Post by: Check Six on 04:31 PM - 01/18/19
I just realized by looking at the Event viewer that I also get a .NET Runtime error:

Log Name:      Application
Source:        .NET Runtime
Date:          18-Jan-19 17:05:00
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Ryzen-7
Description:
Application: XIM Link.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
   at System.Linq.Enumerable.First[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.Collections.Generic.IEnumerable`1<System.__Canon>)
   at XIMThreading.XimWinUSB.Connect()
   at XIMLink.MainWindow.Window_SourceInitialized(System.Object, System.EventArgs)
   at System.Windows.Window.OnSourceInitialized(System.EventArgs)
   at System.Windows.Window.CreateSourceWindow(Boolean)
   at System.Windows.Window.ShowHelper(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Application.RunDispatcher(System.Object)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at XIMLink.App.Main()

Title: Re: XIM Link 1.3 is out
Post by: yashsonu on 06:57 PM - 01/30/19
Getting this error while opening xim



System.InvalidOperationException:Sequence contains no elements
 at System.Linq.Enumerable.First(Tsource)(IEnumerable 1 source)
 at XIMThereading.XimwinUSB.connect0
 at XIMLink.MainWindow.Window_Sourcelnitialized(Object sender,EventArgs e)


Using windows 10 and has plugable usb transfer cable


Thank you

Title: Re: XIM Link 1.3 is out
Post by: W11cE on 07:25 PM - 02/12/19
Thanks for the info. It might be that windows installed wrong drivers. For some reason it is trying to connect to the cable, but is failing to find the correct info.