Error loading WDP 3.7.18 build 180
-
I get this error when starting WDP. I’ve tried reinstalling but that doesnt help. What helped was going into a Training mission then leaving and then it worked. Maybe BMS 4.35.3 is using some defaults in the <callsign>.ini on pilot creation that WDP doesnt like?
----ERROR LOG----
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.InvalidCastException: Conversion from string “Loading Callsign.ini” to type ‘Integer’ is not valid. —> System.FormatException: Input string was not in a correct format.
at Microsoft.VisualBasic.CompilerServices.Conversions.ParseDouble(String Value, NumberFormatInfo NumberFormat)
at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(String Value)
— End of inner exception stack trace —
at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(String Value)
at WeaponDeliveryPlanner.clsLoadDTC.GetCallsignRadio(String fName)
at WeaponDeliveryPlanner.clsLoadDTC.LoadCallsign(String fName, Boolean Version)
at WeaponDeliveryPlanner.cntDTC.GetCampFile()
at WeaponDeliveryPlanner.fclsMain.fclsMain_Load(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Form.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 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: 4.0.0.0
Win32 Version: 4.8.4420.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dllWeaponDeliveryPlanner
Assembly Version: 3.7.18.180
Win32 Version: 3.7.18.180
CodeBase: file:///C:/Program%20Files%20(x86)/Newark/f4/Weapon_Delivery_Planner_3.7.18.180/WeaponDeliveryPlanner.exeMicrosoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dllSystem
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dllSystem.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dllSystem.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4400.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dllSystem.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dllSystem.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dllSystem.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dllSystem.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4084.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dllBMSUtils
Assembly Version: 1.6.3.44
Win32 Version: 1.6.3.44
CodeBase: file:///C:/Program%20Files%20(x86)/Newark/f4/Weapon_Delivery_Planner_3.7.18.180/BMSUtils.DLLdbwdp
Assembly Version: 1.6.0.3
Win32 Version: 1.6.0.3
CodeBase: file:///C:/Program%20Files%20(x86)/Newark/f4/Weapon_Delivery_Planner_3.7.18.180/dbwdp.DLLSystem.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4270.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dllBMSLocation
Assembly Version: 1.0.4.0
Win32 Version: 1.0.4.0
CodeBase: file:///C:/Program%20Files%20(x86)/Newark/f4/Weapon_Delivery_Planner_3.7.18.180/BMSLocation.DLLSystem.Web
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4330.0 built by: NET48REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.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.
-
@neugeniko Yup. same problem, searched the forum and did everything that people pointed out, but I still get the error Sucks because I can’t play withoud WDP.
-
Just tossing this out there, but can you remove the callsign.ini, restart BMS, then try it? Also, try to reload the C Run Libraries?
-
@icer Tried that, nothing works, it gives the same error with a newly generated Viper.ini callsing. Maybe it’s because I’m on Windows 11.
-
@thematate said in Error loading WDP 3.7.18 build 180:
@icer Tried that, nothing works, it gives the same error with a newly generated Viper.ini callsing. Maybe it’s because I’m on Windows 11.
I’m on Win 11, WDP 3.7.18 Build180 works fine so it’s likely something else… and you tried reloading the C++ runtime?
-
@icer Yeah, I also did that I reainstalled Falcon BMS twice, and WDP countless times.
-
@thematate
I’m running Win10, and U3, with WDP 3.7.18.180 and WDP is working OK for me.Maybe try reverting back to WDP 3.7.17.164 (the previous version) and see if that works? PM me if you need a zip of the previous WDP version.
Regards,
TC2 -
@tomcattwo I would highly appreciate If you could send me the previous WDP version.
-
@thematate Done in chat.
R/TC2 -
-