BigD, it's definitely possible that some operations are faster than they were, and I'd like to keep things running at about the same pace as is normally expected. When I optimized the system, it sped everything up. Then I started adding delays to every operation so that it runs at the excepted speed (and will continue to run at the same speed regardless of the speed of CPU and network). But I defined the speed of every operation by a simple callibration. Any operation, when repeatedly done, should pull on average 5% CPU on my test machine. There was no easy way for me to benchmark this against the actual speed of operations in the current game. So wherever something seems too fast, bring it to my attention and I'll slow it down by increasing the associated delay.

In this case, when you say "buydown", there are several delays that are involved in the process. It would be useful to identify the various actions and decide which one to increase the delay on so that only this action is effected and it doesn't unreasonably slow down other actions that you don't feel are running too fast. For starters, please give me the specific actions involved here and we'll go from there.

Buydowns - Lifts off planet, ports at port, option(haggle/no haggle), buys product, lands on planet, drops product.

Mover - Takes product/colonists from one planet and moves it to another.

The common denominators are lifting/landing on planets OR leaving product/colonists.

Not sure what happened, but I just witnessed about a 30 sec Pause.
I was in mid-express warp:

Auto Warping to sector 12850

Sector  : 12850 in uncharted space.
Fighters: 1 (belong to your Corp) [Defensive]
Warps to Sector(s) :  24685 - 24817

Auto Warping to sector 24685

Sector  : 24685 in uncharted space.
Fighters: 1 (belong to your Corp) [Defensive]
Warps to Sector(s) :  3052 - 6728 - 9608 - 11382 - 12850 - 28431

Auto Warping to sector 6728

Sector  : 6728 in uncharted space.
Fighters: 1 (belong to your Corp) [Defensive]
Warps to Sector(s) :  6980 - 12456 - 13397 - 24685

Auto Warping to sector 13397

Just froze entering 24685 hanging on the Sector : 24685 line.
It happened at about 6:45pm cst, or 7:45 gametime.
Hope this helps.

Let's try turning off the bug scanning software and see if that indeed is the cause of these pauses.

They are still happening quite frequently. PITA Hehe...

Isn't it easier to test the game if you had more than 3 player and more than 1 corp.... just sayin

Of course, can you bring more players to the game? I'm open to resetting HHT 2010 Replay or any game edit you and your teammates would care to play.

I wouldn't bring players to that game ever.... worst edit ever... but let us know we will play anytime... low turn 1000-1500 turn.... maybe a time limit. beta testing is fine with us... but different edit...

Cruncher: They are still happening quite frequently. PITA Hehe

I wish it was happening frequently to me. Or at all. That would make it possible to actually debug it. I have yet to recreate this pause once locally or remotely. PITA indeed ;)

Just as an example, Crosby shows, and I've seen other reports of this, that simply moving from sector to sector can cause the pause. That should be easy to recreate. I put up a bot that just moved around space to see if I could catch a pause. I had a trap to report any pause longer than a second. Never got one in an 8 hour run.

There's nothing worse than a bug that only shows up for your users...

Yeah, and I cannot pin-point a specific activity that's triggering it. I do know when I experience it, others in the game do as well.

Well, if that is definitely true, then it points me toward TWGS rather than TW. Any pause TW causes would probably only effect one person. But if TWGS has an issue, it would effect several people.

I made a major change to the version I posted at about 5 pm tonight. I was routing game events through TWGS. I've changed it so all events go directly to games without having to pass through TWGS, and that will lighten the load that TWGS has, allowing it to focus entirely on routing data from TW to the player. Let me know if you see any difference.

If it's something that's happening frequently enough, then that's a good thing. I can start to troubleshoot some systems to see if the problem goes away. We can probably test one system per day to get a feel for whether there's any change. That'll help me narrow it down at least.

OK good. If you can open the Classic game, slot A. I have some testers asking for a slower, low turn, time limit game.

I'd suggest 1250 turns, 100% port regen, and bang ports at 60%, 6 hour time limit.

I think we're going to continue the HHT 2010 Replay just to develop the planets to see what SG had in mind.

And I'll pop into one of the unlimited turn games again, maybe try to beat up Big D in game L.

Game A is set to open at 7pm this evening.

Big D and I experienced a pause that lasted about one minute in game L this evening, around 10pm.

We were just sitting and chatting on fed com.

You need to determine what process, if any, it was that caused the lag. It could be TWGS, it could be something else.

http://technet.microsoft.com/en-us/libr ... 42546.aspx

http://sourceforge.net/projects/cpu-usage-log/

Those are some tools that can help.

Awesome, Sing. I was just wishing Task Manager had a CPU log feature so I could get a better idea what's happening here.