Wierd, seems like there shouldn't be japanese ships out there.

hey D empty your mail box buddy
 

Tryed to send you a link to a file but it says your mail box is full

Does it have to do anything with this line?

CurrentSDepartureDescription=-1.89576e+007,2.54882e+006,242.189

I noticed that too. The original 1.3 departure is:

DepartureDescriptionOut1= -18957616, 2548824, 242.189346

What I wonder is why you need 3 numbers to locate "X" and "Y" on the map.

But I don't think that has anything to do with it as it worked fine going on other missions. This is the first time I have seen Trigger Maru CTD. I gave up that start time as I kept getting a mission in the same location and always CTDed about the same longitude.

Sorry to get back to you so late Ducimus.

I downloaded it 2 times on WiFi and got the same problem. I downloaded it again at home on cable and works fine.

Go figure?

Thanks,

Doom

Ooops, cleared it out. Should be able to PM me now.

Sry, I cant find the proper cfg file or the line I should change- where is it please?

thanks
RM

You need to use minitweaker or S3D on the DC zon file.

I have a question on the Gato availability for the Asiatic Fleet in career mode. It shows that they are not available until Dec 1943, but that the Balao is available in Aug 1943. Is it a mistake and the date should read Dec 1942 for the Gato? I'm aware of several Gato's that started patrols from Fremantle before Dec 1943. Thanks.

Gus

Why is the scene.dat of TM1.5 older than the one from TM1.4?:hmm:

Only thing i can think of, is maybe my computers internal clock is off. I had to reset my CMOS a few times a while back, and i probably forgot to adjust the time on my machine. Otherwise it makes no sense, because 1.5 has Leovampire LBO mod intergrated into the scene.dat

Never trashed the mod, I said it is not for me. Too bad you wigged out on someone having a different opinion.

Seriously, if the keyboard layout is the primary beef, take the 10 minutes it would require to mod it to your liking, lol.

tater

Problem Found and cured!
 

I located the problem. It was a missing audio file called for by an event.ini file for one of my radio stations. This file was supposed to play at 19:00 on June 15, 1943 (see above CTD time and date). I wasn't using the radio but that didn't matter. I discovered this when using Digital_Trucker's "Radio Station Manager" program. It checks all the radio station's event.ini files and shows any mistakes in them.
After correcting the mistakes including replacing the missing file it didn't CTD anymore. I tested this by removing the file again and it CTD'ed at the above time.
You may want to check your radio station's event.ini files for mistakes if your getting CTD's.

Just getting the new version now :yep: Very nice work :up::up:


RDP