Author Topic: 1.7.3 : bug report [solved] (Read 5730 times)

Hollywood_315 · « **on:** November 23, 2018, 12:24:34 AM »

Hi guys, hope you are well.
Just to inform you that I get some reports from VAICOM PRO plugin users after updating to VA 1.7.3.
It appears related to joystick functions. See below, perhaps you can have a look thanks.
All the best,
Hollywood

--------

Unfortunately I'm not having good luck here. The only way I can get 1.7.3 to run is to disable plug in support. Sort of defeats the purpose. Here is the Fault text I'm getting:

11/22/2018 22:58:49***************************************************************************************
System.BadImageFormatException: Could not load file or assembly 'SharpDX.DirectInput, Version=4.1.0.0, Culture=neutral, PublicKeyToken=b4dcf0f35e5521f1' or one of its dependencies. An attempt was made to load a program with an incorrect format.
File name: 'SharpDX.DirectInput, Version=4.1.0.0, Culture=neutral, PublicKeyToken=b4dcf0f35e5521f1' ---> System.BadImageFormatException: Could not load file or assembly '0 bytes loaded from VAICOMPRO, Version=2.5.5.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.
File name: '0 bytes loaded from VAICOMPRO, Version=2.5.5.0, Culture=neutral, PublicKeyToken=null' ---> System.BadImageFormatException: Bad IL format.
at System.Reflection.RuntimeAssembly.nLoadImage(Byte[] rawAssembly, Byte[] rawSymbolStore, Evidence evidence, StackCrawlMark& stackMark, Boolean fIntrospection, Boolean fSkipIntegrityCheck, SecurityContextSource securityContextSource)
at System.Reflection.Assembly.Load(Byte[] rawAssembly)
at VAICOM.Core.AssemblyResolve(Object sender, ResolveEventArgs args)
at System.AppDomain.OnAssemblyResolveEvent(RuntimeAssembly assembly, String assemblyFullName)

at VAJS.VAJS.(Guid , Int32 )
at VAJS.VAJS.()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

Gary · « **Reply #1 on:** November 23, 2018, 01:03:25 AM »

Heya, Hollywood. Is this a widespread issue? How many users are experiencing this?

I'm not able to reproduce the problem here as it seems to be working alright with my setup, however, I did notice that .dll was compiled with the, 'Any CPU' attribute which may be the cause of the problem for some systems. Can I beg a huge favor from you and your users? Could you download this replacement file: http://voiceattack.com/filesend.aspx?id=vajs.dll and just overwrite the VAJS.dll that is located in the VA installation directory. If that fixes the issue, I will start packing it up for another release.

Hollywood_315 · « **Reply #2 on:** November 23, 2018, 02:27:35 AM »

Hi there Gary

Thanks for the fast reponse mate and of course Happy Thanksgiving

I've just had a report on my thread re 1.7.3. but it's also perhaps related to a snag in beta 1.7.2.29 that was mentioned to me earlier. Tbh I cannot reproduce it either - all seems well on my test rig here.

Tell you what let me share that link on my thread and let's see how people get on with it.
If there are more reports like this we'll find out soon enough, will keep you posted on the feedback I get.

Cheers

Hollywood_315 · « **Reply #3 on:** November 23, 2018, 06:09:58 AM »

Did a bit of additional checking to reproduce and look for clues:

With the original 1.7.3 VAJS.dll:
Turns out I cannot assign a joystick device in VA options when plugin support is enabled.
Clicking Assign1 I get this popup: JoyStick Error | unable to start joystick feature: Exception has been thrown by the target of an invocation. When plugin support is disabled (i.e. VAICOM plugin not loaded), joystick assigning works normally.

With the new vajs.dll:
When clicking Assign1 the assign window opens but no joystick device is visible.
Same result with plugin support disabled or not.
When a joystick is assigned (see above using original VAJS.dll) I see this on startup in the log when switching to the new vajs.dll:

An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information. (joysticks disabled).

Just to be complete this was not an issue previously i.e. in 1.7.2.
Hope this helps!
Grtz

Gary · « **Reply #4 on:** November 23, 2018, 08:00:13 AM »

Very, very strange - I am able to use and assign joysticks on this end with the updated VAJS.dll, with and without plugins turned on. All of my sticks are available when I click on, 'Assign 1'. Something I did notice when assigning, though, is that if a stick is assigned, it is not in the list as a choice. Can you make sure that your stick is not already assigned when you open the assign list?

In the meantime, I put a .zip out on the site to try out. It contains the VAJS.dll from 1.7.2, plus the separate supporting files. Simply unzip and place all three files into the VoiceAttack installation directory, replacing the current VAJS.dll:

http://voiceattack.com/filesend.aspx?id=vajs172.zip

Let me know if that makes a difference.

Hollywood_315 · « **Reply #5 on:** November 23, 2018, 08:17:48 AM »

