Weapon Delivery Planner released
-
Hi, Falcas
Is there a way to import MAP png when I made a new one for unsupported theater?
https://www.benchmarksims.org/forum/showthread.php?41090-Kurile-Conflict-Theatre-3-35-1-for-BMS-4-35&p=562366&viewfull=1#post562366thx.
Just add the theater to the WDP database. Its fully open to edit by anybody.
Add the map with the correct name to the directory where the other maps are stored.gr Falcas
-
New version released.
https://www.benchmarksims.org/forum/showthread.php?5293-Weapon-Delivery-Planner&p=66013#post66013Enjoy,
Falcas -
Hi Falcas! Thank you very much for the update and all your efforts. I just gave the new version a go, but it crashes everytime I try to load a campaign or any TE file.
Here’s the crash log:
System.IO.FileNotFoundException: Die Datei oder Assembly “LzssManaged, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null” oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden.
Dateiname: “LzssManaged, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null”
bei WeaponDeliveryPlanner.fclsMain.GetTheater()
bei WeaponDeliveryPlanner.fclsMain.LoadTE()
bei WeaponDeliveryPlanner.cntDataCard.OpenFile(String fName)
bei WeaponDeliveryPlanner.cntDataCard.OpenMission()
bei WeaponDeliveryPlanner.fclsMain.mnuOpenMission_Click(Object sender, EventArgs e)
bei System.Windows.Forms.MenuItem.OnClick(EventArgs e)
bei System.Windows.Forms.MenuItem.MenuItemData.Execute()
bei System.Windows.Forms.Command.Invoke()
bei System.Windows.Forms.Command.DispatchID(Int32 id)
bei System.Windows.Forms.Control.WmCommand(Message& m)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ScrollableControl.WndProc(Message& m)
bei System.Windows.Forms.Form.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)WRN: Protokollierung der Assemblybindung ist AUS.
Sie können die Protokollierung der Assemblybindungsfehler aktivieren, indem Sie den Registrierungswert [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) auf 1 festlegen.
Hinweis: Die Protokollierung der Assemblybindungsfehler führt zu einer gewissen Leistungseinbuße.
Sie können dieses Feature deaktivieren, indem Sie den Registrierungswert [HKLM\Software\Microsoft\Fusion!EnableLog] entfernen.************** Geladene Assemblys **************
mscorlib
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4311.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll.
–--------------------------------------
WeaponDeliveryPlanner
Assembly-Version: 3.7.16.152.
Win32-Version: 3.7.16.152.
CodeBase: file:///D:/sims/tools/WDP/WeaponDeliveryPlanner.exe.Microsoft.VisualBasic
Assembly-Version: 10.0.0.0.
Win32-Version: 14.8.3761.0 built by: NET48REL1.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll.System
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4311.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll.System.Core
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4311.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll.System.Windows.Forms
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4290.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.System.Drawing
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3761.0 built by: NET48REL1.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.System.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.dll.System.Xml
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3761.0 built by: NET48REL1.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll.System.Runtime.Remoting
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3761.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.dll.BMSUtils
Assembly-Version: 1.6.3.33.
Win32-Version: 1.6.3.33.
CodeBase: file:///D:/sims/tools/WDP/BMSUtils.DLL.Microsoft.VisualBasic.resources
Assembly-Version: 10.0.0.0.
Win32-Version: 14.8.3761.0 built by: NET48REL1.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic.resources/v4.0_10.0.0.0_de_b03f5f7f11d50a3a/Microsoft.VisualBasic.resources.dll.System.Windows.Forms.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3761.0 built by: NET48REL1.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.System.Data
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4290.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll.System.Data.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3761.0 built by: NET48REL1.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Data.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Data.resources.dll.System.Transactions
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3761.0 built by: NET48REL1.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll.System.EnterpriseServices
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3761.0 built by: NET48REL1.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll.System.Numerics
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3761.0 built by: NET48REL1.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll.dbwdp
Assembly-Version: 1.6.0.0.
Win32-Version: 1.6.0.0.
CodeBase: file:///D:/sims/tools/WDP/dbwdp.DLL.BMSLocation
Assembly-Version: 1.0.4.0.
Win32-Version: 1.0.4.0.
CodeBase: file:///D:/sims/tools/WDP/BMSLocation.DLL.mscorlib.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.3761.0 built by: NET48REL1.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll.System.Web
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4261.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-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.Zum Beispiel:
<configuration></configuration>
Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt. -
ME too. I also have
LzssManaged, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null’ です。'LzssManaged, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
error -
Hey,
Just download the same file again from the website. Couple of files where missing in the package.
Sorry for this.gr Falcas
-
New version released.
https://www.benchmarksims.org/forum/showthread.php?5293-Weapon-Delivery-Planner&p=66013#post66013Enjoy,
FalcasI get a 404 File not found?
-
-
all okay here, just refresh and download again
-
Yep, file is up again
-
Worked!
See that the ATIS is now working correctly. Thanks Falcas
But I have one question though. Still have problems with the radio tab on DTC. It doesn’t import the freq’s I have on my callsign.ini file, and I checked that they are there. It’ will do, when I hit the Open Callsign.ini File button on the MAIN tab. Is this the normal procedure or is just me?
Thanks in advance. -
Hey,
@MRO:
But I have one question though. Still have problems with the radio tab on DTC. It doesn’t import the freq’s I have on my callsign.ini file, and I checked that they are there. It’ will do, when I hit the Open Callsign.ini File button on the MAIN tab. Is this the normal procedure or is just me?
Thanks in advance.This depends a little on what you are doing. WDP loads the callsign.ini when it gets started. If you have changed your DTC after that. When you change to a different flight in BMS, the frequencies will change. You need to save this to the DTC (which is just a text file) for WDP to be able to load them. But WDP can’t know what and when you have changed your DTC.
As you say… loading the callisign.ini will load the part where the frequencies are located and all is as it should be.gr Falcas
-
But I can make a force load of the callsign.ini as soon as you select a flight (load mission in WDP).
That should help out in this case.Gr Falcas
-
Thanks for the quick reply Falcas, I’ll try it.
-
Thanks Falcas the problem has been fixed!
-
Hello Falcas,
I don’t know if this has been asked before, but could you share how WDP calculates the Min Fuel column on the steerpoints data sheet?
Thanks -
Hello Falcas,
I don’t know if this has been asked before, but could you share how WDP calculates the Min Fuel column on the steerpoints data sheet?
Thanksit calculates consumed fuel between 2 waypoints from starting the last waypoint with a fixed minimun of fuel requested to ensure the landing in security (ideally 1200lbs for block 50) : it calculates backwards step by step for each previous waypoint
-
it calculates consumed fuel between 2 waypoints from starting the last waypoint with a fixed minimun of fuel requested to ensure the landing in security (ideally 1200lbs for block 50) : it calculates backwards step by step for each previous waypoint
Sure, but a bit more details would be great. How much fuel per mile? Does it take into account altitude? airspeed? climb/descent?
-
Sure, but a bit more details would be great. How much fuel per mile? Does it take into account altitude? airspeed? climb/descent?
yes it takes into account altitude
I used:
20lbs/nm for low level
10 lbs/nm for mid level
5 lbs/nm for high levelresults are quasi similar with WDP
I supposed data maybe come from this document : https://info.publicintelligence.net/HAF-F16-FlightChecklist.pdf
-
How can I uninstall WDP? Trying to install the latest version, but keep getting an error when unzipping saying that 3.7.15 has stopped working.
-
This post is deleted!