04-10-22, 08:14 AM
|
#5
|
|
Argentinian Skipper
Join Date: Jul 2009
Location: Somewhere between Buenos Aires and the Bungo Suido
Posts: 5,128
Downloads: 3215
Uploads: 0
|
fitzcarraldo has made a Best of SUBSIM nomination.
Category: Post: Very helpful member
Forum: SH4 Mods Workshop
Posted by: KaleunMarco
Nominated Post: 194305NarwAttu.mis
Quote:
Quote:
Originally Posted by propbeanie
Yes, we do have that KM, thanks. You sent it via PM. Like a few other missions, it is "sharing" a MapZone for both an Objective and a Trigger, which usually just makes the Objective impossible to complete, but a CTD would not surprise me. Does it happen when you are about 12nm from the "Wait" location symbol? :salute:
|
Quote:
Originally Posted by KaleunMarco
my apologies, i couldn't find the exchange in the PM box either. may be i deleted it (it seems like i am always at 99% utilization :oops:).
the CTD happens a bit further than 12 nm from the Wait Pennant Symbol...more like 20-25 nm.
can i remove the "holding objective" without ruining the other objectives and the mission?
addendum: apparently, removing the Hold Area Objective, Triggers, and Zone does not make this mission playable. it still CTDs as we close the landing area.
|
ok....did some additional research and determined that we can get to within approx 34 miles of the first drop zone before CTD (63 km).
so, what mission condition occurs when the user-boat gets to that point?
this is the key to the problem.
i have no idea.
+++
i noticed what could be an anomaly. there are two APD's defined in the mission. one starts life on May 11, 1943 and the other starts life on July 1, 1943. was this purposeful?
++++++
i removed all references to the Holding Area because the first occurrence of the CTD happened as we entered the Holding Area. - made no difference.
changed the entry date of APD#1 to match APD#2 - made no difference.
noticed that the mission briefing was greater than 900 characters. abbreviated a few words to get is under 900. - made no difference.
noticed that the waypoints of APD#2 caused an error message within the Mission Editor. Fixed those. - made no difference.
|
|
|
|