Pilot Archive
Thread: Trouble with WO4 and EO3
Though I know Rapax is right, the week after WO3 is fixed this board is gonna be chock-full of people crying and threatening to quit, wanting to use channel force to power their weapons...etc etc.
ROFL..man you guys hate Jedi, guess I should keep quiet about being both triple Ace and Jedi.
Some guy asked me if force cloak worked in DS the other day. I asked if he was a Klingon, he said no, I told him he would have to re-roll his toon to klingon if he wanted force cloak to work in space.
Mortelli wrote:
I know this thread is a little dated, but AzzixxSWG is right.
Yes, very dated. No, AzzixxSWG is not entirely correct.
The bug is with EO4, and it is that the 10x Drain sometimes sticks after you die or leave DS. Both of those things should reset all Droid Programs, and they properly reset everything else, including RO. When EO4 sticks, it has a tendency to shut the ship down. The right "fix" is to run /pumpReactor, /EWeapons, /EThrust, or /EShields. Those cover all three porofessions and each will reset droid programs either when they are run or when they are done running.
No one should "expect" to run all the highest level OLs possible. There should be pros and cons of each, with different types of ships choosing to use different combinations of OLs. Fixing WO3 might even lead to this. Until then, run some combination of RO3/RO4, WO3, EO3/EO4, and CO3/CO4.
Shona
two things:
1. if you run your overload commands (with the exception of reactor overload) after you get into DS, you can exit without re-running them. if you use reactor overload, you need to run it before you enter, and the rest of the programs afterwards to accomplish the same result. i'm not entirely convined this is a bug, although yes, the damage caused by the overload is repaired on leaving. however, if that's a bug, so is repairing the damage immediately after running the programs at a station. if both of those are bugs, i'd say consider not fixing them, astheynegate substantial downtime, and prevent you from incurring decay due to network disconnection after using the programs.i would agree that dying in DS, and having a program running after you spawn, is a bug, but my experience with that has been sporadic.
2. wasn't WO4 actually broken? i thought there was talk of it not doing the proper amount of damage?
Ducimus wrote:
FataIity wrote:
use WO3 for now.
Oh its gonna rock the foundations of the game when thats fixed.
Ill have plenty of popcorn ready and waiting when it does to watch the show
Except for those of us who've been planning for it.
Mortelli wrote:This has nothing to do with DS or dying with me. I was sitting right outside the Naboo station just trying to get some of the new programs to run. I would hit EO4 and it would partially run (I guess). My speed would get up 980ish using EO4, but I can hit 1014 with EO3.
This works as intended (and properly in fact). As the energy drain grows 10 times, the reactor (with RO I assume) could supply the engines power needs 100%. With the tremendous increase while the engine power increases 1.4 times compared with no EO, power support goes down to X %, making it slower overall than using EO3 with 100% power. It might be cured by providing more power by a higher output reactor and/or running a higher level RO and/or using a smaller RED engine or reverting to EO3.
Mortelli wrote:
And just from hitting EO4, my 2nd weapon became disabled (low power warning). Landing doesn't clear re-enable the weapon. Removing and reloading the weapon doesn't clear it. Repairing doesn't fix it either. You have to unload every damn component and redeed your ship. I played around with other combinations such as RO4 first. And something would always get screwed up (in one of those iterations it was the droid interface that got disabled).
Why components are disabled is explained above. The proper way of fixing these would be to use the reset programs. Yes, they are implemented from the very begining and it all makes sense. I know that random components go out when power gets low, including the droid interface. After all, tweaking is dangerous and you have to do it once to make a setup work. Ever heard of MandalMotors, SoroSuub or Blissex recommending overcharging their components? The moral is the following:
Energy management is just as much part of making a new setup than managing mass, parts and performance, in fact, it is PART of it.
Mortelli wrote:Now if you guys think that is working properly, then my only guess is that you are programmers for Sony.
I am not affiliated with any part of software industry or trade, unless my support for some GNU projects count so. But -aside from WO3, that is bugged to our advantage- everything works properly in term of the overload/overcharge programs. One exception is that they do not reset sometimes exiting DS, but it might be easily cured by using any pilot (not droid) command.
KaylBreinhar wrote:
Ducimus wrote:
FataIity wrote:
use WO3 for now.
Oh its gonna rock the foundations of the game when thats fixed.
Ill have plenty of popcorn ready and waiting when it does to watch the show
Except for those of us who've been planning for it.
what if it's an easter egg? then what will you do? i'll cry. got it all planned out.
Dragon942 wrote:
KaylBreinhar wrote:
My attitude is...
...if you have to use RO4 *now*, you didn't spec your ship right. RO3 is a no-decay 60% boost.
I just find it amazing you're actually able to RUN WO4 - must be a one-gun ship.
Who cares about decay? 30k Prestige = no decay for aces. Another 30% out of your reactor is a HUGE difference. If you aren't using all the mass and energy you possibly can, you probably didn't spec your ship right.And who says they run WO4? I just said that it was absolutely not bugged and working exactly as intended.
Anyway, people use crafted reactors because you can easily replace them...
This has nothing to do with DSor dying with me. I was sitting right outside the Naboo station just trying to get some of thenew programsto run. I would hit EO4 and it would partially run (I guess). My speed would get up 980ish using EO4, but I can hit 1014 with EO3. And just from hitting EO4, my 2nd weapon became disabled (low power warning). Landing doesn't clear re-enable the weapon. Removing and reloading the weapon doesn't clear it. Repairing doesn'tfix it either. You have to unload every damn component and redeed your ship. I played around with other combinations such as RO4 first. And something would always get screwed up (in one of those iterations it was the droid interface that got disabled).
Now if you guys think that is working properly, then my only guess is that you are programmers for Sony. 