By Chris Leffler 1336853
#518104 I am messing around with Beta 1.1.5.0. When configuring PTT, I receive an unhandled exception error. I have isolated it down to my Delcom FS. I do not encounter this issue using the GA version of vSTARs or VRC. I have tried with no success using the FS programmed to transmit F21 or programmed as Button 1 with Joker transmitting as F21.

Any thoughts appreciated...

Code: Select allSee the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
SharpDX.SharpDXException: HRESULT: [0x8007001E], Module: [SharpDX.DirectInput], ApiCode: [DIERR_INPUTLOST/InputLost], Message: The system cannot read from the specified device.

   at SharpDX.Result.CheckError()
   at SharpDX.DirectInput.Device.GetDeviceState(Int32 arg0, IntPtr arg1)
   at SharpDX.DirectInput.CustomDevice`3.GetCurrentState(T& data)
   at SharpDX.DirectInput.CustomDevice`3.GetCurrentState()
   at cs.c()
   at cs.d(Object A_0, EventArgs A_1)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8794 (WinRelRS2.050727-8700)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
vSTARS
    Assembly Version: 1.1.5.0
    Win32 Version: 1.1.5.0
    CodeBase: file:///C:/Program%20Files%20(x86)/vSTARS/vSTARS.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8784 (WinRel.050727-8700)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8800 (WinRelRS2.050727-8800)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8784 (WinRel.050727-8700)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8784 (WinRel.050727-8700)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8784 (WinRel.050727-8700)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
protobuf-net
    Assembly Version: 2.0.0.668
    Win32 Version: 2.0.0.668
    CodeBase: file:///C:/Program%20Files%20(x86)/vSTARS/protobuf-net.DLL
----------------------------------------
j2gy4nvd
    Assembly Version: 1.1.5.0
    Win32 Version: 2.0.50727.8800 (WinRelRS2.050727-8800)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
Tao.Platform.Windows
    Assembly Version: 1.0.0.5
    Win32 Version: 1.0.0.5
    CodeBase: file:///C:/Program%20Files%20(x86)/vSTARS/Tao.Platform.Windows.DLL
----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.8795 built by: WinRel
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
Tao.OpenGl
    Assembly Version: 2.1.0.12
    Win32 Version: 2.1.0.12
    CodeBase: file:///C:/Program%20Files%20(x86)/vSTARS/Tao.OpenGl.DLL
----------------------------------------
Microsoft.DirectX.AudioVideoPlayback
    Assembly Version: 1.0.2902.0
    Win32 Version: 5.04.00.2904
    CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.DirectX.AudioVideoPlayback/1.0.2902.0__31bf3856ad364e35/Microsoft.DirectX.AudioVideoPlayback.dll
----------------------------------------
Microsoft.DirectX
    Assembly Version: 1.0.2902.0
    Win32 Version: 5.04.00.2904
    CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.DirectX/1.0.2902.0__31bf3856ad364e35/Microsoft.DirectX.dll
----------------------------------------
bevzudyc
    Assembly Version: 1.1.5.0
    Win32 Version: 2.0.50727.8800 (WinRelRS2.050727-8800)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
jsvz3sgp
    Assembly Version: 1.1.5.0
    Win32 Version: 2.0.50727.8800 (WinRelRS2.050727-8800)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Management
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8800 (WinRelRS2.050727-8800)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
gchxxbqc
    Assembly Version: 1.1.5.0
    Win32 Version: 2.0.50727.8800 (WinRelRS2.050727-8800)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
SharpDX.DirectInput
    Assembly Version: 2.5.0.0
    Win32 Version: 2.5.0
    CodeBase: file:///C:/Program%20Files%20(x86)/vSTARS/SharpDX.DirectInput.DLL
----------------------------------------
SharpDX
    Assembly Version: 2.5.0.0
    Win32 Version: 2.5.0
    CodeBase: file:///C:/Program%20Files%20(x86)/vSTARS/SharpDX.DLL
----------------------------------------
_p2q_lsa
    Assembly Version: 1.1.5.0
    Win32 Version: 2.0.50727.8800 (WinRelRS2.050727-8800)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
