Weapon Delivery Planner released
-
Hello,
I got a weird issue with aera perimeters on WDP Map.
As shown on this screen, I wanted to highlight two relevant perimeters for my next Multiplayer TE :
- Texaco 4 Tanker area
- KOTAR area
WDP draws the line as if the coordinates were so to speak shifted north-west.
First time I experience such an issue.
Do you guys have any idea what I have done wrong ? Thanks for your help !
Hawk -
The X/Y values in Falcon has been flipped in multiple places. Meaning at one time the X was horizontal and the Y vertical on the map.
At other places this was used the other way around. Note the Objective Editor for example.
In the latest version of WDP all places for X/Y have been checked and set correctly (in the code).
What you see on the map is the database which stored the areas the X/Y are still flipped the wrong way around. This needs to be corrected.
As this database is a simple open XML file, anybody can do this.gr Falcas
-
@SoBad Changed now, thanks
-
@LorikEolmin
Are you sure you pointed WDP to 4.36?
If WDP does not pick up 4.36 this feature is disabled.Working of the backup was checked when implemented, checked the code and tested here myself. Works fine.
-
@Falcas said in Weapon Delivery Planner released:
@LorikEolmin
Are you sure you pointed WDP to 4.36?
If WDP does not pick up 4.36 this feature is disabled.Working of the backup was checked when implemented, checked the code and tested here myself. Works fine.
I’ll have to check that, thank you. I reinstalled it, so I think so, but…
-
Was this an older mission and the ini file was also old already?
What happens if you add the tanker track again?
Move the cursor to the corner of the tanker track (green dashed lines). A window appears with name of the tanker and “Add to line 1,2,3,4”
Click on one of the lines and it should create the line on top of the tanker track.Just checked and works fine here.
-
@Falcas said in Weapon Delivery Planner released:
@LorikEolmin
Are you sure you pointed WDP to 4.36?
If WDP does not pick up 4.36 this feature is disabled.Working of the backup was checked when implemented, checked the code and tested here myself. Works fine.
Fresh news is, forget me. It was directed at 4.36, but now it works fine for me too, nothing else than restarting WDP as far as I know… but I never know.
-
It’s a brand new mission made from scratch in 436.
I confirm your work-around : it works fine when I use your method, thanks !
-
@Falcas Thank you for the latest update!
-
@Falcas
I got this error after selecting TR_BMS_05_AAR.trnSee 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.FillMFD_AG() at WeaponDeliveryPlanner.cntDTC.FillMFD() at WeaponDeliveryPlanner.cntDTC.Camp_TE() at WeaponDeliveryPlanner.cntDTC.GetTEFile(String fName, Boolean blnBackup) at WeaponDeliveryPlanner.cntDataCard.SelectNewFlight(Boolean ByButton) at WeaponDeliveryPlanner.fclsMain.LoadTE() at WeaponDeliveryPlanner.cntDataCard.OpenFile(String fName) at WeaponDeliveryPlanner.cntDataCard.OpenMission() at WeaponDeliveryPlanner.fclsMain.mnuOpenMission_Click(Object sender, EventArgs e) at System.Windows.Forms.MenuItem.OnClick(EventArgs e) at System.Windows.Forms.MenuItem.MenuItemData.Execute() at System.Windows.Forms.Command.Invoke() at System.Windows.Forms.Command.DispatchID(Int32 id) at System.Windows.Forms.Control.WmCommand(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(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.8.4470.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- WeaponDeliveryPlanner Assembly Version: 3.7.19.208 Win32 Version: 3.7.19.208 CodeBase: file:///C:/Weapon%20Delivery%20Planner/WeaponDeliveryPlanner.exe ---------------------------------------- Microsoft.VisualBasic Assembly Version: 10.0.0.0 Win32 Version: 14.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.8.4488.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.8.4488.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.8.4470.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Runtime.Remoting Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.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.dll ---------------------------------------- BMSUtils Assembly Version: 1.6.3.46 Win32 Version: 1.6.3.46 CodeBase: file:///C:/Weapon%20Delivery%20Planner/BMSUtils.DLL ---------------------------------------- dbwdp Assembly Version: 1.6.0.3 Win32 Version: 1.6.0.3 CodeBase: file:///C:/Weapon%20Delivery%20Planner/dbwdp.DLL ---------------------------------------- System.Data Assembly Version: 4.0.0.0 Win32 Version: 4.8.4455.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- BMSLocation Assembly Version: 1.0.4.0 Win32 Version: 1.0.4.0 CodeBase: file:///C:/Weapon%20Delivery%20Planner/BMSLocation.DLL ---------------------------------------- System.Web Assembly Version: 4.0.0.0 Win32 Version: 4.8.4494.0 built by: NET48REL1LAST_B CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll ---------------------------------------- LzssManaged Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Weapon%20Delivery%20Planner/LzssManaged.DLL ---------------------------------------- LzssNative Assembly Version: 0.0.0.0 Win32 Version: CodeBase: file:///C:/Weapon%20Delivery%20Planner/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> <system.windows.forms jitDebugging="true" /> </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.
-
@jc1
This one is because of your Callsign.ini. Not mission related.
Don’t use an old Callsign.ini from 4.35, just create a clean new one. -
@Falcas Thank you. Your advice fixed it for me.
-
I’ve noticed that the Park charts are being rendered as blank pages because they are being created with no name, just the “.png” extension.
They appear in the “Upd keyboard” tool, but not in the DDS file (again, just a blank page )
-
@CriticalMass Mmmm ok, need to check that.
Thanks for the heads-up -
I noticed that Osan AB info (including airport chart) needs update. Currently it appears as having only a single runway while in BMS it has two runways.
-
@dcraig1 Not only Osan
-
@Falcas said in Weapon Delivery Planner released:
@dcraig1 Not only Osan
Is there a list? Checked the changelog, but that AFAIK, only mention changes in voice/spelling. A couple of these I’ve changed locally. I’ve also moved some charts/diagrams over from 4.36 charts. Would it be possible (in a future release), to use the 4.36 charts and the WDP charts as a backup? Annoyingly, the names are different (_Airport vs _diagram)
-
@CriticalMass 4.36 airfield won’t take much more attention at this stage (only important fixes) because we’re completely revamping stuff for 4.37…
So efforts will be placed on 4.37
-
@MaxWaldorf said in Weapon Delivery Planner released:
@CriticalMass 4.36 airfield won’t take much more attention at this stage (only important fixes) because we’re completely revamping stuff for 4.37…
So efforts will be placed on 4.37
Hi @MaxWaldorf , understood, but I wasn’t asking for BMS code changes and I’m with what we have at the moment.
You may or may not know, but I’m a bit of a pedant in regard to the charts in WDP - I’ve created a number of threads here, where I’ve created/updated maps to make them more aligned with BMS (4.35). I’m now really delighted that WDP can dynamically render missing charts (runways and parking spots), though not with the detail available in the AIP (?) charts.
There are still anomalies, and I will be addressing them myself, locally, but will likely make them publically available when I can. I’m even prepared to make myself available to help with the (grunt) work.
-
@CriticalMass said :…I’ve created a number of threads here, where I’ve created/updated maps… …make them publically available when I can.
Cheers, dude…!