Weapon Delivery Planner released
-
Found it, consider it solved in the next update of WDP.
Gr Falcas
-
Question about how WDP works. Does WDP completely overwrite the callsign.ini file, or add to it? I am wondering whether or not target steerpoints and lines, for example, can be added in the campaign planning GUI DTC to the data saved in the .ini file by WDP. Or would saving the campaign planning GUI DTC overwrite and delete the DTC data saved in WDP?
-
Good job Falcas. Im looking forward to the next update.
-
Question about how WDP works. Does WDP completely overwrite the callsign.ini file, or add to it? I am wondering whether or not target steerpoints and lines, for example, can be added in the campaign planning GUI DTC to the data saved in the .ini file by WDP. Or would saving the campaign planning GUI DTC overwrite and delete the DTC data saved in WDP?
You could have just tried it and you would have known
But a very good question.
WDP will read your callsign.ini (and Mission.ini) If you already have PPTs in the callsign.ini, you can see that in the DTCâ>STPT tab. Do note that WDP will load your callsign.ini when WDP starts. So if you have WDP running and then start to add PPTs in your callsign.ini from within BMS, the callsign.ini need to be loaded again in WDP. To do this DTCâ>Main tab.
Your PPT and other setting remain, unless you delete a PPT with WDP ofcourse. Be aware that changes to the callsign.in/mission.ini are only applied when you save the DTC!!!
There is only one exception. The AutoPPT function will first clear all PPTs and then adds its own PPTs to the list.So in short, WDP will not create a new version of your callsign.ini, but it will only add the changes that you make in WDP.
Gr Falcas
-
Falcas, I also have a quick question.
I noticed on one of the airports, the Tower Freq is .005 off from the documented tower freq on UHF, I believe. Would that even matter in game? If it does, Iâll find which one it was and get back to you.
-
Hi Wizard,
WDP has a database with the all the airport data.
As I am still human, I do make mistakes So if you find any, please let me know.
Yes, the name of the airport would be great.
As for the effect in BMS⌠If you tune the wrong freq, you canât contact the towerGr Falcas
-
Iâm not really sure whoâs wrong here. I have a guess though.
Seosan VHF:
BMS Manual = 136.755
WDP = 136.755
Korean Navigation chart from (I think?) Red Dog = 136.75
VHF scratchpad cabability = five digits max = 13675 = 136.75
UI âSet Towerâ = 136.750I think they probably have the manual wrong, and thus led you astray.
-
Well, relax! While confirming my bug with the BMS-manual, it turns out that the navigation chart included by Red Dog?(I think heâs the one who makes them?) is actually the source of the error!
Seosan VHF was the radio in question. You and the manual say 136.755, and the Korea Navigation Volume says 136.75 only.
Thanks for your work on WDP man, awesome stuff.
If you got the idea that I was âstressedâ, I am sorry but text does not always bring the needed emotion.
What I wanted to bring across is that I do make mistakes and I am open to all feedback.Yes, Reddog is the one making all the charts. He is also open to feedback. So If he does not react to this post, drop him a nice note about your findings.
Gr Falcas
-
Check my edit! I think it isnât your bad after all!
And yeah, the ârelaxâ was meant in a positive, encouraging way. I didnât think you were upset at all.
-
Seen your edit, good find!!!
-
Small bug report: thereâs a way to always raise an unhandled exception in the Loadout screen (though I donât think it has a detrimental effect on the program functionality).
Steps to reproduce: go to the Performance tab and click on the Set button; in the loadout screen click on the drop-down menu and select Loadout. Now if you click on the Clear button when the loadout is already clear you will get an unhandled exception; to test this just click on Clear once to clear the payload and then click the same button again.Also: maximizing the window doesnât really maximize it, if the program cannot scale properly maybe you could simply disable the maximize button.
Fantastic program BTW, even though I am still reading the three pdf documents available on your site I am already impressed by itâs functionality.
-
Hi BlackRazor,
I have looked at the CTD and found the problem. Solved in the next update.
The maximize button does work, however the max size of the screen is 1024. So it wonât get bigger than that.
The reason is for us on laptops which usually have a smaller desktop setting.
I might enlarge it on a later stage, but will need a lot of work to change the program.Thanks for the report!!!
Gr Falcas
-
Hi Guys,
Just found out the great work of the DTC, really very helpfull.
Iâm wondering how you do use the WDP as I cannot get it setup properly with 2 screens.
My main screen runs 1680x1050 and my 2nd screen is 1024x768, usinm MultiMon to move progs from one file to the other.I have BMS running in fullscreen mode on main screen and want to run WDP on 2nd screen, somehow the WDP is moving to right side of screen and just shows half.
I can not simply drag the screen to the left and replace it.
Any ideas?
-
I think that has to do with running BMS in fullscreen.
As a test try the following: Go to the launcherâ->configuration.
â> Settings hardware and enable the: Cockpit Displays to external windows.
This will force BMS in windowed mode.If this helps, you might want to check out the Cockpit display extration in the Launcher for more settings.
Gr Falcas
-
Hi Falcas
,
Tkx for prompt reply.This indeed does startup BMS in a windowed mode (size not adjustable) and next to that you have HUD, MFD, DED etc in separate screens.
In fact very helpfull and maybe a way to put your TM MFDâs in front, have to figure out more on this issue later on, if possible to connect >2 screens on my machine it would become even more interstingHowever, when in windowed mode there is no possibility to move your mouse to your 2nd screen. Maybe I do miss some setting alone the line?
-
Hi Sparks,
Alt+Tab will help you to get to the other screens.
Yes, using the external display works great together with the TM MFDs.
I donât have the ones from TM, but the idea is the same. -
Tkx, this should do.
ALT-TAB is working fine, although it normally is giving me problems.
-
Hi,
New version of WDP can be dowloaded at the download section of the WDP website.
Latest version is 2.5.1
For the changes and updates: https://www.benchmarksims.org/forum/showthread.php?5293-Weapon-Delivery-Plannerenjoy
-
hello
I have been trying your TE that came with WPD and after much trial and error I can now see my element and the other packages in the flight in the HSD. I can also talk to the tower. My problem is that I cannot seem to talk to my element or to any of the other members of my flight. I am using package 3724. According to the BMS manual, since I do not hear my requests, I am not on the right channels. I have tried to figure this out but am stumped. I have the tower in channel 15. Thanks -
hello
I have been trying your TE that came with WPD and after much trial and error I can now see my element and the other packages in the flight in the HSD. I can also talk to the tower. My problem is that I cannot seem to talk to my element or to any of the other members of my flight. I am using package 3724. According to the BMS manual, since I do not hear my requests, I am not on the right channels. I have tried to figure this out but am stumped. I have the tower in channel 15. ThanksIf I understand you correctly you are having problems with the comms. But I am not sure if you are in a multiplay situation or a single play?
Reading your post I canât see what you did, but I suppose you used the option of WDP to set a tower frequency to a channel.
This can be very helpfull, however can bite you in the bottom when you donât know what is going on. Every channel has a stored frequency and that is what you are actually using. There is a good chance that you have changed to much channels.
To correct this, go to the DTCâ>Radio tab and you will find a âDefaultâ button on the lower left side. Click this and save your DTC.
Now you have all the channels restored to the default frequencies.My advice , donât change the channels for the tower. If you want to talk to the tower, just change the UHF freq to the tower frequency when you are in the cockpit. After takeoff you can switch to a channel of your choice and you should be able to talk to your element.
Also checking the volume level of COMM 1 and COMM 2 will help once in a while. (Own experiance :mrgreen: )
Hope this will help you a bit, If not, just let me know.
Gr Falcas