begfh87h
    Assembly Version: 1.1.5.0
    Win32 Version: 2.0.50727.8800 (WinRelRS2.050727-8800)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Web.Services
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8784 (WinRel.050727-8700)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll
----------------------------------------
qfludgsy
    Assembly Version: 1.1.5.0
    Win32 Version: 2.0.50727.8800 (WinRelRS2.050727-8800)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
By Chris Leffler 1336853
#518136 Yes, I have tried running as admin and without. I have tried multiple USB ports and through a USB hub on my main PC. I still do not have any luck across multiple PCs. I get a unhandled exception error on my laptop too.

I have no issues with the pedal in VRC and I just tried vPilot as well. I thought maybe I could revert back to non beta vSTARs set the PTT and have it transfer over during beta install. No luck.
By Ryan Savara 1369362
#518137 If you're using Joker, you can set it the virtual F2# key in the config file. I had to do that since the same issue occurs for me. I think the key is in the 130 range.

Ross, I think this relates back to the issue I was having with vPilot and the footswitch.
By Chris Leffler 1336853
#518139 Yeah, I have tested both using Joker to send the F2# signal. As well as changing the programming of the switch to send F2#.

I do remember having a similar issue with vPilot in the past. However, I just checked today and possibly was resolved in an update.
By Ross Carlson 887155
#518141 Chris, are you using any programming software for the foot switch? In other words, is there any software running that is reading the footswitch and translating presses of the switch into, for example, keypresses?
By Chris Leffler 1336853
#518142 I use the Delcom Setup Utility to program the device. I have tried the FS programmed in two flavors:

1. Program the device it self to output Keyboard F21.
http://prntscr.com/gsbir3

2. Program the device itself to output Joystick Button > JS Button 1. Then using Joker to send pubic PTT F21.
http://prntscr.com/gsbkhd

Neither configuration works in the Beta. Both work no issues in VRC or stable vSTARs.
By Ross Carlson 887155
#518143 Can you try NOT running the delcom software? It is not needed for vSTARS. I'm thinking maybe vSTARS and the delcom software are conflicting. Perhaps the delcom software is locking the device so that other apps can't read it.

Note that this is just a test to determine the issue ... it won't be the long-term solution.
By Chris Leffler 1336853
#518145 Sorry, I could have explained that better. The software is simply to program the output of the foot switch. It is a one time program of output. It is not running when trying to work with vSTARs. I will try to reset the foot switch to factory.

***Update*** - I factory reset the switch. It by default outputs a keyboard spacebar. I tried with the Beta to the same result. Do you not have to configure your delcom pedal to output the correct Joystick Button 1?
By Ross Carlson 887155
#518146 No, I don't have to program my pedal. When I plug it in, Windows recognizes it as a HID (Human Interface Device) with a single button. vSTARS recognizes it like any other HID (such as a joystick or yoke.) I've never even installed any Delcom programming software. That's why I'm wondering if you have the Delcom software or driver running in the background and that's preventing vSTARS from reading the device.
By Chris Leffler 1336853
#518161 Restored pedal to factory default. Restarted PC. The Delcom program utility is a run time program and I do not see it running in the background. The pedal by default outputs a keyboard 'space bar'. vSTARs still crashes when attempting to set PTT.

The model # of my pedal is 703600. https://www.delcomproducts.com/productd ... ber=703600

You can see their site references the program utility as needed to configure the device. It also lists a bunch of older pedal models... Maybe this is something newer introduced by Delcom?
By Ross Carlson 887155
#518163 Mine is part number 803651, which is among the list of part numbers that the 703600 replaces.

I read that description as not explicitly requiring that the switch be programmed ... it still says it uses the default Windows USB HID driver, so it should work fine without being programmed. You should only need the programming software if you want it to send a keystroke or a different joystick button.

Do you have any delcom-specific items listed in your add/remove programs list? I'm wondering if maybe a driver was installed when you installed the runtime programming app. Perhaps that driver has an exclusive handle on the switch and no other app can read from it.
By Ross Carlson 887155
#518175 How about in device manager? You may need to look in several different areas including game controllers, USB devices, anywhere else where the driver might show up. If you find the foot switch there, I would recommend you try uninstalling the device driver that way.

If you'd rather not uninstall the driver, then you can download the latest vSTARS beta that I just posted last night, and that should ignore any USB device that it cannot read from.

http://vstars.metacraft.com/Assets/File ... -1.1.6.exe