Japanese Type 13 radar

[michaelm75au]

For those who want to fix the type 13 radar, here is a program that will change the Penetration of device 139 to 500.

**** This only fixes SCENARIO file not the save file. The change will only apply on a new game.

If you do wish to run this, please backup your old wpd###.dat files before applying.

1. Download attachment file in the post #3 to PC, renaming the file to fixtype13.zip. Unzip the file into a directory.
2. Open a Dos/Command window and go to the directory where you saved the program.
3. It would be a very good idea to save the old wpd###.dat file before running this program.
This program has only been tested on XP.
4. Type in fixtype13 /i /s#
where /s# is the scenario you want to update, and /i tells program to look in c:/Matrix Games/War in the Pacific/Scen. You can supply an option /d followed by a directory if the game was not installed in the default directory.
5. If you feel brave, you can leave off the /s# and it will update all 1-16 scenarios.

C:\matrix games\war in the pacific\extras>fixtype13 /i
WITP fix device 139 (Type 13 radar) utility - Version 1.0
Updating scenario # 1
Dumping File C:\Matrix Games\War in the Pacific\scen\wpd001.dat for Devices
Device 139 (Type 13 Radar ) Penetration was 500 is 500.
File has been updated successfully.
Updating scenario # 2
Dumping File C:\Matrix Games\War in the Pacific\scen\wpd002.dat for Devices
Device 139 (Type 13 Radar ) Penetration was 500 is 500.
File has been updated successfully.
Updating scenario # 3
Dumping File C:\Matrix Games\War in the Pacific\scen\wpd003.dat for Devices
Device 139 (Type 13 Radar ) Penetration was 0 is 500.
File has been updated successfully.

[DuckofTindalos]

Very cool! Thanks, Michael![8D]

[michaelm75au]

This attachment contains the same program but with additional libraries builtin.
The other program required certain DLLs which may not be present on your PC.
[They are on my PC but they come with the compiler[:o]]

This attachment needs to have the .TXT removed as it is a zip file. Unzip the program, and follow from step 2 above.

Michael

[FeurerKrieg]

Great! Many thanks Michael! [&o][&o]

[Charles2222]

I can't download that link. It says the site is unavailable or cannot be found.

[michaelm75au]

1. Click on the Attachment in post#3
2. Click on the file name in the window
3. Click on Save and the file name comes up as something like "149AF222F8A94E7986F850749A780CAD.zip"
4. Type over the name as fixtype13.zip and press Okay. File will be downloaded.

Just tried it and it worked okay.
Mcihael

[michaelm75au]

The Type 13 radar was correctly defined in my copy of WITP (v1.0) when I originally bought it.

Sometime during the several patches, the "penetration = 500" on the device got zapped.
So putting it back to the original setting is correct IMHO.
And does not take the guys away from dealing with any coding issues.

Michael

[Charles2222]

Okay, thanks very much. I was using 'save as' and it wasn't working like that. I tried the more conventional left-click method too, but I let the download action when you click on the attachment make me think it had downloaded, which of course didn't show up in my download directory (I still had to click the file to get the download as you said). I don't know what it is about downloading like that, but every time I screw it up thinking it's some sort of download counter and that I don't have to click anything.[:-]

[Charles2222]

Interesting, I already had fixed that. Something tells me that setting that to 500 doesn't fix it though. Sorry I can't be more specific, but perhaps it was because I was having trouble saving it in the editor, though I do wonder if that was the problem I found because apparently it had been saved.

[michaelm75au]

IIRC, 'penetration = 500' is the trigger for air-search.
This is really the only difference between the Allied air-search radar and the Japanese Type 13.

Michael

ORIGINAL: Charles_22

Interesting, I already had fixed that. Something tells me that setting that to 500 doesn't fix it though. Sorry I can't be more specific, but perhaps it was because I was having trouble saving it in the editor, though I do wonder if that was the problem I found because apparently it had been saved.

[pauk]

greetings michaelm and thanks for help!

however, i would ask is there any chance that this fix would be included in next patch, because my computer skills are poor and i don't dare to do it manually (in fact i didn't change anything from stock game - maps, art...etc, due to lack of computer skills)...