Weapon Delivery Planner released
-
Besher52 thank you but it does not.
-
Hi Falcas,
with the latest version - 3.7.2 Build 69, the map is still 4.32 map, areas data too.:neutral:
As I use WDP for creating Korea Aeronautical Information Publication (AIP) object for TACVIEW, do you have a scheduled date of updating theses data and ground map ?Windblow
-
Download Mission commander from Falcas website. Copy the LzssNative.dll from the mission commander folder and paste/overwrite the one in the WDP folder.
That should fix it!Same hereā¦along with the contents of the āDetailsā button:
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 Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(String Value) at WeaponDeliveryPlanner.clsLoadDTC.GetCallsignHud(String fName) at WeaponDeliveryPlanner.clsLoadDTC.LoadCallsign(String fName, Boolean Version) at WeaponDeliveryPlanner.cntDTC.GetCampFile() at WeaponDeliveryPlanner.fclsMain.fclsMain_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.7.2.69 Win32 Version: 3.7.2.69 CodeBase: file:///C:/Weapon%20Delivery%20Planner/WeaponDeliveryPlanner.exe ---------------------------------------- Microsoft.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.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR 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.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.dll ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34251 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.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34270 built by: FX452RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Runtime.Remoting Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34245 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.dll ---------------------------------------- System.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.dll ---------------------------------------- System.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.dll ---------------------------------------- BMSUtils Assembly Version: 1.5.5.0 Win32 Version: 1.5.5.0 CodeBase: file:///C:/Weapon%20Delivery%20Planner/BMSUtils.DLL ---------------------------------------- System.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.dll ---------------------------------------- System.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.dll ---------------------------------------- System.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.dll ---------------------------------------- System.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.dll ---------------------------------------- dbwdp Assembly Version: 1.4.0.0 Win32 Version: 1.4.0.0 CodeBase: file:///C:/Weapon%20Delivery%20Planner/dbwdp.DLL ---------------------------------------- LzssManaged Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Weapon%20Delivery%20Planner/LzssManaged.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.
-
Hello, here SEVERAL days I try to install WDP v 3.7.2 and I have this error that appears toujors my WIN 7 OS is if someone has an idea.
Thank you in advance.http://img110.xooimage.com/files/2/e/f/erreur-wdp-4d7bd75.png
same here
Download Mission commander from Falcas website. Copy the LzssNative.dll from the mission commander folder and paste/overwrite the one in the WDP folder.
That should fix it!work on me, thNX
-
Is there any way to add a custom theater to WDP or are they all hard coded?
-
Iām sorry but Iām fumbling the MP DTC update instructions in the last section of using the updated DTC within the online MP.
The tutorials refer to a timer in a previous version.
Would appreciate a link or an explanation. -
Iām sorry but Iām fumbling the MP DTC update instructions in the last section of using the updated DTC within the online MP.
The tutorials refer to a timer in a previous version.
Would appreciate a link or an explanation.Has been answered a couple of times already
Forget about the timer, BMS code has been fixed already in the latest 4.32 updates.
As so, you wonāt find the button anymore.
Just save your DTC in WDP, go to BMS and load the DTC in the UI.Gr Falcas
-
Is there any way to add a custom theater to WDP or are they all hard coded?
Not hardcoded in the code, but WDP comes with a database with all the available theaters including all the airports.
Currently the database contains just over 1600 airbases.So you can imagine that this database is not open and getting messed up
Gr Falcas
-
Falcas,
Much appreciated ! -
Iām getting this also, any ideas Falcas
Hi, I updated WDP to the latest version - 3.7.2 Build 69 - and now I have a strange error message every time I work with my DTC and save it (see attached image).
I have never seen this before and the DTC seems to be correctly savedā¦ any clues?On a side note Iām running at a screen res of 3840x2160 and a lot of WDP is garbled ( I can supply s/s if youād like) any plans to up the res ?
Many thanks and appreciation for your great work mate.
Best regards.
Fubar2Niner
-
Hey Falcasā¦let me start by saying I love your work with this. One thing Iāve encountered since I upgraded to 4.33 is that steerpoints (and subsequently any recon steerpoints) are rarely shown in the DTC. Furthermore, when they are there, they disappear once I save the datacards, never to return. Am I doing something wrong? Am I missing something?
Cheers!
-
Side note, how do I use Mission Commander to move a spawn point at an airbase?
-
Iām a bit confused about the weather that is stated in the briefing. How do you properly do this?
First I add the *.fmapās generated in the Campaign/Save/weahterupdates or something and I load the first map in the Falcon UI and make sure that auto-update is marked.
Then I save the weather. When going to WDP, I check the briefing and hit Reload WX and it loads correctly mentioning the correct time of the campaign.
But my point is that the wind directions and strength mentioned in WDP Briefing are different from the ones found in the Briefing in the Falcon UI. -
When you load āBilly Bob Frank.camā as the save file it looks for āBilly Bob Frank.fsmapā so it has to exist. When you save a *.cam file in BMS it also saves whatever weather is currently active as the same name as the save game.
There is a bug where the saved current state wind are 180 off from the original FSMAP.
-
When you load āBilly Bob Frank.camā as the save file it looks for āBilly Bob Frank.fsmapā so it has to exist. When you save a *.cam file in BMS it also saves whatever weather is currently active as the same name as the save game.
There is a bug where the saved current state wind are 180 off from the original FSMAP.
So technically by just adding or subtrackting 180 degrees from the heading, you actually get the real weather?
-
I have just started using your program. I think I have the hang of many items. You did a nice job on it, thank you. My questions are:
If I make any changes while in the UI to a campaign mission, I must save at that point before going to the datacrad to load, correct?
When I am in the BMS 4.33 UI and in a campaign, I recon a target site and assign a steerpoint to the target, shouldnāt it appear on my datacard? Ie, letās say I have a normal 10 steerpoint mission, and I assign Steerpoint 11 to a reconned target, I save the campaign, shouldnāt it appear on my datacard once I open the mission? (ie I answer āYesā to the question upon typing in the Pkg number).
Thank you.
-
Falcas ā
BMS 4.33 still allows us to save custom HUD colors to our <callsign>.ini file (using <alt>Cā>S). I like to use a yellow HUD color, and the BMS devs allow this.
But your WMD v3.7.2 declares an error on startup and doesnāt allow me to continue.
If BMS allows a saved yellow HUD color, why donāt you allow it? :)</alt></callsign>
-
falcas, is there a mirror available to download the wdp. I have tried unsucessfuly about a dozen times to download form the link in the forum. Every time i try to extract the files i get the error corrupted zip. When watching the download it gets to about 30 minutes remaining then ends. I think iam being timed out.
-
Try by going to his site. ?
-
I know you can open the airport diagrams via the map with selected āShow Airportā Option.
But there is also a Button for āChartsā in the āPerformanceā-section, but it is grayed out for me and I canāt access the diagrams that way.
Do I have to set a path to the airport diagrams somewhere?