Thanks I'll check that out and let you know.
Funny, I know. To check when running with plugin support are you loading vaicompro.dll?
Just to make sure this is not somehow plugin-specific. In the original bugreport there's reference to VAICOM.Core.AssemblyResolve method, which gets called directly on vaicompro plugin load.
Could be unrelated but it resolves any missing dll references.
Was there a change in 1.7.3. initialization order?
For ref plugin is compiled against .NET 4.5.2, any CPU target, VA interface v4.

Gary · « **Reply #6 on:** November 23, 2018, 08:24:43 AM »

I do not have the Vaicom plugin loaded. If you would, could you please try recompiling that dll as .Net framework 4.5 (not 4.5.2) and set the target to x86 to see if that makes a difference?

I may have had Vaicom in my last machine - I had to replace my computer this summer. I don't have it any more if I did

I'm wondering if there is some conflict with the Vaicom plugin and VAJS being loaded at the same time - there are many, many folks out there using VA's joystick features (Elite and Star Citizen) and this hasn't come up until now (the joystick feature was updated back in July). This forum as well as the Steam discussions would be lit up if this was widespread. Puzzling.

Hollywood_315 · « **Reply #7 on:** November 23, 2018, 08:49:20 AM »

No worries, I think I just tracked down the issue.

I tested with the original 1.7.3 install again and made a change in the plugin code to do with the AssemblyResolve method. Then all again good it seems. This change however will impact the plugin functioning and I would heavily prefer to avoid it if at all possible, especially since it all worked great before

What it comes down to is that the plugin tries to inadvertently solve one of VA's missing assembly references.
It will only do this if not all VA's external dll's (like the VAJS etc.) have been loaded before plugin dll loading kicks in. I'm assuming this was synchronous before and perhaps you now handle this in an asynchronous thread?

Let me know if perhaps you see an easy fix, happy to think along here.

Cheers

Gary · « **Reply #8 on:** November 23, 2018, 08:57:02 AM »

The only differences now (from 1.7.2) is that VAJS.dll now targets .Net framework 4.5 (and not 3.x), the SharpDX dlls are updated to the current version (well, current as of July) and the SharpDX dlls are now IL-merged with VAJS.dll to make a single file to manage (instead of 3). VAJS.dll hard references the SharpDX dlls.

Gary · « **Reply #9 on:** November 23, 2018, 09:04:44 AM »

I double checked source control about the loading and it looks like plugins have always been initialized prior to joystick initialization (it's all synchronous).

Hollywood_315 · « **Reply #10 on:** November 23, 2018, 09:24:49 AM »

Ok clear. It's probably the IL merge then that now somehow makes the plugin trigger the assembly resolve.
I'll have a look can probably get away with some quick code patches and publish a plugin update.
I'll have to iron out any side-effects later then, hopefully there won't be too many :-) Should be fine though.
Much appreciated the help mate, thanks again for the swift support.

Guess my hidden assumption has always been that the plugins would be last in line to initialize after all VA core functions (including joystick etc.) were already loaded.
All was working well so had no reason to even think about it. Rolling out patched plugin version now. Grtz

Vyper · « **Reply #11 on:** November 24, 2018, 01:58:16 AM »

I replaced the 3 dlls and I am still seeing this message in the log with no plugins enabled and plugin support disabled:

12:56:51 AM - An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information. (joysticks disabled)

Hollywood_315 · « **Reply #12 on:** November 24, 2018, 02:17:12 AM »

Hi there Viper please refer to this thread for updates.

https://forums.eagle.ru/showthread.php?t=198297&page=125

You need to use only the original VA 1.7.3 install without any dll changes.
Then use the latest VAICOM PRO plugin build, this is patched.

Vyper · « **Reply #13 on:** November 24, 2018, 01:13:46 PM »

I followed those instructions and I am right back to this error message when I attempt to enable the VIACOM PRO plugin:

11/24/2018 12:12:29 PM***************************************************************************************
System.BadImageFormatException: Could not load file or assembly 'SharpDX.DirectInput, Version=4.1.0.0, Culture=neutral, PublicKeyToken=b4dcf0f35e5521f1' or one of its dependencies. An attempt was made to load a program with an incorrect format.
File name: 'SharpDX.DirectInput, Version=4.1.0.0, Culture=neutral, PublicKeyToken=b4dcf0f35e5521f1' ---> System.BadImageFormatException: Could not load file or assembly '0 bytes loaded from VAICOMPRO, Version=2.5.5.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.
File name: '0 bytes loaded from VAICOMPRO, Version=2.5.5.0, Culture=neutral, PublicKeyToken=null' ---> System.BadImageFormatException: Bad IL format.
at System.Reflection.RuntimeAssembly.nLoadImage(Byte[] rawAssembly, Byte[] rawSymbolStore, Evidence evidence, StackCrawlMark& stackMark, Boolean fIntrospection, Boolean fSkipIntegrityCheck, SecurityContextSource securityContextSource)
at System.Reflection.Assembly.Load(Byte[] rawAssembly)
at VAICOM.Core.AssemblyResolve(Object sender, ResolveEventArgs args)
at System.AppDomain.OnAssemblyResolveEvent(RuntimeAssembly assembly, String assemblyFullName)

