OK this is now totally crazy.
I deleted the game client and razor, removed all legacy registry settings, removed my antivirus and installed a new one (of a different brand). I restarted where appropriate in between those settings.
I installed a fresh copy of the game and.... success! Normal speed again, and I spent a few minute rocking around the Orc cave on my thief.
Curious to see what my ingame ping was (-ping while in game) I ran that command - and then BANG. 1000 MS response time on average and the game crawled to a halt again.
Haha I thought - as it was only after using the ingame ping in the first place that I started experiencing any problems at all. I checked and re-added razor and the UO client to Windows firewall to give them full access... but nothing.
Once again I'm stumped as to the next steps - although it seems that my problems all started when I used that command, and that the problem is how Windows 8 is now treating the traffic once that command has been run. I should note the desktop is Windows 7 (and still runs fine). When I ping the UOF server from a standard command prompt I get a steady 200ms - it's only in game that its always closer to 1000ms.
Is anyone else using Windows 8 who is ready to risk their entire game by running -ping and letting me know the outcome?!?!
The only other thing I can think of (and I'm getting dangerously out of my depth here) is that it is some sort of DNS problem; that the ingame ping is set to go to the old servers address and somehow through me using that command is routing my traffic through a whole bunch of unnecessary steps first? Does anyone else have a marked disparity when using ingame ping vs command prompt ping?
I deleted the game client and razor, removed all legacy registry settings, removed my antivirus and installed a new one (of a different brand). I restarted where appropriate in between those settings.
I installed a fresh copy of the game and.... success! Normal speed again, and I spent a few minute rocking around the Orc cave on my thief.
Curious to see what my ingame ping was (-ping while in game) I ran that command - and then BANG. 1000 MS response time on average and the game crawled to a halt again.
Haha I thought - as it was only after using the ingame ping in the first place that I started experiencing any problems at all. I checked and re-added razor and the UO client to Windows firewall to give them full access... but nothing.
Once again I'm stumped as to the next steps - although it seems that my problems all started when I used that command, and that the problem is how Windows 8 is now treating the traffic once that command has been run. I should note the desktop is Windows 7 (and still runs fine). When I ping the UOF server from a standard command prompt I get a steady 200ms - it's only in game that its always closer to 1000ms.
Is anyone else using Windows 8 who is ready to risk their entire game by running -ping and letting me know the outcome?!?!
The only other thing I can think of (and I'm getting dangerously out of my depth here) is that it is some sort of DNS problem; that the ingame ping is set to go to the old servers address and somehow through me using that command is routing my traffic through a whole bunch of unnecessary steps first? Does anyone else have a marked disparity when using ingame ping vs command prompt ping?