Weapon Delivery Planner released
-
Hey, Falcas.
In WDP , I’ve noticed that precision waypoints are read as nav (most of the time, can’t figure it out) . Something wrong or by design ?
Cheers
-
Hey, Falcas.
In WDP , I’ve noticed that precision waypoints are read as nav (most of the time, can’t figure it out) . Something wrong or by design ?
Cheers
Hey,
Sorry, not enough info to follow you here.
Do you mean on the DTC STPT page?Gr Falcas
-
Hey, Yes. Stp.9 is alternate land .- then 10-14 are precision stps. , but in DTC/STPT they are listed as NAV. … although there is ‘Precision’ type in the list (when you press ‘Change’).
But, I think I get the reason… They are in 1-24 steerpoint group list and not in 50-55/81-99, which are ‘open’ ones.
My bad , should’ve tried to put them in above >25 groups.
Right ?
Anyway.
Regards.
-
Well not really… This has been written before though.
Precision STPT is not how it works IRL and is done so you can have exact coordinates for a STPT. In the mission files, the STPT X/Y are saved as a KM/KM location.
They are not an option IRL as there every STPT is already an precision STPT.
The idea for the precision is to update the existing STPT to a higher precision. But a lot of people “mis-use” the precision STPT to add extra STPTs after the flightplan. This is a bit of cheating the system.Just create your Flightplan and update the coordinates of your target insided the flightplan.
Yes, but I want to use 4 STPTs to place above vehicles or building to I can find them with my TPG….
Sure, better to have them inside your flightplan and not after the last landing point. This way your fuel will be calculated correct for example.
Even be to learn how to use your weapons systems as it should be and you get much better at it overall.
Or at least you see the limitations what pilots have IRL. BMS is just not a “push the button and I hit my target” simBut in the end, everybody is free to do as he (she) likes.
Gr Falcas
-
Yes, It is not insta-sim , I am well aware of that… It is testing ground TE with optional targets, so no part of a original flight plan, just precision targets squeezed inside <24.
Regards.
-
New version of WDP released, latest version is now 3.7.5.92
Plenty of new features and fixes.Enjoy,
Falcas
-
I have just tried to use WDP 3.7.5.92 to auto populate the PPTs on the map for a TE, unfortunately it does not identify the threats along the flightplan. The TE was based in the Korea vanilla Theater Falcon BMS 4.33.3. I have checked other TEs same result!
Is there a bug with this functionality or just an issue my end? I have used previous versions of WDP and this worked great.
Cheers for any help in advance!
EDIT: Just reverted to Weapons Delivery Planner 3.7.4.76 and this works as expected.
-
Falcas,
Thanks for the update. Been a fan of your work since day one.Maybe someone can help clear this up for me, with regards to the Nordic Theater.
There are two theaters Nordic Theater or NTO and Old Corps or CWC
When opening a file with WDP or MC it refers to nordic or Nordic Theater which confuses me. (easily done)
Could you use the same naming conventions as the theater itself?
or at least clarify which is which?Thanks,
-
I have just tried to use WDP 3.7.5.92 to auto populate the PPTs on the map for a TE, unfortunately it does not identify the threats along the flightplan. The TE was based in the Korea vanilla Theater Falcon BMS 4.33.3. I have checked other TEs same result!
Is there a bug with this functionality or just an issue my end? I have used previous versions of WDP and this worked great.
Cheers for any help in advance!
EDIT: Just reverted to Weapons Delivery Planner 3.7.4.76 and this works as expected.
Hey,
Confirmed there is a little issue here. Fixed soon.
Gr Falcas
-
Falcas,
Thanks for the update. Been a fan of your work since day one.Maybe someone can help clear this up for me, with regards to the Nordic Theater.
There are two theaters Nordic Theater or NTO and Old Corps or CWC
When opening a file with WDP or MC it refers to nordic or Nordic Theater which confuses me. (easily done)
Could you use the same naming conventions as the theater itself?
or at least clarify which is which?Thanks,
Hey,
Well this is a bit reversed. Nope, Nordic is only one theater. But the creators are using “tricks” do get more out of the one theater.
Which is a choice, but one of the result is what you are seeing.
Go to your WDP setup and look for the file: “StupidThrNames.txt” and open it up with a text editor.
It explains itself.Gr Falcas
-
Cheers Falcas!
Sent from my iPhone using Tapatalk
-
“StupidThrNames.txt”
Someone had a good mind job to come up with a name like this… [emoji38]
Since it doesn’t have the f word seems ok. [emoji38]A small funny way that a Dev steams off the falcon pain fighting with the beast.
Στάλθηκε από το MI 5 μου χρησιμοποιώντας Tapatalk
-
Just that, and just because of that, Arty…
With best regards,
-
Hey,
Well this is a bit reversed. Nope, Nordic is only one theater. But the creators are using “tricks” do get more out of the one theater.
Which is a choice, but one of the result is what you are seeing.
Go to your WDP setup and look for the file: “StupidThrNames.txt” and open it up with a text editor.
It explains itself.Gr Falcas
Sorry to be dense, I thought I understood what you were telling me But,…
My theater.lst:
Add-On Nordic\Terrdata\theaterdefinition\Nordic.tdf
Add-On Nordic\Terrdata\theaterdefinition\NordicCWC.tdfSo, Nordic.tdf = Nordic NTO and Nordic Theater = Nordic CWC ?
Seems more obvious as I type it out…
Thanks, -
hi,
for some reason i cannot seem to see the threat circles on the map
************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at WeaponDeliveryPlanner.fclsLoadout.FillLoadout()
at WeaponDeliveryPlanner.fclsLoadout.SetSeat()
at WeaponDeliveryPlanner.fclsLoadout.fclsLoadout_Load(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.7.2053.0 built by: NET47REL1
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
–--------------------------------------
WeaponDeliveryPlanner
Assembly Version: 3.7.5.92
Win32 Version: 3.7.5.92
CodeBase: file:///C:/Weapon%20Delivery%20Planner/WeaponDeliveryPlanner.exeMicrosoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.7.2053.0 built by: NET47REL1
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.7.2053.0 built by: NET47REL1
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.7.2053.0 built by: NET47REL1
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.7.2053.0 built by: NET47REL1
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.7.2053.0 built by: NET47REL1
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.7.2053.0 built by: NET47REL1
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.7.2053.0 built by: NET47REL1
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.7.2053.0 built by: NET47REL1
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.1.8
Win32 Version: 1.6.1.8
CodeBase: file:///C:/Weapon%20Delivery%20Planner/BMSUtils.DLLSystem.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2053.0 built by: NET47REL1
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.7.2053.0 built by: NET47REL1
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.7.2053.0 built by: NET47REL1
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.7.2053.0 built by: NET47REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dlldbwdp
Assembly Version: 1.5.0.0
Win32 Version: 1.5.0.0
CodeBase: file:///C:/Weapon%20Delivery%20Planner/dbwdp.DLLBMSLocation
Assembly Version: 1.0.2.0
Win32 Version: 1.0.2.0
CodeBase: file:///C:/Weapon%20Delivery%20Planner/BMSLocation.DLLSystem.Web
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2053.0 built by: NET47REL1
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:///C:/Weapon%20Delivery%20Planner/LzssManaged.DLLLzssNative
Assembly Version: 0.0.0.0
Win32 Version:
CodeBase: file:///C:/Weapon%20Delivery%20Planner/LzssNative.DLL -
A new update is coming soon.
Gr Falcas
-
WDP: 3.7.6.96 released.
Fixes a couple of critical bugs for Thread circles and autoPPT.
Enjoy
-
Great and useful update this too, Falcas!
Thanks a lot.
With best regards,
-
This post is deleted! -
Hi Falcas. Seems that i can’t “Use” Tacan nor ILS for Gioia del Colle AFB into Balkans theater.