Weapon Delivery Planner released
-
it worked now, can’t believe just a click away.
-
now I read the message:
although I have kuwait 128 segment or may be just kuwait is a different one?
-
now I read the message:
although I have kuwait 128 segment or may be just kuwait is a different one?
WDP has a list of theater and the only kuwait theater setup there expect it in
<location>\Add-On Kuwait\Campaign</location>
So if you wan’t to use the 128 segment you need to have to add a speperate entry for it to the WDP\Database\theater.xml file
-
My WDP install suddenly started throwing this error:
************** 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)I’ve tried all the trouble shooting I could find, deleting the callsign.ini and going with a fresh install of WDP. Neither have worked so I’m kind of at a loss.
-
Hello Fellow Pilots,
With assistance from @Icer’s, @Oakdesign’s and @Falcas’ posts above and @SpbGoro, Theater Developer for Mideast 128 Theater, I have completed developing update files to allow Mideast128 Theater to function properly in Weapons Delivery Planner, including support for all 163 airbases/airstrips in the Mideast128 Theater.The update files update stations+ils.dat in Add-On Mideast128, and the Theater.xml, Country.xml, and Airport.xml files for Weapons Data Planner\Database, add 3 new charts to Weapons Data Planner\Charts and provide the Mideast128 Map for Weapons Data Planner\Maps.
The update files and installation instructions can be found in this thread:
@Falcas, after reviewing them, please consider including them in the next update to Weapons Delivery Planner.
These Update files provide the following ID definitions in the WDP database files (based on your latest update to WDP 3.7.17.164):
a) Mideast128 Theater is defined to WDP as ID#15 (right after #14, NATO)
b) Mideast 128 Teams are ID’d to WDP as 107= U.S. ME128, 108= Coalition ME128, 109= IRAN ME128, 110= CIS ME128, 111= Kuwait ME128, 112= IRAQ ME128, 113= Saudi Arabia ME128.
c) Mideast 128 Airbases/AirStrips are ID’d to WDP as IDs #1695 (Kuwait International) through #1857 (Hendorabi AirStrip).
Thanks.Regards,
Tomcattwo -
Had a quick look at the zip file and will merge it if I have some time.
Did notice a couple of things.
- Map size is 2048, as this is a large size theater it should be 4096. (even normal size theaters run 4096, so why you picked 2048 is a big question)
- As you can see in all other maps included with WDP, you should not have any Airport icon or airport names on the map. WDP will draw these when you select this in the options.
- White map is missing.
Gr Falcas
-
Had a quick look at the zip file and will merge it if I have some time.
Did notice a couple of things.
- Map size is 2048, as this is a large size theater it should be 4096. (even normal size theaters run 4096, so why you picked 2048 is a big question)
- As you can see in all other maps included with WDP, you should not have any Airport icon or airport names on the map. WDP will draw these when you select this in the options.
- White map is missing.
Gr Falcas
Thanks Falcas.
- I originally made the map 4096x4096, but every time WDP was run, it resaved the map as 2048x2048. So, I left it at 2048x2048.
- I will see if I can fix the airport names issue on the map and include it in a revision to my update.
- I will generate a white map and include it in a revision to my update.
Regards,
TC2
-
- I originally made the map 4096x4096, but every time WDP was run, it resaved the map as 2048x2048. So, I left it at 2048x2048.
I have no clue what you mean by this, WDP does not save and overwrite the stored maps in the database.
gr Falcas
-
I have no clue what you mean by this, WDP does not save and overwrite the stored maps in the database.
gr Falcas
Thank you @Falcas. I have made all the corrections you recommended. 4096 x 4096 works as designed.
Hello Fellow Persian Gulf Pilots,
Today, I completed Revision 1.03 to the WDP Mideast128 Theater Update.You can download REVISION 1.03 here on the original thread.
Rev 1.03 (8/9/2021)
- Revised stations+ils.dat to remove UHF Approach, Ground, LSO, Ops and ATIS frequencies from all AirStrips. Airstrips now just have UHF (Tower), VHF (Tower) and TACAN functionality.
Rev 1.01 and 1.02 (8/7/2021)
- Minor modifications to installation instructions. v3 of Mideast128 Theater update did not contain the latest stations+ils.dat, which this update provides.
- Revised stations+ils.dat and Airport.xml to resolve overlap between Kish Intl VHF and another ATIS assignment. Kish is now 119.925 MHz.
Rev 1 (8/6/2021)
- Upgraded Mideast128Map.png to a higher resolution 4096 x 4096 map, and removed all airbase symbology and names from the map (WDP will add those automatically if selected by the user), and added borders between countries on the map (in black).
- Added a new Mideast128 “White Map” in 4096 x 4096 resolution, including borders of countries on the map, for use in WDP.
- Adjusted WDP database Theater.xml file to run Mideast128 Theater in 4096 x 4096 resolution.
No other files were changed.
(Thanks to @Falcas for recommending these corrections).
This will work with SpbGoro’s Mideast128_4_35_2v4 and with older versions of Mideast128 Theater.
Regards,
TC2 -
I get this error when launching wdp in bms 4.35 update 2.
Have both visual c++ and .net framework installed
Also tried deleting my callsign.ini, still nothing works!
Any suggestions please?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.4018.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dllWeaponDeliveryPlanner
Assembly Version: 3.7.17.164
Win32 Version: 3.7.17.164
CodeBase: file:///F:/Falcon%20BMS/new%20version/New%20folder/WeaponDeliveryPlanner.exeMicrosoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.8.3752.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.4001.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.4018.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.4001.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.3752.0 built by: NET48REL1
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.3752.0 built by: NET48REL1
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.3752.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.3752.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.38
Win32 Version: 1.6.3.38
CodeBase: file:///F:/Falcon%20BMS/new%20version/New%20folder/BMSUtils.DLLdbwdp
Assembly Version: 1.6.0.2
Win32 Version: 1.6.0.2
CodeBase: file:///F:/Falcon%20BMS/new%20version/New%20folder/dbwdp.DLLSystem.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
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:///F:/Falcon%20BMS/new%20version/New%20folder/BMSLocation.DLLSystem.Web
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dllLzssManaged
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///F:/Falcon%20BMS/new%20version/New%20folder/LzssManaged.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></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. -
Whats the callsign you are using in BMS? Does it contain any non standard characters?
Gesendet von meinem SM-G930F mit Tapatalk
-
Its the default callsign viper.
-
So then could you provide your User/config/viper.ini file in order to have a look on it
Gesendet von meinem SM-G930F mit Tapatalk
-
This post is deleted! -
So then could you provide your User/config/viper.ini file in order to have a look on it
Gesendet von meinem SM-G930F mit Tapatalk
[EWS]
Reqctr=1
Bingo=1
Fdbk=1
Flare Bingo=5
Chaff Bingo=5
PGM 0 Chaff BQ=3
PGM 0 Chaff BI=750
PGM 0 Chaff SQ=3
PGM 0 Chaff SI=2000
PGM 0 Flare BQ=1
PGM 0 Flare BI=0
PGM 0 Flare SQ=1
PGM 0 Flare SI=0
PGM 1 Chaff BQ=1
PGM 1 Chaff BI=750
PGM 1 Chaff SQ=3
PGM 1 Chaff SI=3000
PGM 1 Flare BQ=4
PGM 1 Flare BI=500
PGM 1 Flare SQ=2
PGM 1 Flare SI=1000
PGM 2 Chaff BQ=2
PGM 2 Chaff BI=750
PGM 2 Chaff SQ=4
PGM 2 Chaff SI=3000
PGM 2 Flare BQ=1
PGM 2 Flare BI=0
PGM 2 Flare SQ=1
PGM 2 Flare SI=0
PGM 3 Chaff BQ=2
PGM 3 Chaff BI=750
PGM 3 Chaff SQ=4
PGM 3 Chaff SI=3000
PGM 3 Flare BQ=2
PGM 3 Flare BI=750
PGM 3 Flare SQ=3
PGM 3 Flare SI=3000
PGM 4 Chaff BQ=1
PGM 4 Chaff BI=0
PGM 4 Chaff SQ=1
PGM 4 Chaff SI=0
PGM 4 Flare BQ=1
PGM 4 Flare BI=0
PGM 4 Flare SQ=1
PGM 4 Flare SI=0
PGM 5 Chaff BQ=1
PGM 5 Chaff BI=0
PGM 5 Chaff SQ=1
PGM 5 Chaff SI=0
PGM 5 Flare BQ=1
PGM 5 Flare BI=0
PGM 5 Flare SQ=1
PGM 5 Flare SI=0
[MFD]
Display0-0-0=4
Display0-0-1=6
Display0-0-2=11
Display0-0-csel=2
Display0-1-0=4
Display0-1-1=6
Display0-1-2=11
Display0-1-csel=2
Display0-2-0=5
Display0-2-1=4
Display0-2-2=11
Display0-2-csel=2
Display0-3-0=4
Display0-3-1=6
Display0-3-2=11
Display0-3-csel=2
Display0-4-0=4
Display0-4-1=6
Display0-4-2=11
Display0-4-csel=2
Display1-0-0=8
Display1-0-1=10
Display1-0-2=12
Display1-0-csel=2
Display1-1-0=8
Display1-1-1=10
Display1-1-2=12
Display1-1-csel=2
Display1-2-0=8
Display1-2-1=10
Display1-2-2=12
Display1-2-csel=1
Display1-3-0=8
Display1-3-1=10
Display1-3-2=12
Display1-3-csel=2
Display1-4-0=8
Display1-4-1=10
Display1-4-2=12
Display1-4-csel=2
Display2-0-0=0
Display2-0-1=0
Display2-0-2=0
Display2-0-csel=0
Display2-1-0=0
Display2-1-1=0
Display2-1-2=0
Display2-1-csel=0
Display2-2-0=0
Display2-2-1=0
Display2-2-2=0
Display2-2-csel=0
Display2-3-0=0
Display2-3-1=0
Display2-3-2=0
Display2-3-csel=0
Display2-4-0=0
Display2-4-1=0
Display2-4-2=0
Display2-4-csel=0
Display3-0-0=0
Display3-0-1=0
Display3-0-2=0
Display3-0-csel=0
Display3-1-0=0
Display3-1-1=0
Display3-1-2=0
Display3-1-csel=0
Display3-2-0=0
Display3-2-1=0
Display3-2-2=0
Display3-2-csel=0
Display3-3-0=0
Display3-3-1=0
Display3-3-2=0
Display3-3-csel=0
Display3-4-0=0
Display3-4-1=0
Display3-4-2=0
Display3-4-csel=0
[Bullseye]
BullseyeInfoOnMFD=1
[IFF]
Mode1 On=0
Mode2 On=0
Mode3A On=0
Mode4 On=0
ModeC On=0
ModeS On=0
Mode1 Code=00
Mode2 Code=0000
Mode3A Code=1200
Mode4 Key=1
AutoChange=0
TIME 0 Mode1 Code=00
TIME 0 Mode3A Code=1200
TIME 0 Mode4 Key=1
TIME 0 Criteria=-1
TIME 1 Mode1 Code=00
TIME 1 Mode3A Code=1200
TIME 1 Mode4 Key=1
TIME 1 Criteria=-1
TIME 2 Mode1 Code=00
TIME 2 Mode3A Code=1200
TIME 2 Mode4 Key=1
TIME 2 Criteria=-1
TIME 3 Mode1 Code=00
TIME 3 Mode3A Code=1200
TIME 3 Mode4 Key=1
TIME 3 Criteria=-1
TIME 4 Mode1 Code=00
TIME 4 Mode3A Code=1200
TIME 4 Mode4 Key=1
TIME 4 Criteria=-1
TIME 5 Mode1 Code=00
TIME 5 Mode3A Code=1200
TIME 5 Mode4 Key=1
TIME 5 Criteria=-1
TIME 6 Mode1 Code=00
TIME 6 Mode3A Code=1200
TIME 6 Mode4 Key=1
TIME 6 Criteria=-1
TIME 7 Mode1 Code=00
TIME 7 Mode3A Code=1200
TIME 7 Mode4 Key=1
TIME 7 Criteria=-1
TIME 8 Mode1 Code=00
TIME 8 Mode3A Code=1200
TIME 8 Mode4 Key=1
TIME 8 Criteria=-1
TIME 9 Mode1 Code=00
TIME 9 Mode3A Code=1200
TIME 9 Mode4 Key=1
TIME 9 Criteria=-1
TIME 10 Mode1 Code=00
TIME 10 Mode3A Code=1200
TIME 10 Mode4 Key=1
TIME 10 Criteria=-1
TIME 11 Mode1 Code=00
TIME 11 Mode3A Code=1200
TIME 11 Mode4 Key=1
TIME 11 Criteria=-1
POS 0 Mode1=0
POS 0 Mode2=0
POS 0 Mode3A=0
POS 0 Mode4=0
POS 0 ModeC=0
POS 0 ModeS=0
POS 0 WayPoint= 0
POS 0 Direction=0
POS 1 Mode1=0
POS 1 Mode2=0
POS 1 Mode3A=0
POS 1 Mode4=0
POS 1 ModeC=0
POS 1 ModeS=0
POS 1 WayPoint= 0
POS 1 Direction=0 -
I guess the 2nd line from the bottom has the issue:
POS 1 WayPoint= 0
Here it fails to parse ’ 0’ to an integer.
Try to remove the space:
POS 1 WayPoint=0After that it should be able to parse ‘0’ to an integer.
-
Hi,
I am receiving this msg
“Unable to load DLL ‘LzssNative.dll’. The specified module could not be found. (Exception from HRESULT : 0x800700E).” And then it asks to Quit . Help needed to rectify the issue.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.DllNotFoundException: Unable to load DLL ‘LzssNative.dll’: The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at Lzss.NativeMethods.LZSS_Expand(IntPtr compressedDataBuffer, IntPtr decompressedDataBuffer, Int32 decompressedDataSize)
at Lzss.Codec.Decompress(Byte[] compressedDataBuffer, Int32 compressedDataBufferStartingOffset, Byte[] decompressedDataBuffer, Int32 decompressedDataStartingOffset, Int32 decompressedDataLength)
at Lzss.Codec.Decompress(Byte[] toDecompress, Int32 uncompressedDataSize)
at MissionCommander.fclsMain.SortFiles()
at MissionCommander.fclsMain.LoadTE()
at MissionCommander.fclsMain.OpenFile(String fName)
at MissionCommander.fclsMain.OpenFile()
at MissionCommander.fclsMain.mnuOpenMission_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.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.4400.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
–--------------------------------------
Mission Commander
Assembly Version: 0.5.18.615
Win32 Version: 0.5.18.615
CodeBase: file:///D:/Mission_Commander_0.5.18.615/Mission%20Commander.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.40
Win32 Version: 1.6.3.40
CodeBase: file:///D:/Mission_Commander_0.5.18.615/BMSUtils.DLLdbwdp
Assembly Version: 1.6.0.2
Win32 Version: 1.6.0.2
CodeBase: file:///D:/Mission_Commander_0.5.18.615/dbwdp.DLLBMSLocation
Assembly Version: 1.0.4.0
Win32 Version: 1.0.4.0
CodeBase: file:///D:/Mission_Commander_0.5.18.615/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.dllLzssManaged
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/Mission_Commander_0.5.18.615/LzssManaged.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></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. -
I guess the 2nd line from the bottom has the issue:
POS 1 WayPoint= 0
Here it fails to parse ’ 0’ to an integer.
Try to remove the space:
POS 1 WayPoint=0After that it should be able to parse ‘0’ to an integer.
Thanks a lot. It’s working now.
-
This post is deleted! -
Had the same problem too.
If you have mission commander, try copying the “LzssNative.dll” file from its folder and put it in the wdp folder and replace it.
This worked for me.