Updated to version 01.02:

• Renamed script categories to be more self-descriptive
• Renamed "Regular cruise sonar scan" to "Regular economic speed sonar scan"
• Renamed "Single sonar scan" to "Single cruise speed sonar scan"
• Added "Regular slow speed sonar scan" script
• Added "Regular 1/3 speed sonar scan" script
• Added "Regular standard speed sonar scan" script
• Added "Regular full speed sonar scan" script
• Added "Frequent flank speed sonar scan" script
• Added "Patrol routine plotting" scipt category
• Added "Regular 3'15" (x1) range checks" script
• Added "Regular 6'30" (x2) range checks" script
• Added "Regular 13' (x4) range checks" script
• Added "Regular 32'30" (x10) range checks" script

New scripts added:

• Regular slow speed sonar scan
  Runs at TC x128 in NavMap mode, every ~1 hour does a sonar scan at depth of 20 metres, then goes back to surface to slow speed (bell 1).
  Intended to use in open waters for searching contacts. Runs until stopped by user.
• Regular 1/3 speed sonar scan
  Runs at TC x128 in NavMap mode, every ~1 hour does a sonar scan at depth of 20 metres, then goes back to surface to one third speed (bell 2).
  Intended to use in open waters for searching contacts. Runs until stopped by user.
• Regular standard speed sonar scan
  Runs at TC x128 in NavMap mode, every ~1 hour does a sonar scan at depth of 20 metres, then goes back to surface to standard speed (bell 3).
  Intended to use in open waters for searching contacts. Runs until stopped by user.
• Regular full speed sonar scan
  Runs at TC x128 in NavMap mode, every ~1 hour does a sonar scan at depth of 20 metres, then goes back to surface to full speed (bell 4).
  Intended to use in open waters for searching contacts. Runs until stopped by user.
• Frequent flank speed sonar scan
  Runs at TC x64 in NavMap mode, every 15 minutes does a very fast sonar check at depth of 20 metres, gives you a short period of TC x1 to adjust course, then goes back to surface to flank speed and TC x64.
  Intended to use for course adjustments when chasing already heard target. Runs until stopped by user. Running speed can by very easily modified to suit your needs.

