SM12_PALAU_GAUNTLET.rar
 

Can any one fix this mission ? It crashes !

Link to download: http://dodownload.filefront.com/1234...b7e953ce00a665

Originally Posted by I'm goin' down http://www.subsim.com/radioroom/smartdark/viewpost.gif
SM12 Palau Gauntlet. I have another SM12 Battle of Subiyan Straight. Could that be the problem? It crashes at different times, usually after I sink the patrol boat. One time I think it did not crash but I was far behind the mission schedule and the Yamato had sailded away, so I failed the mission. That is all I can tell you.:damn:


cdrsubron7 " Palau Gauntlet was made by Hazelwood." He seens not to be of Subsims board, perhaps UBI. ?

Someone with a 1.4 install may be able to figure out the problem. It won't open in my 1.5 mission editor. I looked over the file with notepad but didn't see anything that jumped out as being wrong. It may have something in it that is not in 1.5.

Here is a link to the web site of Hazelwood and contains an email link.

http://www.wolfwillow.com/nu/westwin...HIV/index.html

At least this is the link he gave in this forum.

Peabody

Will give it a shot Thxs. peabody
 

I am trying to get SM12_PALAU_GAUNTLET.rar To run on 1.4 version + FOTRS

If you have 1.4 it should open in the mission editor. Try with no mods enabled. That mission was made with 1.4 I am almost certain. It may not run with any mods enabled if the mod change any ships or bunkers since those items are added in the mission.

Peabody

That could be the Goat.:shucks: I will report back.:salute:

Download;http://www.wolfwillow.com/nu/westwind/Simulation_Gaming/SHIV/Downloads/SHIV/
 

Briefing:
You are captain of the "Haddock", urgently diverted from a routine patrol to ensure safe passage of the fleet carrier "WASP" approaching Palau from the northeast on its way to the Celebes Sea. It has just been learned the super-battleship "Yamato" and a heavy cruiser Mojamie will attempt engaging the "wasp" southeast of Koror. You are approaching Palau from the west and must pass through Malakal Harbor to your final way point in vicinity of where the "Pyle" is expected to run into trouble. There you must do your best to thwart Japanese plans.
You are not alone. The battleship "Mildred P. Braithwaite" and a cruiser are speeding to the rescue but may arrive too late to prevent disaster if you do not first engage the "Yamato". The "Pyle" has an escort but it's no match for a battleship. There's an allied patrol operating off the east coast to act as a diversion and this may prove helpful in dealing with the enemy destroyer you may find there.
Note that Malakal Harbor is very shallow and periscope depth is impossible once you come over the reef. Your boat will, therefore, be exposed to Japanese shore batteries. Be careful as there will be a lot of sniping and not much you can do about it. Consider crossing parts of the harbor partially submerged if things get too hot. If you average 10 knots or thereabouts you should arrive on time.
Your contribution will be rated a success if the "WASP" gets past the southeast entrance to Malakal Harbor. There is no way to associate a goal with any unit other than your submarine so judge for yourself if you have saved the "Wasp". Use the map views to determine what has become of the "Wasp" and reward yourself appropriately if it is sailing off to the south.
Very nice night visuals if you use the camera views. If you have time to look,Also note; there is a Sub Net.You will be headed South to intercept "Yamato".At The first gradient to deep water, blow ballast/flank to get over. You are still in-range of shore batt. dive ! This mission works for SH4 version 1.4+ FOTRS.,Extract SM12 Palau Gauntlet file, place it in game, Data/Single missions folder, good to go.

so this wont work in version 1.5 and if i understand correctly there is no way to make it work correct

lt commander lare

deducted from previous posts.
 

It seems that version 1.5 mission editor will not open version 1.4 missions. have not tested same. suspect it would need to be resripted w/1.5 ME.

can you do that for us so it will work in 1.5 and if you dont know how can you ask someone that might and maybe they can get it to work


lt commander lare

Well, the good news is that the mission will open the the ME from v1.4. The bad news is that I'm not sure if it can be translated into a v1.5 mission that is playable. I've contacted a friend who is knowledgeable with the files of SHIV and asked for his help. After he replys back I'll let you guys know what I find out.

thanks cdrsubron7 for working on this and devoting your time to try and fix this along with peabody and everyone else that has been trying as well


lt commander lare

Just a little update for everyone.

Palau Gauntlet does open in the V1.4 ME. I have found alot of inconsistencies in the settings and things. Try to isolate the factors that let it play in v1.4 but not v1.5. The mission plays very well in v1.4 (no mods), I tried it last night.

@Peabody

Maybe you can answer a question for me. The starting dates and versions dates on all ships in the mission did not match. The starting date of the mission is January 1, 1944. I've always thought that dates for all ships in a mission had to match the starting date of the mission. Is this true or not?

I plan to fool around with it some more tonight after I get home from work. I'll keep you guys posted. :yeah:

The starting date of your sub can NOT be after the starting date of the mission, your sub must be there when the mission starts. There was a bug, I don't know if it got fixed, but I think it was the Gato that the version date had to match the starting date or you would not be able to select it. You could write the mission with the Gato but if the version date didn't match you got a different sub.
On the rest of the ships, they do not have to match, except the version date should not be 1945 on a 1944 mission. The version date is there in case the ship had any upgrades to it during the war. I don't even think it applies except for the BB Tennessee which has a 1938 version and a 1943 version.
The start date is there in case you want to start the ships before or after the mission starts. If you just leave it alone they will start when the mission starts (provided they were available at that time) If you put a date after the start of the mission they should spawn at that date.

If you have a start date BEFORE the start of the mission they start when the mission starts UNLESS you check "evolve from entry date". For example, usually you are writting a 'specific' mission and you want it to be the right time and place. But suppose you want to write a mission that has some unknown in it for yourself. Normally if you write a mission you know exactly when and where the ships are. But if you create a Jan 1944 mission put some ships in with waypoint going all over the place and then loop them back to waypoint 1 (or any waypoint so they continue in a big loop) you can set them to Nov 1943 and uncheck "delete on last waypoint" and check "evolve from entry date" and the game will start them moving in November of 1943 and calculate where they should be when the mission starts in Jan 44. So you won't know where those ships are because they have been going in a big "loop" for two months and could be anywhere. You will still know where the waypoints are but not 'specifically' where the ships are. So it will add a little challange for you as well as the other that play it. And if you add in some "alternate paths" they will randomly take different paths making it a bit harder to find them. So even though you wrote the mission, you will not know exactly where they are.

So a long explanation of a simple answer, no the ship start date does not have the match the start of the mission, they will start when the mission starts. Only your sub has to match.

Peabody

Thanks for the explanation, Peabody. I actually learned some things about the ME that I didn't know before. :salute:


As for the mission, sofar I haven't found anything between 1.4 and 1.5 that would make it crash. It may be that the changes made in 1.5 don't work with the older files. But I'll keep trying for awhile.:D

Well, sorry to say I have to admit defeat in this one. I've tried the things I know and no success. The mission keeps crashing at almost the same point every time. And replicating the mission into the v1.5 might be difficult as the mission is rather intricate in it's design.