Weapon Delivery Planner released
-
I can’t get WDP to download . What am I doing wrong?
-
Thank you very much for the help!
-
I just updated to 3.6.3 from 3.6.1 and have noticed that my tanker track line boxes aren’t rectangular anymore, I’m getting parallelograms and some are really thin. The preset airspace boxes are still the right shape. Thanks for your many years of work Falcas!
-
Line thickness have change, so that can be that you see thiner lines.
About the parallelograms, I have to look into it.
In the mean time I think you can find the tanker anywayThanks for the heads-up.
Gr Falcas
-
Hehe, yeah I can find them, I was just trying to be a good bug reporter By thin I was refering to the size of the parallelograms, like less than 5 miles from long edge to long edge (short edges seem to be the proper length, just not at a right angle). Thinnest one I have seen is 1 mile wide and 64 miles long.
-
Yep I got what you mean, I can reproduce it here so I know what you mean.
Thanks for the report.Gr Falcas
-
Can you explain what solved your problem? I’m having the same situation. I have win8.1 so I downloaded a win 8.1version of dotnet3.5 but had no change. I was hoping the new 3.6.3 would not have a dotnet problem but it does. BTW If I understand it, Windows 8.1 comes with dotnet3.5. You have to go into the control panel to programs and then activate it(???). So maybe some win 8.1 experts can help with this.
-
I have win8.1 so I downloaded a win 8.1version of dotnet3.5 but had no change.
Please read the first post, it clearly says (and gives you the link) you need .NET4.0.
Gr Falcas
-
Falcas - Is there any way to change the way WDP assigns AA TACAN signals to your flight? I.E. I just ran a mission with my flight being a 4 ship flight. WDP shows the IDM adresses correctly - they all work as I’d expect. But the AA TACAN is given as 12y, 22y, 75y and 85y for 11, 12, 13 and 14 respectively. But my experience in the sim is that this is not correct, 1 should be @ 75y, 2 should be @ 85y, 3 should be @ 12y and 4 @ 22y. I’m able to adjust it since it is in the yellow field, but this is the default setup. So my ranging is not correct with the AI. Is there a better quick fix for this? Besides that little issue your software fills in the gaps for me very well.
-Babite -
Falcas - Is there any way to change the way WDP assigns AA TACAN signals to your flight? I.E. I just ran a mission with my flight being a 4 ship flight. WDP shows the IDM adresses correctly - they all work as I’d expect. But the AA TACAN is given as 12y, 22y, 75y and 85y for 11, 12, 13 and 14 respectively. But my experience in the sim is that this is not correct, 1 should be @ 75y, 2 should be @ 85y, 3 should be @ 12y and 4 @ 22y. I’m able to adjust it since it is in the yellow field, but this is the default setup. So my ranging is not correct with the AI. Is there a better quick fix for this? Besides that little issue your software fills in the gaps for me very well.
-BabiteHi Babite,
WDP is showing you the correct values now and it is what the AI is using.
And it also depends on which flight inside the package you are in.If you are in the first flight, the tacan is set to:
12Y, 22Y, 75Y, 85YIf you step into the second flight, the tacans get set to:
13Y, 23Y, 76Y, 86YIf you step into the third flight, the tacans get set to:
14Y, 24Y, 77Y, 87YIf you step into the fourth flight, the tacans get set to:
15Y, 25Y, 78Y, 88YIf you step into the fifth flight, the tacans get set to:
16Y, 26Y, 79Y, 89YQuote from the BMS-Manual page124
If humans can select any channel and band, AI (Artificial Intelligence) aircraft are using fixed TACAN channels all in the Y band. AI first flight is set on 12, 22, 75 & 85Y. The next AI flight is the same structure but one number higher: 13, 23, 76 & 86Y. And the BMS code can support up to five flights of AI with this system. That means that you can always find the AI controlled aircraft in the first 5 flights.
Gr Falcas
-
Falcas - I have read that. Maybe I’m misunderstanding the implementation. Or maybe it’s just my system wants to get back at me for something. Still, great program.
-Babite -
Greetings. I’m quite new to this great community Have been searching around the Forums and have recently come across this great piece of software. I am currently using 1 Screen to fly Falcon BMS and my somewhat “newbie” question is; can you use WDP with a single Screen set up. I ask this because to my Knowledge. “Knee Pad” View is not implemented in BMS. I’ve read about the “WDP Knee Pad Updater”/“Pilot Model” Mods, but is there an alternative? Thanks. Jay.
-
Hi Jaycee:
WDP is much much more than having a Knee Pad in cockpit. I recommend you to search in YT for WDP tutorials, (Falcas has published great ones, but there are users who has done also great ones).
Then to answer your question to kneepads: you can export the mission data card generated by WDP and have it in your cockpit. Before, you need a pilot model (at least the legs) from Harpoon. This model originally loads a .dds image with all the airbases data. Its name is 8019.dds and lives in \Falcon BMS 4.32\Data\Terrdata\objects\KoreaObj. You can download a dds viewer to view that file.
Once you know what file is, you could export the mission data card generated by WDP, in dds format, and overwrite the 8019.dds file. You would need to do this for each mission.
The WDP Knee Pad updater is an utility that does this automatically for you.
I hope it all makes more sense now.
S!
-
Small bug report that should be relatively easy to squash.
Loading a package sortie with >4 flights gives a “array index out of bounds” probably because WDP doesn’t expect more than 4 flights in package.
-
Another small thing; on the Threats page, when NATO and SAM Missiles are selected, the list shows the NATO AAA.
Thanks a lot for building this great program!
-
Small bug report that should be relatively easy to squash.
Loading a package sortie with >4 flights gives a “array index out of bounds” probably because WDP doesn’t expect more than 4 flights in package.
Hi,
This can’t be because of package with more that 4 flights. This has been tested (a lot ).
But just to be sure I just checked again and loading missions with 5 flights in a package without any problem.
So it is probably something else.Any chance you send me the mission and tell me which flight to open?
Thanks for the report.
Gr Falcas
-
Another small thing; on the Threats page, when NATO and SAM Missiles are selected, the list shows the NATO AAA.
Thanks a lot for building this great program!
Hi,
Fixed in the next update.
Thanks for the heads up.
Gr Falcas
-
Hi Jaycee:
WDP is much much more than having a Knee Pad in cockpit. I recommend you to search in YT for WDP tutorials, (Falcas has published great ones, but there are users who has done also great ones).
Then to answer your question to kneepads: you can export the mission data card generated by WDP and have it in your cockpit. Before, you need a pilot model (at least the legs) from Harpoon. This model originally loads a .dds image with all the airbases data. Its name is 8019.dds and lives in \Falcon BMS 4.32\Data\Terrdata\objects\KoreaObj. You can download a dds viewer to view that file.
Once you know what file is, you could export the mission data card generated by WDP, in dds format, and overwrite the 8019.dds file. You would need to do this for each mission.
The WDP Knee Pad updater is an utility that does this automatically for you.
I hope it all makes more sense now.
S!
Thanks for your response. Off to check some Vids in YT. Falcon is getting better by the day!
-
Hi,
This can’t be because of package with more that 4 flights. This has been tested (a lot ).
But just to be sure I just checked again and loading missions with 5 flights in a package without any problem.
So it is probably something else.Any chance you send me the mission and tell me which flight to open?
Thanks for the report.
Gr Falcas
It’s weird. I try it again and sometimes it crashes and sometimes not.
https://www.dropbox.com/s/0hy8jvaxmfvkic8/Save-Day%20%201%2014%2002%2011.zipKorea Original
Package #11004See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at WeaponDeliveryPlanner.cntDataCard.FillPackages()
at WeaponDeliveryPlanner.cntDataCard.SelectNewFlight(Boolean ByButton)
at WeaponDeliveryPlanner.flcsMain.LoadTE()
at WeaponDeliveryPlanner.cntDataCard.OpenMission()
at WeaponDeliveryPlanner.cntDataCard.btnOpenTE_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.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
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.0.30319.18444 built by: FX451RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
–--------------------------------------
WeaponDeliveryPlanner
Assembly Version: 3.6.3.0
Win32 Version: 3.6.3.0
CodeBase: file:///B:/Applications/BMS/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.18408 built by: FX451RTMGREL
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.18408 built by: FX451RTMGREL
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:///B:/Applications/BMS/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:///B:/Applications/BMS/WDP/Database.DLLLzssManaged
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///B:/Applications/BMS/WDP/LzssManaged.DLLLzssNative
Assembly Version: 0.0.0.0
Win32 Version:
CodeBase: file:///B:/Applications/BMS/WDP/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 gave your mission a couple of tries, but can’t get it to crash.
Which is good… but also bad. If you have a crash again can you see if you can reproduce it by using the exact same steps?gr Falcas