Weapon Delivery Planner released
-
@Falcas in fact here, what bothers me the most is the erroneous value of the admissible quantity in the chosen configuration (block 50 +2 external tanks )
the value should be 12200lbs ( instead of 5594) and why it is important here ?-> this value influences the data on left side of datacard ( here hidden by the loadout window) for determining the bingo -
@suhkoi69 said in Weapon Delivery Planner released:
@Falcas in fact here, what bothers me the most is the erroneous value of the admissible quantity in the chosen configuration (block 50 +2 external tanks )
the value should be 12200lbs ( instead of 5594) and why it is important here ?-> this value influences the data on left side of datacard ( here hidden by the loadout window) for determining the bingo
Yes, there is something not ok in case the AC has already used fuel (aka in flight)
But this has totally no influence on the bingo (left side of the datacard)
-
@Falcas my bad! I confused it with something else
-
@suhkoi69 said in Weapon Delivery Planner released:
@Falcas my bad! I confused it with something else
No worries.
Basically the amount of fuel is only used during the takeoff performance calculation. Which had the correct value already.
So it was only a wrong fuel value written on the Datacard. (Which has been fixed)Another change, the T/O fuel is no longer shown in case the flight is airborne.
Block fuel remains, although the name shouldn’t be taken literal as its the fuel the AC still has at that moment.Still working on something else which is the set initial fuel. Yes you can set the amount before takeoff lower than maximum.
-
@zeek said in Weapon Delivery Planner released:
@Falcas - I am getting something odd when setting up a HADB profile. when looking at the map in WDP under the profile it doesn’t matching up with the map in BMS also the STPT locations and PPTs don’t match the mission either. Here is what WDP shows vs. what BMS is showing. Thoughts?
@Falcas I too have this issue, with HDAB and TOSS - PopUp appears to be OK.
Firstly, it’s picking the wrong attack STPT - for HDAB, TOSS and PopUp. I’ve edited them, from 7 > 5.
PopUp
HADB and TOSS
not only are the STPTs way off, they are rotated and flipped (mirrored)
-
I’ll take a look when I have some time
-
New version release, latest is 3.7.23.231
Map
Added, Crotale and Roland to thread options.
Datacard
Fixed, Block and T/O fuel value in case the flight was already airborne and used fuel. Changed, In case the flight is already airborne, the T/O fuel is no longer shown. Added, Initial Fuel is now correctly shown on the datacard. (Was already implemented for Performance).
POP-UP
Changed, clicking on the “N”, “E”, “S”, “W” label, sets the heading directly.
HADB
Fixed, Drawing HADB close in map Changed, clicking on the “N”, “E”, “S”, “W” label, sets the heading directly. Changed, clicking on the “0”, “30”, “60”, “90” label, sets the angle off directly.
TOSS
Fixed, Drawing TOSS close in map Changed, clicking on the “N”, “E”, “S”, “W” label, sets the heading directly. Changed, clicking on the “0”, “30”, “60”, “90” label, sets the angle off directly.
-
WDP doing the same as both MC and WC. Black screen and then back on desktop???
-
@NIL said in Weapon Delivery Planner released:
WDP doing the same as both MC and WC. Black screen and then back on desktop???
No problem here with WDP, MC, WC.
Maybe you can check your windows eventlog (application) for any hint?! -
@Falcas Your download says 9 jan. This probably should be 9 feb.
Cheers Obi1
-
February Update:
For some reason, the threat display in the map doesn’t work properly anymore, the only thing that still shows up are the Search Radars (purple) - SAMs (Yellow) are nowhere to be seen, Auto PPT doesn’t do anything either anymore.KTO, 4.37.1, tested on multiple computers
-
Mmm I might have forgotten to enable it again in the code after testing. Will check it
-
New version available, latest is 3.7.24.232.
Nothing new, but the Intel officer has been turned on again
-
Hi Falcas
I found a solution. When I run WDP, MC and WC from the launcher of BMS they work, but when I start the program on it’s own, still an issue, but only on my WIN10 computer. Weird, but it works that way. -
@Falcas Fixed, thank you so much!
-
This post is deleted! -
When I Update Kneeboards the “Don’t Change” option isn’t displaying the DDS for that slot. I’m 99% sure it used to.
-
@CriticalMass said in Weapon Delivery Planner released:
When I Update Kneeboards the “Don’t Change” option isn’t displaying the DDS for that slot. I’m 99% sure it used to.
A little more info. It seems when the Theater doesn’t have its own TerrData\Objects\KoreaObj directory, it’s not falling back on KTO. (I’m specifically looking at Baltic as this seems to be the only Add-On theatre that doesn’t have its own KoreaObj directory).
-
WDP 3.7.24.232 is throwing an unhandled exception when loading TR_BMS_06_ILS_Weather.trn from 4.37 U2. Vanilla installation of 4.37 U2.
Details from the unhandled exception are below:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.OverflowException: Arithmetic operation resulted in an overflow.
at WeaponDeliveryPlanner.cntDataCard.FillCommCard()
at WeaponDeliveryPlanner.cntDataCard.txtC1_VHF_TextChanged(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnTextChanged(EventArgs e)
at System.Windows.Forms.TextBoxBase.OnTextChanged(EventArgs e)
at System.Windows.Forms.Control.set_Text(String value)
at System.Windows.Forms.TextBoxBase.set_Text(String value)
at System.Windows.Forms.TextBox.set_Text(String value)
at WeaponDeliveryPlanner.cntDataCard.FillDataCard()
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.8.9139.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dllWeaponDeliveryPlanner
Assembly Version: 3.7.24.232
Win32 Version: 3.7.24.232
CodeBase: file:///D:/Falcon/Weapon%20Delivery%20Planner/WeaponDeliveryPlanner.exeMicrosoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dllSystem.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9075.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dllSystem
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9139.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dllSystem.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
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.9032.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dllSystem.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9139.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dllSystem.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
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.9032.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dllAccessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dllBMSUtils
Assembly Version: 1.6.3.51
Win32 Version: 1.6.3.51
CodeBase: file:///D:/Falcon/Weapon%20Delivery%20Planner/BMSUtils.DLLdbwdp
Assembly Version: 1.6.0.6
Win32 Version: 1.6.0.6
CodeBase: file:///D:/Falcon/Weapon%20Delivery%20Planner/dbwdp.DLLSystem.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9110.0 built by: NET481REL1LAST_B
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.5.1
Win32 Version: 1.0.5.1
CodeBase: file:///D:/Falcon/Weapon%20Delivery%20Planner/BMSLocation.DLLSystem.Web
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
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:/Falcon/Weapon%20Delivery%20Planner/LzssManaged.DLLLzssNative
Assembly Version: 0.0.0.0
Win32 Version:
CodeBase: file:///D:/Falcon/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>
<system.windows.forms jitDebugging=“true” />
</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. -
Hello, I noticed that in the HARM tab of the DTC there’s a system name reported as -1.
The code is 608, given that the symbol showing in the RWR is listed as 8 I guess it should be SA8 instead.
Not sure if it’s a WDP issue or if it comes from some BMS database.EDIT: I double checked and, in fact, SA8 is in the list… but if I try to select it, code is listed as 0 and symbol as -1.
Also other systems show the same behaviour (e.g. SA9, SA13, SA19, PATRIOT, NIKE and probably more).