Razor, a sharp lag.

Discussion in 'Server & Client Support' started by Sarge, Mar 29, 2016.

  1. Sarge

    Sarge New Member

    Joined:
    Mar 21, 2016
    Messages:
    2
    Likes Received:
    0
    Hey all,

    Having an issue with Razor. Without it, the UO client runs smooth as can be, with it, its unplayable due to lag.

    I've done all i could that could be found on the web and applied the troubleshooting from here. Its all running (client + razor) on admin and service pack 3, smart cpu off. In fact, turned every option on and off to no avail and played around with resolution settings, disabled display, disabled firewalls, nothing.

    Its a longshot but kinda hoping someone might have some insight on what may be the cause of this, just Razor causing this mayhem. I'm running win10.


    Thanks in advance.
  2. wylwrk

    wylwrk Well-Known Member

    Joined:
    Jun 18, 2015
    Messages:
    5,473
    Likes Received:
    8,963
    geneal tab / something about cpu usage / uncheck

    if that's not it I would recommend looking into setting razor in compatibility mode IF applicable

    let us know
  3. Sarge

    Sarge New Member

    Joined:
    Mar 21, 2016
    Messages:
    2
    Likes Received:
    0
    That's not it, have tried all the troubleshooting from here.

    Did another reinstalll, had no lag. Logging out and picking another char, all good, but the moment i relaunch the client, lag was back.

    Could do with a razor slayer weapon right now.

    edit: update: in safe mode it runs like a gem. progress right there :) *cough*
    Last edited: Apr 10, 2016
  4. Mundungu !

    Mundungu ! Member
    UO:R Subscriber

    Joined:
    Apr 7, 2016
    Messages:
    49
    Likes Received:
    46
    I have savage lag with a lj macro...
    Gotta restart razor itself (uo client restart is not enough) every 5 mins.

    All the macro does is double click axe -> last target -> target logs in backpack when stones >= 390 stones (on if condition).
    Then I have to retarget the tree manually.

    It almost stucks up the uo client ( and it is the only macro creating this situation)...

    Any ideas ?

    Edit:
    Sorry if I posted a question and not a possible solution to the op issue.

Share This Page