Just thought I should mention that, after trying this in X3:TC, I got some unwanted results, imo:
- I can understand this being a great script for huge ships, but flying a fighter, most of the time (by far) you don't really need it, but it does impose itself nevertheless. It makes no distinction between ship types. Undocking from a station with a fast M5 and automatically racing at maximum speed right away, straight through anything and everything, really is a frightfull experience every single time. Especially when going straight through the entire interior of a station. I know that this is exactly the point of the script, but the least you can say is that it lacks some finesse in this regard.
- I use a free-jump script (like I'll bet many players do), which lets me jump straight to whatever location in a sector. This is especially handy when you like to end up at an exact spot, say the place where you 'd like to place a sat. When finishing the jump, this script forces the ship (like stated in previous point too) to be at maximum speed right away (forget about the accelerating part). By doing so (you can hear me coming, right?!) the ship clearly 'overshoots' that sweet spot you were aiming for.
- On a more technical level (I bet the most important point), the script seems to devour framerates in my game, resulting in freezes after a short while. I could not play for longer than 5 minutes before getting a freeze of a second or 2. It must be related to this script, because as soon as I turned it off, the problem too disappeared.
I must say that I almost always love the scripts from Gazz. Can't win all the time buddy, but please let me take this opportunity to thank you for many, many very fine scripts you've created, of which I use several all the time. This one isn't for me (in my TC-game!), but undoubtably it has all the uses in other games.
On a sidenote for people wanting to turn this script off again, after having installed it:
I understand that trying to actually uninstall (or even delete) it isn't the best way to go about it, rather than just turning it off (as I did). I can state that this went great in my game, following the advice of DrBullwinkle.
DrBullwinkle wrote:Add "return null" to the top of subroutine Undocking.Watcher.Script:. Around line 32 of setup.gz.safe.undocking.
Thx Gazz and thx DrBullwinkle (seems like I have to thank you a lot these days

)