Weapon Delivery Planner released
-
Thanks for the info, Falcas. Have fun on vacation.
I have started work to update the .xml files for WDP to info in Mideast128. I have finished Theater.xml and Country.xml Now I am trying to figure out how to most easily update Airport.xml
A typical entry in Airport.xml looks like this:
<airport num="1514"><id>1523</id> <countryid>99</countryid> <name>Ahmed Al Jaber</name> <campid>5</campid> <objtype>1</objtype> <type>20</type> <x>1398912</x> <y>1871229</y> <z>429</z> <uhf>292500</uhf> <vhf>141500</vhf> <tcnchnl>87</tcnchnl> <tcnband>X</tcnband> <tcncallsign>32766</tcncallsign> <tcnrange>50</tcnrange> <tcntype>1</tcntype> <layout>Double16R_34_diagram</layout> <tl>150</tl> <icao>OKAJ</icao> <iata>---</iata> <rwy_0_nr>16R</rwy_0_nr> <rwy_0_thrx>1871591</rwy_0_thrx> <rwy_0_thry>1402410</rwy_0_thry> <rwy_0_cntx>1872875</rwy_0_cntx> <rwy_0_cnty>1398884</rwy_0_cnty> <rwy_0_ils>10830</rwy_0_ils> <rwy_0_crs>160</rwy_0_crs> <rwy_0_toda>7671</rwy_0_toda> <rwy_0_lda>7671</rwy_0_lda> <rwy_0_width>155</rwy_0_width> <rwy_1_nr>34L</rwy_1_nr> <rwy_1_thrx>1874046</rwy_1_thrx> <rwy_1_thry>1395666</rwy_1_thry> <rwy_1_cntx>0</rwy_1_cntx> <rwy_1_cnty>0</rwy_1_cnty> <rwy_1_ils>10858</rwy_1_ils> <rwy_1_crs>340</rwy_1_crs> <rwy_1_toda>7671</rwy_1_toda> <rwy_1_lda>7671</rwy_1_lda> <rwy_1_width>155</rwy_1_width> <rwy_2_nr>16L</rwy_2_nr> <rwy_2_thrx>1872478</rwy_2_thrx> <rwy_2_thry>1401449</rwy_2_thry> <rwy_2_cntx>1873483</rwy_2_cntx> <rwy_2_cnty>1398721</rwy_2_cnty> <rwy_2_ils>0</rwy_2_ils> <rwy_2_crs>160</rwy_2_crs> <rwy_2_toda>6027</rwy_2_toda> <rwy_2_lda>6027</rwy_2_lda> <rwy_2_width>255</rwy_2_width> <rwy_3_nr>34R</rwy_3_nr> <rwy_3_thrx>1874354</rwy_3_thrx> <rwy_3_thry>1396295</rwy_3_thry> <rwy_3_cntx>0</rwy_3_cntx> <rwy_3_cnty>0</rwy_3_cnty> <rwy_3_ils>0</rwy_3_ils> <rwy_3_crs>340</rwy_3_crs> <rwy_3_toda>6027</rwy_3_toda> <rwy_3_lda>6027</rwy_3_lda> <rwy_3_width>255</rwy_3_width></airport>
I understand what to do with Airport Num (a unique number you assign; Use the next one after the last one that was used for the last entry in Airport.XML)
ID is a unique ID that you assign, one that is not already used in Airport.xml,
CountryID (from Country.xml for YOUR Mideast128 Theater, in my case, 107 thru 113)
and Name (from MC Objectives Tab or MC Object Strings).
Get CampID from Mission Commander Objectives TabLooks like “ObjType” is the Parent Object Type (1 = Airbase, 2= Airstrip)
“Type” appears to be the subtype (for Al Minhad it is "Kangnung AB (CT3305) - it is 30th on the dropdown list
(Double Click on your airbase in the Objectives tab to see a nice presentation of all the info you will need for this part)
From Falcas’ post: this is unimportant. Just assign a 1 for Object Type and a 0 for “Type”x and y and z come from Mission Commander, Map Tab. Find your airbase on the Map, RIGHT Click on it, and select “View” from the dropdown menu…
You’ll see a RECON level view of the airbase called the Features Map, complete with Lat/Long, X/Y, and a cursor which shows x/y anyplace on the map. That means you can essentially scope out the runway thresholds and centerlines x/y values.
In that Features Map that appears, at the upper right, you will see “FalconXY” and the Lat/Long of the object (your airbase). When you put the FalconXY values into the Airports.xml format (lines 8 and 9 in the code above) you must TRANSPOSE the coordinates thus:
For Al Minhad AB, FalconXY from Mission Commander = 6039763 / 1658030. In the code they should appear as: <x>1658030</x> <y>6039763</y> I don’t know why that is, but if you don’t do it, you will not get the correct Lat/Long in WDP.However all other x/y values in the RWY portions of the Airport.xml code load as expected.
All of the radio and TACAN info and Toda and Lda values for the ILS runways can be found in MC Stations ILS Tab.
<tl>is the Transition Level (where you switch from QNH to Std Barometric Pressure. You can pick this per your theater ops or look it up. For UAE and Saudi Arabia and Kuwait, TL is typically 150 in anyh controlled airspace (Transition Altitude is FL130).
Now for the Runway info (thresholds, center, width). Mission Commander is soooo powerful!!
If you load up MC with a scenario or campaign from Mideast128, and go to the MAP tab, find the airbase on the map, RIGHT Click on it, and select VIEW from the dropdown menu, you’ll see a RECON level view of the airbase called the Features Map, complete with Lat/Long, X/Y, and a cursor which shows x/y anyplace on the map.Two ways to get the Threshold and Centerline info:
- On the Features Map, double-click on the feature (example, THR RWY08), and it will appear on the larger map. Zoom in and put your cursor in the middle of the object and get the x/y coordinates from the cursor position
Al Minhad Airbase RWY08 threshold is x=6057248 y=1656718 (as close as I could get it using the cursors). The code is <rwy_0_thrx>6057248</rwy_0_thrx> <rwy_0_thry>1656718</rwy_0_thry>
or
- Simply copy down the Offset x and Offset y position of the feature, then do the following math (Thanks and a BIG Hat Tip to Oakdesign for the following formula)
Oakdesign's Formula for Falcon X/Y: Falcon X (in feet) = (X+0.5) * 3279.98 where X is the X position of your Airbase (see picture below) Falcon Y (in feet) = (Y+0.5) * 3279.98 where X is the Y position of your Airbase (see picture below) x(feature) = Falcon X + Offset X y(feature) = Falcon Y + Offset y
Example:
Find x and y of Al Minhad Rwy 08 Threshold:I was able to get Al Minhad Airbase to show up and work properly in WDP, assigned to the Coalition team.
Here’s the code I used:
Country.xml code (Mideast128 Theater is Theater ID #15 for me):
<country num="107"><id>107</id> <name>U.S. ME128</name> <theaterid>15</theaterid></country> <country num="108"><id>108</id> <name>Coalition ME128</name> <theaterid>15</theaterid></country> <country num="109"><id>109</id> <name>IRAN ME128</name> <theaterid>15</theaterid></country> <country num="110"><id>110</id> <name>CIS ME128</name> <theaterid>15</theaterid></country> <country num="111"> <id>111</id> <name>Kuwait ME128</name> <theaterid>15</theaterid> </country> <country num="112"><id>112</id> <name>IRAQ ME128</name> <theaterid>15</theaterid></country> <country num="113"><id>113</id> <name>Saudi Arabia ME128</name> <theaterid>15</theaterid></country>
Airport.xml Code:
<airport num="1695"><id>1695</id> <countryid>108</countryid> <name>Al Minhad</name> <campid>2592</campid> <objtype>1</objtype> <type>30</type> <x>1658030</x> <y>6059763</y> <z>151</z> <uhf>225000</uhf> <vhf>145000</vhf> <tcnchnl>68</tcnchnl> <tcnband>X</tcnband> <tcncallsign>32766</tcncallsign> <tcnrange>50</tcnrange> <tcntype>1</tcntype> <layout>Single26_08_diagram</layout> <tl>140</tl> <icao>OMDM</icao> <iata>NHD</iata> <rwy_0_nr>08</rwy_0_nr> <rwy_0_thrx>6057248</rwy_0_thrx> <rwy_0_thry>1656718</rwy_0_thry> <rwy_0_cntx>6062824</rwy_0_cntx> <rwy_0_cnty>1657702</rwy_0_cnty> <rwy_0_ils>80000</rwy_0_ils> <rwy_0_crs>080</rwy_0_crs> <rwy_0_toda>9037</rwy_0_toda> <rwy_0_lda>8908</rwy_0_lda> <rwy_0_width>150</rwy_0_width> <rwy_1_nr>26</rwy_1_nr> <rwy_1_thrx>6066104</rwy_1_thrx> <rwy_1_thry>1658250</rwy_1_thry> <rwy_1_cntx>6062824</rwy_1_cntx> <rwy_1_cnty>1657702</rwy_1_cnty> <rwy_1_ils>26000</rwy_1_ils> <rwy_1_crs>260</rwy_1_crs> <rwy_1_toda>9037</rwy_1_toda> <rwy_1_lda>8918</rwy_1_lda> <rwy_1_width>150</rwy_1_width> <rwy_2_nr>0</rwy_2_nr> <rwy_2_thrx>0</rwy_2_thrx> <rwy_2_thry>0</rwy_2_thry> <rwy_2_cntx>0</rwy_2_cntx> <rwy_2_cnty>0</rwy_2_cnty> <rwy_2_ils>0</rwy_2_ils> <rwy_2_crs>0</rwy_2_crs> <rwy_2_toda>0</rwy_2_toda> <rwy_2_lda>0</rwy_2_lda> <rwy_2_width>0</rwy_2_width> <rwy_3_nr>0</rwy_3_nr> <rwy_3_thrx>0</rwy_3_thrx> <rwy_3_thry>0</rwy_3_thry> <rwy_3_cntx>0</rwy_3_cntx> <rwy_3_cnty>0</rwy_3_cnty> <rwy_3_ils>0</rwy_3_ils> <rwy_3_crs>0</rwy_3_crs> <rwy_3_toda>0</rwy_3_toda> <rwy_3_lda>0</rwy_3_lda> <rwy_3_width>0</rwy_3_width></airport>
I was able to get pretty much all I needed (except Runway width) from MC. I had to do an internet search for the ICAO and IATA but that was easily found. The <layout>info comes from the airport diagram pictures in your …\Weapons Delivery Planner\Charts folder. It’s just the filename (no file extension) of the appropriate diagram
Radio Info is from MC Station ILS Tab. Double-click on your airbase to get a nice concise presentation of all the necessary info.I’ll start going thru the Airport.xml file and converting what is there for already existing airports from other theaters to Mideast128 airports as best I can.
R/
TC2</layout></tl> -
As AFAIK the Airport,xml file is just a backup in case the information could not be retrieved from other BMS Sources. So what I know for sure stuff like frequencies/tacan are taken from the theater station+ils.dat so if the AB is listed in the station+ils.dat these are the ones shown in WDP not the ones from the Airport.xml
-
As AFAIK the Airport,xml file is just a backup in case the information could not be retrieved from other BMS Sources. So what I know for sure stuff like frequencies/tacan are taken from the theater station+ils.dat so if the AB is listed in the station+ils.dat these are the ones shown in WDP not the ones from the Airport.xml
This is why, to me anyway, a detailed manual is as important as the software application itself. Either one, without the other, becomes a mystery…
-
This is why, to me anyway, a detailed manual is as important as the software application itself. Either one, without the other, becomes a mystery…
So for example the frequency and tacan I just know that by try end error testing. Changing values for a certain AB in both files and checking which one of the changed values got taken by the application. I would have the technical knowledge to do it in a more proper way by reverse engineering just don’t want to
-
<airport num=“113”>=> Number of the airport in this XML file
<id>158</id> => Unique database ID of the airport in this database
<countryid>0</countryid> => ID of the country in the WDP database
<name>Kunsan</name> => Name of the airport
<campid>766</campid> => CampId of the Apt. Use MC, load te_new.tac and look for your Apt in the Objective tab. WDP needs this to find the airport in the BMS database
<objtype>1</objtype> => not important, just set it to “1”
<type>23</type> => not important, just set this to “0”
<x>775715.3</x> => X value of the APT in feet. Use MC, open your APT Objective
<y>1307072</y> => Y value of the APT in feet. Use MC, open your APT Objective
<z>10</z> => Apt Elevation. Use MC, On the map move the mouse cursor over the apt so a yellow infobox appears.For the following use MC, Open Objective and click on “Stations + ILS”. Alternative Stations ILS tab.
If WDP managed to read the Station+Ils file AND WDP has found the airport, these values are taken from the station+ils file to make sure you have the latest info.
But not having these values in the WDP database won’t give you any info if WDP runs on a PC where BMS or the theater is not installed.
<uhf>292300</uhf> => Tower UHF
<vhf>126500</vhf> => Tower VHF
<tcnchnl>75</tcnchnl> => TACAN Channel
<tcnband>X</tcnband> => TACAN Band
<tcncallsign>19</tcncallsign> => TACAN Callsign
<tcnrange>100</tcnrange> => TACAN Range (nm)
<tcntype>1</tcntype> => TACAN Type. For ground TCN this should be 1<layout>Kunsan_diagram</layout> => Name of the file of the airport diagram. WDP looks in the Charts/Country/Airport directory
<tl>140</tl> => Transition level for this airport (used in the ATIS)
<icao>RKJK</icao> => ICAO identifier 4 charaters. if not available use “––”
<iata>KUV</iata> => IATA identifier 3 charaters. if not available use “—”Up to 4 runways possible. Rwy_0, Rwy_1, Rwy_2, Rwy_3
<rwy_0_nr>18</rwy_0_nr> => Runway Number/Name (18L, 09R, 28.)
<rwy_0_thrx>1301868</rwy_0_thrx> => Thresshold X in Feet (optional)
<rwy_0_thry>776961.3</rwy_0_thry> => Thresshold Y in Feet (optional)
<rwy_0_cntx>1302175</rwy_0_cntx> => Center of Runway X in Feet (optional)
<rwy_0_cnty>772555.8</rwy_0_cnty> => Center of Runway X in Feet (optional)
<rwy_0_ils>11030</rwy_0_ils> => ILS Frequency for this rwy. Careful do NOT use a decimal!!! Use MC to get the freq from station+ils if possible.
<rwy_0_crs>176</rwy_0_crs> => Runways heading
<rwy_0_toda>8867</rwy_0_toda> => Takeoff distance available. Needed to do the takeoff calculation
<rwy_0_lda>8751</rwy_0_lda> => Landing distance available. (optional)
<rwy_0_width>195</rwy_0_width> => Runway width. (optional)Gr Falcas</airport>
-
Thanks Falcas! Confirms what I found thru trial and error. Your post also confirms what I found about which values to put in <x><y>(FALCONX/Y - but reversed - put X value in the <y>tag and Y value in the <x>tag) and <rwy_x_thrx>and <rwy_y_thry>(x and y values as read)
Please go back on holiday and enjoy the time off!
R/
TC2</rwy_y_thry></rwy_x_thrx></x></y></y></x> -
Hey Falcas dear. I thought you might be interested by this. This is about that old IFF and MFD thing. I load no .cam in WDP, I only use it to load a MFD set for a Hornet. See the result. Nothing dramatic of course, just in case it interests you. I know it does that, so I’m careful if I ever don’t open a cam file first.
-
I running into a strange situation. I downloaded mission commander and you know it comes as a 7-zip format. When double clicking on the downloaded file it installed a folder with the name “mission commander” which allowed access to all features. I did the same with weapon delivery and there no sign of anything being installed! same with other files like Nevada theater. What exactly is going on here why some files get installed and other files go through the same steps but nothing get installed except the 7-zip which was already there? can you help please?
-
I running into a strange situation. I downloaded mission commander and you know it comes as a 7-zip format. When double clicking on the downloaded file it installed a folder with the name “mission commander” which allowed access to all features. I did the same with weapon delivery and there no sign of anything being installed! same with other files like Nevada theater. What exactly is going on here why some files get installed and other files go through the same steps but nothing get installed except the 7-zip which was already there? can you help please?
A 7-zip file doesn’t get intalled per see as it’s an archive. It get’s unpacked or in some cases it can be packed as an self extracting archive. So mybe just try to right click on the 7-zip file and if you have 7-zip or another unarchivier programm installed you should be able to unpack the 7-zip from the context menu
-
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