Weapons Delivery Planner / Constant DDS problem.
-
Hello Forum.
Unfortunately, I’ve become familiar with DDS files becoming corrupted when trying to import an image into the WDP.
No doubt, many members have encountered the “Unhandled Exception” message.
So, I find the faulty DDS in “TerrData Objects KoreaObj” in 4.36, its size will be other than the required 2,049.
Then I Copy/Paste an uncorrupted version from 4.35 and as if by magic, problem sorted.
Until now.
I wanted to import the ground chart for Birgi in the Balkans theatre into the WDP.
But no! “object reference not set to an instance of an object”
All DDS files in 4.36 are correctly set at 2,049. So, what now?
Forgive me for asking, but could there be a coding error in the WDP?
It’s as if the WDP is learning from AI SAM operators in BMS, constantly changing to evade detection.
Any Ideas?
Bayonet.
-
This is totally unknown to me and never happend here. Actually the first time I hear about this, or at least with these details.
Pretty unlikely WDP saves at 2049 as this can’t be send off to be saved as DDS. And in this case the DDS would never be saved at all.But would be handy to report the WDP version you are using.
-
-
@Bayonet said in Weapons Delivery Planner / Constant DDS problem.:
So, I find the faulty DDS in “TerrData Objects KoreaObj” in 4.36, its size will be other than the required 2,049.
In case you mean size as in kb… well there is no required file size at all.
There is only a pixel WxH which should always be 512, 1024, 2048, 4096 and so on -
Hi @Falcas
Yes, my reference to 2,049 refers to the kb.
Previously, I regarded a DDS kb value of less than 2,049 as an indication of corruption.
As I mention above, I copied and pasted a DDS with a kb value of 2,049 from 4.35 into 4.36 and it worked.
But, you say the kb has no relevance.
I have, however, been supplied with a fresh set of DDS files by a friend and the WDP is again active.
Thanks for your reply,
Bayonet.