25 replies to this topic

[Gumballthechewy]

Personally I'd rather just make the fleet respawn each battle to prevent that.

Sometimes I just use raiding parties to slip in under the fleet and take control of the planet which destroys all space stations, then I'll build a couple planetary turolasers and then bring in my fleet.

Aside from the obvious unplug the internet and kill all other possible processes (windows, too), no not yet.

Damn...

[a.fake.name]

I've done that too before gumball, however if I have a world with a salvage bonus I prefer to fight both battles and get as much scrap credits as possible.

You can easily make 10k-20k depending on the fleet the world has.

[NYSNDGUY]

You can do that now if you change the "<pay_as_you_go>True</pay_as_you_go>" value in gameconstants.xml (C:\program files\lucasarts\star wars empire at war forces of corruption\mods\phoenix rising 1.2\xml\gameconstants.xml by default) to false. I've found it helps a bit (not a ton, but a bit) with lag as well.

Anyone know why this value was set to True for PR? I went back and looked at the FOC version of gameconstraints.xml, and it had this value set to False already.

[a.fake.name]

I have no clue, honestly if it didn't cause so much lag I wouldn't really mind it so much.
It was nice in that you could start something and just take an extra week or so (ingame week of course) to finish it rather than having to save the cash up entirely before starting, but at the same time it required careful management of funding to work best, otherwise everything comes to a stop until you get more income.

[evilbobthebob]

Yeah in our current development version we've changed back to the default "pay at start of construction" method from vanilla, since we found it easier to balance and easier for the player to plan ("oh I can make 2-3 cruisers this galactic week")

Edited by evilbobthebob, 08 July 2014 - 01:02 PM.

[a.fake.name]

Well changing 1.2 back to the default pay method has made it a whole new mod for me, since it's killed off 95% of the lag, so I hope it carries over from your dev. version to the next version.