Weapon Delivery Planner released
-
Hi,
This is very normal. US is a guest of ROK, you will find your flight under ROK.
Has been explained already in this thread.Gr Falcas
-
Hi all,
New version of WDP has been released.
Latest version is 3.6.5Changelog:
https://www.benchmarksims.org/forum/showthread.php?5293-Weapon-Delivery-PlannerEnjoy,
Falcas
-
@jc1:
Hi Falcas,
I used your latest WDP v3.6.4.0. So I tried again and had two different outcomes. The first outcome leads to a blank datacard and I exited WDP. The second outcome leads to a successful datacard, but I had messages along the way. I will detail for you all the steps I took for outcome 1 and outcome 2.
Outcome 1:
Start BMS with Korea Theatre
Select Battle for Balkans Theatre
Exit BMS
Start WDP and get a msgClick OK
Get an error msgDetails of above error msg:
Click Continue
WDP opens with “Balkans” Theatre
Click File
Get e msgClick OK
Get error msgDetails of error msg
Continue
Get a blank datacard
Exit WDP
–---------------------------------------------
Now for the second outcome. I almost exited WDP after the first messge of this outcome, but I went all the way and got a good datacard.
Start BMS with Battle for Balkans Theatre
Switch to Korea Theatre
Exit BMS
Start WDP
Get a msgClick OK
WDP opens with Balkans Theatre ( Note: not the Battle for Balkans Theater)
Click File
Select my .tac file Battle for Balkans
Get a msgClick yes
Then I got a choice of which side to fly, made a choice, continued and got a good datacard.I hope these details of my experience with WDP, a fun program, will shed some light on why some error messages pop up. It seems that the second outcome is the correct way to do it. This leads me to believe that before you open WDP, you must have previously exited BMS with the Korea Theatre, not some other theater. Is that right? Did my detailed outcomes show anything that I did incorrectly?
Your new version 3.6.5 released today fixed this. Thank you. Thank you.:D
-
how can it work with IKAROS THEATER??? any info thanks!!
-
how can it work with IKAROS THEATER??? any info thanks!!
It worked for me. Are you having any specific problems?
-
work now!!! ok!!!
-
they dont have IKAROS MAP
WDP 3.6.5 is showing the IKAROS Map for me. Are you using the latest version?
-
I have successfully installed WDP 3.6.5.14 on a PC networked to my Falcon 4 PC. The networked PC with WDP does not have BMS installed on it. I have done this with older WDP versions in order to load my Callsign.ini file for campaign missions from the networked PC. I can not now load the WDP program, because the initial screen asks for my callsign, which it can not then find on the networked PC. The callsign text box will not accept the path to the Falcon BMS PC Callsign.ini file nor allow the program to load without a valid callsign found on the networked PC. Is there a way to overcome this impediment and get to the program where I can direct WDP to the correct .ini file and Falcon BMS Launcher file??
-
Update: After rebooting networked WDP PC, I was able to fully load WDP and settings show correct paths to the BMS files. However, when I attempt to load a mission, I get Unhandled Exception error:
************** Exception Text **************
System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
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 WeaponDeliveryPlanner.fclsMain.GetTheater()
at WeaponDeliveryPlanner.fclsMain.LoadTE()
at WeaponDeliveryPlanner.cntDataCard.OpenFile(String FileName)
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.0.30319.18444 built by: FX451RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
–--------------------------------------
WeaponDeliveryPlanner
Assembly Version: 3.6.5.14
Win32 Version: 3.6.5.14
CodeBase: file:///D:/Game%20Data/WDP/WeaponDeliveryPlanner.exeMicrosoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 11.0.50938.18408 built by: FX451RTMGREL
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.34238 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.18408 built by: FX451RTMGREL
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.18408 built by: FX451RTMGREL
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.18408 built by: FX451RTMGREL
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.34108 built by: FX45W81RTMGDR
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.18408 built by: FX451RTMGREL
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.34234 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.2.0
Win32 Version: 1.5.2.0
CodeBase: file:///D:/Game%20Data/WDP/BMSUtils.DLLSystem.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
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.18408 built by: FX451RTMGREL
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.18408 built by: FX451RTMGREL
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.18408 built by: FX451RTMGREL
CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dllDatabase
Assembly Version: 1.3.0.0
Win32 Version: 1.3.0.0
CodeBase: file:///D:/Game%20Data/WDP/Database.DLLLzssManaged
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/Game%20Data/WDP/LzssManaged.DLL -
I used to do the same with the previous versions of wdp, shame if it can’t be done anymore, it used to be very handy on the second monitor.
Sabre.
-
Installed 3.6.5 and having some issues using with Korea 80’s theater in a campaign.
Gives me some errors that I click continue, but doesn’t seem to be able to AUTOPPT.
Should I be able to use with Korea 80’s?
Great & invaluable tool Falcas
Cheers
-
Hello Falcas.
After a long time I return to the Falcon. and thus the Weapon Delivery Planner and Mission Commander. I have seen, a minimum bug, silly, and I’ll indicated in catches. As they say, a picture is worth more than a thousand words.
Cheers
Toquemao -
Installed 3.6.5 and having some issues using with Korea 80’s theater in a campaign.
Gives me some errors that I click continue, but doesn’t seem to be able to AUTOPPT.
Should I be able to use with Korea 80’s?
Great & invaluable tool Falcas
Cheers
Sure you can use it with the 80s theater as well as with any theater.
But what is more important, what error are you getting?Gr Falcas
-
Hello Falcas.
After a long time I return to the Falcon. and thus the Weapon Delivery Planner and Mission Commander. I have seen, a minimum bug, silly, and I’ll indicated in catches. As they say, a picture is worth more than a thousand words.
Cheers
ToquemaoHi Toquemao,
That is normal. Not all airports have an IATA 3 letter code.
In that case you will see 3x “-”.Gr Falcas
-
Small issue:
AB and MIL climb data and calculated cruise data blocks on Performance page are not undated to reflect loadout (drag index) until cruise selection (radio buttons) are changed. This applies in “free calculate” mode when no flight is loaded.
-
Did you ever find a workaround for this? I reverted back to v3.63 for the very same issue. I’m more curious as to why, more than anything.
v3.63 works really well for what I use it for. Falcas has done a superb job with WDP, I feel like I’m complaining about the the color of a cup holder while sitting in a Porsche:D -
I have successfully installed WDP 3.6.5.14 on a PC networked to my Falcon 4 PC. The networked PC with WDP does not have BMS installed on it. I have done this with older WDP versions in order to load my Callsign.ini file for campaign missions from the networked PC. I can not now load the WDP program, because the initial screen asks for my callsign, which it can not then find on the networked PC. The callsign text box will not accept the path to the Falcon BMS PC Callsign.ini file nor allow the program to load without a valid callsign found on the networked PC. Is there a way to overcome this impediment and get to the program where I can direct WDP to the correct .ini file and Falcon BMS Launcher file??
Did you ever find a workaround for this? I reverted back to v3.63 for the very same issue. I’m more curious as to why, more than anything.
v3.63 works really well for what I use it for. Falcas has done a superb job with WDP, I feel like I’m complaining about the the color of a cup holder while sitting in a Porsche:D -
Have this issue when openning the WDP:
Re-installed and continues… any ideas Falcas?
V. 3.6.5************** Texto da excepção **************
System.ArgumentOutOfRangeException: InvalidArgument=Valor de ‘14’ inválido para ‘SelectedIndex’.
Nome do parâmetro: SelectedIndex
em System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
em WeaponDeliveryPlanner.cntDTC.FillSystemdata()
em WeaponDeliveryPlanner.cntDTC.Camp_TE()
em WeaponDeliveryPlanner.cntDTC.GetCampFile()
em WeaponDeliveryPlanner.fclsMain.fclsMain_Load(Object sender, EventArgs e)
em System.EventHandler.Invoke(Object sender, EventArgs e)
em System.Windows.Forms.Form.OnLoad(EventArgs e)
em System.Windows.Forms.Form.OnCreateControl()
em System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
em System.Windows.Forms.Control.CreateControl()
em System.Windows.Forms.Control.WmShowWindow(Message& m)
em System.Windows.Forms.Control.WndProc(Message& m)
em System.Windows.Forms.ScrollableControl.WndProc(Message& m)
em System.Windows.Forms.ContainerControl.WndProc(Message& m)
em System.Windows.Forms.Form.WmShowWindow(Message& m)
em System.Windows.Forms.Form.WndProc(Message& m)
em System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
em System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
em System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)************** Assemblagens carregadas **************
mscorlib
Versão da assemblagem: 4.0.0.0
Versão Win32: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
–--------------------------------------
WeaponDeliveryPlanner
Versão da assemblagem: 3.6.5.14
Versão Win32: 3.6.5.14
CodeBase: file:///C:/WeaponDeliveryPlanner/WeaponDeliveryPlanner.exeMicrosoft.VisualBasic
Versão da assemblagem: 10.0.0.0
Versão Win32: 12.0.51209.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dllSystem.Windows.Forms
Versão da assemblagem: 4.0.0.0
Versão Win32: 4.0.30319.34209 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
Versão da assemblagem: 4.0.0.0
Versão Win32: 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
Versão da assemblagem: 4.0.0.0
Versão Win32: 4.0.30319.34238 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dllSystem.Runtime.Remoting
Versão da assemblagem: 4.0.0.0
Versão Win32: 4.0.30319.34245 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
Versão da assemblagem: 4.0.0.0
Versão Win32: 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
Versão da assemblagem: 4.0.0.0
Versão Win32: 4.0.30319.34234 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dllBMSUtils
Versão da assemblagem: 1.5.2.0
Versão Win32: 1.5.2.0
CodeBase: file:///C:/WeaponDeliveryPlanner/BMSUtils.DLLSystem.Windows.Forms.resources
Versão da assemblagem: 4.0.0.0
Versão Win32: 4.0.30319.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_pt_b77a5c561934e089/System.Windows.Forms.resources.dllSystem.Data
Versão da assemblagem: 4.0.0.0
Versão Win32: 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.Core
Versão da assemblagem: 4.0.0.0
Versão Win32: 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.dllMicrosoft.VisualBasic.resources
Versão da assemblagem: 10.0.0.0
Versão Win32: 11.0.50938.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic.resources/v4.0_10.0.0.0_pt_b03f5f7f11d50a3a/Microsoft.VisualBasic.resources.dllSystem.Transactions
Versão da assemblagem: 4.0.0.0
Versão Win32: 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
Versão da assemblagem: 4.0.0.0
Versão Win32: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dllSystem.Numerics
Versão da assemblagem: 4.0.0.0
Versão Win32: 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.dllDatabase
Versão da assemblagem: 1.3.0.0
Versão Win32: 1.3.0.0
CodeBase: file:///C:/WeaponDeliveryPlanner/Database.DLLmscorlib.resources
Versão da assemblagem: 4.0.0.0
Versão Win32: 4.0.30319.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_pt_b77a5c561934e089/mscorlib.resources.dllLzssManaged
Versão da assemblagem: 1.0.0.0
Versão Win32: 1.0.0.0
CodeBase: file:///C:/WeaponDeliveryPlanner/LzssManaged.DLLLzssNative
Versão da assemblagem: 0.0.0.0
Versão Win32:
CodeBase: file:///C:/WeaponDeliveryPlanner/LzssNative.DLL************** Depuração JIT **************
Para activar a depuração just-in-time (JIT), o ficheiro .config para esta
aplicação ou computador (machine.config) tem de ter o
valor jitDebugging definido na secção system.windows.forms.
A aplicação também tem de ser compilada com a depuração
activada.Por exemplo:
<configuration></configuration>
Quando a depuração JIT está activada, qualquer excepção não processada
será enviada para o depurador JIT registado no computador
em vez de ser processada por esta caixa de diálogo. -
Have this issue when openning the WDP:
Re-installed and continues… any ideas Falcas?
V. 3.6.5Looks like one of the values in your callsign.ini got changed (not by WDP) and has an invalid value.
You have a couple of options to solve this. Delete your callsign.ini and create a new one.
Or open it with a text editor and find the value. It is one that is in the System tab, as a combobox and the value are looking for is 14.
Delete that line from your callsign.ini should also solve it.gr Falcas
-
Did you ever find a workaround for this? I reverted back to v3.63 for the very same issue. I’m more curious as to why, more than anything.
v3.63 works really well for what I use it for. Falcas has done a superb job with WDP, I feel like I’m complaining about the the color of a cup holder while sitting in a Porsche:DShould work again in the next version.
Gr Falcas