• Regular 3'15" (x1) range checks
  Runs at TC x64 in NavMap mode, and every 3 minutes 15 seconds lets you do your plotting on NavMap (doesn't do it for you).
  Only useful for so called 3'15" (3 minutes 15 seconds) method of determining target's accurate course and speed (for details check: http://www.paulwasserman.net/SHIII/).
  Runs until stopped by user.
• Regular 6'30" (x2) range checks
  Runs at TC x128 in NavMap mode, and every 6 minutes 30 seconds lets you do your plotting on NavMap (doesn't do it for you).
  Only useful for so called 3'15" (3 minutes 15 seconds) method of determining target's accurate course and speed (for details check: http://www.paulwasserman.net/SHIII/).
  Runs until stopped by user.
• Regular 13' (x4) range checks
  Runs at TC x128 in NavMap mode, and every 13 minutes lets you do your plotting on NavMap (doesn't do it for you).
  Only useful for so called 3'15" (3 minutes 15 seconds) method of determining target's accurate course and speed (for details check: http://www.paulwasserman.net/SHIII/).
  Runs until stopped by user.
• Regular 32'30" (x10) range checks
  Runs at TC x128 in NavMap mode, and every 32 minutes 30 seconds lets you do your plotting on NavMap (doesn't do it for you).
  Only useful for so called 3'15" (3 minutes 15 seconds) method of determining target's accurate course and speed (for details check: http://www.paulwasserman.net/SHIII/).
  Runs until stopped by user.

Known issue related to the newly added scripts:
In game clock and script clock are not perfectly synchronised, thus 3:15 minutes can be measured different by your Zentrale clock and by the script you use. Differences do not exceed 5%, so this only slightly affects 3'15" method scripts timing accuracy. Hopefully will be fixed by later versions of "Multiple UIs".


Download: Patrol Routine Scripts v. 01.02 by Avm [contains also v. 01.00]

Reediting this message after I realised I was editing wrong menu.cfg file. :damn:

Edited and works, thanks a lot. Still trying to work out what some of the other lines mean. Main concern right now - how to make the _sound_ make behave in TC > 32 as it was TC =< 32. Now all the sounds are "fast forwarded" in an irritating, non-immersive and unacceptable manner whenever TC > 32 in 3Dmode. Can't find an option to change that though.

Shameless bump with something useful in it:

When you use my "sonar check" series scripts with default game/TDW's mod settings, your TC does NOT drop to x1 when a contact is established (for me it silently drops to TC x32, which is much too much). Here is what I did to change this default behaviour:

Find your TheDarkWraithUserOptions.py file (located in \MODS\NewUIs_TDC_4_3_0_ByTheDarkWraith\data\Script s\Menu - a MUST READ), which you can edit with Notepad, find the line that says:

and make sure the value is True, i.e. the line looks like that after you edit it:

This will let some messages displayed in your message box drop the TC.

Then find the line that says:

and input any TC you want the game to drop to when message is received. You can set it to 0 if you want the game paused, other values must be generally powers of 2, i.e.: 1, 2, 4, 8, 16, 32, 64, 128, 256 and higher. Mine is 1:

The last step is telling your game on what messages it should drop the TC. Find the line that says:

The numbers are associated with records from menu.txt file. The default set that TDW put here is somewhat narrow - no idea why. I added MUCH more values to this line, and now my game does drop to 1 whenever something of significance happens. You can find out your own best set up by going through menu.txt, or you can just copy my one:

All lthe values I added are explained below:
Most probably some of this values are never used by game and do nothing, but this is not a problem for me.

So I have been trying to get this to work with TDWs UI which is of version 6.3 and I still have not seen any of the scripts show up. I can get krauter's and travelly's scripts going so I do not understand it at all. Any help would be appreciated.

he never updated them to the new version the mod expects. I had to make a fundamental change to the way the scripts were coded some versions back.

Thats ok. I was able to stumble upon travelly's scripts 0.3 which do some of what I was looking for. The reminders from this would be nice. I just do not know what is needed to update them else I would myself.

Only glitch I see with travelly's scripts (not really a glitch and not really his fault) is that I am now playing with real navigation and can not set waypoints, so I can not run his patrol script, which does a dive to check SONAR every hour, a turn to check baffles, then surfaces while performing an RtC command. The issue is it calls return to course and my navigator calls all stop since we do not have a plotted course. I am wondering if there is a way to add in a generic course plot. Basically, you would just set a true course as your plot and the return to course command would basically recall what course you were on. I do not know. I am just trying to figure out a workaround for this issue.

that's not going to be solved until I make the next MAJOR fundamental change to Automation - ability to define variables and call functions like I did with the tutorial feature. As it's going to be a daunting task of making this change it's going to take some time to do.

good spot Farinhir

When script runs a dive hydro check (o bearing) followed by a 90 deg starboard - hydro check then return to course.

This could be fixed by changing the "return to course" with a 90deg left turn and a set speed.

just delete lines:-

Return_to_course,0,0,0,0,0,0,5
Surface,0,0,0,0,0,0,5

and insert this:-

Set_new_course,-90,0,0,0,0,0,5
Surface,0,0,0,0,0,0,60

I will add a real nav search on patrol to v0.4

:yeah:

@TDW.
Take your time. I am thankful for the awesome work you have already done.

@Travally.
Good call. This should fix my headache for now. At least the one from in-game stuff, not the one from sinus pressure. ;)

Emergency dive script possible?
 

As I don't know very well how scripts are working, I'm not sure if what I have in mind is possible, but I'll ask anyway:

I'm thinking about an automated behavior that will initiate emergency dive and evasive maneuvers as soon as a plane is spotted. IRL, this was the job of the watch crew, and not that of the captain (he might have been asleep, or eating, or whatever). Relaying the 'plane spotted' message to the skipper and waiting for him to order the emergency dive would have wasted valuable seconds, so it was up to the watch crew to ring the alarm.

Can scripts replicate this behavior, so that the AI takes evasive maneuvers on its own?

See this thread here http://www.subsim.com/radioroom/showthread.php?t=174400

For now it can't run when a plane is spotted. You still need to run the script.

TDW has however posted notes in the automation txt that commands we have in the tutorial files will be added to automation.
When this happen - the script you discribe will then be possible:up:

Now that sounds promising!!

This is the sweep cammand from automation:-

If this could be used without having to be at the station - it could be used to continuously to fix the "my watch crew are blind" problem.

Also if this could be added :-

Then all sorts of things could be done.:up:

Thank you for your answer. I took the time and read the thread you mentioned, and found an idea that looks promising, at least to me. This is one of the posts by TDW in the thread:

Yes the script can either pause or pause the game on contact detected.

If a script can do something like this on contact detected, then imagine a plane evasion script activated at the beginning of the patrol, which stays "silent" until the plane is detected, then runs the series of commands. It's like some sort of "sleeping script" that only activates itself when a certain condition (plane detected) is met. After the evasion maneuvers are completed, the script ends and it is up to the player to reactivate it again when he resurfaces.Is something like this possible? Unfortunately, I know nothing about Python and working with scripts, so here I am bothering you and other people who know.:D

For this to work the sweep scope (uzo) would need to work when not at station. I don't know if this is possible.

When TDW added the message feature he scanned a radius around the boat for contacts and send a message etc.
If this same command could be introduced into automation, it could then be used to set conditions.

It would need to be able to detect height so as to determine ship or aeroplane. I know detecting speed is not possible - so height:06:

If all this could be done it would go a long way to getting better info from your crew. Some scripts could be set to take action and others could just flash up a message for you to take action.

Hello,

are these scripts usable with New UI 7.x.x? Or are they outdated, I'm not shure.:hmmm:

Paco.

Yes they are usable. My Automation class hasn't changed for many, many versions now :up:

Thanks! :up:

Who ever tryed to remake it for Magui interface mod?