Weapon Delivery Planner released
-
Did you add the Kurile theatre to the WDP database?
And added the map to the \Map directory?gr Falcas
I haven’t, mainly because I don’t quite understand what you are referring to?
Is there a guide somewhere on how to do that? -
I haven’t, mainly because I don’t quite understand what you are referring to?
Is there a guide somewhere on how to do that?WDP has an (open) database with all the theaters, countries and airports.
If your theater is not included in the database, you won’t find it in WDP.Gr Falcas
-
Hi Falcas, first, thanks for the WDP, its helps a lot.
Second, just two questions:
-
In balkans theater, my home base is Casale/Brindisi wich have two rwy according to Balkans MAIP 13-31 and 05-23. In WDP (currently i’m using 3.7.14.140), after I load the mission, in the datacard/airbase section it’s showing casale as departure same as arrive, but when i want to choose rwy its states: 01-19 and 15-33. WDP is in Balkans.
-
In WDP, after load the mision, usually Steerpoint 6 has the coordinate all wrong, way to south. Is the only steerpoint off set, all other are OK.
Thanks
Best Regards
Chuno
-
-
Hi Falcas, first, thanks for the WDP, its helps a lot.
Second, just two questions:
-
In balkans theater, my home base is Casale/Brindisi wich have two rwy according to Balkans MAIP 13-31 and 05-23. In WDP (currently i’m using 3.7.14.140), after I load the mission, in the datacard/airbase section it’s showing casale as departure same as arrive, but when i want to choose rwy its states: 01-19 and 15-33. WDP is in Balkans.
-
In WDP, after load the mision, usually Steerpoint 6 has the coordinate all wrong, way to south. Is the only steerpoint off set, all other are OK.
Thanks
Best Regards
Chuno
Hey Chuno,
The answer to 1 is very simple. The version of Balkans which you uses has probably a different (new) airbase.
You need to update the WDP database to match the theater.For question 2,
When you load the mission and select your flight you will get an question if you have saved the DTC specific for this flight.
In 99% of the cases you want to answer this question with NO.
Are you saying yes?Gr Falcas
-
-
Thanks for the quick reply!!
About my first question, thanks, I will look into the database.
About my second question, when the campaing engime fragg a mision of my interest, in the BMS UI i mark the the treaths with the PPT Steerpoints, the target steerpoint, etc. then i save the campaing and the DTC. Then I open WDP and I load the mision to make the final tweaks. As i have previusly save the DTC, when WDP question me, I answer yer. I that what I am doing wrong?
Best Regards
Chuno
-
Don’t answer yes…. answer NO
-
Chuno, I think if you have some steerpoints or lines from a different mission in the DTC you need to clear them or it throws WDP into giving a waypoint somewhere in China or elsewhere.
I’m not sure if this is what is causing this to happen but usually when I have that problem this is the fix I use.I do the same thing as you I make some adjustments to the flight plan, add PPT’s, lines and such in Falcon UI. Then save the DTC first, then save the campaign. When you load the mission in WDP and choose “yes” when it asks if you have saved your DTC it should work. Your PPT’s, lines and waypoints should be correct.
I like to assign targets to waypoints that are after the last flight path waypoint. I usually start with waypoint 15 thru waypoint 24 unless the flight has more than 15 waypoints (usually never more the 15 waypoints but I know some people have more complex flight paths than me). This makes it easy to direct the AI to attack different targets.
-
Don’t answer yes…. answer NO
So I’ll say it again… Don’t answer yes… answer NO
-
You know how that is…
-
I thought Carbide in post #1897 had a good reason for answering Yes. Falcas, you’re insisting to answer No. So when should we answer yes?
-
“So when should we answer yes” all the time … it make for a happier life !!!
-
Only if you have precision STPT saved. And they must be correct and for the flight you are going to use.
Yes I also find this a huge pain in the A… But it is what it is.
You can always check the STPT list in the DTC tab if you want.All the other stuff in the DTC does not matter for the question. They get loaded as they are.
Gr Falcas
-
I have often wondered if I was doing something wrong when I see the flight path with a crazy STPT in China.
I’m glad to know that it is just something that is how it is.
This tool is amazing and this little inconvenience is nothing compared to how useful this tool is! -
Wrong is a big word, but if this is happening to you, you do have a DTC which is not clean and has Precision STPT while it should not.
Yes it is basically a user mistake (wrong data in the DTC) which WDP tries to handle as good as possible.Gr Falcas
-
Falcas i get an error when trying to load mission .ini (happens as soon as i press the button)
OS : W10 home 64biti am including the details of the error below…
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.ArgumentException: The path is not of a legal form. at System.IO.Path.LegacyNormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths) at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths) at System.IO.Path.InternalGetDirectoryName(String path) at WeaponDeliveryPlanner.cntDTC.OpenTEFile() at WeaponDeliveryPlanner.cntDTC.btnGetTEFile_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.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.2110.0 built by: NET47REL1LAST CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- WeaponDeliveryPlanner Assembly Version: 3.7.6.96 Win32 Version: 3.7.6.96 CodeBase: file:///D:/Program_Files/Weapon%20Delivery%20Planner/WeaponDeliveryPlanner.exe ---------------------------------------- Microsoft.VisualBasic Assembly Version: 10.0.0.0 Win32 Version: 14.7.2046.0 built by: NET47REL1 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.7.2110.0 built by: NET47REL1LAST 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.7.2102.0 built by: NET47REL1LAST 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.7.2110.0 built by: NET47REL1LAST 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.7.2046.0 built by: NET47REL1 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.7.2046.0 built by: NET47REL1 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.7.2102.0 built by: NET47REL1LAST 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.7.2114.0 built by: NET47REL1LAST 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.1.8 Win32 Version: 1.6.1.8 CodeBase: file:///D:/Program_Files/Weapon%20Delivery%20Planner/BMSUtils.DLL ---------------------------------------- System.Data Assembly Version: 4.0.0.0 Win32 Version: 4.7.2102.0 built by: NET47REL1LAST CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- System.Transactions Assembly Version: 4.0.0.0 Win32 Version: 4.7.2046.0 built by: NET47REL1 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.7.2046.0 built by: NET47REL1 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.7.2046.0 built by: NET47REL1 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.5.0.0 Win32 Version: 1.5.0.0 CodeBase: file:///D:/Program_Files/Weapon%20Delivery%20Planner/dbwdp.DLL ---------------------------------------- BMSLocation Assembly Version: 1.0.2.0 Win32 Version: 1.0.2.0 CodeBase: file:///D:/Program_Files/Weapon%20Delivery%20Planner/BMSLocation.DLL ---------------------------------------- System.Web Assembly Version: 4.0.0.0 Win32 Version: 4.7.2110.0 built by: NET47REL1LAST CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll ---------------------------------------- LzssManaged Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///D:/Program_Files/Weapon%20Delivery%20Planner/LzssManaged.DLL ---------------------------------------- LzssNative Assembly Version: 0.0.0.0 Win32 Version: CodeBase: file:///D:/Program_Files/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.
I get the same error with latest version of WDP (3.7.14.140). It has to do with file paths, it seems.
@Falcas, does WDP not like paths with embedded blanks, such as the blank between “Falcon” and “stuff” in this?
F:\Falcon stuff\Weapon_Delivery_Planner_3.7.14.140
-
This post is deleted! -
I get the same error with latest version of WDP (3.7.14.140). It has to do with file paths, it seems.
@Falcas, does WDP not like paths with embedded blanks, such as the blank between “Falcon” and “stuff” in this?
F:\Falcon stuff\Weapon_Delivery_Planner_3.7.14.140
The problem is not the WDP directory or blank.
You can do the following to “fix” this for now (future release of WDP has been fixed already)
Just load a mission. This will load the mission.ini for that mission.
Close WDP and this mission.ini file location will be saved in the setup.ini.
Next time you start WDP and click on the button you should be fine.Gr Falcas
-
Yes user mistake.
I apologize if it sounded like I said WDP was not functioning properly. It was I who was not functioning properly. That’s all I was saying.
Thank you again for the clarification.Best regards,
Carbide -
Yes user mistake.
I apologize if it sounded like I said WDP was not functioning properly. It was I who was not functioning properly. That’s all I was saying.
Thank you again for the clarification.Best regards,
CarbideNope, was not taken like that. Just wanted to be clear as well.
But lets face it. RL F-16 does not have precision STPTs as all STPTs are high precision.
We need that as Falcon saves the STPTs with KM grid.
STPTs are saved in 2 files and could be out of sync as well.
Not cleaning/removing these from your DTC will just give you these kind of problems.
Its just one of the complicated things in BMS.Gr Falcas
-
Not your intention, but you’re bringing more fuel to my approach of pretargeting