Weapon Delivery Planner released
-
It’s strange, since I installed fresh BMS 4.34 like today and didn’t even have the time to tamper with its theaters. It’s vanilla installation with only some config options changed.
Don’t worry, found something.
Gr Falcas
-
Still the bug where DED lighting and DED on HUD DTC choices aren’t properly independent.
-
This post is deleted! -
Still the bug where DED lighting and DED on HUD DTC choices aren’t properly independent.
?
-
In my settings I have “auto load last mission” checked.
When I restart WDP, 3.7.11.117.7, I have to reload TR_BMS_01_GroundOPS.trn. Why?
-
@jc1:
In my settings I have “auto load last mission” checked.
When I restart WDP, 3.7.11.117.7, I have to reload TR_BMS_01_GroundOPS.trn. Why?
Training missions is not included in the autoload.
But I’ll add it.Gr Falcas
-
Downloaded latest version of WDP to run with 4.34.
Get this:
??
-
Check attachment, can’t see it.
Gr Falcas
-
?
“HUD Panel, Include in DTC” not checked
“INT Lighting Panel, Include in DTC” checked
DED Brt DIMSave callsign.ini
[INT_LIGHTING]
DED=1
**[Hud]
DED=0Line should not be present**
-
Downloaded latest version of WDP to run with 4.34.
Get this:
??
Attachment reads:
Theater: ‘Korea’ not found in your BMS install
WDP works with limited data.
Copy the theater database to the “WDP/Database” location. -
Attachment reads:
Theater: ‘Korea’ not found in your BMS install
WDP works with limited data.
Copy the theater database to the “WDP/Database” location.This could happen if WDP is not able to locate your installation correctly (registry)
After you have started WDP got to Settings.
Look if the Falcon location is the correct one. if not, use browse.
If all the locations look good after this, you should be fine. Close WDP and start again.In case the TDF location is not good, browse to the theater.lst from the Korea theater.
This is where all the theaters are located in.In case you have modified this file or has been mod by installing a different theater, please check if the locations in the theater.lst are correct.
You can open this file with a normal text editor. Make sure you save it with the correct name, not as txt!!!Gr Falcas
-
Hi Falcas
OA1, OA2, VRP etc … should now take into account the reference altitude of target because the elevations are now corrected in DIST DED page
-
This could happen if WDP is not able to locate your installation correctly (registry)
After you have started WDP got to Settings.
Look if the Falcon location is the correct one. if not, use browse.
If all the locations look good after this, you should be fine. Close WDP and start again.In case the TDF location is not good, browse to the theater.lst from the Korea theater.
This is where all the theaters are located in.In case you have modified this file or has been mod by installing a different theater, please check if the locations in the theater.lst are correct.
You can open this file with a normal text editor. Make sure you save it with the correct name, not as txt!!!Gr Falcas
Thanks Falcas.
Have uninstalled and installed again to check.
Having downloaded all the files in the zip to a separate folder, I click on the .exe file, and I get the message that there is no setup.ini file found. This pops up several times after I cancel it. I then get a message that my callsign.ini file can’t be found. I continue however until I can open the programme, and have then set it to point to the correct installation for 4.34. Maybe it’ll work OK now, but I was surprised with the error messages about the setup.ini file. Should there be one included in the zip file?
-
Thanks Falcas.
Have uninstalled and installed again to check.
Having downloaded all the files in the zip to a separate folder, I click on the .exe file, and I get the message that there is no setup.ini file found. This pops up several times after I cancel it. I then get a message that my callsign.ini file can’t be found. I continue however until I can open the programme, and have then set it to point to the correct installation for 4.34. Maybe it’ll work OK now, but I was surprised with the error messages about the setup.ini file. Should there be one included in the zip file?
Just wait a bit longer and don’t cancel, the .ini will be created automatically [emoji6]
-
Hi Falcas
OA1, OA2, VRP etc … should now take into account the reference altitude of target because the elevations are now corrected in DIST DED page
Maybe later, got too much to do at this time.
Gr Falcas
-
Thanks Falcas.
Have uninstalled and installed again to check.
Having downloaded all the files in the zip to a separate folder, I click on the .exe file, and I get the message that there is no setup.ini file found. This pops up several times after I cancel it. I then get a message that my callsign.ini file can’t be found. I continue however until I can open the programme, and have then set it to point to the correct installation for 4.34. Maybe it’ll work OK now, but I was surprised with the error messages about the setup.ini file. Should there be one included in the zip file?
This is normal for the first time as there is no setup.ini in the package.
If I would add a setup.ini it would overwrite your settings with each update.Gr Falcas
-
Hi. I’ve started trying to use this program but struggling a bit. I open up my campaign save and find my mission, show threats using the auto button then save the DTC.
When I get in the aircraft no threat rings are visible.
Am I missing a really obvious step?
Thanks.
-
Yes, after you have saved the DTC in WDP you need to load it in the BMS UI,
Gr Falcas
-
HI
I am running WDP 3.7.9.114 and I get the following error when I click on “Upd Kneeboard”
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.IO.FileLoadException: Mixed mode assembly is built against version ‘v2.0.50727’ of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information.
at WeaponDeliveryPlanner.cntDataCard.UpdateKneeboard(Int32 LeftBrd, Int32 RightBrd)
at WeaponDeliveryPlanner.cntDataCard.btnKneeboard_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.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
–--------------------------------------
WeaponDeliveryPlanner
Assembly Version: 3.7.9.114
Win32 Version: 3.7.9.114
CodeBase: file:///F:/WDP/WeaponDeliveryPlanner.exeMicrosoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.8.3752.0 built by: NET48REL1
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.8.3752.0 built by: NET48REL1
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.8.3752.0 built by: NET48REL1
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.8.3752.0 built by: NET48REL1
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.8.3752.0 built by: NET48REL1
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.8.3752.0 built by: NET48REL1
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.8.3752.0 built by: NET48REL1
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.8.3752.0 built by: NET48REL1
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.17
Win32 Version: 1.6.1.17
CodeBase: file:///F:/WDP/BMSUtils.DLLSystem.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
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.8.3752.0 built by: NET48REL1
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.8.3752.0 built by: NET48REL1
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.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dlldbwdp
Assembly Version: 1.6.0.0
Win32 Version: 1.6.0.0
CodeBase: file:///F:/WDP/dbwdp.DLLBMSLocation
Assembly Version: 1.0.3.0
Win32 Version: 1.0.3.0
CodeBase: file:///F:/WDP/BMSLocation.DLLSystem.Web
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
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:///F:/WDP/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.Thanks!
-
Yes, after you have saved the DTC in WDP you need to load it in the BMS UI,
Gr Falcas
Thank you, I thought I watched a video where someone wasn’t following this step.