Engines don't respond

[jason210]

I got caught out on a mission because the engines refused to repsond to telegraph orders. The CE said "Cannot comply" and when I went to his station, and tried to operate the telegraph from there, still no response.

All this was after I'd been attacked by a destroyer on the surface. The repair crew fixed everything 100% and hull integrity was 92%. Anyone know what's wrong?

[benetofski]

The only reasons I know for this are either:

1. Not enough crew in the associated engine room!

2. Damage or flooding awaiting repair!

[Shin]

Be sure that your not on "recharge mode" for the batteries, this will cause you to just sit while the diesels spin up the batteries. Normal running leaves you 1 prop for propullsion. Not sure if you can set the diesels to not charge the battery when surfaced; which is kinda gimp.

[FAdmiral]

I had this happen a few times myself. Come to find out that I
had no waypoint course set. I set a waypoint course and
the boat suddenly came to life and started moving...


JIM


PS. Now I always have a course set and just tell the Nav Officer
to resume the previous course.

[Col7777]

I too have had this, I found it does take the engines a minute or two to fire up again once stopped, this can be critical I know if in a situation.
As mentioned above, no way-points or not enough crew in the engine room, another quick fix is press TC (a little) and they usually fire up.

[panthercules]

There has also been a long-standing bug of sorts associated with this that you may have been experiencing - it happened to me again last night, for the first time in a long time, and fortunately I wasn't being attacked at the time. When it happens to me, there is never any other apparent cause (i.e., engine room fully manned and green barred, been maneuvering by rudder without course plotted for a while just fine, no damage, etc.).

I have always been able to "fix" it (get the engines to start up) by clicking on the engine telegraph to set some reverse speed, then forward again - one or two times doing that and it's always fired up for me.

I haven't seen any posts about it for a while, but there were several over the past few months and I never did see any real explanation for it (personally, it seems to happen to me mostly after I've stopped my engines on the surface, which I don't do that often as compared to stopping the electric motors underwater for hydrophone checks - so I suspect maybe they modelled something like a re-cycle time required to restart diesel engines - doesn't seem too likely, but who knows) but the above "fix" seems to have worked for most folks.

Good luck and good hunting!

[jason210]

Thanks for the input.

The engine was crewed up, btw. I never tried reversing the engines, though, as a fix.

As to the course thing, I thought direct navigation orders overrode course orders? All this happened underwater, after a dive.

[america person]

diesals cant be run under water unless you got a snorkel