Weapon Delivery Planner released
-
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
-
Falcas
I am flying in single player. I will try out your suggestions and get back. I think the volume is ok as I can hear the tower. -
I just installed your new version and had no issues with 2.5. However now with 2.51 I get an error message and click continue and it seems to work but the startup graphic stays on the screen.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.OverflowException: Value was either too large or too small for a Decimal.
at System.Decimal…ctor(Single value)
at WeaponDeliveryPlanner.fclsMain.SetTheater()
at WeaponDeliveryPlanner.fclsMain.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: 2.0.0.0 -
I just installed your new version and had no issues with 2.5. However now with 2.51 I get an error message and click continue and it seems to work but the startup graphic stays on the screen.
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.OverflowException: Value was either too large or too small for a Decimal.
at System.Decimal…ctor(Single value)
at WeaponDeliveryPlanner.fclsMain.SetTheater()
at WeaponDeliveryPlanner.fclsMain.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: 2.0.0.0make sure you have .NET 3.5 Framework installed.
-
I just installed your new version and had no issues with 2.5. However now with 2.51 I get an error message and click continue and it seems to work but the startup graphic stays on the screen.
Hi Sobe,
Could you do the following:
Go to your WDP installation directory, you will find a setup.ini file. Delete this and start WDP again.
Let me know what happens.Gr Falcas
-
Falcas
did that and reinstalled net 3.5 and 4.0 and no joy. -
Sobe, check PM.
-
I’m having big problems downloading the 2.5.1 file (WinRAR reports corrupt CRC). Does anyone have a working file?
Cheers
-
I just checked it, redownload the file from the website.
Gr Falcas
-
Dear Falcas, first of all thanks for the great program, it’s definitely a must have for any Falconeer.
Also, I wonder, what you’d think about adding a more graphical and simpler keyfile generator/extractor to WDP module as a new functionality? In the current situation analysing and creating a keyfile is very much manual work and needs one to be a computer genius. (At least I feel that way…:)) And seeing the key bindings in a more structured way is not possibe in BMS controller setup screen IMO. Doing stg like that will not only help to standardize the keyfiles, also make stick profiling much more simple. Best regards,
-
Also, I wonder, what you’d think about adding a more graphical and simpler keyfile generator/extractor to WDP module as a new functionality? In the current situation analysing and creating a keyfile is very much manual work and needs one to be a computer genius. (At least I feel that way…:)) And seeing the key bindings in a more structured way is not possibe in BMS controller setup screen IMO. Doing stg like that will not only help to standardize the keyfiles, also make stick profiling much more simple. Best regards,
I am sorry to say that I do not agree with you here. First of all, there are already key file generation tools.
Keyfiles for BMS can be found everywhere and no need to change anything, except for the keystrokes that might come in the future.
Feel free to use my keystroke if you want: http://www.weapondeliveryplanner.nl/files/other/FalcasAll.key
Changing the keys combination used with a function is done very easily in BMS itself. Just click the key combination so it turns blue. Then hit the combination you want and you are done.
A standardized file is not possible to my opinion. Everybody have a different setup at home, I have a complete cockpit to fly with, others only a joystick. And thus different wishes and different keystrokes…I have been looking at cougar files that other people have made and to my opinion they are made way to complicated. Try to keep it as simple as possible!!! As an example: Why program the gear handle on the joystick? In RL, as in my own cockpit, you have to let go of the throttle to raise the gear. (wow, this could kick off a discussion :D)
Gr Falcas