 |
oldguy2
Wizard
Joined: 17 Jun 2006
Posts: 1201
|
 Posted: Wed Apr 02, 2008 6:54 am
Not again...
|
Okay I don't know what changed between 2.20 and 2.21 that caused this, but I went online and my god it's like wading through quicksand it is so slow. Last week on 2.20 I had no trouble and it was extremely fast even during a combat spar. It's nothing in my scripts. Even if I disable triggers the screen barely moves. Also when I am typing something on the command line and a script runs I can't even finish typing it won't let me continue typing until that simple script stops running. For instance, I have a trigger that when my pipe goes out to relight them. I was typing a sentence in the command line to send a tell and when that happened it wouldn't let me type anything until after it lit the pipes. If I LOOK in a room I see the room name immediately, but then it takes like 5 seconds for the description to scroll up. I sprint a direction it's like trying to jog on broken legs because of how slow the messages are coming.
It's not my connection either. I logged off and got on the game's java client and the text scrolled just fine and I could type all day and enter a command. So something changed, and I have the same crap I did while I was on 2.20.
Another odd thing I noticed is I tried to get on Zmud to see if I could connect and play on that, but it won't even connect to ANY mud now. |
|
|
|
|
Larkin
Wizard
Joined: 25 Mar 2003
Posts: 1113
Location: USA
|
Posted: Wed Apr 02, 2008 11:23 am
|
I had considerable trouble with client-side lag yesterday, but I figured it was because my packages had some bit of corruption from 2.20. I rebuilt all my packages completely anew in 2.21, and I'm hoping it helps with this issue. In the war games I played yesterday, I was falling behind in my trigger processing and having trouble typing on the command line, too. Even if not for the power outage in my building, I probably would've soon been killed, anyway.
|
|
|
|
|
oldguy2
Wizard
Joined: 17 Jun 2006
Posts: 1201
|
Posted: Wed Apr 02, 2008 8:22 pm
|
Edit: Nevermind! It was something I did. I accidentally deleted part of an atomic grouping somehow. I had to go through every trigger one by one but I found it.
Instead of:
It ended up being:
This caused havoc any time I received a line of text. Even typing show something something on the command line and holding down the enter key it took like a whole second for each line to print.  |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Apr 02, 2008 10:44 pm
|
Thanks for letting us know! You had me worried there for a bit because I haven't seen any slowdown here, and I regularly do speed tests to make sure something bad hasn't been broken.
|
|
|
|
|
Guinn
Wizard
Joined: 03 Mar 2001
Posts: 1127
Location: London
|
Posted: Wed Apr 02, 2008 11:11 pm
|
| Quote: |
| I had to go through every trigger one by one but I found it. |
If you really did go through each trigger there must be a faster way ;)
I always found disabling half the classes and trying Ctrl-Q, then disabling the other half and trying again worked well. Narrowing it down that way you can eliminate large chunks of classes at once to pinpoint slow triggers, rather than checking each one. |
|
_________________
CMUD Pro, Windows Vista x64
Core2 Q6600, 4GB RAM, GeForce 8800GT
Because you need it for text... ;) |
 |
|
|
oldguy2
Wizard
Joined: 17 Jun 2006
Posts: 1201
|
Posted: Wed Apr 02, 2008 11:12 pm
|
Yeah not sure how it happened unless when I did a search I had my cursor in that spot on the trigger and went to backspace thinking it was in the search box. Really I have no idea, but that was the problem all because "?>" was missing. Tagged out my processor I guess when I got large lines of text, which is why I couldn't type anything when I was getting text and a script ran. I'll be able to get online more tonight to make sure it solved the typing on the command line thing though. I'm sure it did.
|
|
|
|
|
oldguy2
Wizard
Joined: 17 Jun 2006
Posts: 1201
|
Posted: Wed Apr 02, 2008 11:13 pm
|
| Guinn wrote: |
| Quote: |
| I had to go through every trigger one by one but I found it. |
If you really did go through each trigger there must be a faster way ;)
I always found disabling half the classes and trying Ctrl-Q, then disabling the other half and trying again worked well. Narrowing it down that way you can eliminate large chunks of classes at once to pinpoint slow triggers, rather than checking each one. |
lol...okay every trigger in that class. Yes I disabled all the classes and then worked backwards. |
|
|
|
|
Guinn
Wizard
Joined: 03 Mar 2001
Posts: 1127
Location: London
|
Posted: Wed Apr 02, 2008 11:14 pm
|
Phew, hehe
|
|
_________________
CMUD Pro, Windows Vista x64
Core2 Q6600, 4GB RAM, GeForce 8800GT
Because you need it for text... ;) |
|
|
|
|
|
|
