Pilot Archive
Thread: Problems with droid commands
i think its an actual bug in the way that the game tracks what overloads you have running or not and what numbers are affected....I've noticed when jumping from DS before, that my capacitor will still appear to be overloaded (ie have the extra power bar on my HUD) and recharge to that amount when I fire, but doesnt recharge at the overloaded rate.
What I suspect is happening is that the game is recording a "phantom" energy drain from EO4 on your reactor, and when you re-overload the reactor, the extra power isnt being recognized against the deficit it thinks is there, and soits still registering it as overdrawn.
Like the previous posters have said, though, pilot routines will correctly reset all your systems if this should occur.
Message Edited by droid327 on 07-08-2005 10:31 AM
SheenaBrelya wrote:
MasterSad wrote:
That is pretty much clear to me wat I can't understand is why running RO4 again does not help to reactivate ship parts...
How can you run RO4 with a disabled DI?
Shona
If droid interface is disabled I run pump reactor.
MasterSad wrote:
If droid interface is disabled I run pump reactor.
I do not know very much about Pump Reactor, so you'll have to tell me exactly what it does, including whether or not it is *supposed to* reset Droid Programs and what happens when you run it on a ship that is experiencing an EO4 bug.
You kind of caught me off guard, since you previously said:
"Not using any special abilities - only droid commands."
Shona
Message Edited by SheenaBrelya on 07-09-2005 01:21 PM
SheenaBrelya wrote:
MasterSad wrote:
If droid interface is disabled I run pump reactor.
I do not know very much about Pump Reactor, so you'll have to tell me exactly what it does, including whether or not it is *supposed to* reset Droid Programs and what happens when you run it on a ship that is experiencing an EO4 bug.
You kind of caught me off guard, since you previously said:"Not using any special abilities - only droid commands."
ShonaMessage Edited by SheenaBrelya on 07-09-2005 01:21 PM
What I ment is that I tried to follow advise posted in this thread and run a special command to get rid of the bug and it worked. The most suitable special command for that is pump reactor because droid interface itself can be involved (but many other commands help as well, such as eweapons, etc).I think what happens is that after a special command is executed energy consumption level of components reinitialised (recalculated) and everything returns to normal operation.