Weapon Delivery Planner released
-
Hi Wind,
You are mixing up a lot of old things, please read the changelogs that comes with BMS and WDP.
Note related to the current thread topic regarding “saving/using” the WDP PPTs in a BMS flight (see threat circles on HSD), these steps are required?
- Open BMS and have it running, ensure your pilot is set in a seat for the mission you want to fly;
No, there is no need to have BMS open at all. You can, but it is not a must.
Also no need to be in the pilot seat for the mission you want to fly.
It is even easier if you are NOT in the TE at this point.- While BMS remains open, alt/tab and open WDP, and open the mission identified in step 1;
As in point 1, no need to have BMS open while working on your mission in WDP.
- Ensure PPTs are displayed on map in WDP and are correctly noted in the DTC PPT tab;
- Alt tab back to BMS and fly mission;
After you created the PPTs and set other things you want in WDP, save the DTC.
If you didn’t have BMS running, you want to start BMS at this point (else you can’t fly ).
When you jump into a TE, everything is set and you will see the PPTs on the map.
Nothing more to do and you can fly. No need to Alt/Tab. In case of ramp-start, you do have to load the DTC.For campaign, the PPTs are cleaned from the callsign.ini as you join a campaign. So for campaigns, you need to go to WDP and save the DTC.
Here it becomes tricky… If you did not change anything and the DTC shows green, WDP will not re-save the DTC. This is the most likely spot where people are getting bad results. Make sure you get a message that you callsign.ini is saved ok!!! If you don’t see this, the DTC has not been saved!!!
Back in the BMS UI, go to the DTC screen and click on the load button. After you close this screen again, you will see the PPTs. If you don’t see the PPTs on the MAP at this point, you did something wrong.
If you do have the PPTs on the map, you don’t need to do anything more. Go to the 3D world and you are done.- While countdown clock running, Alt/Tab back to WDP and Save DTC (which noted a save to the callsign.ini file
- Alt tab back to BMS at which point the mission will load when the clock ends and you enter pit;
Totally no need to do this when you have the PPTs on the map in the UI
These steps have worked for me and are the only steps that seem to work. However, wondering if the alt tab back and forth is really necessary? Basically, if you save the DTC in WDP and you simply run BMS, and choose the flight for which you saved the DTC from WDP, and click “Fly” why does the PPTs not stick? Or is it simply required that the WDP save must happen after click “Fly” from the BMS mission planner UI?
If the PPTs will stick or not depends on if you are flying a TE or campaign. For a campaign, the DTC is cleared when you enter.
This is why WDP is even more handy. As if you keep WPD running, you will keep all the PPTs and you adjust them as needed.
Read the BMS changelog, you can see that the Load button for the DTC has been fixed.For a TE they do stick.
Also, say I was in the Pit, and then made an edit in WDP, and saved the DTC. Could I open the DTS in the mfd and click to “load” to pull in the latest updates?
Yes, this is very much possible. But instead of wondering… just try and see will never hurt
Gr Falcas
-
Hello,
Is it possible to redirect the Data Card in a PDF?
thanks
-
Hi Falcas,
I think I’ve encountered an issue:
In Datacard, Delivery zone, regardless of the value I select to show (POPUP, HADB or TOSS), always show Popup values in:
-Ingress alt.
-Ingress Spd.
-Rel Height.
-Rel Spd.
-Atack HDG
-TGT in HUDThank you!
-
-
Hello,
Is it possible to redirect the Data Card in a PDF?
thanks
Print as PDF with PDF Creator?
http://sourceforge.net/projects/pdfcreator/ -
Hi Falcas,
I think I’ve encountered an issue:
In Datacard, Delivery zone, regardless of the value I select to show (POPUP, HADB or TOSS), always show Popup values in:
-Ingress alt.
-Ingress Spd.
-Rel Height.
-Rel Spd.
-Atack HDG
-TGT in HUDThank you!
Hi Ender,
Fixed.
Thanks for the report.Gr Falcas
-
Print as PDF with PDF Creator?
http://sourceforge.net/projects/pdfcreator/could implemented as export as pdf in WDP?
-
could implemented as export as pdf in WDP?
This was already discussed a couple of times… not going to happen.
Gr Falcas
-
Hi Falcas,
I have a question: is it possible to create steerpointlines in WDP for FAOR/essembly area, maybe CTR?
Thanks!
Bloodhound
-
Hi Falcas,
I have a question: is it possible to create steerpointlines in WDP for FAOR/essembly area, maybe CTR?
Thanks!
Bloodhound
Sure you can set lines, right click on the map.
But that might not be what you want.
You need to explain more what you would want.Gr Falcas
-
Hm. I tried, but I don´t get it. I found pre-set lines for MOAs etc. But I´m not able to create lines by myself, better I didn´t understand that “add” and “move”-stuff. I will try again and I´ll :rtfm:
Thanks Falcas,
if there still probs, I´ll ask.
Bloodhound
Edit: Maybe I understand now… a really great tool!
-
Greetings everyone. Have only recently discovered this software and am very keen to use it especially with the “Kneepad Updater”. I’ve downloaded, unzipped and placed the files into the BMS 4.32 folder (yes?) but No Joy! when I attempt to launch the Programme, I get a "Microsoft .NET Framework " error. "Unhandled exception has occurred in your application….Illegal characters in your path. I also get a list of details: See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.ArgumentException: Illegal characters in path.
at System.IO.Path.CheckInvalidPathChars(String path, Boolean checkAdditional)
at System.IO.Path.GetFileName(String path)
at System.IO.FileStream…ctor(String path, FileMode mode)
at WeaponDeliveryPlanner.flcsMain.ReadTdf(String TDF)
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.18449 built by: FX451RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dllWeaponDeliveryPlanner
Assembly Version: 3.6.3.0
Win32 Version: 3.6.3.0
CodeBase: file:///C:/Falcon%20BMS%204.32/WeaponDeliveryPlanner.exeMicrosoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 11.0.50709.17929 built by: FX45RTMREL
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.18045 built by: FX45RTMGDR
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.17929 built by: FX45RTMREL
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.18046 built by: FX45RTMGDR
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.18022 built by: FX45RTMGDR
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.34107 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.18058 built by: FX45RTMGDR
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.34230 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:///C:/Falcon%20BMS%204.32/BMSUtils.DLLSystem.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18046 built by: FX45RTMGDR
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.17929 built by: FX45RTMREL
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.17929 built by: FX45RTMREL
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.17929 built by: FX45RTMREL
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:///C:/Falcon%20BMS%204.32/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.My OS is Win 8 and am pretty sure that it meets to WDP requirements. I’ve re-installed the programme a few times and also ran it as Admin but still no joy. Any help would be greatly appreciated. yours gratefully. Jay
-
Greetings everyone. Have only recently discovered this software and am very keen to use it especially with the “Kneepad Updater”. I’ve downloaded, unzipped and placed the files into the BMS 4.32 folder (yes?) but No Joy! when I attempt to launch the Programme, I get a "Microsoft .NET Framework " error. "Unhandled exception has occurred in your application….Illegal characters in your path. I also get a list of details: See the end of this message for details on
My OS is Win 8 and am pretty sure that it meets to WDP requirements. I’ve re-installed the programme a few times and also ran it as Admin but still no joy. Any help would be greatly appreciated. yours gratefully. Jay
Hi Jay,
Its not really clear what you are doing…
For a start, do NOT install WDP in you BMS directory!!!
Did WDP istall correctly or are you having problems during install?
What file are you opening when you get the error?
And last but not least… What version are we talking about?Gr Falcas
-
Hi Jay,
Its not really clear what you are doing…
For a start, do NOT install WDP in you BMS directory!!!
Did WDP istall correctly or are you having problems during install?
What file are you opening when you get the error?
And last but not least… What version are we talking about?Gr Falcas[/QUOTE
Greetings Falcas. Thanks for your quick response. Please forgive me for not explaining myself properly. I’m not very good when it comes to “PC language”! I’ve got 2 PCs (both have the same OS; Win 8.0 64bit updated). I’ll be more specific; Downloaded latest version, Extracted and installed it into its own Directory. (No problems during install). The install placed a Desktop Shortcut. Proceeded to start the Programme, but the next window that appears, stops Loading and the “Microsoft.NET” error Window comes out! If I click continue, I’m able to get into WDP and even though I still have to get into “grips” with the programme, my first impression is that it’s not working right. For example, the “Mouse” Cursor keeps on displaying a “Loading” Icon. I then proceeded to re-install the Programme into the BMS Directory thinking maybe that’s the Folder it should go ( obviously not). So I then went and installed WDP in my other PC. I want to point out that this time round I used “7Zip” extractor which I have installed in this PC as opposed to my other PC (Windows extractor?). Again no problems during install( WDP’s own Folder). When starting the Programme through the Shortcut, this time a new Window pops up asking me for a “Callsign” ( that didn’t happen with my other install), but after typing the Callsign and pressing " OK", the same “Microsoft.NET” error Msg comes out.
Again by pressing " Continue", I’m able to get into WPD, but have the same issues as my other PC. I’ve never had any problems with my BMS install other than the occasional CTD. Hope this helps. Yours Faithfully. Jay. -
Greetings Falcas. Thanks for your quick response. Please forgive me for not explaining myself properly. I’m not very good when it comes to “PC language”! I’ve got 2 PCs (both have the same OS; Win 8.0 64bit updated). I’ll be more specific; Downloaded latest version, Extracted and installed it into its own Directory. (No problems during install). The install placed a Desktop Shortcut. Proceeded to start the Programme, but the next window that appears, stops Loading and the “Microsoft.NET” error Window comes out! If I click continue, I’m able to get into WDP and even though I still have to get into “grips” with the programme, my first impression is that it’s not working right. For example, the “Mouse” Cursor keeps on displaying a “Loading” Icon. I then proceeded to re-install the Programme into the BMS Directory thinking maybe that’s the Folder it should go ( obviously not). So I then went and installed WDP in my other PC. I want to point out that this time round I used “7Zip” extractor which I have installed in this PC as opposed to my other PC (Windows extractor?). Again no problems during install( WDP’s own Folder). When starting the Programme through the Shortcut, this time a new Window pops up asking me for a “Callsign” ( that didn’t happen with my other install), but after typing the Callsign and pressing " OK", the same “Microsoft.NET” error Msg comes out.
Again by pressing " Continue", I’m able to get into WPD, but have the same issues as my other PC. I’ve never had any problems with my BMS install other than the occasional CTD. Hope this helps. Yours Faithfully. Jay.Hi,
The error is about having wrong type of characters in a path, so it will crash on these strange characters.
Do you use a special keyboard or write your callsign with “strange” characters?Gr Falcas
-
Hi,
The error is about having wrong type of characters in a path, so it will crash on these strange characters.
Do you use a special keyboard or write your callsign with “strange” characters?Gr Falcas
Hello again. The Keyboard I use is the one that comes with the PC, though as far as I know, it’s a simpler model as it contains less keys compared to other models (no Pause key for example). As for the Callsign? Now that I think about it, I still don’t have a Callsign in-game, and the one that I typed into the WDP Callsign request Window, was one that I came up with at that moment. Could this have anything to do with my issue? No strange characters though, just a normal name. Thank you once again. Jay.
-
Hello again. The Keyboard I use is the one that comes with the PC, though as far as I know, it’s a simpler model as it contains less keys compared to other models (no Pause key for example). As for the Callsign? Now that I think about it, I still don’t have a Callsign in-game, and the one that I typed into the WDP Callsign request Window, was one that I came up with at that moment. Could this have anything to do with my issue? No strange characters though, just a normal name. Thank you once again. Jay.
Recommend that you setup a logbook in BMS first. Then when you use the WDP, tie it to your callsign.
-
Recommend that you setup a logbook in BMS first. Then when you use the WDP, tie it to your callsign.
Copy that. Will do. Thanks.
-
Good day Mr. Falcas,
after a full Windows 7 x64 Home Premium ( fully updated*) reinstall and a fresh F4-BMS, I get the dreaded .Net Framework error ( the Unhandled exception thing ).
I did follow your instruction on the first post of this forum and still no-joy.
My install is:
Win7 x64 Home Premium full updates
Admin account
All HOTAS and cockpit stuff
UAC and Windows defender removed
All anti-malware / anti-virus / firewall de-activated
F4-BMS U7 an logbook created ( on SSD )
WDP ver 3.6.3.0Upon install, the setup screens seem slow to react
When I open WDP, the “green bar” stop at 4/5 of the whole way and the title screen remains open. The software screen then opens netx/over the title screen and the error message comes up. Still able to use partially the software, the hourglass remains everywhere and the map does not appear, opening the mission creates the bug again, the Viewing DTC file area ( callsign.ini and Mission.ini ) recreates the error.Here is a dropbox-link for the image ( hope it works )
https://www.dropbox.com/s/89x9x01zwewbtps/WDP_Error.jpg?dl=0If you have any idea, requesting help !
Thanks
Pilotwings
-
Hi,
New version released.
See full changelog over here:
https://www.benchmarksims.org/forum/showthread.php?5293-Weapon-Delivery-Planner&p=66013#post66013Just to pick out 2 new highlights…
- New theater Ikaros added.
- Added a briefing card.
Enjoy,
Falcas