Weapon Delivery Planner released
-
Un-installing the previous version has always been the case.
Most porbably you had already removed the previous version before trying to install the newer one, thus not seeing the message.Gr Falcas
-
E.g. for some reason, 3.5.4 didn’t find some DTC data (EWS, Radio/Nav, Systems) upon first start-up. I had to insert this data manually again, without being able to check in 3.5.3.
If this is the case, your previous callsign.ini was not correct.
What do you mean with manually insert the data?
You do know that WDP comes with a set of default values. You can find have these by loading the backup of the corresponding systems.Gr Falcas
-
Un-installing the previous version has always been the case.
Most porbably you had already removed the previous version before trying to install the newer one, thus not seeing the message.Gr Falcas
Until yesterday, I still had 3.5.1 installed though, along with 3.5.3. Had no issues while installing 3.5.3.
If this is the case, your previous callsign.ini was not correct.
What do you mean with manually insert the data?
You do know that WDP comes with a set of default values. You can find have these by loading the backup of the corresponding systems.Gr Falcas
It worked with 3.5.3, so don’t know what could have corrupted it in the 2-3 minutes between deleting old and installing new version?
I know WDP comes with default values, but e.g. for EWS, I use personalised dispense programmes, that were deleted or not recognised by 3.5.4.
-
Until yesterday, I still had 3.5.1 installed though, along with 3.5.3. Had no issues while installing 3.5.3.
It worked with 3.5.3, so don’t know what could have corrupted it in the 2-3 minutes between deleting old and installing new version?
I know WDP comes with default values, but e.g. for EWS, I use personalised dispense programmes, that were deleted or not recognised by 3.5.4.
I am not sure to which file you are refering at this moment. Are you talking about your callsign.ini or the backup files?
If you used the same callsign as before, WDP just reads your “old” callsign.ini and should have worked as before.
But if you used a different callsign, that will explain everything.If you are talking about the backup files and you have overwritten the default backup files that come with WDP (don’t do this, save it with a different name )
Than this explains it as well.This has been tested by multiple people the last couple of days and is working as it should.
But in the end… Does it work as it should now?
Gr Falcas
-
I was talking about the Callsign.ini, which I confirmed was the same in-game and in WDP. This was read perfectly in 3.5.3, but in 3.5.4 it failed. I lost radio/nav settings, EWS programmes and system settings (all cleared or reset).
The program works fine on following starts though…
-
Hi Falcas.
Just to say that you flight display of flying the Duch Falcon in your webpage is ABSOLUTELY AMAZING!
Congrats!… and thank once again you for WDP, of course
-
Thanks :mrgreen:
Pics are a couple of years old already… They need an update
Gr Falcas
-
Hey Falcas,
I installed the WDP today, but I’m having a few issues as only the Aegean theater shows up. All other theaters are gibberish or not listed and it throws me an error message when I try to change to another theater. (See pic below)
I checked that WDP was looking at the correct location for the .lst file.
C:\Falcon BMS 4.32\Data\Terrdata\theaterdefinition\theater.lst
list of all known theaters
terrdata/theaterdefinition/kto.tdf
terrdata/theaterdefinition/korea.tdf
terrdata/theaterdefinition/korea2.tdf
terrdata/theaterdefinition/korea3.tdf
terrdata/theaterdefinition/korea4.tdf
Add-On Battle For Balkans\Terrdata\theaterdefinition\BattleForBalkans.tdf
Add-On Battle For Balkans\Terrdata\theaterdefinition\StandAlone.tdf
Add-on Battle for Sinai\theaterdefinition\bfs2.2sp.tdf
Add-on Battle for Sinai\theaterdefinition\bfs2.2mp.tdf
Add-On Aegean\Terrdata\theaterdefinition\Aegean.tdfI spoke with a fellow simmer who was having the same problem. I tried to uninstall and reinstall with no luck.
Any thoughts?
Thanks,
DunnageEDIT: Uninstalled, restarted computer, installed, restarted computer and VOILÀ! Success! This is a great tool. I find new ways of using it each flight. Thanks again, Bryan
-
Hi Falcas, thanks for WDP I use it all the time!
I had to rebuild my PC after losing my RAID array, so I’ve installed everything from scratch. When loading the callsign.ini I get an exception in GetCallsignNavOffsets. I don’t think there are any defined in my ini file - it’s trying to cast as string to an int and I reckon it’s trying to use an empty string (since no setting exists for NavOffsets in my ini file). I think you can recreate the problem with just an new callsign.ini - I have the same issue with both the default Viper.ini and my callsign file.
************** Exception Text **************
System.InvalidCastException: Conversion from string “” to type ‘Integer’ is not valid. –-> System.FormatException: Input string was not in a correct format.
at Microsoft.VisualBasic.CompilerServices.Conversions.ParseDouble(String Value, NumberFormatInfo NumberFormat)
at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(String Value)
— End of inner exception stack trace —
at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(String Value)
at WeaponDeliveryPlanner.clsLoadDTC.GetCallsignNavOffsets(String FileName)
at WeaponDeliveryPlanner.clsLoadDTC.LoadCallsign(String FileName, Boolean Version)
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)Thanks,
W.
-
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.InvalidCastException: Conversion from string “” to type ‘Integer’ is not valid. –-> System.FormatException: Input string was not in a correct format. -
code tags might help? [ code ] can go in boxes like these [/ code ]
-
not sure what ya mean Blu……
-
Hi Falcas, thanks for WDP I use it all the time!
I had to rebuild my PC after losing my RAID array, so I’ve installed everything from scratch. When loading the callsign.ini I get an exception in GetCallsignNavOffsets. I don’t think there are any defined in my ini file - it’s trying to cast as string to an int and I reckon it’s trying to use an empty string (since no setting exists for NavOffsets in my ini file). I think you can recreate the problem with just an new callsign.ini - I have the same issue with both the default Viper.ini and my callsign file.
Thanks,
W.
Saving the DTC should fix this.
Don’t remove the NavOffsets from the DTC, they should be there.
Next release will have some more protection against this in the new code.gr Falcas
-
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************
System.InvalidCastException: Conversion from string “” to type ‘Integer’ is not valid. –-> System.FormatException: Input string was not in a correct format.Same bug as Wildcard.
Use the “continue” button, then go to the DTC tab and save the callsign.ini (even as it doesn’t show)
Found one little value without protection, is fixed in the next release.Gr Falcas
-
Hi Dunnage,
Very strange one you got there.
Nope, that list is not populated from the theater.lst.
The theater.lst is loaded by WDP, but used for other things.
WDP has its own database with all the theaters/countries/airports and areas ect. (already 916 different airport in this DB )
This is needed so WDP can also work stand alone and give you much more information.
For example, every threshold coordinate for every runway is availible and can be set as a precision STPT with a mouse clickWhy it did not read the database correctly the first time… hard to tell.
Gr Falcas
Hey Falcas,
I installed the WDP today, but I’m having a few issues as only the Aegean theater shows up. All other theaters are gibberish or not listed and it throws me an error message when I try to change to another theater. (See pic below)
http://i948.photobucket.com/albums/ad325/BryanBedwell/WDP1_zps4b894737.jpgI checked that WDP was looking at the correct location for the .lst file.
C:\Falcon BMS 4.32\Data\Terrdata\theaterdefinition\theater.lst
list of all known theaters
terrdata/theaterdefinition/kto.tdf
terrdata/theaterdefinition/korea.tdf
terrdata/theaterdefinition/korea2.tdf
terrdata/theaterdefinition/korea3.tdf
terrdata/theaterdefinition/korea4.tdf
Add-On Battle For Balkans\Terrdata\theaterdefinition\BattleForBalkans.tdf
Add-On Battle For Balkans\Terrdata\theaterdefinition\StandAlone.tdf
Add-on Battle for Sinai\theaterdefinition\bfs2.2sp.tdf
Add-on Battle for Sinai\theaterdefinition\bfs2.2mp.tdf
Add-On Aegean\Terrdata\theaterdefinition\Aegean.tdfI spoke with a fellow simmer who was having the same problem. I tried to uninstall and reinstall with no luck.
Any thoughts?
Thanks,
DunnageEDIT: Uninstalled, restarted computer, installed, restarted computer and VOILÀ! Success! This is a great tool. I find new ways of using it each flight. Thanks again, Bryan
-
Hi Falcas - another issue I’m afraid… looks like the EWS programs 2-6 are not being saved. Program 1 works fine.
-
For sure a knob’s question, but I find that the wind direction and the RWY in service are not in coherence with the informations in the briefing.:(
Is there a specific operation to do ? or is it a known problem?
Sorry if this has allready been answered, but I didn’t find any answer with the search box.Windblow
-
IIRC, WDP cannot read ATIS info properly if the weather settings are set to probabilistic. Try changing the settings to deterministic. This should work.
-
Hi Falcas - another issue I’m afraid… looks like the EWS programs 2-6 are not being saved. Program 1 works fine.
These kinds of things where to be expected when the reading/writing code is completely redone.
Even with internal testing.So thanks for the reports!!!
Fixed in the next update.
Gr Falcas
-
For sure a knob’s question, but I find that the wind direction and the RWY in service are not in coherence with the informations in the briefing.:(
Is there a specific operation to do ? or is it a known problem?
Sorry if this has allready been answered, but I didn’t find any answer with the search box.Windblow
This is not a problem at all. WDP does read the weahter data without a problem.
However, if you use “probabilistic” in BMS, the weather is changing all the time.
The word “probabilistic” should be changed to automatic changing weather.
The ATIS is a weather obsevation of the last 30min before releasing the ATIS.
So that the weather is not 100% as on paper… welcome to RL flyingGr Falcas