Weapon Delivery Planner released
-
WDP is already 4.33 compatible for a very long time
Gr Falcas
Probably u r talking about a non released version of WDP cause as the posts say if there r going to be core database changes then WDP should adapt them. Unless the changes do not affect the general data structure that WDP uses already.
-
Probably u r talking about a non released version of WDP cause as the posts say if there r going to be core database changes then WDP should adapt them. Unless the changes do not affect the general data structure that WDP uses already.
Nope, current WDP version is already compatible.
Gr Falcas
-
Wow much complaining appreciate what we have. This sim is over a decade old and still rocks. Falcas thanks for your time and commitment to help all.
-
I really do not see any complaints here. Developers must depend on users to report potential issues in a helpful and respectful manner. WDP is recognized as a very useful contribution to the community.
-
Wow much complaining appreciate what we have. This sim is over a decade old and still rocks. Falcas thanks for your time and commitment to help all.
I was thinking the same thing. Nothing is perfect and we should appreciate the great amount of work Falcas has dedicated to this instead. Countless hours of developing and testing is worth thousands thanks.
This is unbelievable.
-
I’m still confused on the threat rings issue. In campaign the threats are spotted, SA-2s in Jordan, for example. In WDP they are not. It’s no big deal since I am usually using the OOB to place threat circles in-game anyway.
-
I’m still confused on the threat rings issue. In campaign the threats are spotted, SA-2s in Jordan, for example. In WDP they are not. It’s no big deal since I am usually using the OOB to place threat circles in-game anyway.
Just standby for a min.
-
Comedian…
There is plenty of testing by multiple people before releasing.
If I would only release anything when I am 100% sure that there are no problems, there wouldn’t be any progress or any release for years.
I am not going to do the same thing as theater builder, only posting nice pics and not releasing anything.And on top of that… there is not extra time needed to fix anything. It does not matter who reports anything, I need the same time to change or fix things
You should be happy with the update rate instead.Gr Falcas
Comedian?
Your ego is offended for no reason, because it was just a positive recommendation after reading 100 pages of bug-reports here.
Personally i am happy with the version you sent me for Redflag and i am still using it.Theaterdevelopement is not a easy thing indeed and many theaters stay in developement forever. But we are happy with having released rock solid stable versions so far (RF, BfB and BfS).
cheers.
-
@A.S:
Comedian?
Your ego is offended for no reason, because it was just a positive recommendation after reading 100 pages of bug-reports here.
Personally i am happy with the version you sent me for Redflag and i am still using it.Theaterdevelopement is not a easy thing indeed and many theaters stay in developement forever. But we are happy with having released rock solid stable versions so far (RF, BfB and BfS).
cheers.
Ego card again… so predictable.
You have already written me this suggestion by PM some time ago. At that time I have already explained you how this works.
We are not going to go into a long discussion again, so this is the last reply on this subject.100 bug reports… And also 100 feature request, 100 questions how things work. Yes, that is exactly what this thread is for.
WDP is too big and has way too many options and differences for all theatres.
Not to mention all the new options/features improvements being added all the time.
Lots of things happen outside WDP that have effect on WDP itself. For example the new release of ITO (great theatre btw)
For the airports the campIDs got changed… The airport database WDP has depends on the campIDs to find the correct airports.
Everybody can understand that things get messed-up in this case… It gets fixed and released before the weekend so that people can enjoy there free days.
ITO and BFS shared the same database entries. This means that for BFS the campIDs are not correct in the database. To separate the two theatres was a bit more time consuming. (already finished) and so a new release will be coming soon.I am currently working on 8 different tools so I am vey happy with an update rate of almost once a month.
This is only possible due to all the reports from users that are being posted in these threads!
I thank everybody for there reports and I hope that the reports will remain as much or even get more.This is what development is all about.
Happy planning.
Gr Falcas
-
Omg Falcas. Too much “wind”. I just wanted to make a suggestion to ease your own job, because replying to all reports/bugs can eat more time than devolping as you know i think. If you think everything is tested well before release (each patch)…well then fine with me.
I am currently working on 8 different tools
This is more interesting between all that text
-
Really great tool, thanks!
If I get a chance to read through this entire thread sometime I might make a suggestion for the tool (to make sure I’m not suggesting old stories)
-
Really great tool, thanks!
If I get a chance to read through this entire thread sometime I might make a suggestion for the tool (to make sure I’m not suggesting old stories)
Your choice
Just post your request here or send me a PM.Gr Falcas
-
I have reinstalled my windows now to win 7 x64 installed WDP 3.5.8 and right after i insert the “pilot name” for it, it hands out a nice “Bug”
i was useing win 8 and it worked fine… uninstalled and reinstalled and from that moment im getting the same error. any ideas?
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.NullReferenceException: Object reference not set to an instance of an object. at WeaponDeliveryPlanner.cntDTC.FillEWS() at WeaponDeliveryPlanner.cntDTC.Camp_TE() at WeaponDeliveryPlanner.cntDTC.GetCampFile() 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.17929 built by: FX45RTMREL CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- WeaponDeliveryPlanner Assembly Version: 3.5.8.0 Win32 Version: 3.5.8.0 CodeBase: file:///D:/Games/Falcon4/wdp/WeaponDeliveryPlanner.exe ---------------------------------------- Microsoft.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.dll ---------------------------------------- System 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/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.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.dll ---------------------------------------- System.Windows.Forms 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.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.17929 built by: FX45RTMREL 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.17929 built by: FX45RTMREL 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.17929 built by: FX45RTMREL 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.17929 built by: FX45RTMREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- F4Utils Assembly Version: 1.5.0.0 Win32 Version: 1.5.0.0 CodeBase: file:///D:/Games/Falcon4/wdp/F4Utils.DLL ---------------------------------------- System.Data 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.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- MILDial Assembly Version: 1.0.5068.19465 Win32 Version: 1.0.5068.19465 CodeBase: file:///D:/Games/Falcon4/wdp/MILDial.DLL ---------------------------------------- System.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.dll ---------------------------------------- System.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.dll ---------------------------------------- System.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.dll ---------------------------------------- Database Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///D:/Games/Falcon4/wdp/Database.DLL ---------------------------------------- LzssManaged Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///D:/Games/Falcon4/wdp/LzssManaged.DLL ---------------------------------------- LzssNative Assembly Version: 0.0.0.0 Win32 Version: CodeBase: file:///D:/Games/Falcon4/wdp/LzssNative.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.
This happens allso on windows 8 and this is the WDP 3.5.8 version.
After long win7 updates the problem have been solved. but i hava a new issue, after i load up a mission , it will not load the PPT’s and when i press AUTO PPT, allso nothing happens… why is that?
-
Hi,
As I can not reproduce the bug reports or the problems reported with the thread circles, you just have to try out the new version
I did do some changes, so please have a look and report if the problems are still current or not.New version 3.5.9
https://www.benchmarksims.org/forum/showthread.php?5293-Weapon-Delivery-PlannerGr Falcas
-
Hi,
As I can not reproduce the bug reports or the problems reported with the thread circles, you just have to try out the new version
I did do some changes, so please have a look and report if the problems are still current or not.New version 3.5.9
https://www.benchmarksims.org/forum/showthread.php?5293-Weapon-Delivery-PlannerGr Falcas
Error: Weather file .twx not found
-
Error: Weather file .twx not found
That report is what you get when you did not save the weather for the mission.
Not a bug, its a featureGr Falcas
-
Can you elaborate, Falcas? I’m seeing that same TWX error for every user generated TE.
-
Can you elaborate, Falcas? I’m seeing that same TWX error for every user generated TE.
When I use a user generated TE, it has two files. One file has an extension of .tac and the other has .twx. I put both files in the save folder. Does your user generated TE contain two files as described?
-
This post is deleted! -
Alfagolf and F4jok are (where) right.
There was a little problem with finding the weather file.Fixed.
http://www.weapondeliveryplanner.nl/files/wdp/WDP3.6.0.rarGr Falcas