Weapon Delivery Planner released
-
Hi Alfagolf,
That is something with the ground battalions in your mission.
Could you send me the mission you are having this problem with?gr Falcas
-
Hi Alfagolf,
That is something with the ground battalions in your mission.
Could you send me the mission you are having this problem with?gr Falcas
I’m experiencing this problem when loading several missions, one of them is attached, thanks for your work!
-
Thanks, that helps a lot.
The missions you are having problem with, don’t have any battalions.
That is the reason for the crash.I’ll upload a new version with that fixed in a min, stby.
Gr Falcas
-
Will the fix be version 3.6.5 or 3.6.4b ??? Just want to know so I can look out for it, many thanks.
Best regards.
Fubar2Niner
-
Hi,
New file has been uploaded. I know, this is not always a good thing, but it has the same version nr. (creating a new version takes longer )
Remove the previous version and delete the 7z file.
Download WDP again and install the newly downloaded file.Thanks for the quick report!!!
The Mission Briefing is not 100% done yet, still need to do a couple of things.
But it was more important to get this version releasedGr Falcas
-
-
A quick question if you don’t mind, nowhere can I find a manual so this is my best point of call.
In the new version I have no ‘Open Mission’ tab, it is replaced Correction - no longer there with ‘Reload WX’ however when I click this tab I get a ‘Weather file not found’ error. Problem is in settings I can’t browse to the weather file ?? This from a fresh install, I also tried installing over the top v3.6.3, tis way gives this error;
Details are as follows:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.MissingFieldException: Field not found: ‘Flightplan.Arrive’.
at WeaponDeliveryPlanner.cntDataCard.FillFlightplan()
at WeaponDeliveryPlanner.cntDataCard.SetSwingFltpln()
at WeaponDeliveryPlanner.flcsMain.Setup()
at WeaponDeliveryPlanner.flcsMain.flcsMain_Load(Object sender, EventArgs e)
at System.EventHandler.Invoke(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.ContainerControl.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.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
–--------------------------------------
WeaponDeliveryPlanner
Assembly Version: 3.6.4.0
Win32 Version: 3.6.4.0
CodeBase: file:///H:/WeaponDeliveryPlanner/WeaponDeliveryPlanner.exeMicrosoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 12.0.51209.34209 built by: FX452RTMGDR
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.34209 built by: FX452RTMGDR
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.34209 built by: FX452RTMGDR
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.34209 built by: FX452RTMGDR
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.34209 built by: FX452RTMGDR
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.34209 built by: FX452RTMGDR
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.34209 built by: FX452RTMGDR
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.34234 built by: FX452RTMGDR
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:///H:/WeaponDeliveryPlanner/BMSUtils.DLLSystem.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
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.34209 built by: FX452RTMGDR
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.34209 built by: FX452RTMGDR
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.34209 built by: FX452RTMGDR
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:///H:/WeaponDeliveryPlanner/Database.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.Any help much appreciated.
Best regards.
Fubar2Niner
-
A quick question if you don’t mind, nowhere can I find a manual so this is my best point of call.
In the new version I have no ‘Open Mission’ tab, it is replaced Correction - no longer there with ‘Reload WX’ however when I click this tab I get a ‘Weather file not found’ error. Problem is in settings I can’t browse to the weather file ?? This from a fresh install, I also tried installing over the top v3.6.3, tis way gives this error;
Any help much appreciated.
Best regards.
Fubar2Niner
Hi Fubar,
Manuals for WDP can be found on the WDP website.
http://www.weapondeliveryplanner.nl/download/index.htmlAs well as youtube videos explaining WDP.
Yes, both manuals as well as youtubes are made with older versions of WDP. And NO, there will be no updates. But than again… Everything is about the same.
Clicking on a button and explore what happens never hurtsTo open a mission… File, Open Mission…
Never install a new version on-top of an older version. As I wrote before, remove the previous version and install from scratch.
Gr Falcas
-
Yep I got all your youtube tuts bookmarked Regarding ‘Open Mission’ the tab no longer exists. I will post a screenshot.
Best regards.
Fubar2Niner
-
Here is the screen from a fresh install;
You see, no ‘Open Mission’ tab Regarding pushing buttons…… The co ordination card has always baffled me, when I ‘Click to Load Pic’ what the hell am I looking for in the popup box ? I can’t see any .img, .jpeg etc files in the default, where should I look? Many thanks for your help and an excellent program.
Best regards.
Fubar2Niner
-
Here is the screen from a fresh install;
You see, no ‘Open Mission’ tab Regarding pushing buttons……
Wow… are you serious? Click on File.
The co ordination card has always baffled me, when I ‘Click to Load Pic’ what the hell am I looking for in the popup box ? I can’t see any .img, .jpeg etc files in the default, where should I look?
Any picture that you have created yourself. Some defaults have been supplied with the tool, see: “…WeaponDeliveryPlanner\Datacards\PlanPic”
gr Falcas
-
Wow… are you serious? Click on File.
Holy sheep, how embarresed am I :oops: Sorry mate got soooo used to seeing the tab on the GUI I didn’t even think to look there ……
Many thanks again and sorry for any inconvenience. I obviously owe you a drink :drink:
Best regards.
Fubar2Niner
-
Greetings. Glad to say that I got WDP to work in my PC. Had to Re-install BMS though. Great job. Thanks very much. Jay.:D
-
Falcas be advised, that if someone inputs wrong callsign on first run, the whole WDP will be INOP. There will be the standard JIT Debuger message, and no program function will be available to the user. Probably a simple check if there is such callsign present, prompting to change if its incorrect, should suffice.
-
Falcas be advised, that if someone inputs wrong callsign on first run, the whole WDP will be INOP. There will be the standard JIT Debuger message, and no program function will be available to the user. Probably a simple check if there is such callsign present, prompting to change if its incorrect, should suffice.
Thanks for the heads-up. Not something I ever tested. (Who would do a thing like that?)
But after WDP has started, you can always change your Callsign again.
DTC->Main tab.I’ll add a check for that.
Thanks again.
Gr Falcas
-
Falcas, I have noticed that in my WDP install, if I try to plan a pop up attack, the given bearing of the OA1 cue is displayed incorrectly on the datacard page. On the pop up page, it displays correctly, but on the datacard it gives a different bearing.
-
Blu3wolf, see PM.
Gr Falcas
-
Hi again. WDP is really great. Along with the “Kneepad Updater”, its an invaluable Tool for BMS. Have an Issue though! Apart from the default BMS Campaigns, I only got the Aegean installed.(with the " Pilot Body" Mod in both theatres). WDP, along with the “Updater” works perfectly in “Korea”, but can’t seem to get it to work in the “Aegean”! Have changed WDP to “Aegean”, and after Loading and saving a TE, when I go in game, the pages on the Kneeboards haven’t changed.(still displaying Korean Map and Info). I’ve noticed that in the Aegean Theater, the Info which is displayed in the Kneeboards is that from a previous Mission which I saved prior to INSTALLING the “Pilot Body” into the Aegean Theater. In “Korea”, I don’t have any problems. The Kneeboards are updated every time I do a new Mission. Hope this makes sense! Am I missing something? Thanks. Jay.
-
the kneemap updater only changes the default Korea theather (8019.dds) If you want the file to be active you have to copy it to the other theater or…. (like i did)
create 8019.dds symbolic hardlinks in other theaters that point to the default 8019.ddsfor example
run dosbox as admin in the specific theater korea object folder:
mklink /h 8019.dds “D:\Falcon\Falcon BMS\Data\Terrdata\objects\KoreaObj\8019.dds”edit: the first dds file is the new created hardlink in the directory you are in
the second (“…8019.dds”) points to the origionalfor extra info
http://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/ -
the kneemap updater only changes the default Korea theather (8019.dds) If you want the file to be active you have to copy it to the other theater or…. (like i did)
create 8019.dds symbolic hardlinks in other theaters that point to the default 8019.ddsfor example
run dosbox as admin in the specific theater korea object folder:
mklink /h 8019.dds “D:\Falcon\Falcon BMS\Data\Terrdata\objects\KoreaObj\8019.dds”edit: the first dds file is the new created hardlink in the directory you are in
the second (“…8019.dds”) points to the origionalThanks for the reply. Please forgive me(for being a “Newbie”)but am not familiar with dosbox!!! Any chance with providing me with a “What-to-do list”? Cheers.