UO Second Age

I am stumped on my problem. Here is the situation. When I login, normally my char appears, then my backpacks open, then my paperdoll if I left it up. Great and fine. However, on some of my chars.. I login and I get a HUGE time delay before I can actually 'open' anything.. be it a door, a player vendor, a runebook in my bag etc. So sometimes I log in, and I'm unable to do anything for 30 seconds-2 minutes due to this delay. I can't figure out the cause of it. All my chars use the same razor profile, if that makes a difference. None of my chars have any significant difference in their default screen layout; I am unable to identify the cause of this delay on some of my chars but not others.

It appears that on some of my characters, upon login, no matter how much time I wait between initial login and actually double clicking... say a runebook.. I'll still get this delay. Since my razor profile is the same between all characters... I cannot understand why this delay exists on some chars, but not on others.

Below is a screenshot. I logged in on my char, and I was able to open the door and walk out thanks to razor auto-open door option. I then tried to double click a player vendor and received the delay message in the bottom left corner of my screen.

This problem did not always exist for me. I am confused since it exists on some chars but not others despite the same razor profile loading, and they are very much the same in terms of what backpacks are loading/spell icons in the black space etc.

I get that when I have tried to pick up to many things. It seems
razor is in the process of completing a task. Like when I make a
potion and there is no where for it to go, the char holds
it. I will have to log off and the item drops to the ground.

I would check all your macros. The ones that are an in game action, like
say [escape recall] isn't playing as you login between chars.

Hope this helps

Check your scavenger agent aswell. You may be trying to scav locked down items upon login.

Also try to shut your client down completely opposed to just logging off then on.

If the problem persists try closing all gumps before logging off. Also check that smart cpu is turned off in razor for good measure.