Weapon Delivery Planner released
-
Hey Falcas,
I get this error at startup right after I put in my callsign.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.ArgumentOutOfRangeException: InvalidArgument=Value of ‘14’ is not valid for ‘SelectedIndex’.
Parameter name: SelectedIndex
at System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
at WeaponDeliveryPlanner.cntDTC.FillSystemdata()
at WeaponDeliveryPlanner.cntDTC.Camp_TE()
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.ContainerControl.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.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
–--------------------------------------
WeaponDeliveryPlanner
Assembly Version: 3.7.0.62
Win32 Version: 3.7.0.62
CodeBase: file:///C:/Weapon%20Delivery%20Planner/WeaponDeliveryPlanner.exeMicrosoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 12.0.20806.33440 built by: FX45W81RTMREL
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.0.30319.34239 built by: FX452RTMGDR
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.0.30319.34209 built by: FX452RTMGDR
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.0.30319.34250 built by: FX452RTMGDR
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.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dllSystem.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34243 built by: FX452RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dllSystem.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
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.0.30319.34230 built by: FX452RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dllBMSUtils
Assembly Version: 1.5.5.0
Win32 Version: 1.5.5.0
CodeBase: file:///C:/Weapon%20Delivery%20Planner/BMSUtils.DLLSystem.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dllSystem.Transactions
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dllSystem.EnterpriseServices
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dllSystem.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dlldbwdp
Assembly Version: 1.4.0.0
Win32 Version: 1.4.0.0
CodeBase: file:///C:/Weapon%20Delivery%20Planner/dbwdp.DLLLzssManaged
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Weapon%20Delivery%20Planner/LzssManaged.DLLLzssNative
Assembly Version: 0.0.0.0
Win32 Version:
CodeBase: file:///C:/Weapon%20Delivery%20Planner/LzssNative.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. -
Did you try it with a clean callsign.ini?
If not, store you current callsign.ini in a save place.
Than make sure you have delete your callsign.ini from BMS.Start WDP and try again.
Gr Falcas
-
Did you try it with a clean callsign.ini?
If not, store you current callsign.ini in a save place.
Than make sure you have delete your callsign.ini from BMS.Start WDP and try again.
Gr Falcas
That did it. I got WDP working.
-
Hey Falcas,
Now that I got it working, I got a problem with Radio/Nav in the WDP. In Radio/Nav I changed Comm1 to 15, from the default 1. I also changed Comm2 to 15 from the default 1. Here’s what my Radio/Nav screen looks like after I made the changes:The problem occurs when I start Falcon. The DED shows Comm1 = 1 and Comm2 = 1. I expected it to show 15 for Comm1 and Comm2. I examined my callsign.ini with a text reader before I started Falcon and it had Comm1 = 15 and Comm2 = 15. Somehow, when Falcon starts, it changes my callsign.ini file to from Comm1=15 to Comm1 = 1 and Comm2 = 15 to Comm2 = 1.
-
@jc1:
Hey Falcas,
Now that I got it working, I got a problem with Radio/Nav in the WDP. In Radio/Nav I changed Comm1 to 15, from the default 1. I also changed Comm2 to 15 from the default 1. Here’s what my Radio/Nav screen looks like after I made the changes:The problem occurs when I start Falcon. The DED shows Comm1 = 1 and Comm2 = 1. I expected it to show 15 for Comm1 and Comm2. I examined my callsign.ini with a text reader before I started Falcon and it had Comm1 = 15 and Comm2 = 15. Somehow, when Falcon starts, it changes my callsign.ini file to from Comm1=15 to Comm1 = 1 and Comm2 = 15 to Comm2 = 1.
If the callsign.ini is fine as you discribe here, WDP did its job as it should be.
So why this happend needs to be found in the user handling the DTC in BMS itself.
Did you load the DTC when needed?Gr Falcas
-
If the callsign.ini is fine as you discribe here, WDP did its job as it should be.
So why this happend needs to be found in the user handling the DTC in BMS itself.
Did you load the DTC when needed?Gr Falcas
Looks like I didn’t load the DTC at the right time. Seems that it’s best not to have Falcon4 loaded when making changes in WDP. The procedure I use that works is:
- Make sure Falcon4 is not loaded.
- Load WDP, open TEmission, make changes in WDP, then save DTC.
- Start Falcon4, Select the TEmission and Takeoff
If there is a better procedure that works when Falcon4 is loaded, please let me know.
-
Sure there is
After you have done the things you want to do in WDP, save the DTC.
Go back to the BMS UI and load the DTC (in UI)gr Falcas
-
Falcas is correct. I open WDP while BMS is open in the 2D map with no problems…not necessary to have BMS closed.
-
Sure there is
After you have done the things you want to do in WDP, save the DTC.
Go back to the BMS UI and load the DTC (in UI)gr Falcas
That only works one time.:( If I do as you said and then end the flight but still in Falcon, but switch to WDP and make another change, save the DTC, return to Falcon, load the Falcon DTC, the change I made in WDP won’t be in the Falcon DTC. In order for the last WDP change to be effective in Falcon, I had to exit Falcon, switch to WDP, save the WDP DTC even though it was green. Then I started Falcon, loaded the TEmission, loaded the Falcon DTC, and this time the last WDP change was effected in Falcon.
To sum up, it seems that I can only make one change to WDP while I have Falcon active. If I need to make another change after I end the TEmission, I got to exit Falcon and also save the WDP DTC again, even though it was green. Then start Falcon again.
-
And yes this is the rule with falcon. Every time you end a mission you restart falcon before going for the next one.
-
Hi,
A little test version for those who are using the Kneeboard Updater tool.
Anybody that want to test this, go ahead and be so kind to report if it still has issues or not.
http://www.weapondeliveryplanner.nl/files/wdp/Weapon_Delivery_Planner_3.7.0.63.7z- Added, New feature the user can select (found under Settings) if the saved Datacard is compatible with Kneeboard Updater.
If you are reading the Datacard with a remote PC or PDA, its recommended to have this feature switched OFF.
Gr Falcas
- Added, New feature the user can select (found under Settings) if the saved Datacard is compatible with Kneeboard Updater.
-
well that was fast Falcas
downloading it now and testing it out actully here in just a second
-
Falcas i am getting this error when i run the program on windows 10. i have uninstalled .net 3.5 and 4.5 and reinstalled them and i still got what is below. can you make heads or tails of it?
it seems when i get this error it wont save anything but the data card main file. none of the pictures are saved. I am not sure about the DTC yet, i am going to go in game and see. I have closed WDP and reopened it and still the same error soon as i try to load a mission file
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at WeaponDeliveryPlanner.cntDataCard.CreateWeatherList()
at WeaponDeliveryPlanner.cntDataCard.OpenFile(String fName)
at WeaponDeliveryPlanner.cntDataCard.OpenMission()
at WeaponDeliveryPlanner.fclsMain.mnuOpenMission_Click(Object sender, EventArgs e)
at System.Windows.Forms.MenuItem.OnClick(EventArgs e)
at System.Windows.Forms.MenuItem.MenuItemData.Execute()
at System.Windows.Forms.Command.Invoke()
at System.Windows.Forms.Command.DispatchID(Int32 id)
at System.Windows.Forms.Control.WmCommand(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(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.6.96.0 built by: NETFXREL2STAGE
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
–--------------------------------------
WeaponDeliveryPlanner
Assembly Version: 3.7.0.63
Win32 Version: 3.7.0.63
CodeBase: file:///C:/Weapon%20Delivery%20Planner/WeaponDeliveryPlanner.exeMicrosoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.6.79.0 built by: NETFXREL2
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.6.79.0 built by: NETFXREL2
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.6.79.0 built by: NETFXREL2
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.6.79.0 built by: NETFXREL2
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.6.79.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dllSystem.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dllSystem.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2
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.6.79.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dllBMSUtils
Assembly Version: 1.5.5.0
Win32 Version: 1.5.5.0
CodeBase: file:///C:/Weapon%20Delivery%20Planner/BMSUtils.DLLSystem.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dllSystem.Transactions
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dllSystem.EnterpriseServices
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dllSystem.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.6.79.0 built by: NETFXREL2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dlldbwdp
Assembly Version: 1.4.0.0
Win32 Version: 1.4.0.0
CodeBase: file:///C:/Weapon%20Delivery%20Planner/dbwdp.DLLLzssManaged
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Weapon%20Delivery%20Planner/LzssManaged.DLLLzssNative
Assembly Version: 0.0.0.0
Win32 Version:
CodeBase: file:///C:/Weapon%20Delivery%20Planner/LzssNative.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>
-
And yes this is the rule with falcon. Every time you end a mission you restart falcon before going for the next one.
Shhhhh…I never do. …
-
I also don’t do this…
-
Hi,
@sirbum69:Falcas i am getting this error when i run the program on windows 10. i have uninstalled .net 3.5 and 4.5 and reinstalled them and i still got what is below. can you make heads or tails of it?
I does not make sense to start reinstalling .Net when a tool starts up fine. If you get a crash, the only thing you have to do is read what the error message is telling you.
And you don’t need to be a coder to have a clue what is going on************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at WeaponDeliveryPlanner.cntDataCard.CreateWeatherList()
at WeaponDeliveryPlanner.cntDataCard.OpenFile(String fName)
at WeaponDeliveryPlanner.cntDataCard.OpenMission()Look at the beginning of the report, “Index was outside the bounds of the array” and “at WeaponDeliveryPlanner.cntDataCard.CreateWeatherList()”
This means that WDP has a problem when creating the weather list.Any information on the mission you are using? Theater? Weather?
Gr Falcas
-
I also don’t do this…
Ditto. I restart after changing theaters but I can’t imagine restarting after each mission, especially if in MP mode with a bunch of guys connected.
-
Hi,
I does not make sense to start reinstalling .Net when a tool starts up fine. If you get a crash, the only thing you have to do is read what the error message is telling you.
And you don’t need to be a coder to have a clue what is going onLook at the beginning of the report, “Index was outside the bounds of the array” and “at WeaponDeliveryPlanner.cntDataCard.CreateWeatherList()”
This means that WDP has a problem when creating the weather list.Any information on the mission you are using? Theater? Weather?
Gr Falcas
sorry i only reinstalled .net because i had read somewhere earlier that it would take care of it.
The campain i am flying is the Korea strong campaign, weather i guess would be the weather it creates. far as i know its stock korea that comes with 4.32 BMS -
Ok, give me some time to give strong Korea a go.
So far I have not been able to reproduce any crash here.Gr Falcas
-
Hi Falcas:
I’m also having a problem installing the latest version of WDP on Windows XP SP3. I am getting the same message from the installer that others have reported…
“Installation Incomplete
The installer was interrupted before Weapon Delivery Planner 3.7.0.62 could be installed. You need to restart the installer to try again.”I have net 4.0 and the C++ 2010 redist installed.
I do not get this problem if I install WDP 3.4.
A search in google returns something about IIS6 not being configured, but I have no idea whether that applies to XP or if that is the source of the problem.
Any ideas on what the problem might be?
Thanks,
Ilmars