at VAJS.VAJS.(Guid , Int32 )
at VAJS.VAJS.()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

Vyper · « **Reply #14 on:** November 24, 2018, 01:32:35 PM »

I don't mean to cause offense but I am an experienced software engineer, 25+ years, so just look at this as advice...

I understand that some of the suggestions are from members that are not in the technical know and honestly I think the moderators should control those posts, especially in this forum. It is important that cohesive instructions are provided so that the software will be stable. All of this copying dlls and upgrading plugin versions only serves to complicate the issue more. Once all of it is working the capabilities are AMAZING! I wish I had the expertise to contribute code and maybe someday I will but in the meantime please consider this advice.

Thanks for your time.

Gary · « **Reply #15 on:** November 24, 2018, 02:18:05 PM »

I don't understand what it is you are explaining - Did you manage to get everything running with what was described?

Sorry for the confusion. This thread was not intended to be a tutorial, but rather is a discussion between Hollywood and myself about how to mitigate a problem stemming from Vaicom. Hollywood and I have a great rapport and don't mind discussing issues out here in the great wide open.

I appreciate your advice. In our defense of this thread tho... it IS in the, 'Issues' category and not the, 'How do I?' category, and in the grand scheme of things should only affect a very small number of users.

Vyper · « **Reply #16 on:** November 25, 2018, 11:15:51 AM »

Okay, I can accept that and maybe I can contribute usefully. ;-)

What I ended up doing was:

1. Uninstalled 1.7.3
2. Installed 1.7.2
3. Installed the version of VIACOM PRO 2.5.5
4. Ignored the update requests for both 1.7.2 and VIACOM PRO

I use CTS-Configurator for TARGET Script to program my Warthog and 3 MFDs. It makes provisions of VIACOM and currently I have PTT for COMM1 and COMM2 that successfully generates commands in VHF and UHF.

I then setup a system restore point and upgraded to 1.7.3 and the trouble started all over again. Once I restored the previous state all was well again.

Please let me know if I can do anything else to help and I would mind testing replacement DLLs and other binaries for you as well. ;-)

dreamingbadger · « **Reply #17 on:** December 09, 2018, 11:57:32 AM »

this error is back...

dreamingbadger · « **Reply #18 on:** December 09, 2018, 12:07:25 PM »

re-installing 1.7.3 from the installer seems to fix it

digitalcleaner · « **Reply #19 on:** January 18, 2019, 06:07:26 PM »

I have a similar issue at windows 10 startup here is the details:

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

************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Speech, Version=11.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.Speech, Version=11.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
at VoiceAttack.frmMain.(Object , EventArgs )
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at VoiceAttack.VABaseForm.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at VoiceAttack.frmMain.(Message& )
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)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3260.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
VoiceAttack
Assembly Version: 0.0.0.1
Win32 Version: 1.7.3
CodeBase: file:///C:/ProgramData/Microsoft/Windows/Start%20Menu/Programs/StartUp/VoiceAttack.exe
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3314.0 built by: NET472REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
LiteDB
Assembly Version: 4.0.0.0
Win32 Version: 1.7.3
CodeBase: file:///C:/ProgramData/Microsoft/Windows/Start%20Menu/Programs/StartUp/VoiceAttack.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
PresentationFramework
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.dll
----------------------------------------
WindowsBase
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
PresentationCore
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/PresentationCore/v4.0_4.0.0.0__31bf3856ad364e35/PresentationCore.dll
----------------------------------------
System.Xaml
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xaml/v4.0_4.0.0.0__b77a5c561934e089/System.Xaml.dll
----------------------------------------
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.Speech
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Speech/v4.0_4.0.0.0__31bf3856ad364e35/System.Speech.dll
----------------------------------------
System.Web
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3282.0 built by: NET472REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.7.3056.0 built by: NET472REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
{9dd5a7db-c847-40ca-8c66-215ffe45bd34}
Assembly Version: 0.0.0.0
Win32 Version: 1.7.3
CodeBase: file:///C:/ProgramData/Microsoft/Windows/Start%20Menu/Programs/StartUp/VoiceAttack.exe
----------------------------------------
Steamworks.NET
Assembly Version: 7.0.0.0
Win32 Version: 1.7.3
CodeBase: file:///C:/ProgramData/Microsoft/Windows/Start%20Menu/Programs/StartUp/VoiceAttack.exe
----------------------------------------

************** 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.

Exergist · « **Reply #20 on:** January 18, 2019, 07:21:31 PM »

IIRC the assembly Microsoft.Speech.dll should be in the VA root folder

Gary · « **Reply #21 on:** January 18, 2019, 08:34:27 PM »

Exergist is correct. You'll want to try reinstalling VA again to make sure all your files are in place.

Author Topic: 1.7.3 : bug report [solved] (Read 5730 times)

Hollywood_315

Hollywood_315

Hollywood_315

Hollywood_315

Hollywood_315

Hollywood_315

Vyper

Hollywood_315

Vyper

Vyper

Vyper

dreamingbadger

dreamingbadger

digitalcleaner